Amazon Technologies, Inc.

Colin Watson

Harshad Vasant Kulkarni

Marvin Michael Theimer

Julien Jacques Ellie

Jeffrey Cicero Canton

Swapandeep Singh

Ullas Sankhla

Paul Anderson

Brian Dahmen

Arjun Raman

Kerry Hart

Yunhan Chen

Yuxin Xie

Fengjia Xiong

Suchi Nandini

Shu Liu

Conor Patrick Cahill

William Frederick Hingle Kruse

Andrew Paul Mikulski

Dmitry Frenkel

Mahendra Manshi Chheda

Alazel Acheson

Meng Li

Srikanth Mandadi

Slavka Praus

Christopher Ryan Baker

James Robert Englert

Sharjeel Sohail

Carlos Daniel Gasperi

Prasad Krishnan

Vijay K Adhikari

Methods, systems, and computer-readable media for orchestration of computations using a remote repository are disclosed. A representation of one or more inputs to a computation is stored in a repository. The computation is assigned to one or more hosts of a plurality of hosts. A representation of program code executable to perform the computation is stored in the repository. A local copy of the one or more inputs is stored on the one or more hosts. The computation is initiated on the one or more hosts using the program code and the local copy of the one or more inputs. The computation is initiated for a plurality of keys. The computation succeeds for one or more keys after the computation has failed for one or more other keys. A representation of one or more outputs of the computation is stored in the repository.

Orchestration of computations using a remote repository

A request to add tags (e.g., labels, key-value pairs, or metadata) to resources can be digitally signed by the entity making the request, such that the source can be verified and an authorization determination made for each tag. For a request involving multiple services (or entities) that can each add tags, any tag added by a service can be included in the request and digitally signed by that service. Each service processing the request can also digitally sign the request before forwarding, so that each service signs a version of the request, which includes elements signed by other services earlier in the request chain. When the request is received to a tagging service, the service ensures that every tag was digitally signed by the appropriate authorized entity or service, and validates the signatures to ensure that no data was modified or omitted, before adding the tags to the designated resource(s).

Contribution signatures for tagging

Updates to a hierarchical data structure may be selectively replicated to other replicas of the hierarchical data structure. An update for a hierarchical data structure may be received and committed to the hierarchical data structure. A determination as to whether any other replicas of the hierarchical data structure have permission to receive the update may be made. For those replicas of the hierarchical data structure with permission to receive the update, the update may be provided to the replicas and committed to the replicas. Different types of replication techniques may be implemented, such as pull-based replication techniques or push-based replication techniques. Replication permissions for objects of the hierarchical data structure may be individually defined, in some embodiments.

Selectively replicating changes to hierarchial data structures

Methods, systems, and computer-readable media for a client-side filesystem for a remote repository are disclosed. One or more files of a repository are sent from a storage service to a client device. The file(s) are obtained by the client using a credential sent by a repository manager. Local copies of the file(s) are accessible via a local filesystem mounted at the client device. One or more new files associated with the repository are generated at the client device. Using the credential, the one or more new files are obtained at the storage service from the client device. The one or more new files are added to the repository.

Client-side filesystem for a remote repository

In an embodiment, processing logic receives a request to perform an operation with respect to a resource associated with an account. Processing logic determines a tag policy for the account, wherein the tag policy specifies a required tag for resources associated with the account, wherein the required tag comprises a key value pair comprising a tag key and an associated tag value. Processing logic determines or more tag compliance rules of the tag policy, wherein the one or more tag compliance rules comprise a required syntax for the tag key and a set of permissible values for the tag value. Processing logic determines that the resource fails to comply with the one or more tag compliance rules of the tag policy and performs a remedial action with respect to the resource.

Tag policies for tagging system

Methods, systems, and computer-readable media for parameter variations for computations using a remote repository are disclosed. A first computation is assigned to a first set of one or more hosts. The first computation is associated with first parameters including one or more inputs and program code. A second computation is assigned to a second set of one or more hosts and is associated with a second set of parameters. Execution of the first computation is initiated using the first set of hosts and the first set of parameters. Local copies of the input(s) and program code are obtained from a storage service using a TO credential supplied by a repository manager. Execution of the second computation is initiated using the second set of hosts and the second set of parameters as obtained using a credential supplied by the repository manager.

Parameter variations for computations using a remote repository

A customer of a computing resource service provider submits a request to a service in a first data region to obtain all customer data stored across all data regions managed by the computing resource service provider. Accordingly, the service may refer to a chatter table that includes a listing of locations wherein customer data may be stored to determine which data regions comprise customer data. Based on the determination, the service may transmit one or more requests to other services within the determined data regions to obtain the customer data while ignoring any data regions that do not comprise customer data. Upon receiving the customer data, the service may aggregate this data and provide the aggregated data to the customer to fulfill the customer request.

Method for aggregating distributed data

In a network-based services platform, customer resources may be automatically associated with a resource creator. Upon receipt of a request to create a computing resource, the computing resource may be created and thereafter executed within the network-based services platform. In response to the request, an entity associated with the request may be identified. In response to the identification of the entity, the computing resource may be automatically associated with the identified entity specifying the entity as the creator of the computing resource. In some embodiments, a cost of operating the resource over a period of time may be calculated, and the cost allocated to the identified entity based at least in part on the creator-to-resource association that was automatically generated upon creation of the resource. In this manner, a usage allocation report may be provided to the customer that shows the cost associated with the entity.

Automated association of computing resources with resource creators for usage allocation

Growing community of inventors

Seattle, WA, United States of America

Colin Watson