While Amazon Web Services typically offers a pay-as-you-go approach for its products, the company’s Relational Database Service (RDS) has been an outlier. Unlike Elastic Compute Cloud (EC2) instances, which can be paused and relaunched as needed, the ability to directly stop and start RDS instances has never been available… until now.
Amazon’s Elastic Compute Cloud (EC2) provides its users with a flexible, highly customizable computing solution without the need to invest in costly on-site servers. And the product’s ability to quickly scale computing capacity up or down means that, if properly utilized, AWS customers only pay for what they actually need. Not only can EC2 users easily start and stop instances on demand, but they can also use EC2 scheduling to set the start and stop times of specific instances in advance, saving time and money in the process. By some estimates, utilizing EC2 scheduling to halt non-essential instances during off hours can lower costs by as much as 70 percent.
Let’s be honest, we are all busy people and where possible, we want to automate tasks. We want to be able to set something up and then forget about it, safe in the knowledge that it’s being taken care of in the background.
Although AWS allow you to take snapshots of your EBS volumes, it still requires some manual effort and is subject to human error. In this blog post, we will look in more detail at the benefits of AWS snapshot and backup automation.
Last week, Amazon Web Services (AWS) released its largest ever virtual server for its Elastic Compute Cloud (EC2). The 2TB X1 instance was originally announced by AWS CTO, Werner Vogels last year at the 2015 AWS RE:Invent conference, and aims to make AWS more usable for enterprise applications and massively large data sets.