Basic AWS Setup
Before you can deploy anything on AWS, you must do a few things.
Last updated
Before you can deploy anything on AWS, you must do a few things.
Last updated
If you don't already have an AWS account, you can .
To install the AWS Command Line Interface (CLI), do the following:
Next, you will need AWS access keys (access key ID and secret access key). If you don’t have those, see .
You should also pick a default AWS region name (e.g. eu-central-1). The AWS documentation has .
Once you’ve got your AWS access key and you’ve picked a default AWS region name, go to a terminal session and enter:
and answer the four questions. For example:
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:
See the appendix .
If you're curious why there's a file:// in front of the path to the public key, see issue .
If you want to verify that your key pair was imported by AWS, go to , 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.