Skip to content

Task 2: serve SPA in AWS S3 and CloudFront#196

Open
bubalehich wants to merge 29 commits into
rolling-scopes-school:task-2from
bubalehich:task-2
Open

Task 2: serve SPA in AWS S3 and CloudFront#196
bubalehich wants to merge 29 commits into
rolling-scopes-school:task-2from
bubalehich:task-2

Conversation

@bubalehich
Copy link
Copy Markdown

@bubalehich bubalehich commented Apr 24, 2026

What has been done

  • S3 Bucket created and configured using AWS CDK
  • Application built and deployed to S3 via CDK (npm run deploy)
  • S3 Website URL is working and accessible
  • CDK stack with CloudFront Distribution + OAC + cache invalidation is implemented and ready
  • CloudFront deployment pending — AWS account requires manual verification by service team (support case opened, in progress)

Links

Notes

CloudFront resources are blocked on this account until AWS Support manually enables the service. The CDK stack (cdk/lib/cdk-stack.ts) contains the full implementation with private S3 bucket, CloudFront Distribution with Origin Access Control, and automatic cache invalidation on deploy. Once the account is verified, npm run deploy will provision CloudFront and the S3 URL will return 403 (bucket becomes private, accessible only via CloudFront).
image

Ilya Valasiuk and others added 29 commits March 18, 2021 11:26
added s3 bucket and cloudfront distribution
CloudFront issue with S3 buckets on different regions
…tack

feat: Update application dependencies
- Private S3 bucket with block public access
- CloudFront distribution with OAC, HTTPS redirect, SPA fallback (403/404 -> index.html)
- BucketDeployment with automatic cache invalidation on deploy
- npm scripts: deploy (build + cdk deploy), destroy (cdk destroy)
- Updated README with deployment instructions and link placeholders
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants