I Tried Increasing the Limits for Email Identities / Tenants / Configuration Sets in Amazon SES via Service Quotas

Introduction

On November 11, 2026, it was announced that the limits for Amazon SES email identities, tenants, and configuration sets can now be increased from Service Quotas.

https://aws.amazon.com/jp/about-aws/whats-new/2026/11/amazon-ses-higher-resource-limits/

In this article, I check the limits for the three items in the Developer Guide and share the results of requesting an increase from 10,000 to 10,001 in the Tokyo Region through Service Quotas.

Limits in the Developer Guide and Whether They Are Adjustable

I compared the Service quotas section of the SES Developer Guide between the 2024-11-17 version and the current version.

https://docs.aws.amazon.com/ses/latest/dg/quotas.html

Tenants, which were released as a new feature in August 2025, are covered by Service Quotas.

https://dev.classmethod.jp/articles/ses-tenant-isolation-automated-reputation-policies/

Requesting an Increase in Service Quotas

I requested an increase for the three items from 10,000 to 10,001 in the Tokyo Region.

Before the requests, all three items had an applied value of 10,000, Adjustable was true, and the request history was empty.

The request command for email identity is as follows. For tenant and configuration set, I replaced --quota-code with the quota code in the table below and submitted the requests.

aws service-quotas request-service-quota-increase --service-code ses --quota-code L-5C01A92C --desired-value 10001 --region ap-northeast-1 --output json

The responses to the requests were all PENDING. I checked the status with the following command.

aws service-quotas get-requested-service-quota-change --request-id <request-id> --region ap-northeast-1

All three had changed to APPROVED. "Time from request to APPROVED" in the following table is the difference between Created and LastUpdated.

This is the response returned when APPROVED came back from checking the status of the email identity request. The account ID, request ID, role name, and session name have been replaced.

{
    "RequestedQuota": {
        "Id": "<request-id>",
        "ServiceCode": "ses",
        "ServiceName": "Amazon Simple Email Service(Amazon SES)",
        "QuotaCode": "L-5C01A92C",
        "QuotaName": "Email identity count",
        "DesiredValue": 10001.0,
        "Status": "APPROVED",
        "Created": "2026-11-13T10:41:17.982000+09:00",
        "LastUpdated": "2026-11-13T10:41:30.363000+09:00",
        "Requester": "{\"accountId\":\"123456789012\",\"callerArn\":\"arn:aws:sts::123456789012:assumed-role/<role-name>/<session-name>\"}",
        "QuotaArn": "arn:aws:servicequotas:ap-northeast-1:123456789012:ses/L-5C01A92C",
        "GlobalQuota": false,
        "Unit": "None",
        "QuotaRequestedAtLevel": "ACCOUNT"
    }
}

After approval, the first time I retrieved the applied values was about 30 to 34 seconds after Created for each request, and Value was 10001.0 for all three items. When I retrieved the list of support cases with the following command, targeting a period that includes the request times, there were 0 cases.

aws support describe-cases --include-resolved-cases --after-time 2026-11-13T00:00:00Z --region us-east-1

Usage Metrics

According to the Service Quotas UsageMetric, the usage of all three items corresponds to the metric ResourceCount in the namespace AWS/Usage. The recommended statistic is Maximum. The items are distinguished by the value of the Resource dimension.

The usage of email identity can be retrieved as a daily Maximum with the following command. For tenant and configuration set, replace the Resource value EmailIdentity with Tenant and ConfigurationSet.

aws cloudwatch get-metric-statistics --namespace AWS/Usage --metric-name ResourceCount --dimensions Name=Type\,Value=Resource Name=Resource\,Value=EmailIdentity Name=Service\,Value=SES Name=Class\,Value=None --start-time 2026-10-30T01:41:00Z --end-time 2026-11-13T01:41:00Z --period 86400 --statistics Maximum --region ap-northeast-1 --output json

For email identity and configuration set, 14 days of daily Maximum values from 2026-10-30 to 2026-11-12 are recorded. All values were 2.0, which matched the actual counts in the account (2 each for email identity and configuration set).

Summary

I confirmed that the limits for Amazon SES email identities, tenants, and configuration sets can be increased from Service Quotas.

The increase this time was the minimum of 1, but it was approved automatically without going through a support case and was reflected almost immediately.

Depending on the value requested, approval may not be immediate. For accounts that manage many email identities or configuration sets, I recommend monitoring usage with CloudWatch metrics and requesting an increase from Service Quotas with plenty of margin once the usage rate against the limit rises.