- Newest
- Most votes
- Most comments
Hello, thank you for your post. Regarding implementing incremental backoff purely in SSM automation, this cannot be directly enabled. The closest option is setting an error threshold on the Run Command page in the SSM console. Reviewing the information you provided, I suspect your document named MyCustomCreateSnapshotRunbook makes use of the CreateSnapshot API or CreateSnapshots. I suspect this is the API for which you are hitting a rate limit. I do recommend you use the CreateSnapshots API, as it takes an instance ID as input and creates snapshots for all volumes attached to the instance[1] - this would make it less likely to reach a rate limit which could occur if the CreateSnapshot API were repeatedly called for individual volume IDs.
As the issue you are facing involves details that are specific to your use case and the resources in your account, I encourage you to open a support case so that our support team can review the API calls that were made and the specific errors that were encountered. This will allow us to provide your better guidance to resolve the issue.
References:
[1] https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateSnapshots.html
Relevant content
- asked a year ago
- Accepted Answerasked 10 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago