JetherVerse News
Security· 1 min read

AWS Secrets Manager now replicates secrets across accounts

AWS Secrets Manager can now keep a synchronized copy of a secret in a second AWS account, for access, backup and disaster recovery. The replica updates automatically, including on rotation, and needs no shared KMS keys.

By JetherVerse News

AWS Secrets Manager now supports cross-account replication. It keeps a synchronized copy of a primary secret in a second AWS account, for access across accounts, for backup and for disaster recovery. It extends the existing multi-Region replication across account boundaries. Access, backup and disaster recovery are three separate needs, so decide which one you are solving before you set it up.

With this feature, a platform or security team owns and rotates a secret in one place, and each consuming account gets a local, current copy. AWS says this works without shared KMS keys or cross-account secret policies. The replica is a full, independent resource, encrypted with a customer managed KMS key owned by the replica account. Secrets Manager updates the replica whenever the primary value changes, including during rotation. You also keep a live copy of critical secrets in a dedicated recovery or failover account, isolated from ransomware or from a compromised primary account. If the primary is lost, you promote the replica to a standalone secret. Cross-account replication is offered in every AWS Region where Secrets Manager runs. AWS documents the AssociateCrossAccountReplica API for setting it up, and pricing details sit on the Secrets Manager pricing page.

Teams with many accounts often copy secrets by hand or write scripts to share them, and both approaches drift out of date or widen access more than intended. A managed replica removes the copying step and keeps ownership clear. Rotation done at the source reaches every copy without extra scripts. It also gives a clean answer to a common audit question, which is where a recoverable copy of each critical credential lives.

For Nigerian fintechs and agencies running multi-account AWS setups under customer data rules, central rotation with isolated replicas fits a sound security routine.

If your recovery plan for credentials is a spreadsheet or a shared password manager, this is a better design to evaluate.

Source: Amazon Web Services

Get the news in your inbox

The tech stories that matter from JetherVerse News, with the source on every one.

Free. Unsubscribe any time.