Add CloudFront invalidation to CodePipeline build stage

[Copilot]

The buildspec.yml had no post-deployment step, leaving CloudFront serving stale assets after each pipeline run.

Changes

• buildspec.yml — new post_build phase with three guarded steps:
  • aws s3 sync dist/ s3://$S3_BUCKET --delete — syncs built assets, removes stale files
  • aws cloudfront create-invalidation on $DISTRIBUTION_ID — primary distribution invalidation
  • Loop over space-separated $EXTRA_DISTRIBUTION_IDS — handles multiple distributions (aligns with the DEV_DIST_ID/IO_DIST_ID pattern already in package.json)

All steps are no-ops when their env var is unset — PR/local builds are unaffected.

Required CodeBuild configuration

Env var	Value
S3_BUCKET	S3 origin bucket name
DISTRIBUTION_ID	Primary CloudFront distribution ID
EXTRA_DISTRIBUTION_IDS	(optional) Space-separated additional distribution IDs

The CodeBuild IAM role also needs s3:PutObject/s3:DeleteObject/s3:ListBucket on the bucket and cloudfront:CreateInvalidation on the distributions.

Original prompt

Review the buildspec.yml. This is deployed via an AWS code pipeline. Is it possible to invalidate the cloudfront distributions upon deployment in the pipeline

Created from VS Code.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.