Amazon Technologies, Inc.

Juan-Pierre Longmore

Eric Paul Wei

Anuj Prateek

Andrew James Lusk

Noel O'Flaherty

Christopher S Vasquez

Pooja Madan

Sean Alexander Monroe

Rajesh Somnath Kamath

Daniel Bien

Donald Patrick McGarry

Peng Gu

Ajay Narendra Malalikar

When a request to transition use of a first data store to a second data store is identified (e.g., when a new regional computing stack is to be brought online in a network), tables in the second data store are created that correspond to respective ones of tables of the first data store. Data items are then accessed from the first data store and translated into a format interpretable by a remote data storage service. Thereafter, a network-based application programming interface (API) call is performed to store the data items in the remote data storage service using the data items in the second format. The data items as stored in the remote storage service are accessed and imported into the second data store.

Database migration for new regions and disparate customer accounts

Systems and methods are provided for bypassing or enforcing constraints regarding actions on network-based services. An account manager can store or maintain an account type of standard or special as account information associated with an account. When a user operating under an account tries to perform an action on a network-based service, the network-based service may retrieve or receive the account type associated with the account from the account manager. If the account type is standard, the network-based service can enforce constraints on the action. Alternatively, if the account type is special, the network-based service can bypass constraints on the action.

Constraint management for network-based service actions

Disclosed are various embodiments for simulating hardware-based faults in a cloud provider network. A first computing device can send a command to an offload card installed on a second computing device to introduce a simulated hardware fault into the second computing device. Then the first computing device can determine whether the second computing device has successfully recovered from the simulated hardware fault. Alternatively, an entry in an access control list (ACL) of a network switch can be modified to block network traffic to a first network interface of a host machine that is connected to the network switch. Then, a command can be sent to a second network interface of the host machine to instruct the host machine to perform a hard reset. Then it can be determined whether the host machine has successfully booted subsequent to the hard reset.

Hardware-based fault injection service

Availability zone and region recovery are described. For an availability zone (AZ), a recovery availability zone (rAZ) may be identified based on available computing capacity of the recovery availability zone and geographic proximity of the availability zone relative to the recovery availability zone. In an instance in which the availability zone is impacted in which at least one of hardware and software of the availability zone is not fully operational, a virtual private cloud (VPC) is generated that establishes a peered connection between the availability zone and the recovery availability zone. A service is executed in the recovery availability zone, permitting any other services executing in the availability zone to invoke the service and become partially or fully operational.

Availability zone recovery using virtual private clouds

Network services are deployed in a networked environment in association with a user account. Dependencies of a network service, such as other network services, may be identified based on an online analysis and an offline analysis of the network service. Further, anomalies associated with the dependencies may be identified in some situations. A call graph may include nodes corresponding to the network services and its dependencies, and may include an identifier corresponding to a part of the call path that has the anomaly. An inspection of the call graph allows software developers to readily recognize that their service depends on a potentially flawed software that may cause a service failure or outage.

Software application dependency insights

Disclosed are various embodiments for centralized and dynamically generated service configurations for data center and other region builds. A computing environment may be configured to receive requests to deploy a new computing stack or service from different geographical regions at a central service. For the individual ones of the requests, the computing environment may identify computing resources of the computing environment required to deploy the new computing stack or service, determine an order of creation of the computing resources, and create at least one virtual process that automatically allocates the computing resources for the new computing stack based on a predetermined order of creation.

Centralized and dynamically generated service configurations for data center and region builds

Satellite virtual private clouds (VPCs) are described. A primary VPC is executed having one or more core services hosted therein that are required by one or more satellite VPCs. A satellite VPC is executed that is logically independent of the primary VPC networked environment. A peered connection between the primary VPC and the satellite VPC is established. The peered connection permits the satellite VPC networked environment to access the at least one core service hosted in the primary VPC. A customer account may be associated with a suitable permission to perform isolated development in the satellite VPC networked environment without impacting any service hosted by the primary VPC networked environment.

Satellite virtual private cloud network environments

For a network service to be deployed in one of a plurality of regional computing stacks, the network service may be partitioned into a region-specific portion and a region-agnostic portion. A first data transfer of the region-agnostic portion of the network service and a second data transfer of the region-specific portion may be performed separate from one another. Configuration settings of the network service as previously deployed in one or more of the regional computing devices may be accessed, and the region-specific portion may be configured using region-specific configuration settings as modified or confirmed by an administrator. The region-specific portion and the region-agnostic portion are deployed in one of the regional computing stacks as part of a networked computing environment.

Homogeneous pre-built isolated computing stacks for data center builds

Disclosed are various embodiments for automating data center builds through the use of service proxies. A proxy is configured in a testing computing environment to receive service calls for a plurality of first services in the testing computing environment. The proxy forwards the service calls to at least one corresponding instance of the plurality of first services not in the testing computing environment. One or more second services in the testing computing environment that generate the service calls for the plurality of first services are then tested. The service calls are handled by the proxy during testing.

Service proxies for automating data center builds

Launching data stores when new computing infrastructure is deployed is described. A proxy data storage service may be provided that receives instances of an application programming interface (API) call to store data and determines one of a first data store or a second data store to store the data. For instance, in response to receipt of a first instance of the API call, the proxy data storage service may store data in a first data store. However, after a provisioning of the second data store, the proxy data storage service may store data in the second data store in response to receipt of a second instance of the API call. In an instance in which the data stored in the second data store also exists in the first data store, the data is deleted from the first data store until an eventual migration of data is achieved.

Growing community of inventors

Seattle, WA, United States of America

Juan-Pierre Longmore