AWS ECS - Setup Amazon ECR and push docker image to ECR (Part 2)

 Setup Amazon ECR and push docker image to ECR — Deploy to AWS ECS Fargate with Load Balancer (Part 2)

In this part, I will be covering setting up AWS ECR and push the backend server’s docker image to ECR.

Setup AWS Elastic Container Registry (ECR)

Docker has made the life of software engineers and DevOps engineers easier. Running a container anywhere besides development environment requires few steps i.e. push right version of docker image to docker registry. It also has been one of the first steps for deployment process. There are multiple container registry services like docker hub, Amazon Elastic Container Registry (ECR). Docker hub provide only one private repository for free to docker hub user account(not usable for organization) so Amazon ECR can be easier and best option.

Let’s get started with Amazon ECR.

Instructions:

  1. Login to AWS console and search for ECR and select Elastic Container Registry.
  2. Click on Create Repository.
  3. Select Visibility Setting for the repository and enter name of container registry. You can also enable tag immutability if you need.

4. In case you require image scan on each image push you can enable it. However, it is now deprecated. Similarly, you can enable KMS encryption if required.

5. Click on Create repository button and we are done with settings.

You have your ECR repository ready.

Push Backend Image to ECR repository

In order to push docker image to the repository, firstly we need aws cli installed and configured.

  1. Install AWS CLI and Configure aws:
    i. Download and install aws cli version 2
    ii. Configure aws and Add Access Key ID, Secret Access Key, Region Name and output format. Refer to this.
~ aws configure

2. Navigate to Amazon ECR Repositories page in aws console and click your repository.

3. Click on View push commands. There you will see few steps to follow to initially push your image to repository.

Note: I, being Linux user, will be following according to macOS/Linux tab. Please go to the OS tabs based on your OS and follow the steps.

a. Copy and run command from Step 1 from the pop-up and paste in your terminal. This step will log you into docker registry.

b. Copy and run command from Step 2 to build your Docker image. In case you have already built your image you can skip this step. (I assume you have built an image while following through Part 1)

c. After the build completes, copy and run command from Step 3 to tag your image so that you can push image to ECR repository.

d. Lastly, copy and run command from Step 4 to push the image to ECR repository.

4. Confirm your first push.

After first push, if you have to push your new image again to the repository, follow last 3 steps or click on View push commands and follow them.

Hurray! You have now successfully setup your Amazon ECR repository and push your backend docker image to it. Now we are going to create ECS set up here in Part 3

Comments

Post a Comment

Popular posts from this blog

Different Types of Reports in Scrum - Agile

Image
  Introduction to Agile Reporting I’m not going to elaborate on the Agile Framework itself here.  1. Sprint Burndown At a Sprint-level, the burndown presents the  easiest way to track and report status  (the proverbial  Red / Amber / Green ), i.e., whether your Sprint is on or off-track, and what are the chances of meeting the Sprint goals. The burndown chart – when used right – can provide  near-real time updates  on Sprint progress. “If your team do it right, then they would take in just the right amount of work into a sprint.” At the beginning of a Sprint, the Scrum team perform Sprint Planning and agree to take on development work worth a certain number of Story points. This forms the basis for the Sprint Burndown chart. The total story points agreed at the beginning of the sprint make up the y-axis, and the individual dates in the Sprint make up x-axis. If your team do it right, then they would take in just the right amount of work into ...
Read more

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources...
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed withou...
Read more