Store authentication credentials for SFTP connectors in Secrets Manager
You can use Secrets Manager to store user credentials for your SFTP connectors. When you create your secret, you must provide a username. Additionally, you can provide either a password, a private key, or both. For details, see Quotas for SFTP connectors.
Note
When you store secrets in Secrets Manager, your AWS account incurs charges. For information about
pricing, see AWS Secrets Manager Pricing
To store user credentials in Secrets Manager for an SFTP connector
-
Sign in to the AWS Management Console and open the AWS Secrets Manager console at https://console.aws.amazon.com/secretsmanager/
. -
In the left navigation pane, choose Secrets.
-
On the Secrets page, choose Store a new secret.
-
On the Choose secret type page, for Secret type, choose Other type of secret.
-
Provide the key/value information for your secret: you need to provide the username, and either a private key or a password.
-
In the Key/value pairs section, choose the Key/value tab.
-
Key – Enter
Username. -
value – Enter the name of the user that is authorized to connect to the partner's server.
-
-
If you want to provide a key pair, choose Add row, and in the Key/value pairs section, choose the Key/value tab.
-
Key – Enter
PrivateKey. -
value – paste in your private key.
Tip: The private key data that you enter must correspond to the public key that is stored for this user on the remote SFTP server.
Note
It is not possible to use a passphrase-protected private key for authentication with an AWS Transfer Family SFTP connector.
For details on how to generate a public/private key pair, see Creating SSH keys on macOS, Linux, or Unix.
-
-
If you want to provide a password, choose Add row, and in the Key/value pairs section, choose the Key/value tab.
-
Key – Enter
Password. -
value – Enter the password for the user.
-
-
-
Choose Next.
-
On the Configure secret page, enter a name and description for your secret. We recommend that you use a prefix of
aws/transfer/for the name. For example, you could name your secretaws/transfer/connector-1. -
Choose Next, and then accept the defaults on the Configure rotation page. Then choose Next.
-
On the Review page, choose Store to create and store the secret.
Secret version fallback
When you rotate credentials for your SFTP connector, external partners might take time to update to the new credentials. During this transition, the connector might fail to authenticate because it only attempts the current version of the secret by default.
To support graceful rotation without downtime, you can configure an ordered
list of version stages on your connector. The connector tries each version stage
in sequence during authentication—it uses the first stage that
authenticates successfully. For example, if you configure ["AWSCURRENT",
"AWSPREVIOUS"], the connector tries the new credentials first. If
authentication fails, the connector falls back to the previous
credentials.
You configure the version stage list once on your connector—subsequent rotations require no manual intervention.
Note
When rotating secrets, you must keep the Username value the
same across all version stages. The connector does not support different
usernames for different version stages. If you need to change the username,
update UserSecretId to point to a new secret rather than
rotating the username within the same secret.
For information about configuring version stage fallback on your connector, see Managing SFTP connectors.
For more information about Secrets Manager version stages, see Version stages in the AWS Secrets Manager User Guide.