Re:Secure Access to 100 AWS Accounts
by throwbacktictac on Sunday March 11, 2018 @01:21PM
(#16563817)
Their reason for multiple accounts seems to be due to API rate limiting imposed by aws? At least thats my understanding.
[ Parent
| on HN ]
Route53 API rate limits are per account and very low.
It sucks not being able to fix the production A record because somebody did a lot of changes on the staging zone.
Re:Secure Access to 100 AWS Accounts
by erik_seaberg on Sunday March 11, 2018 @06:42PM
(#16565128)
I was also alarmed to see that dynamodb:DescribeStream is limited to 10 QPS per account, making low-latency stream consumers into noisy neighbors of each other. Then there's all the "open a support ticket" per-account limits on table provisioning and running EC2 instances…