EventBrige, CloudWatch

CloudWatch

• statsD support

EventBridge

We recommend the use of Java package-name style reverse domain-name strings. Minimum information needed for a valid custom event When you create custom events they must include the following fields:

• detail – A JSON object that contains information about the event. It can be "{}".
• detail-type – A string that identifies the type of event.
• source – A string that identifies the source of the event. Customer-generated events can have any value here, as long as it doesn't begin with "aws."

API destinations are HTTP invocation endpoints that you can use as the target for a rule.

An invocation is an event matching a rule and then being sent to the rule’s targets. If the invocation of a target fails due to a problem with the target service or account throttling, EventBridge reattempts for up to 24 hours.

Limit

• Throughput

  • PutEvents has a soft limit of 600 requests per second by default in ap-east-1.
  • All EventBridge APIs other than PutEvents are limited to 50 requests per second by default.
  • [invocation] Default 300 TPS of invocations per API destination. The invocations quota has a soft limit of 1,100 requests per second in ap-east-1.

• Latency: 500 ms

• No FIFO: ordering is not guaranteed.

• Service quota

  • [EventBus]: Maximum 100 event buses per account.
  • [Rule]: Up to 300 rules per event bus. a hard limit of 5 targets per rule
  • [API destinations]: Up to 3,000 API destinations. Up to 3,000 Connections are used with API destination to define the authorization parameters to use to connect to the destination HTTP endpoint.

• No default email or SMS messages target like SNS