Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RequestLimitExceeded error when resources are a lot #21

Closed
tonerdo opened this issue Mar 19, 2018 · 2 comments
Closed

RequestLimitExceeded error when resources are a lot #21

tonerdo opened this issue Mar 19, 2018 · 2 comments

Comments

@tonerdo
Copy link
Contributor

tonerdo commented Mar 19, 2018

No description provided.

@josh-padnick
Copy link
Contributor

I've hit this as well. It'd be nice to have an exponential backoff retry approach here.

@josh-padnick
Copy link
Contributor

Also, it may be worth prioritizing the EC2 Instances and Auto Scaling Groups first. Those are the most expensive, and this way, even if you've got a ton of AMIs -- as many AWS accounts do -- you can at least knock those out.

For example, in my use case, my goal was to clear out all the ASGs. But I kept hitting the AMI limit, which meant the tool isn't really usable for my use case. If I can knock out the ASGs but then it takes a long time on the AMIs, then I've at least achieved my objective.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants