From 55ec7e33fe8111cfb20c5bcfb3b0b1e05892d295 Mon Sep 17 00:00:00 2001 From: Josh Knapp Date: Sun, 15 Nov 2026 11:59:31 -0800 Subject: [PATCH] docs(aws): fix policy sizes and a constant name Co-Authored-By: Claude Sonnet 5.5 --- aws/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/aws/README.md b/aws/README.md index 8abf8b1..f32b6ba 100644 --- a/aws/README.md +++ b/aws/README.md @@ -384,9 +384,9 @@ module creates the same policy, applied by an account administrator; the admin t Create each file as a **customer managed policy** and attach it. In the console, go to **IAM → Policies → Create policy → JSON**, paste the file, and attach the policy to a user, group or role. Inline policies do not fit: a role's inline policies share 10,240 characters and an -environment admin needs every tier file (about 16,600), and a user's share 2,048. A managed policy +environment admin needs every tier file (about 16,400), and a user's share 2,048. A managed policy may hold 6,144 characters, not counting whitespace. Without whitespace, `workspace-user.json` is -about 6,040 (roughly 100 characters of headroom), `workspace-user-tasks.json` about 1,460, +about 6,040 (roughly 100 characters of headroom), `workspace-user-tasks.json` about 1,200, `environment-admin.json` about 5,800 (340) and `environment-admin-network.json` about 3,340; a unit test (`every_policy_fits_a_managed_policy`) fails before any file outgrows the limit. A tier that outgrows its files gains another file, which