Amazon Technologies, Inc.

Richard Michael Sears

James Christopher Sorenson

Douglas Stewart Laurence

Andrew Gary Hourselt

Christopher Andrew Stephens

Alan Stuart Robbins

Srikanth Satyanarayana

Neha Shetty

Chandan Talukdar

Malik Bouchet

Anna Viktorivna Druzkina

Disclosed are system architectures and techniques for multiple access points for a data container. Control plane and data plane APIs are disclosed for generating access points and associating the access points with data containers, as well as for generating access point policies that specify permissions for the access points. More than one access point may be associated with a single data container. A storage service receives requests directed to the access points, and grants or denies the requests based on the permissions specified in the corresponding policies. Various types of use cases for using access policies are contemplated such as default, regional, or network-based (e.g., VPC-based) use-cases or the like. A system may implement layers of policies such as identity and access management policies, access point policies and data container policies.

Multiple access points for data containers

Disclosed are various embodiments for scalable workflow processing. In one embodiment, a plurality of decision applications each embody a functional expression of a corresponding one of a plurality of workflow definitions. Each of the plurality of decision applications is configured to be repeatedly instantiated. A workflow execution application is configured to orchestrate an execution of each one of a plurality of workflow instances. The workflow execution application is in data communication with each instance of a respective one of the plurality of decision applications. Each of the plurality of decision applications is configured to determine a next action to be taken for respective ones of the plurality of workflow instances.

Scalable workflow processing

Disclosed are various embodiments for scalable workflow processing. To this end, a workflow instance is placed in a queue accessible to a processor-based system, the queue being associated with a workflow. A workflow history associated with the workflow instance is applied to a decision application in response to a poll from the decision application, where the decision application is configured to determine a next action to be taken for the workflow instance. The next action to be taken for the workflow instance is initiated in the processor-based system based on a directive from the decision application generated based on the workflow history.

Methods and apparatus for handling failure of servers in traffic forwarding (TF) systems between networks. A TF system may include units each including multiple servers. Outbound and inbound traffic for a local network may be distributed among the units according to a routing technique, with each unit responsible for an allocated portion of the traffic. Servers in a unit may participate in a health check protocol to detect servers that are not healthy. If the healthy servers in a unit drops below a threshold at which the unit cannot reliably handle its allocated portion of the traffic, the servers may automatically take the unit out of service, for example by stopping advertisement of routes, and the traffic may be reallocated across the remaining units. This may help prevent congestion-related delays, high latency, packet losses, and other problems on connections through the unhealthy unit.

Managing host failures in a traffic forwarding system

Methods and apparatus for handling failure of traffic forwarding (TF) systems in networks that include multiple zones each including a TF system between a production network and a border network. A TF system advertises routes in its zone and handles egress of packets from sources on the local production network onto the border network. TF systems may also advertise low-priority routes in other zones. If a TF system in a zone fails, sources in the zone may make connection requests to the low-priority routes. Instead of egressing the packets onto the border network, the requests on the low-priority routes are responded to with reset messages. Thus, the sources do not have to wait for a connection timeout, and packets for destinations in the zone are not egressed onto local border networks in other zones and sent through thin pipes between the local border networks.

Growing community of inventors

Seattle, WA, United States of America

Richard Michael Sears