Updates AWS managed policies

[udondan]

Updates AWS managed policies

Summary by CodeRabbit

• New Features
  • Enhanced access policies to support additional S3 Express capabilities, including retrieving access point details and managing associated policies.
  • Introduced refined access controls for S3 actions by enforcing account alignment checks, improving overall security and consistency.

[coderabbitai]

Walkthrough

This pull request updates two managed policy JSON documents. In the first file, three new S3 Express permissions are appended to the "Action" array of the Access Analyzer service role policy. In the second file, a new "Condition" block is added to the S3 actions in the Amazon Braket full access policy, ensuring that the "aws:ResourceAccount" matches the "${aws:PrincipalAccount}" value. Both changes adjust access control without removing any existing permissions.

Changes

File(s)	Change Summary
docs/source/_static/managed-policies/AccessAnalyzerServiceRolePolicy.json	Added three new permissions ("s3express:GetAccessPoint", "s3express:GetAccessPointPolicy", "s3express:ListAccessPointsForDirectoryBuckets") to the "Action" array.
docs/source/_static/managed-policies/AmazonBraketFullAccess.json	Introduced a new "Condition" block for S3 actions that checks if the "aws:ResourceAccount" equals the "${aws:PrincipalAccount}".

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant PolicyEvaluator
    participant S3Service

    Client->>PolicyEvaluator: Request S3 Action
    PolicyEvaluator->>PolicyEvaluator: Evaluate Condition (aws:ResourceAccount match)
    alt Condition Met
        PolicyEvaluator->>S3Service: Forward S3 Action Request
        S3Service-->>Client: Action Executed
    else Condition Not Met
        PolicyEvaluator-->>Client: Deny Request
    end

Loading

Possibly related PRs

• Updates AWS managed policies #730: Related modifications in the "AccessAnalyzerServiceRolePolicy.json" file, adding IAM actions with a different focus on permissions.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 613909b and 04f19a2.

📒 Files selected for processing (2)

• docs/source/_static/managed-policies/AccessAnalyzerServiceRolePolicy.json (1 hunks)
• docs/source/_static/managed-policies/AmazonBraketFullAccess.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Test cdk-iam-floyd
• GitHub Check: Automerge CI

🔇 Additional comments (2)

docs/source/_static/managed-policies/AmazonBraketFullAccess.json (1)

14-19: New Condition Block Added Correctly
The new "Condition" block that checks "aws:ResourceAccount": "${aws:PrincipalAccount}" has been correctly appended to the statement. This addition refines the access control for the specified S3 actions by enforcing that the resource account matches the principal account. Please verify that this extra constraint aligns with your intended security posture across your Braket access policies.

docs/source/_static/managed-policies/AccessAnalyzerServiceRolePolicy.json (1)

90-94: Appending New S3 Express Permissions
The addition of the three new permissions—"s3express:GetAccessPoint", "s3express:GetAccessPointPolicy", and "s3express:ListAccessPointsForDirectoryBuckets"—is correctly integrated into the "Action" array. These new permissions complement the existing S3 Express-related actions without disrupting the current permissions. Please double-check that these permissions reflect your desired access control model and that any documentation or downstream processes referencing this policy are updated accordingly.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.