Considerations - Ops Automator

Considerations

Solution Updates

Ops Automator v2.x has been redesigned to improve throughput, simplify the configuration, and add event-triggered tasks. To take advantage of the new features and functionality, you must deploy the latest version of the Ops Automator as a new stack. You cannot update a previously deployed version of the solution stack.

If you are using a v1.x stack, you cannot update to v2.x. To use the latest version of the solution, delete the v1.x stack and follow the Automated Deployment steps to launch v2.x.

If you are using a v2.x stack, you can update to the current version, however we recommend deploying in a test environment first to confirm a successful deployment.

Encrypted Amazon EBS Volumes

If your Amazon EC2 instances contain encrypted Amazon Elastic Block Store (Amazon EBS) volumes, you must grant Ops Automator permission to use the customer’s primary key (CMK) to perform actions. Add the kms:CreateGrant permission to the Ops Automator role (<stackname>-OpsAutomatorLambdaRole -<id>).

Regional Deployments

Some Ops Automator features are not available in the AWS GovCloud (US) Regions. Additionally, the solution uses Amazon Resource Names (ARNs) to perform tasks in secondary accounts. In the AWS GovCloud (US) Regions, ARNs have an identifier that is different from the one in other AWS Regions. Because not all solution features are supported in the Region and the difference in ARNs, Ops Automator is not available in the AWS GovCloud (US) Regions at this time.