AWS IoT Events 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 endpoints
The following table contains AWS Region-specific endpoints that AWS IoT Events supports for control plane operations. For more information, see AWS IoT Events operations in the AWS IoT Events API Reference.
| Region Name | Region | Endpoint | Protocol |
|---|---|---|---|
| US East (Ohio) | us-east-2 |
iotevents.us-east-2.amazonaws.com iotevents-fips.us-east-2.amazonaws.com |
HTTPS HTTPS |
| US East (N. Virginia) | us-east-1 |
iotevents.us-east-1.amazonaws.com iotevents-fips.us-east-1.amazonaws.com |
HTTPS HTTPS |
| US West (Oregon) | us-west-2 |
iotevents.us-west-2.amazonaws.com iotevents-fips.us-west-2.amazonaws.com |
HTTPS HTTPS |
| Asia Pacific (Mumbai) | ap-south-1 | iotevents.ap-south-1.amazonaws.com | HTTPS |
| Asia Pacific (Seoul) | ap-northeast-2 | iotevents.ap-northeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Singapore) | ap-southeast-1 | iotevents.ap-southeast-1.amazonaws.com | HTTPS |
| Asia Pacific (Sydney) | ap-southeast-2 | iotevents.ap-southeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Tokyo) | ap-northeast-1 | iotevents.ap-northeast-1.amazonaws.com | HTTPS |
| Canada (Central) | ca-central-1 |
iotevents.ca-central-1.amazonaws.com iotevents-fips.ca-central-1.amazonaws.com |
HTTPS HTTPS |
| Europe (Frankfurt) | eu-central-1 | iotevents.eu-central-1.amazonaws.com | HTTPS |
| Europe (Ireland) | eu-west-1 | iotevents.eu-west-1.amazonaws.com | HTTPS |
| Europe (London) | eu-west-2 | iotevents.eu-west-2.amazonaws.com | HTTPS |
| AWS GovCloud (US-West) | us-gov-west-1 |
iotevents.us-gov-west-1.amazonaws.com iotevents-fips.us-gov-west-1.amazonaws.com |
HTTPS HTTPS |
Data plane endpoints
The following table contains AWS Region-specific endpoints that AWS IoT Events supports for data plane operations. For more information, see AWS IoT Events data operations in the AWS IoT Events API Reference.
| Region Name | Region | Endpoint | Protocol |
|---|---|---|---|
| US East (Ohio) | us-east-2 |
data.iotevents.us-east-2.amazonaws.com data.iotevents-fips.us-east-2.amazonaws.com |
HTTPS HTTPS |
| US East (N. Virginia) | us-east-1 |
data.iotevents.us-east-1.amazonaws.com data.iotevents-fips.us-east-1.amazonaws.com |
HTTPS HTTPS |
| US West (Oregon) | us-west-2 |
data.iotevents.us-west-2.amazonaws.com data.iotevents-fips.us-west-2.amazonaws.com |
HTTPS HTTPS |
| Asia Pacific (Mumbai) | ap-south-1 | data.iotevents.ap-south-1.amazonaws.com | HTTPS |
| Asia Pacific (Seoul) | ap-northeast-2 | data.iotevents.ap-northeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Singapore) | ap-southeast-1 | data.iotevents.ap-southeast-1.amazonaws.com | HTTPS |
| Asia Pacific (Sydney) | ap-southeast-2 | data.iotevents.ap-southeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Tokyo) | ap-northeast-1 | data.iotevents.ap-northeast-1.amazonaws.com | HTTPS |
| Canada (Central) | ca-central-1 |
data.iotevents.ca-central-1.amazonaws.com data.iotevents-fips.ca-central-1.amazonaws.com |
HTTPS HTTPS |
| Europe (Frankfurt) | eu-central-1 | data.iotevents.eu-central-1.amazonaws.com | HTTPS |
| Europe (Ireland) | eu-west-1 | data.iotevents.eu-west-1.amazonaws.com | HTTPS |
| Europe (London) | eu-west-2 | data.iotevents.eu-west-2.amazonaws.com | HTTPS |
| AWS GovCloud (US-West) | us-gov-west-1 |
data.iotevents.us-gov-west-1.amazonaws.com data.iotevents-fips.us-gov-west-1.amazonaws.com |
HTTPS HTTPS |
Service quotas
| Name | Default | Adjustable | Description |
|---|---|---|---|
| Detector model definition size | Each supported Region: 512 Kilobytes | No | The maximum size (in Kilobytes) of a detector model definition. |
| Detector model versions | Each supported Region: 500 |
Yes |
The maximum number of versions of a single detector model for this account. |
| Detector models | Each supported Region: 50 |
Yes |
The maximum number of Detector models for this account. |
| Detector models per input | Each supported Region: 10 | No | The maximum number of Detector models associated with a single input. |
| Detectors per detector model | Each supported Region: 100,000 |
Yes |
The maximum number of detectors created by a detector model. |
| Inputs | Each supported Region: 50 |
Yes |
The maximum number of inputs for this account. |
| Maximum actions per alarm model | Each supported Region: 10 |
Yes |
The maximum number of actions allowed in an alarm model. |
| Maximum actions per event | Each supported Region: 10 |
Yes |
The maximum number of actions allowed in an event in a detector model. |
| Maximum alarm model versions per alarm model | Each supported Region: 500 |
Yes |
The maximum number of versions of a single alarm model for this account. |
| Maximum alarm models per account | Each supported Region: 200 |
Yes |
The maximum number of alarm models for this account. |
| Maximum alarm models per input | Each supported Region: 10 | No | The maximum number of alarm models associated with a single input. |
| Maximum alarms per alarm model | Each supported Region: 100,000 |
Yes |
The maximum number of alarms created by an alarm model. |
| Maximum events per state | Each supported Region: 20 |
Yes |
The maximum number of events allowed in a state in a detector model. |
| Maximum messages per alarm per second | Each supported Region: 10 | No | The maximum number of messages sent in 1 second to an alarm. |
| Maximum number of alarm models per property in an AWS IoT SiteWise asset model | Each supported Region: 10 |
Yes |
The maximum number of alarm models that can be created for a given property in an AWS IoT SiteWise asset model |
| Maximum number of recipients per notification action in an alarm model | Each supported Region: 10 |
Yes |
The maximum number of recipients that can be specified in a notification action in an alarm model |
| Maximum total messages evaluated per second | Each supported Region: 1,000 |
Yes |
The maximum number of message evaluations across all detectors and alarms in a second for this account. |
| Maximum transition events per state | Each supported Region: 20 |
Yes |
The maximum number of transition events allowed in a state in a detector model. |
| Message size | Each supported Region: 1 Kilobytes |
Yes |
The maximum size of a message (in Kilobytes). |
| Messages per detector per second | Each supported Region: 10 | No | The maximum number of messages sent in 1 second to a detector. |
| Minimum timer duration | Each supported Region: 60 Seconds |
Yes |
The smallest duration a detector model timer can be set (in seconds). |
| Number of detector model analyses in RUNNING status | Each supported Region: 10 |
Yes |
The maximum number of detector model analyses in RUNNING status for this account. |
| State variables per detector model definition | Each supported Region: 50 |
Yes |
The maximum number of state variables in a detector model definition. |
| States per detector model | Each supported Region: 20 |
Yes |
The maximum number of states allowed in a detector model. |
| Timers scheduled per detector | Each supported Region: 5 |
Yes |
The maximum number of timers scheduled by a detector. |
| Trigger expressions | Each supported Region: 20 |
Yes |
The maximum number of trigger expressions per state |
For more information, see AWS IoT Events quotas in the AWS IoT Events User Guide.
