AWS AppSync endpoints and quotas
The following are the service endpoints and service quotas for this service. To connect programmatically to an AWS service, you use an endpoint. In addition to the standard AWS endpoints, some AWS services offer FIPS endpoints in selected Regions. For more information, see AWS service endpoints. Service quotas, also referred to as limits, are the maximum number of service resources or operations for your AWS account. For more information, see AWS service quotas.
Service endpoints
AWS AppSync control plane
| Region Name | Region | Endpoint | Protocol |
|---|---|---|---|
| US East (Ohio) | us-east-2 | appsync.us-east-2.amazonaws.com | HTTPS |
| US East (N. Virginia) | us-east-1 | appsync.us-east-1.amazonaws.com | HTTPS |
| US West (N. California) | us-west-1 | appsync.us-west-1.amazonaws.com | HTTPS |
| US West (Oregon) | us-west-2 | appsync.us-west-2.amazonaws.com | HTTPS |
| Africa (Cape Town) | af-south-1 | appsync.af-south-1.amazonaws.com | HTTPS |
| Asia Pacific (Hong Kong) | ap-east-1 | appsync.ap-east-1.amazonaws.com | HTTPS |
| Asia Pacific (Hyderabad) | ap-south-2 | appsync.ap-south-2.amazonaws.com | HTTPS |
| Asia Pacific (Jakarta) | ap-southeast-3 | appsync.ap-southeast-3.amazonaws.com | HTTPS |
| Asia Pacific (Melbourne) | ap-southeast-4 | appsync.ap-southeast-4.amazonaws.com | HTTPS |
| Asia Pacific (Mumbai) | ap-south-1 | appsync.ap-south-1.amazonaws.com | HTTPS |
| Asia Pacific (Osaka) | ap-northeast-3 | appsync.ap-northeast-3.amazonaws.com | HTTPS |
| Asia Pacific (Seoul) | ap-northeast-2 | appsync.ap-northeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Singapore) | ap-southeast-1 | appsync.ap-southeast-1.amazonaws.com | HTTPS |
| Asia Pacific (Sydney) | ap-southeast-2 | appsync.ap-southeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Tokyo) | ap-northeast-1 | appsync.ap-northeast-1.amazonaws.com | HTTPS |
| Canada (Central) | ca-central-1 | appsync.ca-central-1.amazonaws.com | HTTPS |
| Europe (Frankfurt) | eu-central-1 | appsync.eu-central-1.amazonaws.com | HTTPS |
| Europe (Ireland) | eu-west-1 | appsync.eu-west-1.amazonaws.com | HTTPS |
| Europe (London) | eu-west-2 | appsync.eu-west-2.amazonaws.com | HTTPS |
| Europe (Milan) | eu-south-1 | appsync.eu-south-1.amazonaws.com | HTTPS |
| Europe (Paris) | eu-west-3 | appsync.eu-west-3.amazonaws.com | HTTPS |
| Europe (Spain) | eu-south-2 | appsync.eu-south-2.amazonaws.com | HTTPS |
| Europe (Stockholm) | eu-north-1 | appsync.eu-north-1.amazonaws.com | HTTPS |
| Europe (Zurich) | eu-central-2 | appsync.eu-central-2.amazonaws.com | HTTPS |
| Israel (Tel Aviv) | il-central-1 | appsync.il-central-1.amazonaws.com | HTTPS |
| Middle East (Bahrain) | me-south-1 | appsync.me-south-1.amazonaws.com | HTTPS |
| Middle East (UAE) | me-central-1 | appsync.me-central-1.amazonaws.com | HTTPS |
| South America (São Paulo) | sa-east-1 | appsync.sa-east-1.amazonaws.com | HTTPS |
AWS AppSync data plane
| Region Name | Region | Endpoint | Protocol |
|---|---|---|---|
| US East (Ohio) | us-east-2 | appsync.us-east-2.amazonaws.com | HTTPS |
| US East (N. Virginia) | us-east-1 | appsync.us-east-1.amazonaws.com | HTTPS |
| US West (N. California) | us-west-1 | appsync.us-west-1.amazonaws.com | HTTPS |
| US West (Oregon) | us-west-2 | appsync.us-west-2.amazonaws.com | HTTPS |
| Africa (Cape Town) | af-south-1 | appsync.af-south-1.amazonaws.com | HTTPS |
| Asia Pacific (Hong Kong) | ap-east-1 | appsync.ap-east-1.amazonaws.com | HTTPS |
| Asia Pacific (Hyderabad) | ap-south-2 | appsync.ap-south-2.amazonaws.com | HTTPS |
| Asia Pacific (Jakarta) | ap-southeast-3 | appsync.ap-southeast-3.amazonaws.com | HTTPS |
| Asia Pacific (Melbourne) | ap-southeast-4 | appsync.ap-southeast-4.amazonaws.com | HTTPS |
| Asia Pacific (Mumbai) | ap-south-1 | appsync.ap-south-1.amazonaws.com | HTTPS |
| Asia Pacific (Osaka) | ap-northeast-3 | appsync.ap-northeast-3.amazonaws.com | HTTPS |
| Asia Pacific (Seoul) | ap-northeast-2 | appsync.ap-northeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Singapore) | ap-southeast-1 | appsync.ap-southeast-1.amazonaws.com | HTTPS |
| Asia Pacific (Sydney) | ap-southeast-2 | appsync.ap-southeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Tokyo) | ap-northeast-1 | appsync.ap-northeast-1.amazonaws.com | HTTPS |
| Canada (Central) | ca-central-1 | appsync.ca-central-1.amazonaws.com | HTTPS |
| Europe (Frankfurt) | eu-central-1 | appsync.eu-central-1.amazonaws.com | HTTPS |
| Europe (Ireland) | eu-west-1 | appsync.eu-west-1.amazonaws.com | HTTPS |
| Europe (London) | eu-west-2 | appsync.eu-west-2.amazonaws.com | HTTPS |
| Europe (Milan) | eu-south-1 | appsync.eu-south-1.amazonaws.com | HTTPS |
| Europe (Paris) | eu-west-3 | appsync.eu-west-3.amazonaws.com | HTTPS |
| Europe (Spain) | eu-south-2 | appsync.eu-south-2.amazonaws.com | HTTPS |
| Europe (Stockholm) | eu-north-1 | appsync.eu-north-1.amazonaws.com | HTTPS |
| Europe (Zurich) | eu-central-2 | appsync.eu-central-2.amazonaws.com | HTTPS |
| Israel (Tel Aviv) | il-central-1 | appsync.il-central-1.amazonaws.com | HTTPS |
| Middle East (Bahrain) | me-south-1 | appsync.me-south-1.amazonaws.com | HTTPS |
| Middle East (UAE) | me-central-1 | appsync.me-central-1.amazonaws.com | HTTPS |
| South America (São Paulo) | sa-east-1 | appsync.sa-east-1.amazonaws.com | HTTPS |
Service quotas
| Name | Default | Adjustable | Description |
|---|---|---|---|
| API keys per API | Each supported Region: 50 | No | Maximum number of API keys per GraphQL API |
| APIs per region | Each supported Region: 25 |
Yes |
Maximum number of APIs per region |
| Authentication providers per API | Each supported Region: 50 | No | The maximum number of authentication providers per API |
| Evaluated resolver template size | Each supported Region: 5 Megabytes | No | Maximum size of the evaluated resolver template |
| Functions per pipeline resolver | Each supported Region: 10 | No | Maximum number of functions per pipeline resolver |
| Iterations in a foreach loop in mapping templates | Each supported Region: 1,000 | No | Maximum number of iterations in #foreach...#end loop in mapping templates |
| Max Batch Size | Each supported Region: 2,000 | No | The maximum length of the resolver request list that will be sent to a single Lambda function for a BatchInvoke operation. |
| Number of caching keys | Each supported Region: 25 | No | The maximum number of caching keys |
| Number of custom domain names | Each supported Region: 25 |
Yes |
The maximum number of custom domain names per region |
| Rate of connections per API | Each supported Region: 2,000 per second |
Yes |
The maximum number of connect requests per second. |
| Rate of inbound messages per API | Each supported Region: 10,000 per second |
Yes |
The maximum number of inbound messages per second. Each subscription type invoked by a mutation generates one inbound message. |
| Rate of outbound messages per API | Each supported Region: 1,000,000 per second |
Yes |
The maximum number of outbound messages per second. One outbound message is equal to 5 KB of payload data delivered. |
| Rate of request tokens |
us-east-1: 10,000 per second us-east-2: 10,000 per second us-west-2: 10,000 per second ap-northeast-1: 10,000 per second ap-northeast-2: 10,000 per second ap-south-1: 10,000 per second ap-southeast-1: 10,000 per second ap-southeast-2: 10,000 per second eu-central-1: 10,000 per second eu-west-1: 10,000 per second eu-west-2: 10,000 per second Each of the other supported Regions: 5,000 per second |
Yes |
The maximum number of request tokens per second in this account in the current Region. AWS AppSync allocates tokens to mutation and query requests based on the amount of resources (processing time and memory) that they consume. For more details on tokens, see the Monitoring section in the AWS AppSync documentation. |
| Rate of subscription invalidation requests | Each supported Region: 100 per second | No | The maximum number of invalidation requests per second per account per region |
| Request execution time for mutations, queries, and subscriptions | Each supported Region: 30 Seconds | No | Maximum GraphQL request (queries, mutations, subscriptions) execution time |
| Request mapping template size | Each supported Region: 64 Kilobytes | No | Maximum size of the request mapping template |
| Resolvers executed in a single request | Each supported Region: 10,000 | No | The maximum number of resolvers that can be executed in a single request |
| Response mapping template size | Each supported Region: 64 Kilobytes | No | Maximum size of the response mapping template |
| Schema document size | Each supported Region: 1 Megabytes | No | Maximum size of the schema document |
| Subscription payload size | Each supported Region: 240 Kilobytes | No | Maximum size of the message received via subscriptions |
| Subscriptions per connection | Each supported Region: 100 |
Yes |
Subscriptions code statements per client in a single WebSocket connection. Each statement allows the client to receive multiple messages related to the specific subscription. |
Rate of request tokens is the maximum number of request tokens per second in this account in the current Region. AWS AppSync allocates tokens to mutation and query requests based on the amount of resources (processing time and memory) that they consume. For more details on tokens, see Using token counts to optimize your requests in the AWS AppSync developer guide.
