Amazon Elastic Container Registry (ECR)

 What Is Amazon Elastic Container Registry?

Amazon Elastic Container Registry (ECR) is a managed AWS Docker registry service. Amazon ECR is a secure and reliable AWS service. Just like any other cloud computing service, we can scale it up or scale it down based on our requirements. Amazon ECR uses AWS Identity and Access Management (IAM) to enable resource-based permissions for private Docker repositories. Through the Docker command line interface (CLI) we can push, pull, and manage images.


Components of Amazon ECR:


Amazon ECR has the following components:


  • Registry:
    Each AWS account has an access to Amazon ECR registry. In registry, we can create image repositories and we can also store its image.
  • Authorization Token:
    Before pushing and pulling of images, your Docker client must authenticate to Amazon ECR registries as an AWS user. The Amazon web services command line interface (CLI) has a command called get-login which provides the user with an authentication credential to be passed to docker.
  • Repository:
    The docker image is contained inside the Amazon ECR image repository.
  • Repository Policy:
    The repository policies enables the users to have control on the access to their repository and the image within it.
  • Image:
    The user can very easily push or pull the docker images to their repository. The user can use the image of the repository on their local system or it could be used in Amazon ECS task definitions.

List Of Available Commands:

  • batch-check-layer-availability
  • batch-delete-image
  • batch-get-image
  • complete-layer-upload
  • create-repository
  • delete-lifecycle-policy
  • delete-repository
  • delete-repository-policy
  • describe-images
  • describe-repositories
  • get-authorization-token
  • get-download-url-for-layer
  • get-lifecycle-policy
  • get-lifecycle-policy-preview
  • get-login
  • get-repository-policy
  • initiate-layer-upload
  • list-images
  • list-tags-for-resource
  • put-image
  • put-lifecycle-policy
  • set-repository-policy
  • start-lifecycle-policy-preview
  • tag-resource
  • untag-resource
  • upload-layer-part

Comments

Post a Comment

Popular posts from this blog

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 and services.
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 without them. If these are not fulfilled, the project is con
Read more

Kubernetes

  Using containers to host applications and other processes has gone mainstream. As more and more workload is moved into containers, management systems are needed to handle the demands of containerized applications at scale. One of the most popular options for managing  container-based workload is Kubernetes . Kubernetes combines container management automation with an extensible API to create a cloud-native application management powerhouse. At its core, Kubernetes manages the placement of pods, which can consist of one or more containers, on a Kubernetes cluster node. Additionally, if one of these pods crashes, Kubernetes can create a new instance of it. If a cluster node is removed, Kubernetes can move any affected workload to a different node in the cluster. On top of that, Kubernetes pods can be scaled to provide more or less throughput to meet scale demands and these scale operations can be triggered manually or automatically using Kuberentes horizontal pod auto-scaling. Finally,
Read more