AWS Delivery

PROJECT 001 / AWS INFRASTRUCTURE · CI/CD

From a commit to the cloud.

A production AWS platform with automated infrastructure and multi-environment delivery across Dev, Demo, and Production.

The context

The work brought infrastructure and application delivery together: compute, container images, PostgreSQL, authentication, networking, and visibility into the running system.

My contribution

  • Built AWS infrastructure using ECS, ECR, RDS/PostgreSQL, IAM, VPC, and CloudWatch.
  • Created GitHub Actions checks for formatting, linting, type checks, builds, and tests against a PostgreSQL service container.
  • Published Docker images to ECR with commit SHA tags and automated branch-based deployments with concurrency controls and notifications.
  • Integrated Cognito and Lambda authentication triggers, with container builds targeting linux/amd64 for Lambda.

The workflow

CommitCI checksDocker / ECRECS
workflow.yml · representative excerpt
# Illustrative excerpt, not the complete project workflow
name: Application checks
on: [push, pull_request]

concurrency:
  group: checks-${{ github.ref }}
  cancel-in-progress: true

# After checkout and dependency setup:
# - run: pnpm lint
# - run: pnpm test
# - run: docker build -t app:${{ github.sha }} .

Client repositories and infrastructure details remain private. This excerpt explains the approach; it is not a complete deployable workflow.

Alvin K Sabu ›AWS DeliveryMade to be explored.

alvin — bash — 80 × 24

Welcome to Alvin’s desktop.

Type help to explore. This is a browser simulation.

esc to close

Search this desktop

↑ ↓ to navigate ↵ to openesc to close

A little desktop tour

Click an app in the dock or a folder in the sidebar. The window controls work, too.

Search everything
Ctrl / ⌘ K
Open terminal
`
Overview / Projects / About / Toolbox / Contact
1 — 5
Close a dialog or menu
Esc

Pipeline Lab and Terminal are local demos. They never connect to production infrastructure.