📦 Overview

ECS Action Test provides a reusable GitHub Action that provisions and updates AWS ECS infrastructure using Terraform. Automate your VPC, ECS clusters, task definitions, and more directly from your CI/CD workflows.

🚀 Usage

Create a GitHub workflow in .github/workflows/deploy.yml:

name: Deploy ECS

on:
  workflow_dispatch:

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Run ECS Terraform Action
        uses: quantumci/ecs-action-test@v1
        with:
          base_conf_var: './Base_Infra/config.tfvars'
          platform_conf_var: './Platform_Infra/config.tfvars'
          aws_access_key: ${{ secrets.AWS_ACCESS_KEY_ID }}
          aws_secret_access_key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
          aws_region: 'us-east-1'
          remote_bucket_name: 'my-terraform-state-bucket'
          remote_bucket_region: 'us-east-1'
          action: 'apply'

⚙️ Inputs

• base_conf_var: Path to your base TFVars (e.g. ./Base_Infra/config.tfvars).
• platform_conf_var: Path to your platform TFVars (e.g. ./Platform_Infra/config.tfvars).
• aws_access_key: AWS Access Key ID (set as GitHub secret).
• aws_secret_access_key: AWS Secret Access Key (set as GitHub secret).
• aws_region: AWS region (e.g. us-east-1).
• remote_bucket_name: S3 bucket for Terraform state.
• remote_bucket_region: Region of the S3 bucket.
• action: Terraform action to perform (apply or destroy).

🔧 Steps

1. Define your .tfvars files under Base_Infra and Platform_Infra.
2. Set AWS credentials as repository secrets: AWS_ACCESS_KEY_ID & AWS_SECRET_ACCESS_KEY.
3. Commit your workflow and trigger via “Run workflow” in the Actions tab.
4. The Action will initialize, plan, and apply your Terraform configurations.