docs: document the minimal IAM policy for the executor#48
Conversation
|
Warning Review limit reached
Next review available in: 3 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Add a "Required IAM permissions" section to docs/further.md giving the minimal core policy the executor role needs (batch:SubmitJob/DescribeJobs/ RegisterJobDefinition/DeregisterJobDefinition/TerminateJob/DescribeJobQueues/ DescribeComputeEnvironments and iam:PassRole), plus a single tags add-on (batch:TagResource, with an ecs:TagResource note for tag propagation). Each permission is tied to the feature that needs it, and the register/deregister and PassRole statements are called out as conditional (pre-existing job definitions, and only when --aws-batch-job-role is set). Cross-linked from the README.
Adds a "Required IAM permissions" section to
docs/further.mdgiving the minimal policy the executor role needs:batch:SubmitJob,batch:DescribeJobs,batch:RegisterJobDefinition,batch:DeregisterJobDefinition,batch:TerminateJob,batch:DescribeJobQueues,batch:DescribeComputeEnvironments, andiam:PassRole.--aws-batch-tags/SNAKEMAKE_AWS_BATCH_JOB_TAGS):batch:TagResource, with a note thatecs:TagResourcemay also be required depending on the account's tag-authorization settings (for tag propagation to ECS).Each permission is tied to the feature that needs it, and the register/deregister and
PassRolestatements are called out as conditional (register/deregister can be dropped with a pre-existing job definition;PassRoleis only needed when--aws-batch-job-roleis set, and should be scoped to that role ARN). Cross-linked from the README.Docs-only — no code changes.