A developer's second post on the Cloud Resume Challenge details practical infrastructure lessons. They use Cypress for smoke tests, managing binary caching in GitHub Actions. Staging and production environments are handled via Git workflows, with releases tagged for promotion. Cross-account access uses HCP Terraform with OIDC, assuming roles for DNS modifications in a separate admin account.

Key gotchas emerge from serverless and database choices. Lambda functions require structured JSON logging for better observability and unit tests for business logic. DynamoDB operations benefit from using the `ADD` command for atomic updates. The post recommends auto-generated table names to ease resource replacement and restoring from backups instead of reinitializing data.

The most complex issue involves GitHub OIDC for multiple environments. To allow a single repository to assume roles across different AWS accounts, the `sub` claim must be configured with a wildcard. This setup uses a pattern like `repo:<org>/<repo>:*`, relaxing the typical single-repository restriction. This approach streamlines secure CI/CD pipelines for complex deployments.