- Notifications
You must be signed in to change notification settings - Fork 647
Open
Labels
feature-requestNew feature or enhancement. May require GitHub community feedback.New feature or enhancement. May require GitHub community feedback.p3This is a minor priority issueThis is a minor priority issueresponse-requestedWaiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.service-apiThis issue is due to a problem in a service API, not the SDK implementation.This issue is due to a problem in a service API, not the SDK implementation.
Description
Describe the feature
The GetEmailIdentityResponse, and it's subtypes, should include the Resource ARN for ease of use. Most other Get or List responses seem to include the ARN, so this seems like a reasonable addition.
Use Case
I'm working to implement the new SESv2 Email Tenant feature adding some domain EmailIdentitys as resources. The CreateTenantResourceAssociationCommand input requires the ARN of the resource, but there is currently no way to directly get the ARN of an EmailIdentity. The only way to do it is to manually construct the ARN as arn:aws:ses:${aws_region}:${account_id}:identity/${domain_name}, which works, but is cumbersome.
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
SDK version used
3.934.0
Environment details (OS name and version, etc.)
Node 22
Metadata
Metadata
Assignees
Labels
feature-requestNew feature or enhancement. May require GitHub community feedback.New feature or enhancement. May require GitHub community feedback.p3This is a minor priority issueThis is a minor priority issueresponse-requestedWaiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.service-apiThis issue is due to a problem in a service API, not the SDK implementation.This issue is due to a problem in a service API, not the SDK implementation.