AWS Systems Manager announces integration of Automation with Change Calendar
Today, we are excited to announce integration of Systems Manager Automation with Systems Manager Change Calendar. Customers can now reduce the risks associated with changes to their production environment by allowing Automation runbooks to run during an allowed time window. With this feature, users in your account can only run automations during the time periods allowed by your Change Calendar. For example, you can avoid the risk of application downtime due to system update during high traffic time period, by blocking the time period in Change Calendar and enforcing Automation to check Change Calendar before updating your Amazon EC2 instance types.
Today, we are excited to announce integration of Systems Manager Automation with Systems Manager Change Calendar. Customers can now reduce the risks associated with changes to their production environment by allowing Automation runbooks to run during an allowed time window. With this feature, users in your account can only run automations during the time periods allowed by your Change Calendar. For example, you can avoid the risk of application downtime due to system update during high traffic time period, by blocking the time period in Change Calendar and enforcing Automation to check Change Calendar before updating your Amazon EC2 instance types.
You can start using the feature by enabling the Change Calendar integration in the Automation Preferences page and selecting a calendar. Once enabled, Automation runbooks will run only if Change Calendar allows changes, else the user will get an error message describing the restriction.
This feature is available in all AWS Regions including AWS GovCloud (US) Regions. For more information on this feature see our documentation. To learn about Automation and Change Calendar visit AWS Systems Manager product detail page.