Scheduled Reserved Instances are a new feature of AWS where you can make a reserved instance purchased based on a recurring schedule rather than 24 hours a day for an entire year. An example where this may be useful could be an application that processes data for 4 hours each Saturday. Using Scheduled Reserved Instances, you can reserve an EC2 instance to run for 4 hours each Saturday. Because you’ve reserved it, it’s
The announcement from AWS about Scheduled Reserved Instances can be found here: https://aws.amazon.com/blogs/aws/new-scheduled-reserved-instances/.
Chaos Monkey is a tool built by Netflix that randomly terminates instances within your infrastructure. The reason for doing this is to help ensure that your applications continue to run in times of instance failures.
By introducing “automated failure” into your infrastructure, you are forcing your DevOps, IT, and developers to plan for failure. This is one of the key mantras of cloud computing. By forcing an instance failure at known and/or friendly times, your team can react if your application does not behave positively.
Recently, we announced a new action called “Terminate EC2 Instances”. Using this new action, you can easily implement your own version of Chaos Monkey. Today, we’ll walk you through this process.
We have created a new-and-improved version of our “Terminate EC2 Instance” action called “Terminate EC2 Instances”. This new action allows you to terminate multiple EC2 instances based on various matching criteria:
We have created a new-and-improved version of our “Reboot EC2 Instance” action called “Reboot EC2 Instances”. This new action allows you to reboot multiple EC2 instances based on various matching criteria:
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: