docs(security): add SigV4 verification + IAM enforcement reference page#402
Merged
vieiralucas merged 1 commit intomainfrom Apr 15, 2026
Merged
docs(security): add SigV4 verification + IAM enforcement reference page#402vieiralucas merged 1 commit intomainfrom
vieiralucas merged 1 commit intomainfrom
Conversation
Wraps up the opt-in security rollout (batches 1-8) with user-facing documentation and a README bullet. No code changes. - New /docs/reference/security.md: full reference for the two opt-in flags, the reserved test/test root-bypass convention, the SigV4 verification flow, the three IAM modes (off/soft/strict), the Phase 1 evaluator scope (implemented vs explicitly not), the enforced-service list (IAM, STS, SQS, SNS, S3 with ARN shapes), and a practical bootstrap-alice-then-deny example. - limitations.md: replaced the 'SigV4 signatures are not validated' section with a pointer to the new security page, explaining the Phase 1 scope so users don't expect condition blocks. - services/iam.md: updated the 'Gotchas' section to describe the opt-in evaluation path. - README.md: added a 'Why fakecloud' bullet calling out opt-in SigV4 verification + IAM enforcement as a differentiator.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Final batch (9 of 9) for the opt-in SigV4 + IAM enforcement rollout — ships the user-facing documentation. No code changes.
/docs/reference/security.md: full reference for the two opt-in flags, the reservedtest/testroot-bypass convention, the SigV4 verification flow, the three IAM modes (off/soft/strict), the Phase 1 evaluator scope (implemented vs explicitly not), the enforced-service list (IAM, STS, SQS, SNS, S3 with ARN shapes), and a practical bootstrap-alice-then-deny example.limitations.md: replaced the "SigV4 signatures are not validated" section with a pointer to the new security page, explicitly listing Phase 1 scope so users don't expectConditionblocks or resource-based policies.services/iam.md: updated the "Gotchas" section to describe the opt-in evaluation path instead of "policies are stored but not evaluated".README.md: added a "Why fakecloud" bullet calling out opt-in SigV4 verification + IAM enforcement as a differentiator.What shipped across the full rollout
IamMode+is_root_bypass+ startup WARNcredential_secretlookupPrincipalTypeclassifier +AwsRequest.principalplumbingServiceMetadatahooks onAwsService+ dispatch enforcement wiring + soft/strict audit loggingEnforcement surface: IAM, STS, SQS, SNS, S3 — matches the same services LocalStack Pro ships for its paid IAM feature.
Cubic caught 5 real bugs across the rollout (identified by cubic): multi-byte panic on root-bypass prefix check,
PrincipalType::Rootfallback silently bypassing enforcement, pathed IAM user names not resolving,CreateServiceLinkedRolewrong parameter, S3?attributes/?restoremissing method guards, SNSCreateTopicaccount id inconsistency, SNSConfirmSubscriptionwrong ARN field. All fixed on the same PRs they were raised on.Test plan
cargo clippy --workspace --all-targets -- -D warningsclean (docs-only PR, no new code)/docs/reference/securitypage renders with all internal links resolvingSummary by cubic
Adds a new security reference page documenting opt-in SigV4 verification and Phase 1 IAM enforcement, and updates limitations, IAM docs, and README to point to it. No code changes.
docs/reference/security.mdcovering--verify-sigv4,--iam off|soft|strict, reservedtest/testroot-bypass, SigV4 verification flow, Phase 1 IAM scope, enforced services (IAM, STS, SQS, SNS, S3), and a quick-start example.docs/reference/limitations.md: replaces the old SigV4 note with a link to the new page and the Phase 1 scope.docs/services/iam.md: updates “Gotchas” to describe opt-in evaluation and what’s out of scope.README.md: adds a “Why fakecloud” bullet highlighting opt-in SigV4 + IAM (--verify-sigv4,--iam) with a link to the security docs.Written for commit 63002b1. Summary will update on new commits.