(aws-sesv2): Whole service missing

[TomasChmelik]

Describe the feature

https://docs.aws.amazon.com/cli/latest/reference/sesv2/

This service was released in 2020. Is it planned to implement it? Or include new resources in aws-ses?

Use Case

In my specific case: CreateEmailIdentityPolicy is not supported by CDK

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

AWS CDK Library version (aws-cdk-lib)

latest

AWS CDK CLI version

latest

Environment details (OS name and version, etc.)

latest

[pahud]

Thanks for raising this! There's no bug to reproduce here, so I verified the coverage situation against the installed aws-cdk-lib and the CloudFormation registry instead. Two things worth clarifying:

SESv2 is mostly already in CDK. CloudFormation models the SES API v2 under the existing AWS::SES::* namespace (there is no separate AWS::SESV2::* namespace), and CDK's L1 constructs are auto-generated from that registry. The aws-ses module currently ships 21 L1s — CfnEmailIdentity, CfnConfigurationSet, CfnDedicatedIpPool, CfnMultiRegionEndpoint, CfnTenant, the MailManager family, and more — all of which are SESv2-surface resources. So a dedicated aws-sesv2 module isn't planned, because the CloudFormation namespace it would be generated from doesn't exist.

Your specific ask is blocked upstream, not in CDK. CreateEmailIdentityPolicy (identity authorization policies) has no CloudFormation resource type at all, so CDK has nothing to generate an L1 from. This is tracked in the CloudFormation coverage roadmap — I'd encourage you to 👍 it, since that's what drives prioritization:

aws-cloudformation/cloudformation-coverage-roadmap#1576

In the meantime, you can manage identity policies declaratively from CDK today with AwsCustomResource, calling the SESv2 API on create/update/delete:

new cr.AwsCustomResource(this, 'IdentityPolicy', {
  onUpdate: {
    service: 'SESv2',
    action: 'CreateEmailIdentityPolicy',
    parameters: {
      EmailIdentity: identity.emailIdentityName,
      PolicyName: 'AllowCrossAccountSend',
      Policy: JSON.stringify(policyDocument),
    },
    physicalResourceId: cr.PhysicalResourceId.of('AllowCrossAccountSend'),
  },
  onDelete: {
    service: 'SESv2',
    action: 'DeleteEmailIdentityPolicy',
    parameters: {
      EmailIdentity: identity.emailIdentityName,
      PolicyName: 'AllowCrossAccountSend',
    },
  },
  policy: cr.AwsCustomResourcePolicy.fromSdkCalls({
    resources: cr.AwsCustomResourcePolicy.ANY_RESOURCE,
  }),
});

Could you confirm whether this covers your use case? Once CloudFormation ships AWS::SES::EmailIdentityPolicy, the corresponding CDK L1 will be generated automatically in a following release — no CDK-side change needed. If there are other specific SESv2 operations you're missing beyond identity policies, listing them here would help us check whether they're similarly CFN-blocked or something we can act on.

[github-actions]

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

[TomasChmelik]

Ah, I wasn't aware of this dependency on CF team. Yes, I'm currently using custom resource to do this.