Skip to content
View chrispsheehan's full-sized avatar

Highlights

  • Pro

Block or report chrispsheehan

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don't include any personal information such as legal names or email addresses. Markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
chrispsheehan/README.md

Hi, I'm Chris 👋

Senior Platform Engineer


🌱 About Me

  • 🔧 Currently building scalable apps with AWS, Terraform, and Terragrunt
  • 🧪 Passionate about automation, CI/CD, and clean architecture
  • 📝 More at chrispsheehan.com

🚀 Tech Stack

💡 Category 🔧 Tools & Technologies
🧠 Languages TypeScript · Python · Bash
⚙️ DevOps Terraform · Docker · GitHub Actions
☁️ Cloud AWS (ECS · Lambda · API Gateway · S3 · CloudFront)

Pinned Loading

  1. aws-serverless-github-deploy aws-serverless-github-deploy Public

    Terraform + GitHub Actions for AWS serverless: Lambda + API Gateway with CodeDeploy blue/green (all-at-once/canary/linear) and provisioned concurrency (none/fixed/autoscaled), shipped via OIDC + Ju…

    HCL 1

  2. fargate-nextjs-webapp fargate-nextjs-webapp Public

    Run nextjs in AWS with Fargage, ECS and App load balancer.

    HCL 6

  3. lambda-ssr-react-app lambda-ssr-react-app Public

    A ReactJS SSR application deployed on AWS Lambda, hosted on AWS infrastructure and managed using Terraform.

    HCL 2

  4. performance-test-framework performance-test-framework Public

    Run performance tests against an API using k6.

    TypeScript 12 3

  5. fargate-auto-scaled-backend fargate-auto-scaled-backend Public

    ECS Auto-Scaling backend using a blue/green deployment strategy, within a private VPC

    HCL 2

  6. ecs-internal-service ecs-internal-service Public

    Terraform-defined AWS stack with configurable ECS services: public/internal DNS APIs or headless SQS workers, all wired via VPC, IAM roles, security groups, and OpenTelemetry tracing.

    HCL