Amazon Technologies, Inc.

Christopher Sam Goosen

Diwakar Gupta

Bret David Kiraly

Johannes Stephanus Jansen Van Rensburg

Aletta Johanna Blanken

Jacob Adam Gabrielson

Marcin Piotr Kowalski

Shane Ashley Hall

Michael Groenewald

Izak Van Der Merwe

Ryan Walter Jason Waite

Adam Scott King

Cindy-Lee Engelbrecht

At a managed control plane service, constituent services and operational requirements of an application are identified. In response to an end-user request directed to the application, contents of an inter-service request are generated at a resource selected by the managed control plane service for a first constituent service, and a response to the message is generated at another resource selected for a second constituent service. Tasks to be performed for the operational requirements are initiated by the managed control plane service.

Managed integration of constituent services of multi-service applications

Techniques are described for enabling users of a service provider to manage placement preferences used to launch virtualized computing resources into a fleet of dedicated physical servers. Users can use one or more service provider interfaces to provide input indicating various placement preferences associated with a fleet of physical servers dedicated for use by a user of the service provider. These placement preferences can be used to determine at which physical server virtualized computing resources&#x2014;for example, virtual machine (VM) instances, containers, and the like&#x2014;are launched in response to launch requests. Among other benefits, the ability to configure customized placement preferences enables users to better satisfy various performance, reliability, software licensing, and other considerations users may have with respect to how their resources are placed within physical server fleets.

Managed computing resource placement as a service for dedicated hosts

Techniques are described for enabling customers of a service provider network to modify and extend the functionality of application programming interfaces (APIs) provided to customers by various services of the provider network. Services of a service provider network provide interfaces that enable customers and other users to define custom API actions representing functionality to be performed by the services upon receipt of corresponding API requests. In this manner, the functionality exposed by provider network services to customers via APIs becomes extensible and customizable to fit customers' particular use cases and without the provider network needing to contemplate and explicitly implement all possible customer-specific API action variations.

User-customizable application programming interfaces in a provider network

Techniques for managing fault domains using cells are described. An area of a provider network may be divided into multiple cells, with each cell representing a different fault domain of the area of the provider network. A customer can provide domain definitions for their service or application and a cell management service can use the domain definitions to place the infrastructure and compute resources underlying the customer's application or service in appropriate cells within an area of the provider network. In some embodiments, the domain definitions may be account-based, where the domain definition may be to place resources in different fault domains depending on the account they are associated with. Alternatively, the customer may tag resources with an identifier such that resources tagged with a first identifier may be placed in a first cell while resources tagged with a second identifier may be placed in a second cell.

User controlled fault domains

Growing community of inventors

Seattle, WA, United States of America

Christopher Sam Goosen