EC2 Instances with Scheduled Events
Cloud Conformity allows you to automate the auditing process of this resolution page. Register for a 14 day evaluation and check your compliance level for free!
Start a Free Trial Product featuresCloud Conformity allows you to automate the auditing process of this resolution page. Register for a 14 day evaluation and check your compliance level for free!
Start a Free Trial Product featuresDetermine if there are any EC2 instances scheduled for retirement and/or maintenance in your AWS account and take the necessary steps (reboot, restart or re-launch) to resolve them. The EC2 instances support multiple types of scheduled events such as Reboot (instance-reboot or system-reboot) - the instance or the underlying host machine is rebooted, Instance Stop (instance-stop) – the instance is stopped and started to migrate it to a new host machine, Instance Retirement (instance-retirement) - the instance is terminated and System Maintenance (system-maintenance) - the instance is taken offline for a short period of time, then rebooted.
Monitoring EC2 scheduled events within your AWS account will help you prevent unexpected downtime and data loss, improving the reliability and availability of your AWS EC2 fleet. Note: This guide assumes that your EC2 instances are associated with Elastic IPs. If your instances do not have Elastic IPs attached, you will have to update their public IP reference(s) in your application code or within the DNS zone file after you stop and start the necessary instances, as each restarted instance gets a new public IP address.
To determine if Connection Draining is enabled, perform the following:
To resolve EC2 instances scheduled for retirement/maintenance based on the event type (see Audit section to identify the event type(s) assigned to your instance(s)), perform the following:
Actions for instance-reboot event:
No action is required on your end. The system reboot is managed by AWS and occurs during its scheduled maintenance window. AWS will send you an email prior to the system-reboot event with all the necessary details, including the start and the end date of the event.