aws: Amazon Web Services

1 readers
0 users here now

A general discussion on topics for aws: Amazon Web Services

founded 1 year ago
MODERATORS
1
 
 

I'm self-learning for those two certificates with Cantrill material.

I'm curious about the length of your journey to get those certificates. How do you pace yourself to learn with your job and life?

2
3
 
 

On August 1, 2023, the free tier for the Amazon Simple Email Service (SES) will change. We are adding more features to the SES free tier: it now includes more outbound email message sources, SES’ new Virtual Deliverability Manager, and a higher limit for receiving inbound messages. We are also lowering the free tier limit for outbound messages and reducing the duration of the SES free tier to 12 months.

This may affect your bill starting in August 2023. Since you are already using SES, you will be able to take advantage of the revised free tier for another 12 months (until August 2024). Based on your SES usage in May 2023, this change would not have affected your SES bill. Note this is an estimate based on your usage, and actual billing impact may vary depending on your usage patterns each month and any discounts you may have.

The revised SES free tier offers you more flexibility. Previously, the SES free tier included up 1,000 inbound email messages per month and up to 62,000 outbound messages per month when sent from AWS compute services such as Amazon EC2. The revised free tier includes up to 3,000 messages each month. You can receive inbound messages, send outbound messages sent from anywhere (not just AWS compute services), or try Virtual Deliverability Manager, which gives you easy access to detailed metrics to explore and monitor your email delivery and engagement rates. For new SES customers, the revised free tier is available for the 12 months after you start using SES; for existing SES customers, the revised free tier is available for 12 months starting August 1, 2023.

The revised SES free tier goes live on August 1, 2023, and your account(s) will be enrolled automatically. As part of this change, you will see the label you see on your SES bill for the pricing unit for inbound messages change from “Message” to “Count” - this matches the same way we label outbound messages. We are not able to offer an option to remain on the previous SES free tier model.

To learn more about SES' deliverability tools through Virtual Deliverability Manager, please see the documentation [1]. For more details about the previous free tier, visit the pricing page [2].

If you have any questions or concerns, please reach out to AWS Support [3].

[1] https://docs.aws.amazon.com/ses/latest/dg/vdm.html [2] https://aws.amazon.com/ses/pricing/ [3] https://aws.amazon.com/support

4
 
 

Transferring Files from Local System to Remote AWS Instance using AWS SSM

Hey everyone! Today, I want to share with you a convenient and efficient way to transfer files from your local system to a remote instance in AWS. We'll be using AWS Systems Manager (SSM), a powerful service that enables remote management of your EC2 instances. Let's get started!

Step 1: Set up AWS SSM

Before we begin, make sure you have AWS CLI installed and configured on your local system. Also, ensure that the target EC2 instance is running and has the SSM Agent installed.

Step 2: Create an S3 Bucket (Optional)

If you want to transfer files using S3 as an intermediate storage location, you can create an S3 bucket in the same AWS region as your EC2 instance. This step is optional if you prefer transferring files directly from your local system to the remote instance without using S3.

Step 3: Prepare the File for Transfer

Locate the file you want to transfer on your local system and ensure it is accessible.

Step 4: Initiate the File Transfer

Open a terminal or command prompt on your local system and run the following AWS CLI command to initiate the file transfer:

aws ssm send-command --instance-ids <INSTANCE_ID> --document-name "AWS-RunShellScript" --parameters "commands=['aws s3 cp /path/to/local/file s3://your-bucket-name/file']" --output text

Replace <INSTANCE_ID> with the instance ID of your target EC2 instance. If you opted to use S3, replace /path/to/local/file with the actual path to the file on your local system and your-bucket-name/file with the S3 bucket and file location.

Step 5: Verify the File Transfer

To verify the successful transfer, you can either log in to your EC2 instance and check the destination path or use the AWS CLI command to download the file from S3 to your EC2 instance:

aws ssm send-command --instance-ids <INSTANCE_ID> --document-name "AWS-RunShellScript" --parameters "commands=['aws s3 cp s3://your-bucket-name/file /path/on/ec2/instance']" --output text

Again, replace <INSTANCE_ID> with your instance ID and adjust the S3 and destination paths accordingly.

That's it! You have successfully transferred a file from your local system to a remote instance in AWS using AWS SSM. This method eliminates the need for complex setup or manual file transfers, making it convenient and scalable for large-scale deployments.

Feel free to explore more features of AWS SSM, such as executing commands remotely, managing instances, and automating tasks. Happy file transferring!