#Amazon aws postgresql images install#

Use django-ec2 for the name, and click on Create role: Select AWS Service and EC2, then click on Next: Permissions:Įnter container in the search box, select the AmazonEC2ContainerRegistryPowerUser policy, and click Next: Tags:Ĭlick Next: Review. Since we won't be allowing public access to the Docker image on ECR, you'll need to create an IAM role with permissions to pull Docker images from ECR and attach it to your EC2 instance.Ĭlick Roles in the left sidebar and then Create role: We'll be using AWS ECR to pull images from AWS ECR to our EC2 instance during deployment. Select your instance and click Associate: Navigate to Elastic IPs and click Allocate Elastic IP address:Ĭlick on Associate this Elastic IP address: It's recommended to use one for your production setup. pem key that we downloaded in the 'AWS EC2' step.īy default, instances receive new public IP address every time they start and re-start.Įlastic IP allows you to allocate static IPs for your EC2 instances, so the IP stays the same all the time and can be re-associated between instances. Navigate back to the EC2 console, select the newly created instance, and grab the public IP address:Ĭonnect to your EC2 instance using the.

#Amazon aws postgresql images install#

In this section, we'll install Docker on the instance, add an Elastic IP, and configure an IAM role.

It will take a few minutes for the instance to spin up. After the key pair is downloaded, click on Launch Instances: Select Create a new key pair and name it djangoletsencrypt. You need it for SSH connection to your instance.

SSH must be allowed for you to connect to the instance for set up and deployment.Ĭlick Review and Launch. Unless you have some additional security requirements, you'll probably want to allow HTTP and HTTPS traffic from anywhere for instances hosting web apps. Security group inbound rules are used to limit access to your instance from the internet. These rules are needed to issue certificates and to access the app. With Create a new security group selected, set the name and description to django-ec2 and add two rules: Then click Next a few times until you're at the Configure Security Group step. Click on Next: Configure Instance Details:Īt the Configure Instance Details step, leave everything as it is to keep things simple. In the next step, stick with the t2.micro instance. Use Ubuntu Server 18.04 LTS (HVM) for the server image (AMI): Next, navigate to the EC2 console and click Launch instance: Use SSH to connect to a remote server and SCP to copy files over to the server.įirst, create an AWS account if you don't already have one.Secure a containerized Django app running behind an HTTPS Nginx proxy with Let's Encrypt SSL certificates.Containerize a Django app along with Postgres, Nginx, and Gunicorn.This post builds on the Dockerizing Django with Postgres, Gunicorn, and Nginx and Securing a Containerized Django Application with Let's Encrypt posts. Run the Django app behind an HTTPS Nginx proxy with Let's Encrypt SSL certificates.Utilize Amazon Elastic Container Registry (ECR) image registry to store built images.Configure and use an Elastic IP address.By the end of this tutorial, you'll be able to: