Last year, Amazon announced that longer EC2 resource IDs were coming. Today, they are available and you can opt-in. In December 2016, they will be turned on for anyone who has not opted-in yet. More information can be seen in their official announcement:
We’re excited to announce a new addition to our library of DevOps actions: Delete EBS Volumes. This brings our total to over 65 actions.
Using the new Delete EBS Volumes action, you can delete unattached EBS volumes on a regular schedule, manually, or in reaction to an SNS message, such as an AWS CloudWatch alert or an AWS Config rule violation. The action can delete all unattached volumes, those that match a particular tag value, or those that have been unattached for a minimum time period. In addition, to ensure you don’t lose your data, the action can create a final EBS snapshot of your volume before it’s deleted.
Amazon announced the ability to copy AMI images between AWS accounts. More information about the announcement can be seen here:
Creating Amazon EBS snapshots allows you to copy those snapshots to another region and/or AWS account. Copying your EBS snapshots can be a valuable tool:
Amazon announced the ability to share and copy RDS snapshots between AWS accounts. More information about the announcement can be seen here:
Today, Amazon has announced support for M4 instance classes in Amazon RDS managed database service. The announcement can be seen here:
EC2 Run Command (based on Amazon SSM) is a new feature added to EC2 which allows your DevOps and system administrators to send various commands to your EC2 instances without requiring them to login to the instances (eg. using RDP or SSH). Currently, EC2 Run Command is supported only by Windows instances, but Amazon says that Linux support is coming.
More information about EC2 Run Command and it’s announcement can be found on the AWS blog: https://aws.amazon.com/blogs/aws/new-ec2-run-command-remote-instance-management-at-scale/.
For example, using EC2 Run Command, you can issue Powershell commands to your EC2 instances as part of a maintenance schedule.
Object versioning is a powerful feature of Amazon S3. When you enable object versioning on your S3 bucket, S3 will automatically preserve previous versions of your objects. This allows you to retrieve previous versions in cases of incorrect overwrites or accidental deletion.
However, by preserving previous versions of your objects, you will be charged for the storage occupied by those older versions. For example, if you have an object of 100 megabytes and you overwrite it with an object of 50 megabytes, you will be charged for 150 megabytes.
Using AWS Storage Gateway, you can connect your on-premises storage solutions with Amazon’s cloud-based storage solutions for backup, DR, and caching purposes.
AWS Storage Gateway allows you to create snapshots of your gateway volumes for backup purposes. But until today, creating these snapshots was a manual process using the AWS Management Console.
Amazon DynamoDB is a managed NoSQL database service from Amazon Web Services. Using DynamoDB, you can store data without requiring a fixed schema. Amazon DynamoDB is priced based on your desired read and write capacity. Meaning, you’ll pay more for more available reads and writes per second, and pay less for fewer available reads and writes per second.
For some databases with predictable performance requirements, scheduling the through-put of your DynamoDB tables may be an effective cost-reduction strategy. For example, if your database is predominantly used during business-hours, and rarely used after-hours or on weekends, then reducing your table’s read and/or write through-put can help reduce your AWS costs. Until today, adjusting your table’s read or write capacity needed to be done manually or by using and managing your own scripts.