Repository navigation
feat(email): add the OIDC role that sets up the SES account - #6186
Conversation
SES production access and the account's pricing plan have no Crossplane resource. Declare a platform-owned GitHub OIDC role that only devantler-tech/aws's protected main branch may assume. It holds just ses:GetAccount, ses:PutAccountDetails and ses:PutAccountPricingAttributes, limited to the relay's region, so that repository's main-only workflow can switch the plan to pay-per-use, request production access and read the result back. Part of #5481. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅
|
✅
|
…surface Approve the one new entry of the rendered authorization ledger: the ses-account-setup OIDC role, assumable only from devantler-tech/aws main, with ses:GetAccount, ses:PutAccountDetails and ses:PutAccountPricingAttributes in eu-central-1. Part of #5481. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Authorization ledger approval (f8b382f)
Validator tests pass locally at this head. 🤖 Generated with Claude Code |
devantler
left a comment
There was a problem hiding this comment.
🤖 Generated by the Agentic Engineer (interactive Claude Code session)
Self-review (fallback — CodeRabbit, Codex and Cursor Bugbot unavailable)
Reviewed commit: f8b382f
- CodeRabbit: repository quota spent at 2026-11-13T07:13:58Z ("Your plan provides up to 1 included review per hour; 0 remain after this review"), #6185 (comment)
- Codex: account usage limit at 2026-11-13T00:00:50Z ("You have reached your Codex usage limits for code reviews"), no reset stated and no Codex artifact since, devantler-tech/agent-plugins#697 (comment)
- Cursor Bugbot: team usage limit at 2026-11-12T22:36:57Z (devantler-tech/monorepo#4991 (comment)) and a run refusal at 2026-11-13T03:29:37Z ("Bugbot couldn't run - GitHub account mismatch"), devantler-tech/ksail#8242 (comment)
Verdict: no P0/P1 findings
🤖 Generated with Claude Code
|
Readiness at Held as a draft: merging creates a new AWS role, which the maintainer confirms in the interactive session first. devantler-tech/aws#79 lands after this. 🤖 Generated with Claude Code |
|
The maintainer confirmed creating this role in the interactive session ("Yes, go ahead", SES region eu-central-1). Promoting and enqueueing at 🤖 Generated with Claude Code |

Why
Before company mail can go out through Amazon SES, the AWS account must leave the SES sandbox and be on the pay-per-use plan. Neither setting can be declared as a managed resource, and nobody should have to click through the AWS console for them.
What
This adds a narrow AWS login that only the aws repository's protected main branch can use. It can read the SES account, set the pricing plan and request production access, in the relay's region only. It cannot send or read mail, or change anything else.
Part of #5481
👉 After merge/promotion: this creates a new AWS role. The maintainer confirms that in the interactive session before it merges; the aws repository's workflow then uses it.
🤖 Generated with Claude Code