Light, fluffy, and always free - The AWS Local Emulator alternative
docs(ses): describe how v2 boolean members are read (#4967)
Kenshin Okinakaddfea8b1612e
diff --git a/docs/services/ses.md b/docs/services/ses.mdindex 2868dc33a3..5f599fbd4f 100644--- a/docs/services/ses.md+++ b/docs/services/ses.md@@ -440,6 +440,8 @@ ARN handling is otherwise uniform across the types (probe-confirmed against realThe same AWS-compatible validation applies wherever tags are set (including `CreateContactList` and `TagResource`): at most 50 tags, unique keys, keys 1–128 / values 0–256 code points, characters limited to letters, numbers, Unicode whitespace and `_ . : / = + - @`, and the reserved `aws:` key prefix. `TagResource` applies the 50-tag limit to the merged (existing + incoming) set. Violations return `BadRequestException` with AWS's messages.+Boolean request members (such as `UnsubscribeAll`, `SendingEnabled`, `SigningEnabled` or an event destination's `Enabled`) follow AWS's restJson1 deserializer: a JSON string is accepted when it reads, case-insensitively, as `true`, `yes`, `y`, `t` or `1`, or as `false`, `no`, `n`, `f` or `0`, and any other string is a `SerializationException`. An omitted member stores `false` (omitting a whole `SendingOptions` or `ReputationOptions` block on `CreateConfigurationSet` keeps the default `true`), and an explicit `null` is a `SerializationException`, except on `PutAccountDetails`, where a `null` `ProductionAccessEnabled` is stored as `false`.+Identity, identity-policy, template, custom-verification-template, configuration-set, and sent-message state is shared between the v1 Query API and the v2 REST JSON API, so a template created with `CreateTemplate` resolves through `SendEmail` on v2 (and vice versa), a policy written with `PutIdentityPolicy` (v1) is returned by `GetEmailIdentityPolicies` (v2), a custom verification email template created with `CreateCustomVerificationEmailTemplate` (v1) is returned by `GetCustomVerificationEmailTemplate` (v2), a configuration set created with `CreateConfigurationSet` is visible to both `DescribeConfigurationSet` (v1) and `GetConfigurationSet` (v2), delivery options written with either `PutConfigurationSetDeliveryOptions` read back through both (v1 spells the policy `Require`/`Optional`, v2 `REQUIRE`/`OPTIONAL`, matching each API), and every send appears in the same `GET /_aws/ses` inspection mailbox.The template, identity, configuration-set, custom-verification-template and export-job lists page with `PageSize` (`MaxItems` on v1, `MaxResults` for v1 custom verification templates) and `NextToken`, with the page-size bounds and error messages real SES answers (probed 2026-09-25 to 2026-09-27). Templates and export jobs are listed newest first; identities, configuration sets and custom verification templates by name, since SES's own identity order varies between calls and its custom verification template order could not be observed. A token belongs to the kind of resource listed, as on AWS: a v1 token continues the v2 list of the same resources and the other way round, while any other list, and the same list in another region, refuses it. Without a page size the template lists serve 10, `ListEmailIdentities` 25, and the configuration-set and custom-verification-template lists 50, and a v1 page size outside the bound is served 100 on `ListTemplates` and 50 on `ListConfigurationSets` and `ListCustomVerificationEmailTemplates` rather than refused, all as on AWS. Floci's own choices, where AWS documents no default and none could be measured: v1 `ListIdentities` without `MaxItems` serves up to 1000, and `ListExportJobs` without a `PageSize` serves 100.