Docs
Reference

AWS Secrets Manager

Move secrets to and from a Secrets Manager name prefix.

Move secrets to and from a Secrets Manager name prefix.

The connection

WhatThis provider
VendorAmazon Web Services
Keyaws-secrets
Availabilityavailable. You can connect it today.
Credential penv holdsaws-iam
Values read backyes
Activationimmediate

What it moves

DirectionWhat it does
importReads names and values out of the store into penv.
exportWrites names and values from penv into the store.

When a written value goes live

immediate. The running app sees a new value at once.

What happens to a name that exists

DirectionPolicies you can pick
importskip_existing, new_version, fail
exportcreate_only, overwrite, overwrite_and_prune

How syncs work says what each one does.

How you connect

You paste a credential you already hold. penv seals it and never shows it again.

FieldLabelKindRequiredWhat it is
accessKeyIdAccess key IDtextyes
secretAccessKeySecret access keysecret, masked here and sealedyes

What the connection asks for

Fixed when you connect, and shared by every mapping on it.

FieldLabelKindRequiredAdvancedWhat it is
regionRegiontextyesnoThe region this connection reaches. One connection covers one region.
accountIdAccount IDtextnoyesIf supplied, the generated policy names the account instead of a wildcard.
basePrefixBase prefixtextyesnoThe widest secret name prefix this connection may touch. Every sync scope will sit under it.

What a mapping asks for

Answered once per environment you map.

FieldLabelKindRequiredAdvancedWhat it is
namePrefixSecret name prefixtextyesnoMaps onto this environment. One key becomes one secret beneath it.

Permissions it needs

penv probes for these when it verifies the connection.

PermissionDirectionsBlockingWithout it
sts:GetCallerIdentityevery directionyesWe cannot confirm which IAM identity this credential is.
secretsmanager:ListSecretsevery directionyesPreview cannot list what is under this prefix.
secretsmanager:GetSecretValueimportyesImport cannot read any value.
secretsmanager:CreateSecretexportyesExport cannot add a key that is not there yet.
secretsmanager:PutSecretValueexportyesExport cannot update a key that already exists.
secretsmanager:DeleteSecretexportnoThe overwrite_and_prune policy cannot remove remote keys.
secretsmanager:RestoreSecretexportnoA key pruned in the last 30 days cannot be written again.
kms:DecryptimportnoSecrets under a customer-managed KMS key will not import.
kms:GenerateDataKeyexportnoExport cannot write under a customer-managed KMS key.