We are delighted to announce that you can now configure your AWS EC2 Auto Scaling Groups to operate on your chosen schedule using the CloudRanger platform. Previously, this functionality was only available through the AWS Application Programming Interface (API), Command Line Interface (CLI), and AWS CloudFormation.
AWS EC2 Auto Scaling based on a schedule allows you to scale your application in response to predictable load changes. For example, if the traffic to your web application consistently increases on Wednesday, remains high on Thursday, and starts to decrease on Friday, you can use scheduled Auto Scaling to automatically increase capacity to match the predictable traffic patterns of your web application.
AWS EC2 Auto Scaling allows you to automatically scale your EC2 resources based on demand within certain parameters. CloudRanger Auto Scaling schedules allow you to adjust these parameters, in a fully automated way. The minimum, maximum and desired values of an Auto Scaling Group (ASG) are the boundaries to which your scaling is confined. We allow you to dynamically adjust these limits and in case of emergency, to perform a one-off adjustment to your ASG.
We are delighted to release the CloudRanger Public REST API that customers and partners can use to integrate the CloudRanger platform with third-party applications and systems. Customers and managed service providers (MSPs) can use the CloudRanger API to manage customized backup policies and schedule server resources on AWS cloud.
Access to the CloudRanger Public REST API is controlled by your API key generated in the CloudRanger dashboard and token. This will allow you to manage your Amazon EBS, EC2, RDS and Redshift resources and backup policies across multiple AWS regions and accounts with ease.
In previous blogs, we have explained why properly tagging AWS resources is necessary, and we have explored some of best practices and recommended strategies for applying tags for your AWS cloud environment. Amazon Web Services have now taken this further and provided some great new support features for tagging Amazon EBS Snapshots so you can exercise more control them. You can now tag your Amazon Elastic Block Store (Amazon EBS) Snapshots at the time of creation. You can do this from the Amazon EC2 console or through the CreateSnapshot API. By tagging resources at the time of creation, you can eliminate the need to run custom tagging scripts after resource creation.
Ensuring business continuity in the face of a man-made or natural disaster may seem like a daunting task. Luckily, today’s cloud-based computing platforms such as Amazon Web Services are particularly well suited to meet the disaster recovery planning needs of most businesses. However, the versatile, decentralized nature of the cloud is wasted in the absence of a proper, well tested DR plan and the ability to adapt to changing often unforeseen circumstances. So in the following article, we’ll take a look at some best practices for utilizing AWS cloud to develop your own DR plan in order to help maintain business continuity during a disaster situation.