The Reading Room · Technology · Architecture Notes
Your cache is fast. Is it allowed to answer?
Two customers. Same invoice number. One cache key.
Both users are signed in. That still doesn’t give them permission to read each other’s invoices.
Before returning protected content, establish trusted tenant context, check resource permission, and reuse only an appropriately partitioned cache entry. Test both the hit and miss paths. A tenant-specific key still doesn’t grant every user access to every invoice.
For CloudFront signed URLs, the application establishes entitlement and issues the URL. CloudFront validates its signature and policy before serving the protected response. AWS explains the workflow here:
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-signed-urls.html
Try this architecture review question: what happens when a user’s permission changes while an object remains cached?
We’re Disperity, publisher of AWS Architecture Decisions by Ethan H. Arlen. Volume I explores architecture, data, AI and security through worked scenarios and original practice questions.
Explore Volume I and its retailer sample:
https://www.amazon.com/dp/B0HQ6H5RLZ
India Kindle:
https://www.amazon.in/dp/B0HQPHX16S
Independent educational material. No AWS endorsement or guaranteed exam result.