2: Multi-Account Envs
·1 min
Table of Contents
Why deploy to multiple accounts?
- Apply appropriate security to each account
- Appropriate security for access to the env
- Appropriate security for access to database
- Isolation is good: Limit impact of errors
What sort of accounts might we want?
- Dev
- Test
- Prod
Who can use prod?
- Only: An admin, and the pipeline
How to publish to another account?
- Cross-account role is instrumental here