Cloud Automation with Bash & CLI Tools Guide

In this tutorial, you'll learn about Cloud Automation with Bash & CLI Tools Guide. We cover key concepts, practical examples, and best practices to help you understand and apply this topic effectively.

Cloud automation with Bash and CLI tools lets you manage cloud infrastructure programmatically — provisioning resources, deploying applications, and handling routine tasks without manual clicks.

What You'll Learn

You'll learn how to write Bash scripts that automate cloud resource creation, use CLI tools for AWS, Azure, and GCP, and build reusable automation pipelines that save time and reduce human error.

Why It Matters

Manual cloud management does not scale. A single misclick in the console can expose data or run up costs. Automation ensures consistency, repeatability, and speed. DodaZIP uses automated Bash pipelines to provision build servers across AWS, Azure, and GCP simultaneously.

Real-World Use

A DevOps team manages 200 EC2 instances across three regions. Instead of logging into each server, they run a single Bash script that patches all instances, rotates credentials, and sends a summary report — all in under two minutes.

Automation Architecture

flowchart LR
  A[Bash Script] --> B[CLI Tool]
  B --> C[AWS CLI]
  B --> D[Azure CLI]
  B --> E[gcloud CLI]
  C --> F["EC2 / S3 / Lambda"]
  D --> G["VMs / Blob / Functions"]
  E --> H["Compute / Storage / Cloud Run"]
  style A fill:#48f,color:#fff
  style B fill:#f90,color:#fff

AWS Automation with CLI

The AWS CLI is the foundation for automating AWS infrastructure.

# Launch an EC2 instance with tags
INSTANCE_ID=$(aws ec2 run-instances \
  --image-id ami-0abcdef1234567890 \
  --instance-type t3.micro \
  --key-name my-key \
  --query "Instances[0].InstanceId" \
  --output text)

aws ec2 create-tags \
  --resources $INSTANCE_ID \
  --tags Key=Name,Value=automated-server Key=Environment,Production

echo "Launched instance $INSTANCE_ID"

Expected output:

Launched instance i-0abc123def456

Azure Automation with CLI

Azure CLI scripts integrate with Azure Resource Manager for full infrastructure control.

# Create a resource group and deploy a VM
RG="automation-rg"
LOCATION="eastus"

az group create --name $RG --location $LOCATION

az vm create \
  --resource-group $RG \
  --name auto-vm \
  --image UbuntuLTS \
  --admin-username azureuser \
  --generate-ssh-keys \
  --output json

echo "VM created in resource group $RG"

Expected output:

VM created in resource group automation-rg

GCP Automation with gcloud

GCP's gcloud CLI provides similar scripting capabilities for Google Cloud resources.

# Create a Compute Engine instance with gcloud
INSTANCE_NAME="auto-instance"
ZONE="us-central1-a"

gcloud compute instances create $INSTANCE_NAME \
  --zone=$ZONE \
  --machine-type=e2-micro \
  --image-family=ubuntu-2404-lts \
  --image-project=ubuntu-os-cloud \
  --tags=http-server,https-server

gcloud compute instances list \
  --filter="name=$INSTANCE_NAME" \
  --format="value(name,status,networkInterfaces[0].accessConfigs[0].natIP)"

Expected output:

auto-instance  RUNNING  34.123.45.67

Error Handling in Automation Scripts

Production scripts must handle failures gracefully.

#!/bin/bash
set -euo pipefail

deploy_app() {
  local ENV=$1
  echo "Deploying to $ENV environment..."

  if ! aws s3 sync ./dist/ "s3://myapp-$ENV-bucket/"; then
    echo "ERROR: S3 sync failed for $ENV"
    exit 1
  fi

  echo "Deployment to $ENV completed successfully"
}

deploy_app "staging"
deploy_app "production"

Common Automation Mistakes

1. Hardcoding credentials in scripts — Use environment variables or secret managers instead. Never commit secrets to version control.
2. Not testing scripts in isolation — A script that works on your laptop may fail in CI. Test with set -x for debug output.
3. Ignoring exit codes — Always check command exit codes. Use set -e to Fail Fast and prevent cascading errors.
4. Missing idempotency — Scripts should be safe to run multiple times. Check if a resource exists before creating it.
5. No logging or notifications — When automation runs at 3 AM, you need logs. Pipe output to CloudWatch, Azure Monitor, or a simple log file.

Practice Questions

1. What does set -euo pipefail do in a Bash script? It exits on any error (-e), treats unset variables as errors (-u), and catches pipeline failures (-o pipefail).
2. How do you make an AWS CLI script idempotent? Check if the resource exists before creating it with describe-* commands, and only create if absent.
3. What is the difference between aws and aws-shell? AWS CLI is command-line, while aws-shell provides an interactive shell with auto-completion.
4. How do you pass environment variables to a cloud CLI script? Use export VAR=value before running, or use --parameter flags. Never hardcode.
5. Challenge: Write a Bash script that creates a weekly snapshot of all EBS volumes tagged Backup=true and deletes snapshots older than 30 days.

Mini Project

Build an automated inventory script that:

• Lists all EC2 instances, Azure VMs, and GCP Compute instances
• Outputs their name, status, and public IP in a unified CSV
• Emails the report using SES or SendGrid API
• Runs via a cron job every Monday at 9 AM

This is the same approach DodaTech uses to track infrastructure across cloud providers for Durga Antivirus Pro's update servers.

FAQ

Built by the developers of Doda Browser, DodaZIP, and Durga Antivirus Pro.