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 - 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.
How to get the data/report of ssm installed in aws instancesAccepted Answerasked 7 months ago
Is it redundant to have an EC2 instance and its EBS volumes in the same AWS Backup resource assignment?Accepted Answerasked 9 months ago
Is there a way to cancel the creation of a snapshot?asked 3 years ago
AWS Trigger Automation from CloudWatch scheduled eventasked 3 years ago
It there a way to add Exponential Backoff to AWS:ExecuteAutomation in an SSM Automation Document?asked 5 months ago
SSM Automation - Download file from S3 - Assume Roleasked 6 months ago
SSM Document Timeout in CDKasked 2 months ago
Running an automation document starting from a specific step?Accepted Answerasked 8 months ago
SSM Automation Run Command longer than default 3600 secondsasked 5 years ago
How much does it cost to connect to private ec2 using aws ssm ?Accepted Answerasked 5 months ago