Updates AWS managed policies

[udondan]

Updates AWS managed policies

Summary by CodeRabbit

• Documentation
  • Updated ReadOnlyAccess.json policy with simplified service permissions
  • Replaced specific list actions with wildcard List* actions for chatbot, notifications, and wellarchitected services
  • Consolidated multiple granular list permissions into broader access permissions

[coderabbitai]

Walkthrough

The pull request modifies the ReadOnlyAccess.json managed policy document located in the documentation directory. The changes involve simplifying the permission structure for three AWS services: chatbot, notifications, and wellarchitected. Instead of listing multiple specific list-related actions for each service, the policy now uses wildcard List* actions, which provide a more generalized read-only access approach for these services.

Changes

File	Change Summary
docs/source/_static/managed-policies/ReadOnlyAccess.json	Replaced specific list actions with wildcard List* for chatbot, notifications, and wellarchitected services

Possibly related PRs

• Updates AWS managed policies #1053: Modifies the ReadOnlyAccess.json policy by adding new permissions
• Updates AWS managed policies #1095: Updates the ReadOnlyAccess.json policy with additional 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 d97576e and e688ccd.

📒 Files selected for processing (1)

• docs/source/_static/managed-policies/ReadOnlyAccess.json (3 hunks)

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

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

🔇 Additional comments (3)

docs/source/_static/managed-policies/ReadOnlyAccess.json (3)

359-359: Assess wildcard usage for Chatbot permissions.

Replacing specific allowable actions with a wildcard (chatbot:List*) simplifies maintenance but may grant additional list privileges if new actions are introduced. Consider verifying that no undesired privileges are inadvertently included.

You can run the following script to check for any references aligning with “chatbot:List” in other files:

✅ Verification successful

Wildcard usage for Chatbot List operations is appropriate

The chatbot:List* permission in ReadOnlyAccess.json safely covers all available Chatbot list operations (Associations, CustomActions, MicrosoftTeams configurations, and Tags), which are all read-only in nature. This aligns with the policy's intent, and future List operations would naturally fall within the same read-only scope.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Searches the codebase for chatbot:List references. 
rg '"chatbot:List'

Length of output: 1059

---

Script:

#!/bin/bash
# Fetch AWS Chatbot API actions documentation
curl -s "https://awscli.amazonaws.com/v2/documentation/api/latest/reference/chatbot/index.html" | grep -o 'href="[^"]*list[^"]*' || echo "Failed to fetch documentation"

# Alternative: Check if there's a policy simulator json or similar file in the repo
fd -t f -e json . | xargs grep -l "chatbot.*Action"

Length of output: 428

---

1788-1788: Evaluate potential overreach for Notifications wildcard.

Using notifications:List* instead of enumerating each list action may ease policy updates but could become overbroad if AWS adds new list-based APIs. Confirm this is intentional and continues to align with a read-only posture.

You can run the following script to see if any usage or comments reference “notifications:List*”:

✅ Verification successful

Wildcard usage for notifications:List is appropriate and consistent with read-only access pattern*

The List* wildcard follows AWS's consistent service API design where List operations are strictly read-only. This pattern is used across 127 AWS services in this policy and aligns with the intended read-only posture.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Searches the codebase for notifications:List references.
rg '"notifications:List'

Length of output: 114

---

Script:

#!/bin/bash
# Check for List* patterns and surrounding context in the policy
rg -B 2 -A 2 '".*:List\*"' docs/source/_static/managed-policies/ReadOnlyAccess.json

# Count total List* occurrences to understand the pattern
rg -c '".*:List\*"' docs/source/_static/managed-policies/ReadOnlyAccess.json

Length of output: 17484

---

2406-2406: Verify wildcard action for WellArchitected.

Replacing granular list actions with wellarchitected:List* might unintentionally expand read-only permissions if new list APIs appear. Ensure this aligns with your least-privilege objectives.

Run this script to locate any references to “wellarchitected:List” and confirm no unexpected usage:

✅ Verification successful

Wildcard usage aligns with AWS read-only policy patterns

The wellarchitected:List* wildcard is appropriately used in both policies:

• WellArchitectedConsoleReadOnlyAccess bundles it with other read-only actions (Get*, ExportLens)
• ReadOnlyAccess includes it alongside granular Get* permissions
• Both maintain strict read-only scope without write permissions

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Searches the codebase for wellarchitected:List references.
rg '"wellarchitected:List'

Length of output: 230

---

Script:

#!/bin/bash
# Check if these are AWS managed policies and look for documentation/metadata
rg -A 5 '"IsAWSManagedPolicy"' docs/source/_static/managed-policies/

Length of output: 70

---

Script:

#!/bin/bash
# Examine the wellarchitected-related sections of both policies
rg -A 5 -B 5 '"wellarchitected:List' docs/source/_static/managed-policies/

Length of output: 2194

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.