3 ms·
Pretty easy to dunk on this kind of thing as architectural wankery, but it can be useful for companies that need to build opinionated platforms on which busines
by jcims 4y ago
Pretty easy to dunk on this kind of thing as architectural wankery, but it can be useful for companies that need to build opinionated platforms on which business applications run.
I recently left a role at a company with ~4,000 AWS accounts and they will likely have ~20,000 within a couple of years. It's extremely helpful to see a nicely abstracted architecture that you can cherry pick from when building your platform.
- seunosewa 4y agoWhy do they need that many AWS accounts?
- nivertech 4y agoThey're probably using AWS accounts for all or some of the following: 1. Compartmentalization (security incidents and manual mistakes are isolated per account). On the extreme side even some sensitive [micro]services may run in separate AWS a/c. 2. One AWS a/c per environment (i.e. dev, staging, prod). 3. One AWS a/c per large enterprise tenant (in case of the multi-tenancy). 4. Every team/division inside the organization have their own sets of AWS accounts usually with separate billing.
- jcims 4y agoYep. Once you get the processes and pipelines built to manage account lifecycle, they provide a lot of valuable compartmentalization properties.