AWS IoT Greengrass V2 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
Control plane operations
The following table contains AWS Region-specific endpoints that AWS IoT Greengrass V2 supports for operations to manage components, devices, and deployments.
| Region Name | Region | Endpoint | Protocol |
|---|---|---|---|
| US East (Ohio) | us-east-2 |
greengrass.us-east-2.amazonaws.com greengrass-fips.us-east-2.amazonaws.com greengrass.us-east-2.api.aws greengrass-fips.us-east-2.api.aws |
HTTPS |
| US East (N. Virginia) | us-east-1 |
greengrass.us-east-1.amazonaws.com greengrass-fips.us-east-1.amazonaws.com greengrass.us-east-1.api.aws greengrass-fips.us-east-1.api.aws |
HTTPS |
| US West (Oregon) | us-west-2 |
greengrass.us-west-2.amazonaws.com greengrass-fips.us-west-2.amazonaws.com greengrass.us-west-2.api.aws greengrass-fips.us-west-2.api.aws |
HTTPS |
| Asia Pacific (Mumbai) | ap-south-1 |
greengrass.ap-south-1.amazonaws.com greengrass.ap-south-1.api.aws |
HTTPS |
| Asia Pacific (Seoul) | ap-northeast-2 |
greengrass.ap-northeast-2.amazonaws.com greengrass.ap-northeast-2.api.aws |
HTTPS |
| Asia Pacific (Singapore) | ap-southeast-1 |
greengrass.ap-southeast-1.amazonaws.com greengrass.ap-southeast-1.api.aws |
HTTPS |
| Asia Pacific (Sydney) | ap-southeast-2 |
greengrass.ap-southeast-2.amazonaws.com greengrass.ap-southeast-2.api.aws |
HTTPS |
| Asia Pacific (Tokyo) | ap-northeast-1 |
greengrass.ap-northeast-1.amazonaws.com greengrass.ap-northeast-1.api.aws |
HTTPS |
| Canada (Central) | ca-central-1 |
greengrass.ca-central-1.amazonaws.com greengrass-fips.ca-central-1.amazonaws.com greengrass.ca-central-1.api.aws greengrass-fips.ca-central-1.api.aws |
HTTPS |
| China (Beijing) | cn-north-1 | greengrass---cn-north-1.amazonaws.com.rproxy.goskope.com.cn | HTTPS |
| Europe (Frankfurt)) | eu-central-1 |
greengrass.eu-central-1.amazonaws.com greengrass.eu-central-1.api.aws |
HTTPS |
| Europe (Ireland) | eu-west-1 |
greengrass.eu-west-1.amazonaws.com greengrass.eu-west-1.api.aws |
HTTPS |
| Europe (London) | eu-west-2 |
greengrass.eu-west-2.amazonaws.com greengrass.eu-west-2.api.aws |
HTTPS |
| AWS GovCloud (US-West) | us-gov-west-1 |
greengrass.us-gov-west-1.amazonaws.com greengrass.us-gov-west-1.api.aws |
HTTPS |
| AWS GovCloud (US-East) | us-gov-east-1 |
greengrass.us-gov-east-1.amazonaws.com greengrass.us-gov-east-1.api.aws |
HTTPS |
AWS IoT device operations
The following table contains AWS Region-specific Amazon Trust Services (ATS) endpoints for AWS IoT device management operations, such as shadow sync. This is a data plane API.
To look up your account-specific endpoint, use the aws iot describe-endpoint --endpoint-type iot:Data-ATS command.
| Region name | Region | Endpoint | Protocol |
|---|---|---|---|
| US East (Ohio) | us-east-2 | prefix-ats.iot.us-east-2.amazonaws.com | HTTPS, MQTT |
| US East (N. Virginia) | us-east-1 | prefix-ats.iot.us-east-1.amazonaws.com | HTTPS, MQTT |
| US West (Oregon) | us-west-2 | prefix-ats.iot.us-west-2.amazonaws.com | HTTPS, MQTT |
| Asia Pacific (Mumbai) | ap-south-1 | prefix-ats.iot.ap-south-1.amazonaws.com | HTTPS, MQTT |
| Asia Pacific (Seoul) | ap-northeast-2 | prefix-ats.iot.ap-northeast-2.amazonaws.com | HTTPS, MQTT |
| Asia Pacific (Singapore) | ap-southeast-1 | prefix-ats.iot.ap-southeast-1.amazonaws.com | HTTPS, MQTT |
| Asia Pacific (Sydney) | ap-southeast-2 | prefix-ats.iot.ap-southeast-2.amazonaws.com | HTTPS, MQTT |
| Asia Pacific (Tokyo) | ap-northeast-1 | prefix-ats.iot.ap-northeast-1.amazonaws.com | HTTPS, MQTT |
| Canada (Central) | ca-central-1 | prefix-ats.iot.ca-central-1.amazonaws.com | HTTPS, MQTT |
| China (Beijing) | cn-north-1 | prefix.ats---iot---cn-north-1.amazonaws.com.rproxy.goskope.com.cn | HTTPS, MQTT |
| Europe (Frankfurt) | eu-central-1 | prefix-ats.iot.eu-central-1.amazonaws.com | HTTPS, MQTT |
| Europe (Ireland) | eu-west-1 | prefix-ats.iot.eu-west-1.amazonaws.com | HTTPS, MQTT |
| Europe (London) | eu-west-2 | prefix-ats.iot.eu-west-2.amazonaws.com | HTTPS, MQTT |
| AWS GovCloud (US-West) | us-gov-west-1 | prefix-ats.iot.us-gov-west-1.amazonaws.com | HTTPS, MQTT |
| AWS GovCloud (US-East) | us-gov-east-1 | prefix-ats.iot.us-gov-east-1.amazonaws.com | HTTPS, MQTT |
Note
Legacy Verisign endpoints are currently supported for some Regions, but we recommend that you use ATS endpoints with ATS root certificate authority (CA) certificates. For more information, see Server Authentication in the AWS IoT Developer Guide.
Data plane operations
AWS IoT Greengrass uses the AWS IoT Core Region-specific ATS endpoints for data plane operations,
such as ResolveComponentCandidates. For a complete list, see AWS IoT Core - data plane endpoints. You must set
greengrassDataPlaneEndpoint to iotdata. For
more information, see AWS IoT Greengrass nucleus configuration.
We recommend you use the AWS IoT endpoints for data plane operations. For backwards compatibility, AWS IoT Greengrass supports the following legacy endpoints.
| Region name | Region | Endpoint | Protocol |
|---|---|---|---|
| US East (Ohio) | us-east-2 | greengrass-ats.iot.us-east-2.amazonaws.com | HTTPS |
| US East (N. Virginia) | us-east-1 | greengrass-ats.iot.us-east-1.amazonaws.com | HTTPS |
| US West (Oregon) | us-west-2 | greengrass-ats.iot.us-west-2.amazonaws.com | HTTPS |
| Asia Pacific (Mumbai) | ap-south-1 | greengrass-ats.iot.ap-south-1.amazonaws.com | HTTPS |
| Asia Pacific (Seoul) | ap-northeast-2 | greengrass-ats.iot.ap-northeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Singapore) | ap-southeast-1 | greengrass-ats.iot.ap-southeast-1.amazonaws.com | HTTPS |
| Asia Pacific (Sydney) | ap-southeast-2 | greengrass-ats.iot.ap-southeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Tokyo) | ap-northeast-1 | greengrass-ats.iot.ap-northeast-1.amazonaws.com | HTTPS |
| Canada (Central) | ca-central-1 | greengrass-ats.iot.ap-northeast-1.amazonaws.com | HTTPS |
| China (Beijing) | cn-north-1 | greengrass---ats---iot---cn-north-1.amazonaws.com.rproxy.goskope.com.cn | HTTPS |
| Europe (Frankfurt) | eu-central-1 | greengrass-ats.iot.eu-central-1.amazonaws.com | HTTPS |
| Europe (Ireland) | eu-west-1 | greengrass-ats.iot.eu-west-1.amazonaws.com | HTTPS |
| Europe (London) | eu-west-2 | greengrass-ats.iot.eu-west-2.amazonaws.com | HTTPS |
| AWS GovCloud (US-West) | us-gov-west-1 | greengrass-ats.iot.us-gov-west-1.amazonaws.com | HTTPS |
| AWS GovCloud (US-East) | us-gov-east-1 | greengrass-ats.iot.us-gov-east-1.amazonaws.com | HTTPS |
Note
Legacy Verisign endpoints are currently supported for some Regions, but we recommend that you use ATS endpoints with ATS root CA certificates. For more information, see Server authentication in the AWS IoT Developer Guide.
Supported legacy endpoints
We recommend that you use the ATS endpoints in the preceding tables with ATS root CA certificates. For backward compatibility, AWS IoT Greengrass V2 currently supports legacy Verisign endpoints in the following AWS Regions. This support is expected to end in the future. For more information, see Server authentication in the AWS IoT Developer Guide.
When using legacy Verisign endpoints, you must use Verisign root CA certificates.
Service quotas
The following tables describe quotas in AWS IoT Greengrass V2. For more information about quotas and how to request quota increases, see AWS service quotas.
| Resource | Quota | Adjustable |
|---|---|---|
| Maximum length of a core device thing name | 124 bytes of UTF-8 encoded characters | No |
| Resource | Quota | Adjustable | Notes |
|---|---|---|---|
| Maximum number of components | 5,000 components per Region | No | |
| Maximum number of component versions | 5,000 versions per component per Region | No | |
| Maximum size of component recipe | 16 KB | No | |
| Maximum total size of component artifacts | 2 GB | No | This quota applies to the sum of all artifacts for a component. |
| Resource | Quota | Adjustable | Notes |
|---|---|---|---|
| Maximum size of deployment document for a thing deployment (without large configuration support) | 7 KB | No | The deployment document includes the component configurations, deployment configurations, and payload overhead. |
| Maximum size of deployment document for a thing group deployment (without large configuration support) | 31 KB | No | The deployment document includes the component configurations, deployment configurations, and payload overhead. |
| Maximum size of deployment document with large configuration support | 6 MB | No | The deployment document includes the component configurations, deployment configurations, and payload overhead. |
| Resource | Quota | Adjustable | Notes |
|---|---|---|---|
| Request rate for CreateComponentVersion | 1 request per second per Region | No | |
| Request rate for other API operations | 30 requests per second per Region | No |
This quota applies to the combination of API requests for all control plane operations. Exceptions
|
