dropthejase slams the doors on the cloud setup

Two fixes close the open-by-default holes in this fork's cloud infrastructure, so document access is locked to the app itself.

securityinfrastructure

When dropthejase first stood up the cloud plumbing for this fork, a few things were left wide open by default - the kind of placeholder settings that work in a demo but shouldn't survive to production. This pair of changes tightens them. Document storage now only answers requests coming from the fork's own web address, rather than from anywhere on the internet, and the same lock is applied to the main back-end gateway.

The second fix matters most for anyone thinking about confidentiality: when a user signs out, their access to stored documents is now revoked promptly, instead of lingering until a cached session quietly expired. Sign-out finally means sign-out.

So what Anyone evaluating this fork for handling sensitive client files should note it's moved from demo-grade defaults to access controls that hold up.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from dropthejase/louis, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date

685c7ad5 security: lock CORS to CloudFront domain, enable Identity Pool token check Jason Lee 2026-05-08 ↗ GitHub

SHA	Subject	Author	Date
`685c7ad5`	security: lock CORS to CloudFront domain, enable Identity Pool token check	Jason Lee	2026-05-08	↗ GitHub
commit body - serverSideTokenCheck: true on Identity Pool - revoked tokens can no longer exchange for IAM credentials until expiry - docsBucket CORS allowedOrigins locked to CF distribution domain via Fn::GetAtt (no longer '*'); resolved at deploy time by CloudFormation - ApiStack FRONTEND_URL wired to CF domain token for API Gateway CORS - Removed dev-only RemovalPolicy.DESTROY / autoDeleteObjects from docsBucket; enterprise POC always retains data
`54937c3a`	fix: lock API Gateway CORS allowOrigins to CloudFront domain	Jason Lee	2026-05-09	↗ GitHub

commit body

- serverSideTokenCheck: true on Identity Pool - revoked tokens can no
  longer exchange for IAM credentials until expiry
- docsBucket CORS allowedOrigins locked to CF distribution domain via
  Fn::GetAtt (no longer '*'); resolved at deploy time by CloudFormation
- ApiStack FRONTEND_URL wired to CF domain token for API Gateway CORS
- Removed dev-only RemovalPolicy.DESTROY / autoDeleteObjects from
  docsBucket; enterprise POC always retains data

54937c3a fix: lock API Gateway CORS allowOrigins to CloudFront domain Jason Lee 2026-05-09 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-350.md from inside the repo you want the changes in.

⬇ Download capture-thread-350.md