
Photo by Samantha Lam on Unsplash
One of the parameters required for launching an EC2 instance is a Key Pair which is effectively an SSH Key used for interactive logging into the default user account — on Amazon Linux it’s the ec2-user account — or for decrypting the Windows Administrator’s password.
It is easy to create a new Key Pair / SSH Key as part of the EC2 launch process however as soon as you start using more regions and more accounts you will quickly end up with heaps of different Keys and unless you are diligent with their naming both on the filesystem and in AWS you will end up with a mess. Like I used to.
Fortunately there is a way to re-use an existing Key Pair in other regions or even in other AWS accounts. And it’s actually pretty easy.
Before we start I assume you’ve got an existing Key Pair or SSH Key stored in a PEM file. Either one created in the AWS EC2 console, or your own usual SSH Key created using ssh-keygen. Either will work. Let’s say it’s saved as ~/.ssh/michael.ludvig-key.pem.
Mining Bitcoin and other crypto on AWS
The Bitcoin mania has struck again. Take part in the frenzy and start mining crypto on AWS using our complete guide.
Importing existing Key Pair
To import this key to a new region switch to that region and go to Services ➞ EC2 ➞ Key Pairs and click Import Key Pair.

The key pair name must be unique within the region (i.e. you can’t have two different keys with the same name) but you should use the same name in all the regions. Keeping it consistent across the regions greatly simplifies your automation — you won’t need a per-region key name mapping.
Now the Public key contents — that’s the part that took me a while to figure out because as of now Amazon provides misleading information both online and in the aws-cli help.
The format of the public key must be in RFC4716 format, not in the openssh format starting with ssh-rsa AAAAB3... format that’s suggested by Amazon’s docs yet rejected by the import tool. Convert any of your SSH keys to RFC4716 with this command:
~ $ ssh-keygen -e -m RFC4716 -f ~/.ssh/michael.ludvig-key.pem
Enter passphrase: ****
---- BEGIN SSH2 PUBLIC KEY ----
Comment: "2048-bit RSA, converted by michael.ludvig from Open"
AAAAB3NzaC1yc2EAAAADAQABAAABAQC3Y5e3oNnxHXZAAPMHjlxuzhXnqt+3q2
HdF3HZskjKlFIjW83iBPcAsMi3sf0CGnFvcP0U9o6MAXHhLtKIEjmybAfNP/AJ
[...]
u9RxTR1zR87JY4D8w5vFQMXyjj/6p2xRyTwwCHVcU92mxARi4ipjH27uM8SpVj
a2mi2HkhsWtDA6JIkd1qpogtj
---- END SSH2 PUBLIC KEY ----
Using the same command you can also convert your public keys (e.g. ~/.ssh/id_rsa.pub) to RFC4716 format and import them to Amazon.
Now simply copy and paste the output including the BEGIN and END lines and click Import.

You will see it’s successfully imported with a Fingerprint displayed:

Importing with AWS-CLI
The key can also be imported from the command line using aws cli tool. It’s a two-step process, first save the public key to a file. Note the .pub extension, be careful to not overwrite your private .pem key!
~ $ ssh-keygen -e -m RFC4716 -f ~/.ssh/michael.ludvig-key.pem > michael.ludvig-key.pub
The next step is the import:
~ $ aws --region=xy-abcd-1 \
ec2 import-key-pair \
--key-name=michael.ludvig-key \
--public-key-material=file://michael.ludvig-key.pub
{
"KeyName": "michael.ludvig-key",
"KeyFingerprint": "ab:9c:38:ef:4b:99:1e:b1:f6:60:e6:fe:a5:fc:10:fa"
}
Obviously the KeyFingerprint should be the same as with the GUI import.
If the provided file was in a wrong format you will receive an error:
A client error (InvalidKey.Format) occurred when calling the ImportKeyPair operation: Key is not in valid OpenSSH public key format
Importing to all regions
With a simple for loop over the list of regions it’s easy to import the key into all available regions in a few seconds.
~ $ for REGION in $(aws --output text ec2 describe-regions --query 'Regions[].RegionName[]'); do
echo "== ${REGION} =="
aws --region=${REGION} ec2 import-key-pair \
--key-name=... --public-key-material=...
done
That’s it. This way you can use the same SSH Key across all the AWS regions.