Dev News Daily ENDE

AWS Secrets Manager replicates secrets across accounts under the receiving account's KMS key

AWS Secrets Manager can now keep a synchronised copy of a secret in a different AWS account. The feature, announced on 13 November, extends the existing multi-Region replication across account boundaries and is available in every Region where Secrets Manager runs.

The model AWS describes is a split of ownership. A platform or security team owns the primary secret and rotates it centrally. Each consuming account receives a local copy that Secrets Manager updates automatically whenever the primary value changes, including after a rotation. According to the announcement, this works without shared KMS keys and without cross-account secret policies, the two mechanisms teams have used so far to let one account read a secret held in another.

The replica is described as a full, independent resource. It is encrypted with a customer managed KMS key that belongs to the replica account, not to the account that owns the primary. That keeps decryption rights inside the account that uses the secret.

AWS also positions the feature for recovery. A live copy of critical secrets can sit in a dedicated recovery or failover account, which the announcement calls isolated from ransomware or from a compromised primary account. If the primary becomes unusable, the replica can be promoted to a standalone secret.

The API entry point named in the announcement is AssociateCrossAccountReplica, documented alongside a user-guide section on replicating secrets across accounts. Pricing follows the standard Secrets Manager pricing page.

AWS Secrets Manager replicates secrets across accounts under the receiving account's KMS key
AWS Secrets Manager replicates secrets across accounts under the receiving account's KMS key — Dev News Daily

Why it matters

Cross-account access to secrets has usually meant a resource policy on the secret plus a key policy on a shared KMS key, two documents that have to agree and that widen who can decrypt. A replica encrypted with the consumer's own key moves the trust decision to replication time. What the announcement does not say is how a replica behaves when the primary is deleted or how quickly an update propagates; both are worth checking in the user guide before relying on it for failover.

Written by Victoria Shinder.