Skip to content

Latest commit

 

History

History
36 lines (31 loc) · 3.53 KB

eventbridge.md

File metadata and controls

36 lines (31 loc) · 3.53 KB

EventBridge

AWS's eventbus service · portable interface driver.EventBus · AWS index

Operations (16)

Operation Description
CreateEventBus Bus management
DeleteEventBus
DeleteRule
DisableRule
EnableRule
GetEventBus
GetEventHistory Event history (replay)
GetRule
ListEventBuses
ListRules
ListTargets
PutEvents Event publishing
PutRule Rule management
PutTargets Target management
RemoveTargets
UpdateEventBus UpdateEventBus replaces the mutable fields (tags) of an existing

Not in scope

  • AWS: API destination targets are called in the background after PutEvents returns, at most 64 deliveries at a time per emulator. A failed call is retried 2 times by default (AWS retries up to 185 times over 24 hours); an explicit RetryPolicy.MaximumRetryAttempts is honored. A Retry-After from the endpoint delays the next attempt by at most 5 seconds, and one delivery stops retrying after 30 seconds, whatever MaximumEventAgeInSeconds says. Then the event goes to the target's dead-letter queue.
  • AWS: in-flight API destination deliveries, their retry state and cached OAuth tokens are not persisted in snapshots, and a delivery still running when the emulator stops is dropped.
  • AWS: PutEvents with EndpointId works against a custom endpoint URL. aws-sdk-go-v2 and the AWS CLI (which needs the bundled awscrt) keep the configured endpoint instead of <EndpointId>.endpoint.events.amazonaws.com and sign the request with SigV4a. cloudemu does not verify SigV4a, so with --enforce-auth such a request is refused. A SigV4a signature carries no Region, so cloudemu serve handles the request in its default Region (--region), and the endpoint must be created there.
  • AWS: a global endpoint has no second Region behind it. Route 53 health checks are not evaluated, so events never fail over, and event replication to the secondary Region is not performed. PutEvents through an endpoint goes to its event bus in the endpoint's home Region: an entry with no EventBusName, or one naming either endpoint bus by name or ARN, lands on the bus of that name, and an entry naming another bus goes to that bus.
  • AWS: CreateEndpoint and UpdateEndpoint answer CREATING and UPDATING. Reads then show ACTIVE, at once or after a short window with --async-settle. DeleteEndpoint removes the endpoint at once, without a DELETING phase, so ConcurrentModificationException and the *_FAILED states never occur.
  • AWS: partner event sources run in one account. The partner-side operations (CreatePartnerEventSource, PutPartnerEvents and the rest) are served by the same emulator and account as the customer side, and any 12-digit Account is accepted. Only a source created for the emulator's own account shows in ListEventSources and DescribeEventSource, gets a partner event bus, and has its events delivered; sources for other accounts are visible only to the partner-side operations.
  • AWS: a partner event source that stays PENDING for two weeks is not deleted. ExpirationTime is reported but not enforced.
  • AWS: PutPartnerEvents for a source that is not ACTIVE in this account, or whose partner event bus was deleted, answers with an EventId and drops the event. Deleting a partner event bus moves its source back to PENDING, and DeletePartnerEventSource leaves the partner event bus in place.