Repository navigation
feat(email): create the send-only SMTP credential for the SES relay - #6185
Conversation
Company Email relays outbound mail through Amazon SES. Declare its SMTP identity platform-side: an IAM user whose only permission is ses:SendRawEmail on the company mail domain's identity in eu-central-1, with the sender limited to that domain, and an access key whose provider- derived SES SMTP password a PushSecret copies to OpenBao. The shared store gets an exact-key grant for that one record, and nobody reads it. Delete is omitted from every policy, so a prune cannot revoke outbound mail; rotation declares a new key first. Part of #5481. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The mail credential guard allowed exactly the three mailbox credentials. Add the relay's SMTP credential as a fourth exact data and metadata grant, and pin its PushSecret: one connection Secret, Replace without deletion, and only the username and SMTP password of that key. Part of #5481. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approve the four new entries of the rendered authorization ledger: the SMTP IAM user, its send-only policy and attachment, and its access key. The policy allows only ses:SendRawEmail on the company mail domain's identity in eu-central-1 with a sender on that domain. Part of #5481. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Authorization ledger approval (5295f0e) Four new platform-owned entries, none of which widens an existing one:
None of these is writable by the tenant: its Role gains no IAM kind. Validator tests pass locally at this head. 🤖 Generated with Claude Code |
✅
|
Code coverage overviewLanguages: Go Go / code-coverage/go
Line coverage data for the main branch is not yet available. View coverage of the 10 most covered files.
ℹ️ Calculations represent line coverage. Results may change as calculations are updated. Updated |
✅
|
|
@coderabbitai review 🤖 Generated with Claude Code |
Action performed
|
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
|
Readiness at Held as a draft for two reasons:
🤖 Generated with Claude Code |
…ntial-5481 # Conflicts: # k8s/providers/hetzner/apps/aws/kustomization.yaml # scripts/validate-eks-ci-role-policy/approved-surface.txt
Merged |
|
@coderabbitai review 🤖 Generated with Claude Code |
Action performed
|
|
Readiness at The prerequisite holds: #6184 is deployed, the IAM User, UserPolicyAttachment and AccessKey kinds are Active, and the provider is Healthy. The maintainer confirmed creating this SMTP login and key in the interactive session. After deploy, I'll check read-only that the User, Policy and AccessKey are Ready and that the PushSecret synced. Promoting and enqueueing. 🤖 Generated with Claude Code |

Why
Company mail will be relayed through Amazon SES, and the mail server needs a password to log in to it. That password should be able to send only as the company domain, and nobody should ever have to see or copy it.
What
This creates a dedicated SES sending login that can only relay mail from the company domain. The platform keeps it in its secret store, where the mail server will read it; no person reads it. The public aws tenant cannot change what this login may do.
Part of #5481
👉 After merge/promotion: this creates a new AWS login and access key. The maintainer confirms that in the interactive session before it merges.
🤖 Generated with Claude Code