Managing SSH and PGP keys in Transfer Family
In this section, you can find information about SSH keys, including how to generate them
and how to rotate them. For details about using Transfer Family with Amazon Lambda to manage keys, see the
blog post Enabling user self-service key management with AAmazon Transfer Family and Amazon Lambda
Note
Amazon Transfer Family accepts RSA, ECDSA, and ED25519 keys for SSH authentication.
This section also covers how to generate and manage Pretty Good Privacy (PGP) keys.
For a comprehensive overview of all supported encryption and key algorithms, including recommendations for different use cases, see Encryption and Key Algorithms Overview.
Encryption and Key Algorithms Overview
Amazon Transfer Family supports different types of algorithms for different purposes. Understanding which algorithms to use for your specific use case helps ensure secure and compatible file transfers.
Use Case | Recommended Algorithm | FIPS Compliant | Notes |
---|---|---|---|
SSH/SFTP Authentication | RSA (rsa-sha2-256/512), ECDSA, or ED25519 | RSA: Yes, ECDSA: Yes, ED25519: No | Compatible with all SSH clients and servers |
PGP Key Generation | RSA or ECC (NIST) | Yes | For workflow decryption |
PGP File Encryption | AES-256 | Yes | Determined by PGP software |
SSH Authentication Algorithms
These algorithms are used for SSH/SFTP authentication between clients and Amazon Transfer Family servers. Choose one of these when generating SSH key pairs for user authentication or server host keys.
- RSA (Recommended)
-
Compatible with all SSH clients and servers, and FIPS-compliant. Use with SHA-2 hashing for enhanced security:
-
rsa-sha2-256
- Recommended for most use cases -
rsa-sha2-512
- Higher security option
-
- ED25519
-
Modern and efficient. Smaller key sizes with strong security:
-
ssh-ed25519
- Fast and secure, but not FIPS-compliant
-
- ECDSA
-
Elliptic curve option. Good balance of security and performance:
-
ecdsa-sha2-nistp256
- Standard curve -
ecdsa-sha2-nistp384
- Higher security curve -
ecdsa-sha2-nistp521
- Highest security curve
-
Note
We support ssh-rsa
with SHA1 for older security policies. For
details, see Cryptographic algorithms.
Choosing the right SSH algorithm
-
For most users: Use RSA with
rsa-sha2-256
orrsa-sha2-512
-
For FIPS compliance: Use RSA or ECDSA algorithms
-
For modern environments: ED25519 offers excellent security and performance
PGP Encryption and Decryption Algorithms
PGP (Pretty Good Privacy) uses two types of algorithms working together to encrypt and decrypt files in workflows:
-
Key pair algorithms - Used to generate the public/private key pairs for encryption and digital signatures
-
Symmetric algorithms - Used to encrypt the actual file data (the key pair algorithms encrypt the symmetric key)
PGP Key Pair Algorithms
Choose one of these algorithms when generating PGP key pairs for workflow decryption:
- RSA (Recommended)
-
Recommended for most users. Widely supported, well-established, and FIPS-compliant. Provides good balance of security and compatibility.
- ECC (Elliptic Curve Cryptography)
-
More efficient than RSA with smaller key sizes while maintaining strong security:
-
NIST curves - Standard curves widely supported and FIPS-compliant
-
BrainPool curves - Alternative curves for specific compliance requirements
-
- ElGamal
-
Legacy algorithm. Supported for compatibility with older systems. Use RSA or ECC for new implementations.
Important
Curve25519 keys are not supported.
For detailed instructions on generating PGP keys, see Generate PGP keys.
PGP Symmetric Encryption Algorithms
These algorithms encrypt your actual file data. The algorithm used depends on how the PGP file was created by your PGP software:
FIPS-compliant algorithms (recommended for regulated environments)
-
AES-128, AES-192, AES-256 - Advanced Encryption Standard (recommended)
-
3DES - Triple Data Encryption Standard (legacy, use AES when possible)
Other supported algorithms
-
IDEA, CAST5, Blowfish, DES, TwoFish, CAMELLIA-128, CAMELLIA-192, CAMELLIA-256
Note
You don't choose the symmetric algorithm directly when using Amazon Transfer Family workflows - it's determined by the PGP software used to create the encrypted file. However, you can configure your PGP software to prefer FIPS-compliant algorithms like AES-256.
For more information about supported symmetric algorithms, see Supported symmetric encryption algorithms.