Set Up AWS¶
These instructions assume you have:
- a working version of Pushkin (see Starting a Pushkin Project)
- access to AWS
- a Docker (Hub) account
Define security groups¶
You’ll need two security groups: one for rancher and one for the databases.
The rancher EC2 security group should be open to all traffic on ports
Port Protocol 80 TCP 443 TCP 8080 TCP 500 UDP 4500 UDP
This is for normal web access, the rancher management web UI, and the Rancher host infrastructure. The database security group should be open to all TCP traffic on ports 3306 (MySQL) and 5432 (Postgres).
Instructions on creating an EC2-security-group can be found on AWS. * Note: Link for linux instances *
- >>>>>>> c3e5433b7e0799acba0b27a06014ae3af1704178
- Instructions on creating a database-security-group can be found on AWS.
Get an EC2¶
The most straightforward way to do this is to use the official Rancher OS already on Amazon. Create it with the AMI from the list here appropriate to your region.
Instructions on creating EC2 instances can be found on AWS.
Get databases (RDS)¶
You’ll need three databases. One’s for rancher, one’s for transactions, and one’s for stored data, which we will refer to as Main DB. Launch all three with the database security group created previously. t2.medium is the recommended size for all of them.
- Rancher DB: MySQL
- Transaction DB: Postgres
- Main DB: Postgres
Instructions on creating RDS Instances can be found on AWS.
Prepare the transactions database¶
The transaction database serves as a running log of queries to the Main DB, recording all activity which passes through it.
Connect to the transactions database just created using any Postgres client and run the following code to make a transactions table:create table transactions ( id SERIAL PRIMARY KEY, query TEXT not null, bindings TEXT )
Get an S3 Bucket¶
Next, you’ll need an S3 bucket for file backups, data storage, and retrieval. Create a new S3 bucket with open permissions for all traffic.
Instructions on creating S3 buckets can be found on AWS.
Now, you will need an AWS CloudFront distribution. CloudFront connects to an S3 bucket, and serves to distribute the contents of that bucket, which could include pickled objects, data-sets, and other resources, to any web application which possesses a CloudFront URL.
This URL is provided to Pushkin in the .env file located in the root folder.
Instructions on creating CloudFront distributions can be found on AWS.
Get AWS CLI Tools¶
Set up IAM Users and Roles¶
You will need some way of securely controlling access to AWS services and resources. This can be done by setting up IAM roles and users, which allows other developers and contributers to access your resources without needing to share access keys or passwords.
More information on IAM users can be found here_