Amazon Technologies, Inc.

Lee-Ming Zen

Yu Gu

Andrey Mizik

Minli Lai

Yohanes Santoso

Rebecca Claire Weiss

Vadim Meleshuk

Ronald Andrew Hoskinson

Gavin Derek McCullagh

Yi Cheng Chen

Ivan Mistrianu

Pavlo Kaplin

Kyle Benjamin Schultheiss

Xin Yi Liu

Kalyanaraman Prasad

Sean Henry Lewis Meckley

Valeri Liborski

Daniel Lee McCarriar

Fan Xiang

Andrew Charles Wantuch

Leonardo Lizcano

Sergey Royt

Steven Hunton Ngo

Nicholas Trebon

Domain Name System (DNS) requests can be routed to either a private DNS server or a public DNS server based on a determination made by a DNS classifier. The private DNS server allows customers to use custom DNS names for internal resources without exposing the names or IP addresses to the public Internet.

Selective routing of domain name system (DNS) requests

Systems and methods are described to enable health checking of computing devices within a virtual private cloud (VPC) networking environment, without requiring that the devices be accessible via a public network address. An endpoint is placed within the VPC, which enables interaction with an external health checking system via a substrate network. The endpoint handles communications between the heath checking system and the VPC, and can modify data originating from the health checking system such that it appears to originate from the endpoint. From the viewpoint of the VPC, the endpoint itself may appear to be conducting health checking. Thus, external health checking can be used on a VPC without compromising the security of the VPC by requiring that a portion of the VPC be externally addressable.

External health checking of virtual private cloud network environments

Systems and methods are described to enable adaptive handling of domain resolution requests originating from a virtual private cloud (VPC) networking environment. An administrator of the VPC can provide a set of rules specific to the VPC that designates how requests for a domain name should be handled. The rules may specify, for example, that a request for a given domain name should be routed to a particular domain name server, which may include a private domain name server, should be dropped, or should be routed according to a default behavior (e.g., a public domain name system). Resolution requests originating in the VPC can be associated with a VPC identifier. When an adaptive resolution system receives the request, it can retrieve rules associated with the VPC identifier, and apply the rules to determine further routing for the request.

Adaptive resolution of domain name requests in virtual private cloud network environments

Systems and methods are described to enable health checking of computing devices within a virtual private cloud (VPC) networking environment, without requiring that the devices be accessible via a public network address. An endpoint is placed within the VPC, which enables interaction with an external health checking system via a substrate network. The endpoint handles communications between the heath checking system and the VPC, and can modify data originating from the health checking system such that it appears to originate from the endpoint. Thus, from the viewpoint of the VPC, the endpoint itself may appear to be conducting health checking. Thus, external health checking can be used on a VPC without compromising the security of the VPC by requiring that a portion of the VPC be externally addressable.

A service is described that makes it easy and cost-effective to configure network traffic flowing to multiple endpoints. Enterprises and developers can easily manage the way that end-users are routed to applications running in different geographic regions. Customers can route traffic based on multiple criteria in a customer policy. Customers can manage large-scale, multi-region applications, increase application availability, and minimize latency to end-users. The service can consider the state of end-users, such as their geography, their network, and their latency to different geographic regions. The service can also consider the state of the customer's applications, such as the load on the application, the application's health, the cost of using that application (e.g., resource costs), resource states (e.g., disk throughput), resource location, customer-provided endpoint cost parameters, etc.

Network traffic management system using customer policy settings

Growing community of inventors

Seattle, WA, United States of America

Lee-Ming Zen