<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Avishka Weeraddana on Medium]]></title>
        <description><![CDATA[Stories by Avishka Weeraddana on Medium]]></description>
        <link>https://medium.com/@avishkaw?source=rss-05265004f1ee------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5I69r4XXICJcVbzFnPE_tQ.jpeg</url>
            <title>Stories by Avishka Weeraddana on Medium</title>
            <link>https://medium.com/@avishkaw?source=rss-05265004f1ee------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:46:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@avishkaw/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What Is Amazon EC2? A Beginner’s Guide to Virtual Servers in AWS]]></title>
            <link>https://medium.com/awsfullstack/what-is-amazon-ec2-a-beginners-guide-to-virtual-servers-in-aws-8faa198b03d3?source=rss-05265004f1ee------2</link>
            <guid isPermaLink="false">https://medium.com/p/8faa198b03d3</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[amazon-ec2]]></category>
            <category><![CDATA[virtual-machine]]></category>
            <category><![CDATA[cloud-infrastructure]]></category>
            <dc:creator><![CDATA[Avishka Weeraddana]]></dc:creator>
            <pubDate>Fri, 08 May 2026 05:24:31 GMT</pubDate>
            <atom:updated>2026-05-08T05:24:31.884Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BePiR0ihmsWRWUoO7QCm3A.jpeg" /></figure><p>Amazon EC2 (Elastic Compute Cloud) is a service that provides virtual servers, called <strong>instances</strong>, in the cloud. You can choose the operating system, configure resources like CPU and memory, and start or stop the server anytime.</p><p>The ‘Elastic’ part means you can easily scale your resources up or down based on your application needs. Instead of managing physical hardware, you can run everything on AWS infrastructure.</p><p>It works like renting a computer in the cloud. You only pay for what you use, and you can adjust your setup at any time.</p><p><strong>In simple terms,</strong></p><ul><li>Not a physical server</li><li>Not serverless</li><li>It is a <strong>virtual machine in AWS.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8H91gjwcuX3tNiZxpbxxLA.png" /><figcaption>what-is-amazon-ec2</figcaption></figure><h3>Why Do Developers Use EC2?</h3><p>Developers use Amazon EC2 because it gives full control over the server environment. You can install software, configure settings, and run applications just like on a real machine. This makes it useful for many types of workloads.</p><p>EC2 is also flexible and scalable. You can launch a single instance for small tasks or scale to thousands of instances for larger applications. It allows teams to grow their infrastructure based on demand without upfront hardware costs.</p><p><strong>Key reasons developers use EC2</strong></p><ul><li>Fast Setup: Launch server in minutes</li><li>Scalable: Run one instance or thousands as needed</li><li>Full control: Root access to install and configure software</li><li>Reliable: Support high availability across regions</li><li>Cost-effective: Pay only for what you use</li></ul><h3>What Key Amazon EC2 Concepts Should Beginners Know?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*82RusYXZCIWGc2oJAQrBwg.png" /><figcaption>amazon-ec2-core-components</figcaption></figure><p>Before using EC2, it is important to understand a few basic concepts that are used when creating and managing instances.</p><p><strong>Important Concepts,</strong></p><ul><li>AMI (Amazon Machine Image): A template that contains the operating system and required software.</li><li>Instance Types: Different combinations of CPU, memory, and performance</li><li>Security Groups: A virtual firewall that controls incoming and outgoing traffic.</li><li>Key Pairs: Used to securely connect to your instance.</li></ul><p>These concepts help you configure and manage EC2 instances effectively.</p><h3>How to Launch Your First EC2 Instance</h3><p>Launching your first EC2 instance is one of the easiest ways to get started with AWS. You can do everything from the AWS Management Console, and the process only takes a few minutes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u54Yj4MJSsfNrhU8r4UO0Q.png" /><figcaption>How to Launch Your First EC2 Instance</figcaption></figure><p>To launch your first EC2 instance, start by logging in to the AWS Management Console and opening the EC2 dashboard. From there click “Launch Instance” to begin the setup process. Next, choose an operating system by selecting an AMI, such as Amazon Linux or Ubuntu, which are good options for beginners. After that, select an instance type like t2.micro or t3.micro, which are suitable for basic use and learning. Then configure your security settings by creating a security group that allows SSH for Linux or RDP for Windows. You will also need to create and download a key pair, which is required to securely connect to your instance later. Finally, click Launch, and your EC2 instance will start running in AWS.</p><h3>How to Connect to and Manage EC2</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LhCXzX0N41xGUJq9XCm5-w.png" /><figcaption>How to Connect to and Manage EC2</figcaption></figure><p>Once your EC2 instance is running, the next step is to connect to it and start managing your server. For Linux instances, you can use an SSH client like Terminal or PuTTY along with your key pair. For Windows instances, you can connect using Remote Desktop (RDP). AWS also provides EC2 Instance Connect, which allows you to connect directly from your browser through the AWS Console.</p><p>After connecting, you can manage your instance easily from the AWS console. You can start, stop, or reboot the instance, monitor its performance, and attach storage when needed. This gives you full control over your virtual server, just like managing a real machine.</p><h3>Common EC2 Use Cases</h3><p>Amazon EC2 is used in many real-world scenarios because it gives flexibility and control over computing resources. Developers and teams can use it for both small projects and large-scale applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l9oveekU7zu1jWKV4p8Hbg.png" /><figcaption>Common Amazon EC2 Use Cases</figcaption></figure><h3>Amazon EC2 Pricing Basics</h3><p>Amazon EC2 pricing depends on how you use your instance. The cost is mainly based on the type of instance you choose, how long it runs, the storage you use, and the data transferred. This flexible model allows you to control costs based on your actual usage.</p><p><strong>Purchase options</strong></p><ul><li><strong>On-Demand</strong>: Pay as you go with no long-term commitment.</li><li><strong>Savings Plans</strong>: Lower cost when you commit to usage for 1–3 years.</li><li><strong>Spot Instances</strong>: Up to 90% cheaper, but can be stopped by AWS when capacity is needed.</li></ul><h3>Beginner Tips and Common Mistakes</h3><p>When starting with Amazon EC2, most issues come from small mistakes rather than complex problems.</p><ul><li>Leaving instances running and increasing cost</li><li>Choosing the wrong instance type</li><li>Misconfiguring security groups</li><li>Losing the key pair file</li><li>Not monitoring usage and billing</li></ul><p><strong>Quick Tips for Using AWS EC2</strong></p><ul><li>Stop or terminate instance when not in use</li><li>Use small instance types for learning</li><li>Monitor usage in the billing dashboard</li><li>Keep your key pair secure and never share it</li></ul><h3>Final Thoughts</h3><p>Amazon EC2 is a strong starting point for anyone learning AWS because it helps you understand how virtual servers work in the cloud. It gives you full control over your environment while still being flexible and scalable for different use cases. AWS EC2 provides a solid foundation for anyone beginning their journey with cloud infrastructure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8faa198b03d3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/awsfullstack/what-is-amazon-ec2-a-beginners-guide-to-virtual-servers-in-aws-8faa198b03d3">What Is Amazon EC2? A Beginner’s Guide to Virtual Servers in AWS</a> was originally published in <a href="https://medium.com/awsfullstack">AWS Fullstack</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automating Docker Image Deployment to AWS ECR with GitHub Actions]]></title>
            <link>https://medium.com/awsfullstack/automating-docker-image-deployment-to-aws-ecr-with-github-actions-e519936fee7d?source=rss-05265004f1ee------2</link>
            <guid isPermaLink="false">https://medium.com/p/e519936fee7d</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[aws-ecr]]></category>
            <category><![CDATA[github-actions]]></category>
            <dc:creator><![CDATA[Avishka Weeraddana]]></dc:creator>
            <pubDate>Wed, 29 Apr 2026 14:01:05 GMT</pubDate>
            <atom:updated>2026-04-30T05:31:36.065Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hEJh8ZopT2zb5Y-QGfuxRw.png" /></figure><p>Building and pushing Docker images manually can help you understand the basics, but it’s not a good way to do things once projects start to grow. When teams make changes more often, doing the same things by hand over and over again takes a long time and isn&#39;t always accurate. and is easy to mess up. A lot of teams use a CI/CD pipeline to automate building and deploying images for this reason.</p><p>GitHub Actions makes the process much easier by connecting your source code directly to AWS ECR. Instead of building and pushing Docker images manually every time, you can create a workflow that does it automatically whenever code is updated. In this guide, we will look at how to automate Docker image deployment to AWS ECR with GitHub Actions and make the path from code change to deployment-ready image much simpler.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NVtgzXFj02CP27EV2AW2Eg.png" /><figcaption>automate-docker-deployment-aws-ecr-actions</figcaption></figure><h3>Why Should You Automate Docker Deployment With a CI/CD Pipeline?</h3><p>Relying on developers to manually build and push containers from their local machines creates a massive bottleneck and introduces severe security risks. When you automate Docker deployments using a robust CI/CD pipeline, every single code commit is automatically tested, packaged, and delivered to your registry without manual intervention. GitHub Actions is particularly powerful because it lives right alongside your source code, meaning you do not have to integrate or pay for a completely separate deployment tool.</p><p><strong>Key Benefits of Automation</strong></p><ul><li>Better consistency</li><li>Faster Delivery</li><li>Improved Traceability</li><li>Better support for regular releases</li></ul><h3>What Prerequisites Do You Need for AWS ECR and GitHub Actions?</h3><p>Before you automate Docker deployment to AWS ECR, a few things need to be ready. You need both your AWS setup and your GitHub repository in place so the workflow can build and push images without issues. Getting these basics ready first makes the automation process much easier to follow.</p><p>At a minimum, you should have an AWS account, an existing ECR repository, and a GitHub repository that already contains your application code. Your project should also include a Dockerfile, since GitHub Actions will use it to build the Docker image. On top of that, AWS permissions must be configured correctly so the workflow can be authenticated and push the image to ECR.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dDByax67JCrXXzFIvsdXpw.png" /><figcaption>prerequisites-aws-ecr-github-actions-setup</figcaption></figure><h3>How Do You Securely Store AWS Credentials in GitHub?</h3><p>Connecting your GitHub repository to your AWS environment requires authorization, but hardcoding sensitive credentials into your codebase is a catastrophic security mistake. Instead, you must utilize GitHub Repository Secrets, which encrypt your sensitive data and keep it entirely hidden from anyone browsing the public or private code. You can find this secure storage area by navigating to your repository settings, selecting &quot;Secrets and Variables,” and clicking on &quot;Actions.&quot;</p><p>Here you will safely store your AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY as securely encrypted environment variables. When your GitHub Actions workflow eventually runs, it will pull these secrets dynamically, allowing it to log into your AWS cloud ecosystem without ever exposing your private keys in the build logs.</p><h3>How Do You Write the GitHub Actions Workflow File?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TU1kFsf8K6VnRGhhCm46Pw.png" /><figcaption>github-actions-workflow-docker-ecr-pipeline</figcaption></figure><p>The GitHub Actions workflow file is the part that tells your automation what to do and when to do it. It is written in YAML and stored inside the <strong>.github/workflows/ </strong>folder in your repository. This file defines the event that starts the workflows, such as a push to the main branch, and the steps GitHub Actions should run after that.</p><p>In this case, the workflow usually starts by checking out your code and preparing access to AWS. After that, it logs in to AWS ECR, builds the Docker image, applies the right tag, and pushes the image to your ECR repository. Once this file is in place, GitHub Actions can handle the same process automatically every time new code is pushed.</p><h3>Long-Lived IAM Keys vs. OIDC: Which Authentication Method Is Better?</h3><p>When setting up GitHub Actions for AWS ECR, you need a way for GitHub to authenticate with AWS. One option is to use long-lived IAM access keys, which are stored as GitHub secrets. This method is easier for beginners to understand, but it also creates more security risk because the keys stay valid until you rotate or remove them. GitHub’s OIDC guidance specifically positions OIDC as a way to avoid storing long-lived cloud credentials in GitHub secrets.</p><p>A more modern option is OIDC. With OIDC, GitHub Actions requests a short-lived identity token during the workflow run, and AWS exchanges that token for temporary credentials tied to an IAM role. That means you do not need to keep permanent AWS secrets in GitHub, and the credentials expire after the workflow instead of staying active indefinitely. AWS IAM documents this model as exchanging an OIDC token for temporary AWS security credentials mapped to an IAM role.</p><p>OIDC takes a little more setup because you need to create an IAM OIDC provider, configure a trust relationship, and let the workflow request an ID token. The official AWS credentials action for GitHub Actions recommends OIDC as the quick start and preferred approach, and GitHub’s AWS OIDC guide explains that the workflow needs it id-token: write so GitHub can request the token.</p><p><strong>Simple takeaway</strong></p><ul><li><strong>IAM access keys </strong>are easier for quick learning</li><li><strong>OIDC </strong>is safer for real CI/CD pipelines</li><li><strong>OIDC</strong> avoids storing long-lived AWS secrets in GitHub</li><li><strong>OIDC </strong>is usually the better choice for production workflows.</li></ul><h3>How Do You Verify Your Automated Docker Deployment?</h3><p>After the workflow runs, the next step is to make sure the Docker image was pushed to AWS ECR successfully. The easiest place to start is the <strong>Actions </strong>tab in your GitHub repository, where you can see whether the workflow passed or failed. This helps you confirm that the build, logging, and push steps all completed as expected.</p><p>Once the workflow shows success, you can check AWS ECR in the AWS console. Open your repository and confirm that the new image appears there with the expected tag and a recent timestamp. This gives you quick proof that the automation is working and that the image is ready for deployment or testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NH7MAMGnzIEMYNgSUEFhaQ.png" /><figcaption>verify-github-actions-aws-ecr-deployment</figcaption></figure><h3>What Are the Common CI/CD Pipeline Mistakes to Avoid?</h3><ul><li>Using incorrect AWS credentials</li><li>Forgetting to store secrets properly in GitHub</li><li>Tagging the image with the wrong ECR repository URI</li><li>Missing IAM permissions for AWS ECR access</li><li>Using the wrong AWS Region</li><li>Not checking workflow logs when a run fails</li></ul><p><strong>Quick Tips for a Better Pipeline</strong></p><ul><li>Use Git SHAs for image tags</li><li>Enable caching to speed up builds</li><li>Never print secrets or token in logs</li><li>Review workflow logs when something fails</li><li>Clean up old images to avoid extra storage costs</li></ul><h3>Final Thoughts</h3><p>GitHub Actions makes it easier to automate Docker deployments to AWS ECR by removing manual steps and creating a consistent, repeatable workflow. It helps teams move faster with fewer errors and also provides a good starting point for building more advanced CI/CD setups like multi-environment deployments and integrations with services such as ECS or EKS.</p><p><a href="https://medium.com/awsfullstack/aws-ecr-for-beginners-how-to-store-and-manage-docker-images-in-aws-3b971ca27a8f">AWS ECR for Beginners: How to Store and Manage Docker Images in AWS</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e519936fee7d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/awsfullstack/automating-docker-image-deployment-to-aws-ecr-with-github-actions-e519936fee7d">Automating Docker Image Deployment to AWS ECR with GitHub Actions</a> was originally published in <a href="https://medium.com/awsfullstack">AWS Fullstack</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS ECR for Beginners: How to Store and Manage Docker Images in AWS]]></title>
            <link>https://medium.com/awsfullstack/aws-ecr-for-beginners-how-to-store-and-manage-docker-images-in-aws-3b971ca27a8f?source=rss-05265004f1ee------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b971ca27a8f</guid>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws-ecr]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Avishka Weeraddana]]></dc:creator>
            <pubDate>Mon, 20 Apr 2026 14:01:04 GMT</pubDate>
            <atom:updated>2026-04-20T14:01:04.076Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/788/0*uqCIsZfnxVMoFup8.png" /></figure><p>Many beginners learn how to build Docker images locally, but they are not always sure where those images should live once they move into cloud-based workflows. This is where AWS ECR becomes useful, because it gives teams a secure and managed place to store container images inside AWS.</p><h3>What Is AWS ECR?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/0*QRyB-6U6AK5ZSyB1.png" /></figure><p>AWS Elastic Container Registry, or AWS ECR, is a managed AWS service used to store, organize, and share container images. You can also connect it to Docker-based workflows, which makes it easier for developers to move applications from development to deployment.</p><p><strong>In simple terms</strong></p><ul><li>It is not a container runtime</li><li>It is not Kubernetes</li><li>It is not where you build images</li><li>It is where <strong>images are stored and retrieved.</strong></li></ul><p><strong>Benefits of AWS ECR</strong></p><ul><li>Easy to store and manage container images.</li><li>Works smoothly with AWS services like ECS and EKS.</li><li>Improves security with IAM access control.</li><li>Make deployments easier with stored Docker images.</li></ul><p><strong>Why Do Developers Use AWS ECR Instead of Just Keeping Images Locally</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/0*37WkyIxn6ER3NHyi.png" /><figcaption>Why Do Developers Use AWS ECR Instead of Just Keeping Images Locally.</figcaption></figure><h3>Private vs. Public Repositories in ECR</h3><p>AWS ECR supports both private and public repositories, but they serve different needs.</p><p><strong>A private AWS ECR repository</strong> usually focuses on:</p><ul><li>Restricted access through AWS IAM</li><li>Internal team or company use</li><li>Private application images and proprietary code</li><li>Authentication for both and pull actions</li></ul><p><strong>A public AWS ECR repository</strong> is different. It is more open and shareable. It is built for:</p><ul><li>Public access over the internet</li><li>Open source tools and public base images</li><li>Easier image distribution to a wider audience</li><li>Authentication required for push, not for pull</li></ul><h3>How Do You Create Your First AWS ECR Repository?</h3><p>Creating an ECR repository is usually the first real step when you start working with AWS ECR. While you can create a repository in AWS ECR using the CLI or infrastructure as code, the AWS console is often the easiest option for beginners because it makes the setup process easier to follow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/0*_eSrrogti4R3S-l1.png" /><figcaption>Basic steps to create a repository in AWS ECR</figcaption></figure><p>Once you review the setup and create the repository, your AWS ECR repository is ready to receive Docker images.</p><h3>How Can You Push a Docker Image to AWS ECR?</h3><p>Once your repository is ready, the next step is to move a local Docker image into it. This is the point where many beginners start to see how ECR fits into real development work. In simple terms, the process usually involves an AWS ECR login, selecting or building the image you want to upload, applying the right image tagging, and then pushing it into the repository.</p><p>The most important thing to understand is that Docker cannot send images to AWS ECR until it is authenticated. After that, the image needs to be tagged with the correct ECR repository URI so AWS knows exactly where it should go. When those two steps are done, you can push the Docker image to ECR and make it available for deployment, testing, or later use in your workflows.</p><p>Basic workflow to push a Docker image to ECR</p><ul><li>Authenticate Docker to AWS ECR</li><li>Build or choose a local Docker Image</li><li>Apply image tagging with the ECR repository URI</li><li>Push the image to ECR</li></ul><h3>How Do You Pull a Docker Image from AWS ECR?</h3><p>Pulling a Docker image from AWS ECR is what allows you to retrieve a stored image when you need to run it again. This matters because of services like Amazon ECS, Amazon EKS, and other container platforms that need a source to fetch images from, and AWS ECR serves that role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/0*v8wjdDNpBVcv-k2T.png" /><figcaption>Basic workflow to pull a Docker image from AWS ECR</figcaption></figure><p>For private repositories, the process usually starts with authentication. Docker needs permission to access the repository before it can download the image. After that you use the correct Docker image URI and tag to pull the next exact version you need from AWS ECR.</p><p>AWS ECR is not only where images are stored but also where they are retrieved when applications are ready to run. Once the image is pulled, it can be used for development, testing, or deployment.</p><h3>Where AWS ECR Fits in Real Workflows</h3><p>AWS ECR fits between building your app and deploying it. After a developer writes code and pushes changes, a CI/CD pipeline can build a Docker image and store it in AWS ECR. This gives the team one central place to keep container images.</p><p>Then services like Amazon ECS or Amazon EKS can pull that image from ECR and run it. This makes deployments easier and more consistent. Instead of doing everything manually, teams can use a smoother and more automated workflow.</p><h3>What Are the Most Common AWS ECR Mistakes to Avoid?</h3><ul><li>Forgetting to authenticate Docker before pushing images</li><li>Tagging the image with the wrong repository URI</li><li>Confusing public and private repositories</li><li>Using unclear image tags like “latest” for everything</li><li>Ignoring cleanup and repository management</li></ul><p><strong>Quick Tips for Using AWS ECR</strong></p><ul><li>Use lifecycle policies to remove old or unused images.</li><li>Keep Docker images small for faster push and pull times</li><li>Turn on image scanning to catch security issues early.</li></ul><h3>Final Thoughts</h3><p>AWS ECR is a good starting point for beginners who want to learn how Docker images in AWS are stored and managed. It gives you a simple and managed way to store, organize, and retrieve container images without setting up your own registry. That makes it easier to move from local Docker to real container workflows in AWS.</p><p>It also fits well with services like ECS, EKS, and CI/CD pipelines, which makes it useful beyond just image storage. Once you understand the basics of AWS ECR, you can start exploring more advanced features like image scanning, lifecycle policies, access control, and other production-ready practices. That makes it a strong foundation for anyone getting started with containers in AWS.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b971ca27a8f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/awsfullstack/aws-ecr-for-beginners-how-to-store-and-manage-docker-images-in-aws-3b971ca27a8f">AWS ECR for Beginners: How to Store and Manage Docker Images in AWS</a> was originally published in <a href="https://medium.com/awsfullstack">AWS Fullstack</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>