Amazon Technologies, Inc.

William Ashley

Anthony Nicholas Liguori

Eric Samuel Stone

Yang Lin

Richard Hazen Galliher, Iii

David James Goodell

Steven Anthony Kady

Patrick John Lawrence

Dharm Raj

A first service of a provider network obtains an identification of one or more substrate addressable devices included in an extension of the provider network. Based on the identification, a launch of one or more compute instances within the provider network is initiated. The one or more compute instances are to connect the provider network to the extension of the provider network across at least a third-party network by receiving a first control plane message directed to a first substrate addressable device of the one or more substrate addressable devices, by updating a message state data store based at least in part on the first control plane message, and by sending a second control plane message to the first substrate addressable device via a secure tunnel.

Provider network connectivity management for provider network substrate extensions

A first message of a first type and having a first destination address is received in a provider network. The first destination address is associated with a virtual network address of the provider network and an address of a first device in an extension of the provider network, the extension of the provider network in communication with the provider network via at least a third-party network. A message state data store is updated based on at least a portion of the first message. A first payload of the first message is sent to the first device a first secure tunnel through the third-party network.

Provider network connectivity to provider network substrate extensions

Synchronizing data with metadata includes simultaneously triggering a metadata generation unit to produce metadata that are stored in a reliable metadata queue, and a data unit producing unit that produces data units that are processed in a lossy processing pipeline. A synchronizer obtains a processed data unit, and considers one or more statistics associated with the metadata queue to determine whether it is likely that a data unit was dropped by the lossy processing pipeline. For example, an increase in the depth of the queue may be used to infer that a data unit was dropped. If so, enough metadata entries may be dequeued such that the next metadata entry is correctly synchronized with the data unit. The synchronized data unit and metadata unit are output together. Another technique may take the output from two or more different systems and align data units from each system based on the metadata.

Data/metadata synchronization using metadata queue statistics

Growing community of inventors

Seattle, WA, United States of America

William Ashley