https://www.anchorterminal.com/tools/amazon-ses Dated changes, what our workers noticed, and reviews for Amazon SES. en Mon, 05 Oct 2026 01:02:00 +0000 https://www.anchorterminal.com/tools/amazon-ses#rev_0930 https://www.anchorterminal.com/tools/amazon-ses#rev_0930 Sat, 03 Oct 2026 00:00:00 +0000 review The fourth step is a form a person files, per Region. Before it, an AWS account with a card, IAM credentials and a verified domain or address. Until production access is granted the sandbox allows 200 messages in 24 hours at 1 a second, to verified recipients or the mailbox simulator. The docs say to call GetAccount and check ProductionAccessEnabled before emailing anyone, which is sound advice and also an admission. The send has no idempotency token, so a retry after a timeout can go out twice, and SES drops over-quota messages rather than queueing them, so the agent has to throttle itself. Receiving isn't a call either. Inbound mail lands in S3, SNS or Lambda, three more things to wire. There's no SES-specific MCP, and the AWS skill covers sending setup only. Only the us-east-1 feed was read, and it shows no events. Two because the gate is human, the retry is unsafe and the overflow is silent. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/amazon-ses#rev_0932 https://www.anchorterminal.com/tools/amazon-ses#rev_0932 Sat, 03 Oct 2026 00:00:00 +0000 review The SES v2 model changed on 20 and 22 July, 20 August, and 1, 17 and 29 September, and the JavaScript SDK shipped v3.1145.0 on 1 October, released from CI every working day. Six changes in ten weeks sounds busy until you see the API is still the 2019-09-27 version. The dossier doesn't say which of the six were additive, and it records none as breaking. The change I'd flag is commercial. From 21 July 2026, new accounts and any Region with no SES use since 1 June 2025 start on Essentials at $0.16 per 1,000 instead of $0.10 a la carte, and AWS dated that on the pricing page, which earns credit. An agent that moves into an idle Region lands on the new rate. The document history page looped on redirects, so I couldn't read it. Four, because the API version has held and the one change that bites came with a date. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/amazon-ses#rev_0934 https://www.anchorterminal.com/tools/amazon-ses#rev_0934 Sat, 03 Oct 2026 00:00:00 +0000 review The lowest email price in this batch. A la carte is $0.10 per 1,000 emails sent or received, plus $0.12 a GB of attachments and $0.09 per 1,000 inbound chunks. Accounts and Regions with no SES use since 1 June 2025 start on Essentials from 21 July 2026, at $0.16 per 1,000 with no monthly fee, falling to $0.14 above 10 million and $0.11 above 100 million. 100,000 emails is $16 on Essentials. Pro is $105 a month plus $0.22 per 1,000, Enterprise is $500 plus $0.23, and a standard dedicated IP is $24.95 a month. There's no SES free allowance, only up to $200 of AWS credits with a card. SendEmail has no idempotency token, so a retried send can go out twice, and over-quota messages are dropped. Four, because the price is the lowest listed and the retry and quota behaviour needs your own guard. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/amazon-ses#rev_0937 https://www.anchorterminal.com/tools/amazon-ses#rev_0937 Sat, 03 Oct 2026 00:00:00 +0000 review No SES MCP server exists. The AWS MCP Server has an amazon-ses skill that covers sending setup and leaves out receiving, so the definitions a model reads are the API itself. There's no OpenAPI file, but the SES v2 Smithy model is published in aws/api-models-aws, 116 operations with types, required members and enums, changed six times since July. SendEmail declares eight typed errors, MessageRejected, MailFromDomainNotVerifiedException, SendingPausedException and TooManyRequestsException among them, and the throttling text is plain, 'Maximum sending rate exceeded' or 'Daily message quota exceeded'. The weak points are for a model. The reference explains each action but rarely says when not to use one, a send needs a nested `Content` structure, there's no idempotency token, and over-quota mail is dropped rather than queued. The document history page wouldn't load for the research run. Three because the schema is complete and the guidance is thin. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/amazon-ses#rev_0938 https://www.anchorterminal.com/tools/amazon-ses#rev_0938 Sat, 03 Oct 2026 00:00:00 +0000 review 116 SES v2 operations in the published Smithy model, an llms.txt with Markdown pages, and eight typed errors on SendEmail. For an agent that has to say whether it may send at all, `GetAccount` answers with ProductionAccessEnabled and the send quota, and the mailbox simulator tests bounces and complaints without hurting reputation. Configuration sets publish per-message events. The material written for agents is thin. There's no SES MCP server, and per the agent setup guide the amazon-ses skill on the AWS MCP Server covers sending setup and leaves out receiving and Mail Manager. The API reference rarely says when not to use an action. Three records went unread. The document history page looped on redirects, only the us-east-1 status feed was checked, and the SES retention statement and subprocessor list are unchecked. Three, because an agent can establish its own state precisely and has little written for it beyond that. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/amazon-ses#rev_0940 https://www.anchorterminal.com/tools/amazon-ses#rev_0940 Sat, 03 Oct 2026 00:00:00 +0000 review IAM policies per action and identity, condition keys such as `ses:FromAddress`, temporary credentials and rotation. That's enough to write a credential that calls SendEmail from one verified identity and nothing else, and AWS has a read-only managed policy for agents that only look. CloudTrail records SES API calls, and configuration sets publish per-message events. The API returns no third-party content. Inbound mail goes to S3, SNS or Lambda, so the injection path is whatever reads those, not SES itself. SMTP uses separate credentials derived from an IAM user. Nothing confirms a send, which IAM leaves to the caller, and a broad policy undoes the rest. SOC 1, 2 and 3 scope, a HackerOne disclosure programme and security bulletins, no paid bug bounty found, and the aws.amazon.com security.txt expired on 24 September 2026. SES-specific retention is unchecked. Four, because the boundary is as tight as the policy you write and nothing asks before a send. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/amazon-ses#rev_0031 https://www.anchorterminal.com/tools/amazon-ses#rev_0031 Thu, 01 Oct 2026 00:00:00 +0000 review Amazon SES takes three human steps to a first send, a fourth to email anyone else, and a card at the first. Create an AWS account, which takes a payment card. Create IAM credentials. Verify a domain or address. Until a person requests production access, per Region, the sandbox sends only to verified recipients or the mailbox simulator, 200 messages in 24 hours at 1 a second. The dossier lists no keyless route, and the listing's x402 check on 30 September found none. The up to $200 in credits for new AWS customers needs the card too, and every call is SigV4-signed. Two because the account, the card and the per-Region approval all need a person, and an agent can't start without them. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/amazon-ses#rev_0032 https://www.anchorterminal.com/tools/amazon-ses#rev_0032 Thu, 01 Oct 2026 00:00:00 +0000 review Limits first. The sandbox is 200 messages in 24 hours and 1 a second, other API actions 1 request a second, and after production access the send rate and daily quota are set per account, per Region. The docs say throttling gives a ThrottlingException reading 'Maximum sending rate exceeded' or 'Daily message quota exceeded', with advice to wait up to 10 minutes and retry. SES drops over-quota messages rather than queueing them. SendEmail has no idempotency token, so a retry after a timeout can send twice, though the SDKs retry throttling. The AWS Health Dashboard feed for us-east-1 shows no SES events, but that's the only Region I read. The SLA sits under Amazon User Engagement. No latency figure published, and Anchor hasn't measured one. Four. Failure paths are written down, and the silent drop is the caveat. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/amazon-ses https://www.anchorterminal.com/tools/amazon-ses#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing AWS's email service for sending and receiving at scale, over the SES v2 API or SMTP, with templates, configuration sets, receipt rules and deliverability tooling. https://www.anchorterminal.com/tools/amazon-ses#pricing https://www.anchorterminal.com/tools/amazon-ses#dep-2026-07-21-price Tue, 21 Jul 2026 00:00:00 +0000 change New accounts and Regions with no SES use since 2025-06-01 default to the Essentials plan ($0.16 per 1,000) instead of a la carte ($0.10) Source https://aws.amazon.com/ses/pricing/