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

spread the load for the api calls #1

Open
kisst opened this issue May 31, 2019 · 2 comments
Open

spread the load for the api calls #1

kisst opened this issue May 31, 2019 · 2 comments

Comments

@kisst
Copy link
Owner

kisst commented May 31, 2019

in case there are a lot of stacks, aws can limit the api-calls, which can cause, the detect not to run, with an SQS, and queue processing, this can be fixed, which also should provide an option for retry, as right now it's fire and forget only

@AndreyZaslavskiyWMG
Copy link

Did you experienced that kind of problems? And how much stacks if limit for current solution like "fire-and-forget" ?

@kisst
Copy link
Owner Author

kisst commented Oct 23, 2020

Yes I had cases where I got throttled, but at the same time that was for accounts where I had to already request CFN limit increase as there was more then 200 Stacks in each region in use. In general for most use-case this already works, but in a local draft branch I have most of the pieces for the fancy DynamoDB / Queue based solution, just haven't had time to complete it, but happy to push it to GH if want to pick it up.

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