- Newest
- Most votes
- Most comments
Hi,
One way to handle this is to have separate accounts for reach environment (1 per developer + 1 for integration + 1 for production + etc.) sharing a common code repo where you can use your standard branching strategy to separate the work of the different devs.
This way, each dev can deploy independently via CDK in his account without interfering with others. The code repo (CodeCommit for ex) for CDK and application has to shared across the various accounts.
Of course, to simplify the management of those N accounts, AWS Organizations should be implemented as well.
This strategy works best for pay-as-use architecture (i.e. serverless most often) because the duplicated AWS resources across accounts cost only when they get effectively used.
Best,
Didier
Relevant content
- asked 2 years ago
- asked a year ago
- Accepted Answerasked 2 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago