AWS's eventbus service · portable interface driver.EventBus · AWS index
| 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 |
- AWS: API destination targets are called in the background after
PutEventsreturns, 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 explicitRetryPolicy.MaximumRetryAttemptsis honored. ARetry-Afterfrom the endpoint delays the next attempt by at most 5 seconds, and one delivery stops retrying after 30 seconds, whateverMaximumEventAgeInSecondssays. 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:
PutEventswithEndpointIdworks against a custom endpoint URL. aws-sdk-go-v2 and the AWS CLI (which needs the bundledawscrt) keep the configured endpoint instead of<EndpointId>.endpoint.events.amazonaws.comand sign the request with SigV4a. cloudemu does not verify SigV4a, so with--enforce-authsuch a request is refused. A SigV4a signature carries no Region, socloudemu servehandles 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.
PutEventsthrough an endpoint goes to its event bus in the endpoint's home Region: an entry with noEventBusName, 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:
CreateEndpointandUpdateEndpointanswerCREATINGandUPDATING. Reads then showACTIVE, at once or after a short window with--async-settle.DeleteEndpointremoves the endpoint at once, without aDELETINGphase, soConcurrentModificationExceptionand the*_FAILEDstates never occur. - AWS: partner event sources run in one account. The partner-side operations (
CreatePartnerEventSource,PutPartnerEventsand the rest) are served by the same emulator and account as the customer side, and any 12-digitAccountis accepted. Only a source created for the emulator's own account shows inListEventSourcesandDescribeEventSource, 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
PENDINGfor two weeks is not deleted.ExpirationTimeis reported but not enforced. - AWS:
PutPartnerEventsfor a source that is notACTIVEin this account, or whose partner event bus was deleted, answers with anEventIdand drops the event. Deleting a partner event bus moves its source back toPENDING, andDeletePartnerEventSourceleaves the partner event bus in place.