4a008e51e3
* Reorganized docs * Fixed internal links in basic usage * fixed the docker-compose command and volume for docs * fixed docs tests * fix travis docs test * tox ini file * fixed readme localhost links * edited tox and test docs to previous state * Fix tests errors related to docs reorganization Signed-off-by: David Dashyan <mail@davie.li> * Added ansible script installation option Signed-off-by: Lana Ivina <lana@ipdb.io> * Added ansible script to network setup guide Signed-off-by: Lana Ivina <lana@ipdb.io> * Hid the non-working button for now. Signed-off: Lana Ivina <lana@ipdb.io> * Try now button Co-authored-by: David Dashyan <mail@davie.li>
2.7 KiB
Basic AWS Setup
Before you can deploy anything on AWS, you must do a few things.
Get an AWS Account
If you don't already have an AWS account, you can sign up for one for free at aws.amazon.com.
Install the AWS Command-Line Interface
To install the AWS Command-Line Interface (CLI), just do:
pip install awscli
Create an AWS Access Key
The next thing you'll need is 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.
Generate an RSA Key Pair for SSH
Eventually, you'll have one or more instances (virtual machines) running on AWS and you'll want to SSH to them. To do that, you need a public/private key pair. The public key will be sent to AWS, and you can tell AWS to put it in any instances you provision there. You'll keep the private key on your local workstation.
See the appendix page about how to generate a key pair for SSH.
Send the Public Key to AWS
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.