Comment on page
Basic AWS Setup
Before you can deploy anything on AWS, you must do a few things.
To install the AWS Command Line Interface (CLI), do the following:
pip install awscli
Next, you will need AWS access keys (access key ID and secret access key). If you don’t have those, see the AWS documentation about access keys.
You should also pick a default AWS region name (e.g.
eu-central-1). The AWS documentation has a list of them.Once you’ve got your AWS access key and you’ve picked a default AWS region name, go to a terminal session and enter:
aws configure
and answer the four questions. For example:
AWS Access Key ID [None]: AKIAIOSFODNN7EXAMPLE
AWS Secret Access Key [None]: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
Default region name [None]: eu-central-1
Default output format [None]: [Press Enter]
This writes two files:
~/.aws/credentials and ~/.aws/config. AWS tools and packages look for those files.Eventually, you’ll have one or more instances (virtual machines) running on AWS and want to SSH to them. To do that, you need a public/private key pair. The public key will be sent to AWS; you can tell AWS to put it in any instances you provision there. You will keep the private key on your local workstation.
To send the public key to AWS, use the AWS Command Line Interface:
aws ec2 import-key-pair \
--key-name "<key-name>" \
--public-key-material file://~/.ssh/<key-name>.pub
If you're curious why there's a
file:// in front of the path to the public key, see issue aws/aws-cli#41 on GitHub.If you want to verify that your key pair was imported by AWS, go to the Amazon EC2 console, select the region you gave above when you did
aws configure (e.g. eu-central-1), click on Key Pairs in the left sidebar, and check that <key-name> is listed.Last modified 1yr ago