EBS volumes enable you to regularly create EBS snapshots. Automating those snapshots is crucial to a healthy Disaster Recovery strategy. But getting a regular report on the health of your infrastructure can be incredibly beneficial, especially if the report can quickly inform you that you may not be meeting your DR requirements.
Today, we’ve added a new action to our arsenal of reporting actions: EBS Volume Snapshot Report. Here is an example report I ran yesterday:
Amazon RDS recently announced the ability to start and stop RDS instances. This allows you to stop and restart RDS instances overnight, on weekends, and other times where your RDS instance isn’t needed. By following this best practice, you can drastically reduce your RDS costs, in some cases, by as much as 65%.
The catch though, is that it’s only supported on single-AZ, non-replicated RDS instances. This means that your Multi-AZ RDS instance is not supported.
But there is an alternative that will allow you to reduce your RDS costs for Multi-AZ RDS instances.
DevOps and DevOps practices are growing in popularity every day, especially in the cloud-computing world. One key aspect in DevOps is automation. By automating your infrastructure and using infrastructure-as-code, you:
AWS CloudFormation is Amazon’s infrastructure-as-code solution. By using CloudFormation, you can manage your AWS resources “the DevOps way”.
Today, I wanted to show an example of managing EC2 backups using CloudFormation. We will create our EC2 backups using EBS snapshots. AWS does not have a built-in mechanism for automating EBS snapshots, so we’ll use Skeddly to perform the actual backups. CloudFormation will be used to add our new EC2 resources into our Skeddly backup schedule.
Yesterday, Amazon announced the ability to start and stop RDS instances. This is a welcome feature since it now allows you to easily save money for development environments by stopping your RDS instances when they are not needed, like overnight and on weekends.
This new feature only works for RDS instances that are not Multi-AZ and are not part of a replication group.
Skeddly has had the capability to provide similar RDS cost-savings for quite some time, however, it involved deleting and restoring your RDS instances.
Today, we’re happy to announce a new action: Start RDS Instances. It allows you to take advantage of the new RDS start/stop functionality.
Amazon Athena is a query service that allows you to query data directly from Amazon S3. We have talked about Amazon Athena before. Athena is part of Amazon’s “serverless” services. Simply dump data into S3, define a table schema, and start querying. You don’t need to allocate servers to host your data.
Today, we’re happy to announce a new action: Run Athena Query. It’s the first utilizing the Amazon Athena services.
Using IAM roles with your EC2 instances has been the recommended best practice for managing AWS credentials deployed to your instances. Previously, an EC2 instance needed to have an IAM role assigned to it at launch time. Only recently has AWS allowed IAM roles to be associated with EC2 instances after the EC2 instance has been launched.
Today, we’re happy to announce a new action in our ever-growing list of action types: Attach IAM Role to EC2 Instances.
Amazon Elastic Block Store (or EBS for short) is a service for providing block storage to your EC2 instances. In other words, it provides reliable volumes (hard drives) to your cloud servers.
One very useful function of Amazon EBS is creating EBS snapshots of your EBS volumes. EBS snapshots are backups of your EBS volumes. But how do they work, and how can you use them? Let’s take a look.
Yesterday, AWS announced that their regional benefit EC2 reserved instances can be applied against any EC2 instance in the same EC2 instance family. We’ll explain to you exactly what that means.