Amazon Technologies, Inc.

Sairam Suresh

Christopher Brian Barclay

Alireza Farhangi

Sean Henry Lewis Meckley

Pierre Rognant

Deepak Singh

Yu Gu

Alec Peterson

Sharon Shapira

Dana B Northcott

Gregory M DiBiase

Jon Heath Dixon

Jan Svab

Rasam Hafezi

Sean Meckley

An agent of a domain management intermediary service obtains a security key using a client credential indicated in a request for a read-write domain management operation. A registry credential is obtained using the security key, and the read-write domain administration operation is initiated using the registry credential. A separate read-only agent obtains the completion status of the read-write domain administration operation and provides the status to the client.

Domain management intermediary service

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

Growing community of inventors

Vancouver, Canada

Sairam Suresh