Summary
- Original article title, translated: "[SoftBank Hackathon 2025] - A DevOps Pipeline Built with AWS Serverless." Square brackets were removed from the filename because they break wikilinks, and the title was joined with a colon; the original title remains in an alias. Published 2025-11-14 · slug
softbank-hackathon-2025-cicd-pipeline · category "Projects, hackathons, and competitions / Infrastructure hackathons" · source article recorded in Korean and English. - A retrospective on "Chiikawa, Deploying Again Today," built at SoftBank Hackathon 2025 on November 9 with team Watermelon. The project was an "Emotional DevOps" system: a zero-downtime Blue/Green deployment pipeline using AWS ECS Fargate and Lambda, controlled through a Slack bot. My role was Serverless & Cloud Infrastructure: controlling deployment logic with Lambda, integrating API Gateway, and configuring IAM security.
- Four workflow stages: Trigger (a Slack command or Git push) → CI (GitHub Actions builds a Docker image and pushes it to GHCR) → CD (AWS CodeDeploy and ECS Blue/Green deployment) → Interaction (Lambda detects deployment-stage hooks and relays updates to Slack).
- ChatOps details: an ECS Blue/Green deployment from one Slack command, built within 48 hours. Slash Command → API Gateway → first Lambda invocation, responding within three seconds → asynchronous self-invocation →
repository_dispatch → GitHub Actions → ECS → CodeDeploy → Lambda hooks → DynamoDB (DeploymentStatus) and Slack. The asynchronous pattern eliminated Slack's operation_timeout. Later sections cover the GitHub Actions workflow, DynamoDB and CodeDeploy hooks, permissions, observability, troubleshooting, and Blue/Green implementation. - Lessons: regretting that the infrastructure was not managed as code (IaC), and adding a playful touch to DevOps.
Mentioned
- SoftBank Hackathon 2025: the hackathon project discussed in the article.
- SoftBank: the hackathon organizer.
Connections
- Writing · Projects
- Atomic notes: Explain a project through Dockerization, CI, and CD; interviewers want to know how it runs · Handle Slack's three-second limit with asynchronous self-invocation: the first Lambda responds, then invokes itself asynchronously · Console-created infrastructure is hard to reproduce; postponing IaC during the hackathon remained a regret
- Concepts: AWS ECS Fargate · AWS Lambda · CI/CD · Docker · GitHub Actions · IaC (Terraform) · OAuth and JWT authentication · Prometheus and Grafana · Slack bots · i18n and multilingual support · Running a technical blog · Intent classification · Blue/Green deployment · Cloud and CI
Local graph
Notes 2 · Links 1