Amazon Technologies, Inc.

Christopher Brian Barclay

Alireza Farhangi

Sairam Suresh

Sean Henry Lewis Meckley

Pierre Rognant

Nicholas Alexander Allen

David John Ward, Jr

Derek Solomon Pai

Anthony Joseph Suarez

Michael R Foster

Devlin Roarke Dunsmore

Gautam Shanbhag

Eric Jason Brandwine

Gregory Branchek Roth

Diwakar Gupta

Ishwardutt Parulkar

Upendra Bhalchandra Shevade

Georgios Elissaios

Anirudh Balachandra Aithal

Dougal Stuart Ballantyne

Deepak Singh

Daniel Robert Gerdesmeier

Jia Bi Zhang

Shridhar Kulkarni

William Trotter Shelton

Yu Gu

Archana Srikanta

Sharon Shapira

Cornelle Christiaan Pretorius Janse Van Rensburg

Carlos Eduardo Lopez Biagi

Techniques are described for a location-aware service-oriented application deployment management ('SOADM') service that abstracts the complexities of deploying distributed applications in a cloud provider network providing many possible deployment zones of one or multiple types. These deployment zone types can include traditional cloud provider regions and availability zones as well as so-called edge locations (e.g., cloud provider operated edge locations, customer-operated edge locations, third-party operated edge locations, communications service provider (CSP) associated edge locations). The SOADM service enables users to create service group configurations representing a service-oriented application, including its constituent services and dependent resources, and specify distribution strategies for deploying and/or redistributing application services and resources, among other configurations. Using such configurations, the SOADM service automatically deploys and scales simple or complex, single or multi-service applications for users across any number of deployment zones and deployment zone types.

Latency-based service discovery and routing for multi-location service-oriented applications

Techniques for utilizing dual-stack network addressing for compute instances hosted in an edge location of a cloud provider network along with communications service provider (CSP) network addresses are described. A first network address is assigned to the compute instance from a pool of network addresses of the cloud provider network, and a second network address is associated with the compute instance that is provided by the CSP network. A gateway of the edge location is updated to direct packets addressed to the second network address to the compute instance via use of the first network address.

Dual-stack network addressing in cloud provider network edge locations

User-configured multi-location service deployment and scaling

Method and apparatus for remotely accessing a computing resource service provider are disclosed. In the method and apparatus, a first computing environment sends, to a second computing environment, a request for information usable for accessing the second computing environment. In response to the request, the information that is usable to remotely access a subset of the computing resources of the second computing environment is made available to a computing system of the first computing environment, whereby the subset of the computing resources is provisioned for a customer of the second computing environment and the customer of the second environment operates the first computing environment.

Techniques for remote access to a computing resource service provider

Techniques for instantiating container instances from a pool of available container instances are described herein. An instance type is determined from a container description such that the instance type satisfies the resource parameters in the container description. An instance of the instance type is selected from a pool of running container instances, the instance is provisioned, and a container is instantiated on the instance.

Managed container instances

At least one instance of an application is launched in a set of software containers that are distributed among a set of virtual machine instances. A set of measurements corresponding to resource utilization by a software container of the set of software containers is obtained and a timestamp is generated for the set of measurements. The set of measurements is aggregated, with other sets of measurements corresponding to the set of software containers for the application, into a set of aggregated measurements grouped in a time window group, based at least in part on the timestamp, and, as a result of fulfillment of a condition, the time window group is outputted.

Container telemetry

A resource manager may monitor resources offered by a resource provider. The resource manager receives computing metrics from the resources and may perform a management action when a customer defined usage limit is satisfied. The management action may include the resource manager generating an alert, or the resource manager preventing the customer from further accessing the resources offered by the resource provider. The resource manager may also be used to reduce the cost of running a customer's application that uses resources offered by the service provider. The resource manager may also receive business metrics from the customer and determine rates of return using the business metrics and the computing metrics.

Resource manager

Systems and methods are described to enable automation of service discovery records, such as domain name system (DNS) records, based on rules. An administrator of a hosted server, such as a virtual machine instance, may submit a rule to a rule-based DNS resolution system for generating DNS records to assist in discover of the hosted server. The rule may include criteria specifying servers to which the rule applies, as well as criteria for generating a domain name to associate with the server within a DNS record. The rule-based DNS resolution system can integrate with a hosting system providing the hosted server to obtain configuration information of the hosted server and generate DNS records in accordance with the rule. Rules may also be utilized to automate other aspects of the rule-based DNS resolution system, such as health checking and load balancing.

Rule-based automation of DNS service discovery

Systems and methods are described to enable integrating operation of a service record system with operation of an automatically scaled service hosting system. The service hosting system can maintain a set of servers to provide a network-accessible service, and the service record system can maintain records identifying the set of servers as endpoints for the service. The service hosting system can further modify the number of servers within the set based, for example, on demand. When the service hosting system intends to remove a server from the set, it may notify the service record system. The service record system, in turn, can determine whether any valid records are predicted to exist that identify the to-be-removed server as an endpoint for the service. If such records are predicted to exist, removal of the server can be delayed until those records expire, to prevent errors resulting from client reliance on those records.

Integration of service scaling and service discovery systems

Systems and methods are described to enable integrating operation of a service record system with operation of a hosting system. The service hosting system can maintain a set of servers to provide a network-accessible service, and the service record system can maintain records identifying the set of servers as endpoints for the service. The service record system can periodically transmit health check data to servers within the set, to verify their health status. When the service record system determines that a server is unhealthy, it can notify the hosting system. If the hosting system removes the server from the pool, it can notify the service record system, so that the service record system can halt further health checking of the server.

Integration of service scaling and external health checking systems

In a system that provides network-based infrastructure services, customer resources are tagged in accordance with policies provided by the customers. Resources may be automatically tagged upon creation based on the provided policies. In addition, existing resources may be analyzed and automatically tagged to indicate characteristics of the resources that may be of interest to the customer. The customers may also specify configuration policies in terms of resource tags, and the system may be configured to apply and/or enforce the configuration policies.

Tag-based resource configuration control

Growing community of inventors

Seattle, WA, United States of America

Christopher Brian Barclay