Amazon Technologies, Inc.

Nikita Pinski

Ahmed Usman Khalid

Jakub Mateusz Narloch

Mohamed Marzouk Adedoyin Mounirou

Nicholas Smit

Derek Solomon Pai

Eric Samuel Stone

Kunal Chopra

Timothy William Bray

Rishi Baldawa

Alexander Kulikov

Jamie Christopher Dool

Rebecca Claire Weiss

Christopher Richard Jacques De Kadt

Brad Eugene Marshall

Akhilesh Mritunjai

Shawn Jones

Mai-Lan Tomsen Bukovec

Dennis Tighe

Jesse Marcus Dougherty

Asim Himani

Igor Subbotin

Gustavo Soto Ridd

Jerry Connolly

Tim Bray

Sanket Deepak Nayak

Denis Delimarschi

Catalin Clapon

Methods and apparatuses for the authorization of events received for an event bus service that hosts an event bus are described herein. The event bus service receives a plurality of events that were published from an event publisher. The event bus service determines an authorization scheme for the first event, and information to authenticate the identity of the event publisher of the first event. The event bus service authenticates the first event using the authorization scheme and the information to authenticate the identity of the event publisher. The event bus service provides the authenticated first event to the event bus.

Automated authorization verification of events received for an event bus

Techniques for role-based permission delegation in a provider network. The techniques include an assuming service in the provider network sending a request to a temporary credential service in the provider network to assume a delegation role. The assuming service, acting in the delegation role, sending a request to the temporary credential service to assume the customer role in accordance with a down scoping policy. The assuming service, acting in the customer role, performing an action in a strict subset of actions on a customer resource. The techniques improve the operation of the provider network by allowing a permission to perform an action on the customer resource that is granted by the customer to a delegating service in the provider network to be delegated to the assuming service while complying with the access control principle of least privilege.

Role-based permission delegation in a provider network

Techniques for a service provider network to communicatively couple services and/or applications in a serverless computing environment. A pipe component can configure a pipe to integrate two services by transmitting data between services and/or applications using the pipe. The pipe may also be configured to transform how a service processes an event, control timing of event transmissions using the pipe, define an event structure for an event, and/or batch events. Pipes enable an application or service to exchange data with a variety of services provided by the service provider network while controlling what type of data is generated, stored, or transmitted.

Defining event data in an event-driven architecture

Transforming data between cloud entities in an event architecture

Batching event data in an event-driven architecture

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.

Egress rate control in an event bus service

Controlling timing of event data transmissions in an event architecture

Integration of cloud entities in an event architecture

A computing resource associated with a user is scheduled to undergo a transition. Prior to the scheduled transition, the computing resource is placed in a pending state. The user is notified that the computing resource is scheduled to undergo the transition. In response to an input received from the user, the computing resource is allowed to undergo the transition when the input indicates that the transition can proceed.

Computing resource transition notification and pending state

Technology for scaling computing instances is provided. In one example, a method may include identifying vertical scaling rules defining a criterion for vertically scaling a computing instance from a first instance type to a second instance type. The method may further include monitoring usage of the computing instance and vertically scaling the computing instance from the first instance type to the second instance type based on the usage as compared to the vertical scaling rules.

Vertical scaling of computing instances

Growing community of inventors

Vancouver, Canada

Nikita Pinski