Role boundaries & destructive capabilities
Separate backup writing from deletion
Lesson 7 of 20 · 12 min · Module 3: Protect boundaries and reuse intent
Writing a recovery copy and deleting recovery copies should be separately reviewed capabilities.
Start this lesson →Free. No installation: you write and run the code in your browser, and it is checked automatically.
By the end, you’ll be able to…
- Define the writer role narrowly
- Constrain the relevant prefix
The idea
An access policy connects an effect, a permitted action, and a resource boundary. Review those parts together instead of treating any single word as proof of safe access.
01Define the writer role narrowly
The job creates daily backup objects. It does not need to erase older copies or modify account-wide settings merely to upload one object.
02Constrain the relevant prefix
The daily/ prefix narrows the object boundary. A real deployment should also consider encryption, retention, and ownership requirements.
03Review independent recovery controls
A backup writer that can delete every copy creates a dangerous shared failure boundary. Separate retention and deletion responsibilities where appropriate.
Your turn
What the checks look for
- Allows only object writes
- Scopes writes to the daily prefix
Take this with you
Design recovery access around independent responsibilities.
Go a little further
Describe a retention policy and who should be allowed to change it.