Abstract: A system for redistributing traffic in response to failure of a service region. An event bus service is configured to monitor performance of computing resources in a first region of the plurality of regions, wherein events are received from one or more event sources at the event bus via a network endpoint created for the event bus and delivered to one or more event targets by the event bus service in the primary region. Based on the monitoring of the performance of the computing resources in the first region, the event bus service detects a region change event for the event bus in the first region, after detection of the region change event, redirects further events to the event bus in the secondary region, wherein the further events are delivered to the one or more event targets by the event bus service in the secondary region.

Abstract: A system is configured to replicate events to be processed by service regions. The system implements an event bus service that hosts an event bus in respective ones of a plurality of regions. The event bus service is configured to receive, at the event bus in a secondary region of the plurality of regions, a replicated indication of an event that is replicated from the event bus in a primary region of the plurality of regions. The event bus service determines, at the event bus in the secondary region, whether the primary region has completed processing of the event. Based on a determination that the primary region has not completed processing of the event within the pre-determined time period, the event bus service processes the event according to the replicated indication and indicates, in the replication record, that the secondary region has completed processing of the event.

Abstract: Techniques are described for enabling a cloud-based service to provide rate controls for events to be delivered by the service to event targets. An event bus service, for example, broadly enables users to create and configure event buses that receive events from event sources and from which the event bus service filters, transforms, routes, and delivers events to selected event targets according to configurable rules. A new event egress call pattern is provided that estimates a rate of attempted event traffic to event targets and a rate of successfully delivered event traffic (also referred to as a local rate estimation), and that uses the rate estimations to determine when it may be appropriate to throttle event delivery, thereby reducing stress on downstream systems experiencing capacity issues and potentially reducing a number of event delivery retries to be handled by the event bus service.

Abstract: A system is configured to simulate outages of network resources. The system is configured to provide a control plane for computing resources of a provider network. The control plane is configured to cause simulated outages of a primary region of the plurality of regions selected to host the plurality of different computing resources. During the simulated outages, the control plane moves respective workloads of the plurality of different computing resources to be performed in the one or more secondary networks and tracks a performance of the one or more secondary regions hosting the moved respective workloads of the plurality of computing resources. After completing individual ones of the simulated outages of the first network, the control plane moves the respective workloads of the plurality of different computing resources back to the primary region.

Abstract: An event routing service may be used to implement lightweight reactive workflows through internal event generation and matching. The service may receive, from a client, specification of event routing rules as well as internal event rules. The internal event rules specified by the client are for matching internal events generated by the service and performing actions in response to the matching of the internal events. For example, when the event routing service determines that one of the incoming events has been successfully delivered to a target service, then the event routing service generates an internal event indicating the successful delivery. The event routing service determines that the internal event matches one of the internal event rules specified by the client. In response, the service performs an action specified by the internal event rule (e.g., send the incoming event to another target or generate a message).

Abstract: A message-level policy implemented with for a message routing system may be used to mediate between a variety of message sources and message targets that receive and use messages. The message-level policy may allow fine grained message-by-message policy assessment that a message routing system policy may be able to provide. The message-level policy may furthermore interact with the message routing system policy to provide mechanisms to avoid accidental leakage of protected messages or spill-over to protected regions.

Abstract: A probabilistic data structure such as a bloom filter may be used to provide a space efficient representation of rules that define events of interest to sources and may be used to reduce the number of events ingested by an event bus system. An event bus system may generate a probabilistic data structure based on the rules that may be used at the event source as a filter. The probabilistic data structure predetermines whether the events to be sent to the event bus system will be of interest to any event targets and if an event is of no interest to any of the event targets, the event will not be sent.

Abstract: A message-level policy implemented with for a message routing system may be used to mediate between a variety of message sources and message targets that receive and use messages. The message-level policy may allow fine grained message-by-message policy assessment that a message routing system policy may be able to provide. The message-level policy may furthermore interact with the message routing system policy to provide mechanisms to avoid accidental leakage of protected messages or spill-over to protected regions.

Abstract: Technology is described for receiving an event notification produced by a source service. A negative cache may be searched for a cache entry for the event notification. The negative cache may be determined to not include the cache entry for the event notification. The event notification may be determined to satisfy a filter rule included in a filter rules table, which may indicate that the event notification is useful information for a destination service. The event notification may be transmitted to the destination service.

Abstract: Technology is described for receiving an event notification produced by a source service. A negative cache may be searched for a cache entry for the event notification. The negative cache may be determined to not include the cache entry for the event notification. The event notification may be determined to satisfy a filter rule included in a filter rules table, which may indicate that the event notification is useful information for a destination service. The event notification may be transmitted to the destination service.