{"id":16000,"date":"2023-11-28T12:24:28","date_gmt":"2023-11-28T06:54:28","guid":{"rendered":"https:\/\/opstree.com\/blog\/\/?p=16000"},"modified":"2023-11-28T12:54:57","modified_gmt":"2023-11-28T07:24:57","slug":"amazon-ecr-container-images-across-accounts-or-regions","status":"publish","type":"post","link":"https:\/\/opstree.com\/blog\/2023\/11\/28\/amazon-ecr-container-images-across-accounts-or-regions\/","title":{"rendered":"Amazon ECR Container Images Across Accounts or Regions"},"content":{"rendered":"\n

Want to implement an AWS Elastic Container Registry Replication practice in your DevOps solution? But don\u2019t know how to start and where to go. Folks, now you are on the right path.<\/p>\n\n\n\n

We’re pursuing this to safeguard our production resources in the ap-south-1 (Mumbai) region from potential disasters and connectivity issues. Ensuring resource distribution across other AWS regions is critical. Our microservices-driven applications rely on Docker images, including custom ones crucial for disaster recovery. AWS Container Registry offers a secure, efficient solution for storing and managing Docker images, simplifying image storage, and enabling seamless sharing across private or public environments.<\/p>\n\n\n\n

So, here you may wonder how we can replicate the same images from its registry to another AWS Account(cross-accounts) or in the same account in different regions(cross-region).<\/p>\n\n\n\n

\n

Pre-requisite:<\/strong> <\/p>\n\n\n\n

    \n
  1. Need two AWS Accounts with admin access to Amazon ECR service and programmatic access for it(to pull\/push images). <\/li>\n\n\n\n
  2. Login\/Signup:  https:\/\/aws.amazon.com\/console\/<\/a><\/li>\n<\/ol>\n\n\n\n
    \n

    Note: 1st AWS Account: Source account<\/em><\/p>\n\n\n\n

    2nd AWS Account: Destination account<\/em><\/p>\n<\/div>\n<\/div>\n\n\n\n

    \"\"
    The architecture<\/figcaption><\/figure>\n\n\n\n

    Enough theory part let’s take action for this, <\/p>\n\n\n\n\n\n\n\n

    \n

    Login to 1st AWS Account: Source(select the respective region I have chosen here ap-south-1(Mumbai)) <\/p>\n\n\n\n

    We have to create a replication rule. A Source account enables the Replication rule, as below: <\/p>\n<\/div>\n\n\n\n

    \n

    Action 1: Go to Amazon Elastic Container Registry<\/strong><\/p>\n\n\n\n

    Action 2: Select Private Registry<\/strong> in the left pane and in that select Replication<\/strong><\/p>\n\n\n\n

    Action 3: Click on the Add rule<\/strong>, and you will get 4 Steps.<\/p>\n\n\n\n

    Action 4: Choose step 1: Destination types<\/strong> have two types:<\/p>\n\n\n\n

    i) Cross-region replication<\/strong>: click on the first toggle<\/strong> button If you need ECR replication across regions within the same account that is Cross-region replication,<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    Click on Next for Step 2, and then you will get the cross-region replication step where you have to select your destination region names. You can mention multiple regions. <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    Click on Next, in step 3, As per your repository naming convention in your organization you can put a filter on it and if you don’t want to apply any filter then just simply put it blank as this is an optional step but this means like all repository will replicate to other regions of AWS. Click on next and review & submit the rule.<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    So till now, we have set up cross-region replications.<\/p>\n\n\n\n

    <\/p>\n\n\n\n

    ii) Cross-account replication<\/strong>: click on the second toggle<\/strong> button if you need ECR replication across different accounts that are Cross-account replication.) Click the next button.<\/p>\n\n\n\n

    <\/p>\n<\/div>\n\n\n\n

    \n

    In Step 2: Cross-account replication<\/strong>, you have to put the destination account number and the region. <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    Click on Next, and you may put the filter as the above step mentioned in cross-region replication. then Review and Submit.<\/p>\n\n\n\n

    Here we go, we have created the replication rule in the Source account.<\/p>\n\n\n\n

    \"\"<\/figure>\n<\/div>\n\n\n\n
    \n

    iii) Cross-account & Cross-region Replication:<\/strong> You can enable both toggles for cross-account with multiple regions in the destination account. The steps will be the same as discussed in the i), and ii) steps.<\/p>\n\n\n\n

    Action 5: Then, we have to create registry permissions in the Destination account to allow ECR repos images as below, <\/p>\n\n\n\n

    whereas, <\/p>\n\n\n\n

    1. principal of source account root(arn:aws:iam::<source_account>:root), <\/p>\n\n\n\n

    2. Taking action on “ecr:*” is the best practice that aws suggested, we can perform all actions from creating a repository to replicating images and many more.<\/p>\n\n\n\n

    3. Take ecr resource of the source account like “arn:aws:ecr:ap-south-1:<source_account>:repository\/*”. All repositories can replicate to this destination account. see the below permission:<\/p>\n<\/div>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    So let’s see the magic now, I have created one replication-testing repository in the source account. and will be pushing one sample image with the latest tag.<\/p>\n\n\n\n

    \"\"
    Source Account ECR Repository manually created<\/em><\/figcaption><\/figure>\n\n\n\n
    \"\"
    Destination Account there is no ECR repository name called replication-testing<\/em><\/figcaption><\/figure>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    \"\"
    The ECR Repository \u201creplication-testing\u201d has the image with the latest tag<\/em><\/figcaption><\/figure>\n\n\n\n
    \"\"
    The ECR repository name replication-testing in the destination account syncs the image from the source to the destination account.<\/em><\/figcaption><\/figure>\n\n\n\n
    \n

    Folks, here you can see the newly created pushed images in the destination account and specified region. <\/p>\n<\/div>\n\n\n\n

    Summarizing it: <\/strong><\/h3>\n\n\n\n
    \n
    \n
    \n
      \n
    1. This is the best practice and strategy for disaster recovery plans, where once everything is set, in your hands all ECR repos will be there in the destination account.<\/li>\n\n\n\n
    2. We don’t have to create any AWS private ECR repository in the destination account, it will be created automatically, once the replication rule and permission are applied.<\/li>\n\n\n\n
    3. The only thing is that AWS still won’t support the feature of old image replication. Only newly pushed images can be replicated.<\/li>\n\n\n\n
    4. Also, manifests of images can be replicated within the repos.<\/li>\n\n\n\n
    5. If we wanted to delete the image from the source\/destination repository it would delete only from that repos. Don’t worry about other images residing in the destination\/source repository.<\/li>\n<\/ol>\n<\/div>\n\n\n\n
        \n
      1. A replication configuration may contain up to 10 rules, with up to 25 unique destinations across all rules and 100 filters per each rule.<\/li>\n\n\n\n
      2. Cost: Prices may vary for respective regions. Will pay only for what we have replicated images. Can apply life cycle policy. To delete older images with tags.<\/li>\n<\/ol>\n<\/div>\n\n\n\n

        Example: If 1GB image size then the price for the ap-south-1(Mumbai) region would be,
                           1 GB per month x 0.10 USD = 0.10 USD<\/strong><\/p>\n<\/div>\n\n\n\n

        That’s all from this blog, keep learning!!<\/p>\n\n\n\n

        \n

        References:<\/strong><\/p>\n\n\n\n

        https:\/\/aws.amazon.com\/blogs\/containers\/using-amazon-ecr-replication-rules-to-optimize-your-application-delivery-process\/ https:\/\/aws.amazon.com\/blogs\/containers\/amazon-ecr-in-multi-account-and-multi-region-architectures\/ <\/p>\n\n\n\n

        https:\/\/invenioit.com\/continuity\/disaster-recovery-statistics\/<\/p>\n\n\n\n

        https:\/\/n2ws.com\/blog\/aws-cloud\/aws-cloud-data-protection-survey<\/p>\n<\/div>\n\n\n\n

        Blog Pundits: Prakash Jha<\/strong><\/a> <\/a>and Sandeep Rawat<\/a><\/strong><\/p>\n\n\n\n

        OpsTree is an End-to-End DevOps Solution<\/a> Provider.<\/strong><\/p>\n\n\n\n

        \n
        Contact Us<\/a><\/div>\n<\/div>\n\n\n\n

        Connect with Us<\/strong><\/p>\n\n\n\n