Links a primary secret in your account to a replica secret in a different Amazon Web Services account and starts replication to this replica. The replica secret must already exist in the other Amazon Web Services account. Create the replica with
CreateSecret and set its
CrossAccountPrimaryARN field set to this primary secret's ARN. When you call AssociateCrossAccountReplica, Secrets Manager calls AcceptCrossAccountReplication on the replica secret on your behalf.
The primary and replica secrets must be in the same Amazon Web Services Region and partition, and you must call this operation from the account that owns the primary secret. A primary secret can have at most one cross-account replica. This operation is idempotent, so you can call it again for the same replica to repair replication. If the association fails, Secrets Manager does not modify either the primary or replica secret.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see
Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:AssociateCrossAccountReplica,
secretsmanager:GetSecretValue on the primary secret, and
secretsmanager:AcceptCrossAccountReplication on the replica secret. You must also have
kms:Decrypt permission for the Key Management Service (KMS) key that encrypts the primary secret, and
kms:Encrypt permission for the Amazon Web Services KMS key that encrypts the replica secret. If you supply
ReplicationRoleARN, you also need
iam:PassRole for that role. For more information, see
IAM policy actions for Secrets Manager and
Authentication and access control in Secrets Manager.