Based on latest AWS recommendations and best practices lots of custom products are divided into separate aws accounts. For example development environment in one account, stage in other and production in the third. Even production workloads cloud be divided into separate accounts like web tier, app tier and databases tier in order to have best possible isolation between application tiers. Would be very useful under same project have multiple aws secrets manager integrations for every staging environment.
Why would it be useful?
Under same project bind different aws account secret manager/parameter store to particular staging environments. For example:
Project(My fancy app):
Staging evironments:
dev - aws secret manager integration aws account 1
Even if secret individually could have separate aws secret manager integration to aws account would be even better. For example aws secret manager integration could be attached into staging environment as a whole or to particular secret only.
Feature description
Based on latest AWS recommendations and best practices lots of custom products are divided into separate aws accounts. For example development environment in one account, stage in other and production in the third. Even production workloads cloud be divided into separate accounts like web tier, app tier and databases tier in order to have best possible isolation between application tiers. Would be very useful under same project have multiple aws secrets manager integrations for every staging environment.
Why would it be useful?
Under same project bind different aws account secret manager/parameter store to particular staging environments. For example:
Even if secret individually could have separate aws secret manager integration to aws account would be even better. For example aws secret manager integration could be attached into staging environment as a whole or to particular secret only.
Additional context