Repository navigation
feat(crossplane): install the AWS SES provider for company mail - #6184
Conversation
Company Email's outbound mail moves to Amazon SES, so the platform needs the SES v2 member of the Upbound AWS provider family, pinned to the family's release and verified with the same Upbound signature check and name guard as the IAM provider. This prerequisite revision also activates the kinds the next revisions use: the SES domain identity and MAIL FROM domain, which the aws tenant may write, and the IAM user, policy attachment and access key of the SMTP sending identity, which stay platform-owned. The provider may reach only the SES v2 API in the account's region, and its singleton gets the same Coroot availability acceptance and Kubescape secret-reader exception as the other AWS providers. No AWS resource is created yet. Part of #5481. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅
|
✅
|
Approve the three moved entries of the rendered authorization ledger: the new SES provider package and its runtime config, and the aws tenant Role, whose only change is write access to the two SES kinds. The Role's pinned diagnostic hash moves with it. Part of #5481. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Authorization ledger approval (d3a6ef5)
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 not completed
|
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
The runtime config was copied from the IAM provider and kept its comments about IAM, EKS and having no managed resources. Say instead why the SES provider pins its STS region and keeps a writable /tmp. Part of #5481. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@coderabbitai review 🤖 Generated with Claude Code |
Action performed
|
|
Readiness at
Promoting and enqueueing. 🤖 Generated with Claude Code |
Main moved the AWS provider family and the IAM provider to v2.9.4 (#5111), and every family member must run the family's release. Merge main, pin provider-aws-sesv2 to v2.9.4, and re-approve its ledger entry, which moves with the package version. The tenant Role and runtime config entries are unchanged. Part of #5481. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The platform moved the AWS provider family to v2.9.4, and the SES provider follows it (devantler-tech/platform#6184). Validate this tenant's manifests against the same release for both declared providers. Part of devantler-tech/platform#5481. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@coderabbitai review 🤖 Generated with Claude Code |
Action performed
|
|
Readiness at 🤖 Generated with Claude Code |
* feat(email): declare the SES sending identity for company mail Company Email's outbound mail is relayed through Amazon SES. Declare the mail domain as an SES identity with 2048-bit Easy DKIM, and a custom MAIL FROM domain so SPF aligns for DMARC. Both are in the account's existing region and omit Delete from their management policies. CI now validates the SES v2 kinds against their provider package and compares each declared provider pin with the platform's. The platform must activate and grant these kinds first (devantler-tech/platform#5481). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore(email): validate against the platform's v2.9.4 AWS providers The platform moved the AWS provider family to v2.9.4, and the SES provider follows it (devantler-tech/platform#6184). Validate this tenant's manifests against the same release for both declared providers. Part of devantler-tech/platform#5481. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Why
The maintainer switched outbound company mail to Amazon SES. The platform manages the AWS account through Crossplane, but it has no SES provider yet, so the sending identity cannot be declared.
What
This installs the SES member of the AWS provider family, with the same signature check, pinning and network limits as the IAM provider. It also activates the SES and IAM-user kinds that the next changes use. The public aws tenant may write only the SES identity; the SMTP sending user and its key stay platform-owned. No AWS resource is created by this change.
Part of #5481
🤖 Generated with Claude Code