CIEM-685: add bedrock service to AWS IAM actions database#35
Merged
Conversation
![orca-security-eu[bot]](https://avatars.githubusercontent.com/in/276244?s=60&v=4){kind=small}
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
 Passed |
Secrets |  0  0  0  0 |
View in Orca |
| Passed |
Vulnerabilities | 0 0 0 0 |
View in Orca |
The bundled database had no `bedrock` service, so denies (SCP / permission boundary) on bedrock actions were silently dropped during policy expansion and never applied. This adds the `bedrock` service (255 actions) to the existing database; no other service is added, removed, or changed. - services: 363 -> 364 (only `bedrock` added; all other services byte-identical) - bump version 1.1.6 -> 1.1.7 Scoped intentionally to bedrock for CIEM-685; a full database refresh is tracked separately.
yanas-orca
force-pushed
the
CIEM-685/update-aws-iam-actions-db
branch
from
4f58840 to
c06f5ac
Compare
yanas-orca
changed the title
|
Tohar-orca
approved these changes
Jul 5, 2026
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
2 participants
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.
What
Adds the
bedrockservice (255 actions) to the bundled AWS IAM actions database. No other service is added, removed, or changed — every other service is byte-identical to before.bedrockadded)Why
The bundled database had no
bedrockservice at all. Actions absent from the database are silently dropped during policy expansion (expand_policy.py), so aDeny(SCP / permission boundary) on bedrock actions — e.g.bedrock:CreateGuardrail/UpdateGuardrail/DeleteGuardrail— was never applied, and the effective policy resolved as if the deny didn't exist. Adding the bedrock service makes those denies take effect.Scope
Intentionally scoped to bedrock for CIEM-685, to keep the change minimal and its blast radius confined to bedrock. A full database refresh (the DB had been frozen since 2023) is tracked separately (CIEM-691, dynamic-updates automation) so the ~3-year jump across all services can be staged there rather than landing in one shot.
Testing
pytest: 38 passed), including thetest_e2egolden effective-policy test.bedrockadded; all other 363 services unchanged.