Dockerized Continuous Deployment on AWS: Automating Delivery with Bash


In today's fast-paced development environments, automation and rapid delivery are crucial for meeting competitive demands. Combining Docker, AWS, and Bash scripting allows you to create a highly efficient continuous deployment (CD) pipeline that simplifies application delivery. This post explores how to automate deployment workflows using Docker containers and Bash scripts in an AWS environment.

Why Continuous Deployment?

Continuous Deployment (CD) bridges the gap between development and operations by automating software release processes. It ensures that every code change, once committed and tested, is automatically deployed to production, resulting in:

  • Faster time-to-market

  • Reduced human errors

  • Greater consistency across environments

Why Docker for Deployment?

Docker packages your application and its dependencies into a container, making it portable and consistent across development, staging, and production environments. This containerization ensures:

  • Environment consistency

  • Faster startup and rollback

  • Simplified scaling on AWS ECS, EKS, or EC2

Prerequisites

Before building your Dockerized CD pipeline, ensure the following:

  • An AWS account with access to services like EC2, ECS, or EKS

  • A Dockerized application with a Dockerfile

  • AWS CLI configured with IAM permissions

  • Bash is installed on your CI/CD runner or deployment machine

  • (Optional) GitHub Actions, GitLab CI, Jenkins, or any other CI tool

Sample Bash Script for Dockerized Deployment on AWS EC2

Here’s a simplified example of a Bash script to build and deploy your Docker container:


#!/bin/bash


# Variables

APP_NAME="my-app"

AWS_REGION="us-east-1"

IMAGE_TAG="latest"

EC2_INSTANCE="ec2-user@ec2-XX-XX-XX-XX.compute-1.amazonaws.com"

DOCKERFILE_PATH="."


# Step 1: Build Docker Image

docker build -t $APP_NAME:$IMAGE_TAG $DOCKERFILE_PATH


# Step 2: Tag and Push to Amazon ECR (if using ECR)

aws ecr get-login-password --region $AWS_REGION | docker login --username AWS --password-stdin <aws_account_id>.dkr.ecr.$AWS_REGION.amazonaws.com

docker tag $APP_NAME:$IMAGE_TAG <aws_account_id>.dkr.ecr.$AWS_REGION.amazonaws.com/$APP_NAME:$IMAGE_TAG

docker push <aws_account_id>.dkr.ecr.$AWS_REGION.amazonaws.com/$APP_NAME:$IMAGE_TAG


# Step 3: SSH into EC2 and deploy container

ssh -i my-key.pem $EC2_INSTANCE << EOF

  docker pull <aws_account_id>.dkr.ecr.$AWS_REGION.amazonaws.com/$APP_NAME:$IMAGE_TAG

  docker stop $APP_NAME || true

  docker rm $APP_NAME || true

  docker run -d --name $APP_NAME -p 80:80 <aws_account_id>.dkr.ecr.$AWS_REGION.amazonaws.com/$APP_NAME:$IMAGE_TAG

EOF


Automating with Git Hooks or CI Tools

You can trigger this Bash deployment script automatically using:

  • Git hooks (e.g., post-merge)

  • GitHub Actions for pushing on merge

  • Jenkins or GitLab CI will run it on each successful pipeline.

Best Practices

  • Use environment variables instead of hardcoded values.

  • Secure sensitive information with AWS Secrets Manager.

  • Use Docker Compose for multi-container orchestration.

  • Implement health checks and rollback mechanisms.

  • Logging and monitoring are integrated using CloudWatch or the ELK stack.

Benefits of This Approach

  • Lightweight and easy to understand

  • Doesn’t require large CI/CD tools to get started

  • Portable across cloud providers or hybrid deployments

  • Compatible with infrastructure-as-code tools like Terraform

Conclusion

With Docker, AWS, and a little Bash, you can build a robust yet straightforward continuous deployment pipeline. This setup is ideal for startups, hobby projects, and even production systems where simplicity and control are paramount.


Comments

Post a Comment

Popular posts from this blog

HTTP Basic vs API Key Auth: Best Practices for Secure API Development

Image
Picture this: You’ve spent weeks building your API, and now your security approach boils down to a coin flip between HTTP Basic and API Keys. Choose wrong, and your data’s basically wearing a “hack me” sign. Every developer faces this exact decision, yet most guides leave you with more questions than answers. When implementing authentication for your API, the choice between HTTP Basic Authentication and API Key Authentication can significantly impact your security posture and user experience. So what makes one better than the other? When should you use HTTP Basic over API Keys? Is there ever a scenario where the “simpler” option is actually more secure? The answers might surprise you – and they definitely aren’t what most Stack Overflow threads would have you believe. Understanding API Authentication Fundamentals Why API Security Matters in Modern Development API security isn’t just some technical checkbox—it’s the fortress protecting your digital kingdom. With businesses exposing crit...
Read more

ECS Deployment Best Practices: Blue/Green with CodePipeline and CodeDeploy

Image
DevOps engineers and AWS cloud architects looking to improve their container deployment processes will benefit from implementing blue/green deployments with Amazon ECS. This guide walks through setting up reliable, zero-downtime deployments using AWS CodePipeline and CodeDeploy for your containerized applications. We’ll cover how to configure your ECS environment properly, create automated deployment pipelines, and implement blue/green deployment strategies that minimize risk during updates. Understanding ECS Deployment Strategies What is Amazon ECS and why it matters Amazon Elastic Container Service (ECS) isn’t just another tool in AWS’s massive catalog—it’s the backbone of modern containerized applications. At its core, ECS is a fully managed container orchestration service that handles all the complex tasks of running, stopping, and managing Docker containers. Think of ECS as the conductor of an orchestra where each container is an instrument. Without proper coordination, you’d just...
Read more

AWS Console Not Loading? Here’s How to Fix It Fast

Image
When the AWS Management Console refuses to load, it can be incredibly frustrating, especially when trying to deploy, debug, or manage production infrastructure. Fortunately, quick and effective fixes get you back on track. This guide outlines common causes and step-by-step solutions to resolve the issue quickly. 1. Check AWS Service Status Start by verifying if AWS itself is experiencing issues: Visit the AWS Health Dashboard to check for regional outages. Look for service-specific issues affecting IAM , EC2 , S3 , or the Console itself . Tip: Subscribe to AWS status updates on Twitter for real-time alerts. 2. Clear Browser Cache and Cookies Corrupted cache or cookies often prevent pages from rendering correctly. Steps: Open browser settings. Clear cache , cookies , and site data for aws.amazon.com . Reload the page. Try logging in using Incognito/Private Mode to rule out browser extensions interfering. 3. Try a Different Browser or Device Sometimes, browser-specific quirks b...
Read more

YouTube Channel