No description
Find a file
Daisuke 8cd30da394 fix: resolve Lambda invocation failure from API Gateway
- Align Dockerfile with AWS official documentation for provided runtime
- Remove DefinitionBody from SAM template to avoid conflict with Events property
- This enables SAM to automatically generate AWS::Lambda::Permission resource
- Fixes 500 error when Forgejo webhook triggers API Gateway endpoint"
2026-01-12 21:25:06 +09:00
.github/skills/commit-message-generator chore: add CI/CD tooling and project configuration 2026-01-04 12:47:40 +09:00
ci feat: simplify blog lambda deployment pipeline 2026-01-11 17:03:10 +09:00
cmd/lambda refactor: improve Lambda handler and update Go to 1.25.5 2026-01-04 10:02:12 +09:00
docker fix: resolve Lambda invocation failure from API Gateway 2026-01-12 21:25:06 +09:00
infra/cfn fix: resolve Lambda invocation failure from API Gateway 2026-01-12 21:25:06 +09:00
scripts chore: add CI/CD tooling and project configuration 2026-01-04 12:47:40 +09:00
test
.gitignore chore: add CI/CD tooling and project configuration 2026-01-04 12:47:40 +09:00
go.mod
go.sum
README.md

n-daisuke-blog-deployment-source

Infrastructure as Code (IaC) for automating static blog deployment using AWS services.

This repository defines the infrastructure required to update and publish blog articles via AWS CodePipeline and Lambda (written in Go). It includes CloudFormation templates for provisioning all necessary components, such as:

  • S3: Source bucket for blog content
  • CloudFront: CDN for blog delivery
  • CodePipeline: CI/CD pipeline triggered by source updates
  • Lambda (Go): Custom deployment logic executed within the pipeline
  • ECR: Container repository for Lambda packaging
  • Secrets Manager: Secure storage for deployment keys

All infrastructure is declaratively managed via CloudFormation templates under infra/cfn/.

The Lambda source code and related tests are located in:

  • cmd/lambda/ Lambda entrypoint (Go)
  • test/ Unit tests for Lambda logic