Support SES Global Endpoint

[robincsamuel]

Describe the feature

The SES CLI accepts an endpoint-id argument to support global endpoints.

Use Case

https://docs.aws.amazon.com/ses/latest/dg/global-endpoints.html#integrating-with-application

Support for Endpoint ID

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.955.0

Environment details (OS name and version, etc.)

OSX 26.3.1, Node.js 24

[aBurmeseDev]

Hey @robincsamuel, thanks for checking in!

This's already supported, on the@aws-sdk/client-sesv2 client rather than the v1 @aws-sdk/client-ses. Global endpoints are an SES v2 feature, so they aren't modeled on the v1 surface.

Both SendEmailCommand and SendBulkEmailCommand accept an EndpointId input, though note that requests to the global endpoint sign with SigV4A, so you need @aws-sdk/signature-v4a on the import path (or@aws-sdk/signature-v4-crt). Here's code example:

import "@aws-sdk/signature-v4a"; // or @aws-sdk/signature-v4-crt
import { SESv2Client, SendEmailCommand } from "@aws-sdk/client-sesv2";
const client = new SESv2Client({ region: "us-east-1" });

await client.send(
  new SendEmailCommand({
  	EndpointId: "abc123",
  	FromEmailAddress: "from@example.com",
  	Destination: { ToAddresses: ["to@example.com"] },
  	Content: {
  		Simple: { Subject: { Data: "hi" }, Body: { Text: { Data: "hello" } } },
  	},
  }),
);                                                                     
// POST                                                                     
// https://abc123.endpoints.email.amazonaws.com/v2/email/outbound-emails         

Hope that helps but let me know if you have any other questions!

[github-actions]

This issue has not received a response in 1 week. If you still think there is a problem, please leave a comment to avoid the issue from automatically closing.

[robincsamuel]

Thanks, @aBurmeseDev! I've tested, and it's working :)

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.