We are comprehensive cloud management for modern enterprises, services providers, and the public sector.
Total visibility cloud management
FedRAMP Ready cloud management
Advanced security for regulated industries
IT costs across hybrid cloud
Built to optimize the best features of the major cloud providers in a single pane of glass.
With an integrated ecosystem carefully chosen for your success.
Our technology partners amplify the advantages of the cloud.
Everything you need to manage and allocate costs, optimize spending, and save money.
Unified secure configuration, activity monitoring, and IAM tracking for the public cloud.
The next step in cloud security—ensure your cloud infrastructure is audit-ready for 35 regulatory standards.
Know what you have and ensure the right sizes of the right resources to eliminate waste.
Take the guesswork out of managing your cloud and free up resources with dynamic automation.
As most users are aware, the AWS Auto Scale default is to terminate instances by age – with the oldest being the first to go. Now, AWS has added a feature that increases user flexibility by allowing users to craft their own termination policies. We recommend that, as a best practice, users review their EC2 and Auto Scale usage to determine if the default policy of first on/first terminated is best for their needs.
See the attached announcement for more information.
We are pleased to announce that you can now configure Auto Scaling policies to determine which Amazon EC2 instances to terminate when decreasing the size of your Auto Scaling groups.
Using termination policies, you now have more control over which instances you prefer to run within your group. For example, you can specify that Auto Scaling should terminate the oldest instance, the newest instance, the instance with the oldest launch configuration, or the instance that is nearest to the next instance-hour. If you use Auto Scaling to balance your instances across multiple availability zones, Auto Scaling will also use these termination policies when an instance must be removed to maintain balance.
By default, Auto Scaling will continue to choose the instance with the oldest launch configuration when decreasing the size of your group. No action is required on your part. You can replace this default policy if you prefer. For example, you may want configure a termination policy that allows you to keep instances that have the most current version of your application, instances that have been running long enough to accumulate more data, or instances that have more time remaining before they use another full instance-hour.
For more information, please visit the termination policies section of the Auto Scaling Developer Guide at: https://docs.amazonwebservices.com/AutoScaling/latest/DeveloperGuide/us-termination-policy.html
The Amazon Web Services team