AWS Ops Automator
AWS Ops Automator

Appendix G: Troubleshooting Capacity Issues

When the automated process is triggered, an instance of the solution’s main AWS Lambda function must select all applicable resources within a five-minute period. If the solution fails to process a task for a large number of resources, such as copying or deleting a large amount of Amazon Elastic Block Store (Amazon EBS) snapshots, it is often because the Lambda function does not have enough memory to select those resources within the timeout period. The primary solution template includes a Lambda size (MB) parameter, which allows you to increase the memory of the main AWS Ops Automator Lambda function.

You can review the logs for your Lambda function in Amazon CloudWatch to see if insufficient memory is causing execution issues. In the AWS Lambda console, choose the function named <stackname>-SchedulerDefault. In the Monitoring tab under Invocation duration, choose Jump to Logs to view the function’s log files directly in the Amazon CloudWatch console. If there are entries that show execution times close to five minutes, or executions that were timed out by the five-minute limit, then you need to increase the memory size of the Lambda function. Use the Lambda size (MB) parameter in the primary solution template to adjust this value.