feat(ses): add fromEmailIdentityArn

[hassaku63]

Issue # (if applicable)

Closes #33981

Reason for this change

The SES module currently lacks a method to import an EmailIdentity by its ARN, which is inconsistent with many other CDK resource libraries. Supporting this would allow users to follow a consistent pattern when managing resources across CDK stacks.

Description of changes

• Added a new static method EmailIdentity.fromEmailIdentityArn(scope, id, emailIdentityArn) to enable importing an EmailIdentity by ARN.

Describe any new or updated permissions being added

No new IAM permissions are required, as this change does not perform any operations requiring permissions. It only allows referencing an existing SES Email Identity by ARN.

Description of how you validated changes

• Added unit tests in email-identity.test.ts to verify that the ARN is correctly parsed and the resulting IEmailIdentity behaves as expected.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

(This review is outdated)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.98%. Comparing base (74cbe27) to head (e2d4d64).
Report is 10 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #33984   +/-   ##
=======================================
  Coverage   83.98%   83.98%           
=======================================
  Files         120      120           
  Lines        6976     6976           
  Branches     1178     1178           
=======================================
  Hits         5859     5859           
  Misses       1005     1005           
  Partials      112      112           

Flag	Coverage Δ
suite.unit	83.98% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
packages/aws-cdk	∅ <ø> (∅)
packages/aws-cdk-lib/core	83.98% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[hassaku63]

Exemption Request

I would like to request an exemption from the requirements to update the README and integration test files, based on the following reasons:

• The existing method fromEmailIdentityName, which provides similar functionality (i.e., importing an identity by name), does not have a corresponding section in the README.
• There is also no integration test or snapshot that covers fromEmailIdentityName.

Since this feature follows the same usage pattern and abstraction level as fromEmailIdentityName, I believe it's reasonable to apply the same documentation and testing scope.

[QuantumNeuralCoder]

Can we add an integ test and a readme please?

[QuantumNeuralCoder]

Please let me know if you need help with writing the test. There are few samples that can be referred from within the repo.

[hassaku63]

@QuantumNeuralCoder Thanks for the feedback.

Regarding the integration test, I will work on adding one. Since the newly added method does not create or modify any actual AWS resources—it's a static method for importing an existing resource by ARN—I initially considered its behavior sufficiently covered by unit tests. However, I understand the value of having integ test coverage for completeness and consistency, and I’ll follow up with an appropriate test case.

As for the README, I’d appreciate a bit more detail on what kind of addition you’d like to see. The fromEmailIdentityArn method follows a common static import pattern used across many L2 constructs, and based on a quick review of similar modules, this type of method is often not explicitly documented unless it’s part of a usage example. Would it make sense to update an existing example in the README to use fromEmailIdentityArn instead of constructing a new resource? I’d be happy to revise the documentation accordingly once I better understand the intended scope.

[shikha372]

Thanks @hassaku63 for submitting the change, can we add a section to Readme for this, would be helpful for the users.

clicked by mistake

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[hassaku63]

@QuantumNeuralCoder @shikha372 Dear reviewers,

Thank you very much for your reviews. I have addressed the points you raised and, as suggested, I have added the information to the README.

[shikha372]

LGTM.. Thank you @hassaku63 for your contribution

Pull request has been modified.

Pull request has been modified.

[shikha372]

@hassaku63 build started failing with below error, needs to be fixed before approval

aws-cdk-lib: /codebuild/output/src1876009486/src/github.com/aws/aws-cdk/packages/aws-cdk-lib/aws-ses/lib/email-identity.ts
aws-cdk-lib:   411:13  error  Expected a non-default error object to be thrown  @cdklabs/no-throw-default-error

[hassaku63]

@shikha372 Thanks for your noting yes I will commit fix this problem 👍

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: e65e904
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.