Observed Signal · Sep 8, 2026 · Technical Release · Source: DEV Community · Impact: 1/5 · Sentiment: Neutral
AWS Serverless Resume Site: Lessons Learned
A DevOps engineer shares their experience building a serverless resume site on AWS, detailing the architecture and several challenges encountered. The project uses S3, CloudFront, Lambda, DynamoDB, API Gateway, Terraform, and GitHub Actions. Key issues included a failed domain registration due to a fraud alert, an SSL certificate expiring while waiting, Terraform and console configuration mismatches, a corrupted code file from a text editor, local Python environment issues, and a rejected GitHub push due to missing workflow scope. The article provides practical lessons on troubleshooting, verifying errors, and securing CI/CD pipelines with least-privilege IAM roles.
Personal project with no industry impact.
Track Amazon Web Services (AWS) Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- The site is built using S3, CloudFront, Lambda, DynamoDB, API Gateway, Terraform, and GitHub Actions.
- The domain registration failed due to an AWS fraud alert triggered by an account upgrade.
- An ACM certificate request failed because DNS validation required a hosted zone that didn't exist yet.
- Terraform and console configurations had discrepancies, including IAM role paths and Lambda runtime compatibility.
- A dedicated least-privilege IAM user was created for GitHub Actions to limit permissions.
Connected Companies & Entities
1 Entity mapped“The article discusses using various AWS services like S3, CloudFront, Lambda, DynamoDB, API Gateway, and Route 53....”
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Building a Production Company Website on AWS
Josh Blair published a technical guide showing how to wire GitHub, AWS CodePipeline and CodeBuild to implement automated CI/CD for a static React + Vite site deployed to Amazon S3 and delivered via CloudFront. The pipeline is defined in a CloudFormation stack (infra/stacks/pipeline.yml) and uses an AWS CodeStar Connection (GitHub App) for source, an S3 artifact bucket, a CodeBuild project that runs a buildspec.yml (npm ci, npm run build, aws s3 sync --delete, CloudFront invalidation), and narrowly scoped IAM roles for CodePipeline and CodeBuild. The article documents a required manual approval step to authorize the GitHub App in the AWS Console, explains DetectChanges:true for automatic triggers on git push, and reports an end-to-end deployment timeline of roughly 90 seconds. This post appears to be part of the author’s broader DEV.to series about building a production site on AWS and supplements that series with detailed pipeline configuration and troubleshooting guidance.
Production-grade 3-tier AWS architecture with Terraform
A Dev.to author publishes a detailed walkthrough and full GitHub repo (vatul16/terratier) that provisions a production-minded, modular Terraform stack for a small Go/Node.js app on AWS. The design uses a four-tier VPC (public, frontend private, backend private, database isolated) across two Availability Zones, two ALBs (public and internal), RDS Postgres, Secrets Manager for credentials, and SSM alongside a bastion host. The post explains trade-offs: an internal ALB for stable backend scaling, Secrets Manager usage vs. environment variables, a single-NAT cost/availability option, robust user-data with retry loops, layered health checks, and observability endpoints. The author lists next steps (CI/CD, move to ECR, remote Terraform state) and includes the full Terraform source, module docs, and an architecture diagram on GitHub.
Modern DevOps Guide to Architecting on AWS
This technical guide outlines modern DevOps practices for architecting reliable, scalable systems on AWS. It argues the DevOps role has shifted from console-driven sysadmin work to platform engineering—building automated, self-service internal developer platforms. Key recommendations include treating infrastructure as code using tools like Terraform, Pulumi, and the AWS CDK; adopting a multi-account strategy with AWS Organizations and Control Tower for isolation, security, and cost attribution; embedding security via automation (e.g., OIDC for CI/CD, continuous posture checks with Security Hub and GuardDuty); making cloud cost optimization an engineering metric (Graviton, VPC Endpoints, tagging); and improving observability with tracing tools such as AWS X-Ray or OpenTelemetry. The piece emphasizes developer experience via “golden paths” and self-service modules to maintain velocity while ensuring secure, compliant deployments.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.