AWS Secrets Manager Cross-Account Replication: Setup, Pricing and Limits
AWS Secrets Manager now replicates secrets to another account. Step-by-step CLI setup, KMS and IAM permissions, limits, pricing and how it compares.

AWS Secrets Manager can now replicate a secret from one AWS account into another, natively. Announced on 13 November 2026, cross-account replication keeps a read-only copy of a secret in a second account and pushes every change, including rotations, to it automatically. It works in every Region where Secrets Manager is available, but both secrets must sit in the same Region, the replica needs a customer managed KMS key, and each replica is billed as its own secret.
Below: what the feature does, how it differs from multi-Region replication and resource-policy sharing, the exact setup steps and permissions from AWS's documentation, the limits that will trip you up, and what it costs.
What is Secrets Manager cross-account replication?
Until now, Secrets Manager could replicate a secret to other Regions in the same account, and you could let another account read your secret through a resource policy and a shared KMS key. What you couldn't do natively was keep a separate, local copy in a different account.
The new feature fills that gap. According to the AWS announcement, the replica is "a full, independent secret" encrypted with a KMS key owned by the replica account, so no shared KMS keys or cross-account secret policies are needed for consumers to read it. When the primary secret changes, including through rotation, Secrets Manager pushes the new value to the replica.
AWS pitches three uses:
- Central rotation, local consumption: a platform or security team owns and rotates the secret; application accounts read a local copy.
- Backup and disaster recovery: keep a live copy in an isolated recovery account, away from a compromised primary account.
- Promotion: if needed, the replica account can cut the link and turn the replica into a normal, standalone secret.
Cross-account replication vs. multi-Region replication vs. resource policies
This is the comparison most teams will need before choosing an approach.
| Cross-account replication (new) | Multi-Region replication | Resource policy sharing | |
|---|---|---|---|
| Copy lives in | Another account, same Region | Same account, other Regions | No copy; consumers read the original |
| KMS key | Customer managed key in the replica account (required) | AWS managed or customer managed key per Region | Customer managed key shared with the other account |
| Replicas per secret | One cross-account replica | Multiple Regions | N/A |
| Tags and resource policy | Not replicated; each account manages its own | Replicated | N/A |
| Rotation | Rotate the primary; changes sync to replica | Rotate the primary; changes sync to replicas | One secret, rotated once |
| Survives loss of primary account | Yes, can be promoted to standalone | No | No |
| Billing | Replica billed as a distinct secret | Each replica billed as a distinct secret | One secret |
Rule of thumb: use multi-Region for latency and regional resilience, resource policies when a handful of consumers just need read access, and cross-account replication when you need a copy that keeps working even if the primary account is unavailable or compromised.
How does it work?
Per the Secrets Manager user guide, it's a two-party handshake:
- The replica-account owner creates an empty replica secret that points at the primary secret's ARN, encrypted with its own customer managed KMS key.
- The primary-account owner associates that replica with the primary secret, which starts replication.
Replication is asynchronous and eventually consistent, so a replica can briefly lag the primary. Each secret reports a status: Pending, InProgress, InSync, Failed or Detached.
What gets copied: the secret value and version data, the description, the secret type, and version/staging label mappings (such as AWSCURRENT and AWSPREVIOUS). What doesn't: tags, resource policy and KMS key, which each account manages separately.
How to set up cross-account replication (step by step)
The commands below are taken from AWS's documentation; account IDs are AWS's placeholders (111122223333 = primary, 444455556666 = replica). Swap in your own ARNs.
Step 1: In the replica account, create a symmetric customer managed KMS key in the same Region as the primary secret. The AWS managed key aws/secretsmanager won't work for cross-account access.
Step 2: In the replica account, create the replica secret pointing at the primary (create guide):
aws secretsmanager create-secret \
--name MyReplicaSecret \
--cross-account-primary-arn arn:aws:secretsmanager:us-east-2:111122223333:secret:MyPrimarySecret-a1b2c3 \
--kms-key-id arn:aws:kms:us-east-2:444455556666:key/{{replica-key-id}}
Secrets Manager attaches a read-only, system-managed resource policy named cross-account-replication to the replica. Because of that, the caller needs secretsmanager:PutResourcePolicy on the new secret as well as permissions to use the KMS key.
Step 3: Update the replica KMS key policy so the primary account can call kms:Encrypt, ideally scoped to the replica secret's ARN through the encryption context. AWS's example statement:
{
"Sid": "AllowCrossAccountReplication",
"Effect": "Allow",
"Principal": "*",
"Action": "kms:Encrypt",
"Resource": "*",
"Condition": {
"StringEquals": {
"kms:CallerAccount": "111122223333",
"kms:EncryptionContext:SecretARN": "arn:aws:secretsmanager:us-east-2:444455556666:secret:{{MyReplicaSecret}}-a1b2c3"
}
}
}
Step 4: In the primary account, associate the replica (associate guide):
aws secretsmanager associate-cross-account-replica \
--secret-id MyPrimarySecret \
--cross-account-replica-arn arn:aws:secretsmanager:us-east-2:444455556666:secret:MyReplicaSecret-a1b2c3 \
--replication-role-arn arn:aws:iam::111122223333:role/SecretsManagerCrossAccountReplicationRole
By default the replica restriction is SameOrg, meaning both accounts must be in the same AWS Organization. To replicate outside your organization, add --replica-restriction NoRestriction. AWS notes the restriction is only checked at first association.
Step 5: Check the status until it reads InSync:
aws secretsmanager describe-secret \
--secret-id MyPrimarySecret
The response includes a CrossAccountReplicas list with each replica's ARN, replication role and ReplicationStatus.
Which IAM permissions do you need?
The identity that runs the association needs:
secretsmanager:AssociateCrossAccountReplicaandsecretsmanager:GetSecretValueon the primary secretsecretsmanager:AcceptCrossAccountReplicationon the replica secretkms:Decrypton the primary secret's KMS keykms:Encrypton the replica secret's KMS key (cross-account)iam:PassRoleif you pass a replication role
Every replication decrypts with the primary key and re-encrypts with the replica key. AWS gives you two ways to authorize that:
- Replication role (recommended): Secrets Manager assumes an IAM role that trusts
secretsmanager.amazonaws.comand holds both KMS permissions. Individual writers don't need cross-account KMS access. This requires the primary secret to use a customer managed key too. - Forward access sessions: with no role, Secrets Manager uses the identity that changed the secret (for example the
PutSecretValuecaller). That identity then needs cross-accountkms:Encrypt; if it lacks it, replication fails.
AWS also warns that an organization-level SCP or RCP can block these KMS calls even when identity and key policies allow them, a common cause of a Failed status.
What are the limits and gotchas?
- Same Region only. A primary in
us-east-2can only replicate to a replica inus-east-2in another account. You also can't fan the replica out to more Regions, becauseReplicateSecretToRegionsis blocked on a replica. - One cross-account replica per primary. A second association fails.
- Customer managed KMS key required for the replica (and for the primary if you use a replication role).
- Replicas are read-only.
PutSecretValue,UpdateSecret,DeleteSecret,RotateSecret,CancelRotateSecret,UpdateSecretVersionStage,ReplicateSecretToRegionsandRemoveRegionsFromReplicationreturnInvalidRequestException.GetSecretValue,DescribeSecret, resource-policy and tag operations still work. - Empty until first sync.
GetSecretValueon a new replica returnsResourceNotFoundExceptionuntil the first value arrives. - Deletion order matters. Neither side can delete its secret until it has stopped replication from its own side.
- No published latency figure. AWS describes replication only as eventually consistent; plan for a short lag after rotation.
How do you stop replication or promote a replica?
Either side can stop at any time (stop guide). From the primary account:
aws secretsmanager disassociate-cross-account-replica \
--secret-id MyPrimarySecret \
--cross-account-replica-arn arn:aws:secretsmanager:us-east-2:444455556666:secret:MyReplicaSecret-a1b2c3
From the replica account, which turns the replica into a standalone secret (the caller also needs secretsmanager:DeleteResourcePolicy, because this removes the system-managed policy):
aws secretsmanager stop-replication-to-replica \
--secret-id MyReplicaSecret
That second command is your break-glass step for disaster recovery: once it runs, the secret in the recovery account is independent and writable.
How much does cross-account replication cost?
AWS's pricing page says "a replica secret is considered a distinct secret" and is billed per replica per month at the same rate as a secret. Its worked examples use US$0.40 per secret per month and US$0.05 per 10,000 API calls, prorated by the hour for secrets stored less than a month. So one primary plus one cross-account replica costs roughly US$0.80 a month before API calls, plus AWS KMS charges for the customer managed keys involved (see KMS pricing). These are our calculations from AWS's listed rates; your bill may differ by Region.
New AWS customers can offset small costs with Free Tier credits; our AWS Free Tier 2026 explainer covers how those work.
What are developers saying?
We searched Reddit, Hacker News and AWS community forums and found no substantial public discussion of the launch yet, so we have no community quotes to share. Google's autocomplete shows what people are trying to do: "aws secrets manager replicate to another account", "secrets manager cross account access" and "aws secrets manager replication terraform". On that last one, we haven't confirmed Terraform or CloudFormation support for the new APIs; check your provider's changelog before automating.
Editor's take
This is a small launch that removes a real chore. Before this, a cross-account copy usually meant custom automation (such as a Lambda function triggered on rotation) or sharing a KMS key, and that glue is easy to break without noticing. A native, status-reporting replica with its own key is cleaner, and the ability to promote it makes it a credible part of a recovery-account strategy. The trade-offs are real, though: one replica per secret, same Region only, and mandatory customer managed keys. For broad fan-out to dozens of accounts, resource policies will still be simpler; for "keep a copy we control in our vault account," this is now the obvious choice.
FAQ
Can AWS Secrets Manager replicate to another account?
Yes. Since 13 November 2026, Secrets Manager supports native cross-account replication via the CreateSecret (with CrossAccountPrimaryARN) and AssociateCrossAccountReplica APIs.
Can Secrets Manager replicate to another account in a different Region?
Not directly. The primary and replica must be in the same Region, and a cross-account replica can't itself be replicated to other Regions.
Can I use the aws/secretsmanager key for a cross-account replica?
No. The replica must use a customer managed KMS key; the AWS managed key doesn't support cross-account access.
Does rotation work with cross-account replicas?
Yes. You rotate the primary; the new value replicates to the replica automatically. Rotation can't be configured on the replica itself.
Do both accounts need to be in the same AWS Organization?
By default, yes (SameOrg). You can set --replica-restriction NoRestriction at association time to replicate outside your organization.
How much does a cross-account replica cost?
AWS bills each replica as a distinct secret. Using the US$0.40 per secret per month rate from AWS's pricing examples, a primary plus replica is about US$0.80/month before API calls and KMS costs.
How do I delete a cross-account replica?
Run stop-replication-to-replica in the replica account first, then DeleteSecret. Calling DeleteSecret on an active replica fails.
Is cross-account replication available in my Region?
AWS says it's available in all Regions where Secrets Manager is offered. For brand-new Regions, such as the AWS Chile Region that is still in early access, check the AWS Region table to confirm Secrets Manager is listed.
New to AWS? Start with our explainer on what AWS is and how it works. Also today on 9to5Amazon: Amazon's first North American union contract, explained.
Sources
- AWS What's New: AWS Secrets Manager now supports cross-account replication (13 November 2026)
- AWS docs: Replicate AWS Secrets Manager secrets across accounts
- AWS docs: Create a replica secret
- AWS docs: Associate the replica with a primary secret
- AWS docs: How Secrets Manager authorizes cross-account replication
- AWS docs: Stop cross-account replication
- AWS docs: Replicate secrets across Regions
- AWS: Secrets Manager pricing
Featured image: Part of AWS's us-west-2 Region in Oregon, showing data centre buildings (a general AWS infrastructure photo, not specific to Secrets Manager), by Tedder, CC BY-SA 4.0, via Wikimedia Commons. Source