Contribution signatures for tagging

• US 10,536,277 B1
• Filed: 12/22/2015
• Issued: 01/14/2020
• Est. Priority Date: 12/22/2015
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Kruse, William Frederick Hingle, Cahill, Conor Patrick, Canton, Jeffrey Cicero, Frenkel, Dmitry, Kulkarni, Harshad Vasant, Watson, Colin, Mikulski, Andrew Paul
• Primary Examiner(s): Le, Chau
• Assistant Examiner(s): Little, Vance M
• Application Number:
  US14/979,308
• Time in Patent Office: 1,484 Days
• CPC Class Codes: G06F 12/1408 by using cryptography for digital transmission H04L9/00
• CPC Class Codes: G06F 21/604 Tools and structures for managing or administering access control systems
• CPC Class Codes: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures
• CPC Class Codes: G06F 2212/402 Encrypted data
• CPC Class Codes: H04L 63/061 for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 9/3247 involving digital signatures

Abstract

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).

Claims

1. A computer-implemented method, comprising:

receiving, to a resource management service, a first request to provision a resource in a multi-tenant environment and on behalf of a customer, the first request including a first key-value pair to be applied to the resource on behalf of the customer, the first key-value pair and the first request both digitally signed using a customer cryptographic key;

determining an additional service to perform a task with respect to the first request;

generating, via the resource management service, a second request including a second key-value pair to be added to the resource on behalf of the resource management service, the second key-value pair and the second request both digitally signed using a resource management cryptographic key for the resource management service, the second request including the first request and the first key-value pair both digitally signed using the customer cryptographic key;

forwarding the second request to the additional service;

generating, by the additional service, a third request digitally signed using a service cryptographic key for the additional service, the third request including the second key-value pair and the second request, digitally signed using the resource management cryptographic key, and the first key-value pair and the first request, digitally signed using the customer cryptographic key;

causing the third request to be provided to a notation service of the multi-tenant environment;

determining, from the third request and by the notation service, the first key-value pair and the second key-value pair to be applied to the resource;

determining that the first key-value pair is digitally signed using the customer cryptographic key and the second key-value pair is digitally signed using the resource management cryptographic key;

validating respective digital signatures for the customer cryptographic key, the resource management cryptographic key, and the service cryptographic key contained in the third request to verify contents of the third request;

causing the notation service to apply the first key-value pair and the second key-value pair to the resource; and

provisioning the resource in the multi-tenant environment.

2. The computer-implemented method of claim 1, further comprising:

verifying, by the notation service, that a series of the first request, the second request, and the third request corresponds to a valid request chain for provisioning of the resource on behalf of the customer.

3. The computer-implemented method of claim 1, further comprising:

verifying, by the notation service, that the customer is authorized to have the first key-value pair applied to the resource and the resource management service is authorized to have the second key-value pair applied to the resource.

4. The computer-implemented method of claim 1, further comprising:

determining that one or more additional cryptographic keys is included in the third request for additional recipients receiving at least the second request; and

verifying the additional cryptographic keys before causing the first key-value pair and the second key-value pair to be applied to the resource.

5. A computer-implemented method, comprising:

receiving, from a first source to a receiving component of a computing resource environment, a first request to provision a resource, the first request comprising tagging metadata to be applied to the resource, the first request and the tagging metadata both digitally signed by the first source;

generating a second request digitally signed by the receiving component, the second request including additional metadata and including the first request and the tagging metadata both signed by the first source;

receiving the second request in a processing component of the computing resource environment;

analyzing, the second request to determine that the second request is signed by the receiving component, the first request is signed by the first source, and the tagging metadata is signed by the first source;

validating a first signature for the first request and a second signature for the second request to verify contents of the second request;

processing the second request to cause, the tagging metadata to be applied to the resource; and

provisioning the resource.

6. The computer-implemented method of claim 5, wherein the processing component is a notation service for the computing resource environment, and further comprising:

causing the tagging metadata to be stored to a metadata repository for the computing resource environment, the metadata repository searchable, using a search key and an associated value, by the notation service to determine metadata that are currently applied to resources in the computing resource environment.

7. The computer-implemented method of claim 6, further comprising:

causing at least the first signature to be stored with the tagging metadata in the metadata repository, the first signature indicating a source of the tagging metadata for the resource.

8. The computer-implemented method of claim 5, further comprising:

determining that a specific instance of metadata to be applied to the resource is not signed by a customer associated with the tagging metadata;

determining that the second request includes a token indicating that the receiving component is authorized to have the specific instance of metadata applied to the resource on behalf of the customer; and

causing the specific instance of metadata to be applied to the resource.

9. The computer-implemented method of claim 8, further comprising:

verifying a request chain contained in the token before causing the specific instance of metadata to be applied to the resource.

10. The computer-implemented method of claim 8, wherein the token includes a signature generated using a customer cryptographic key associated with the customer.

11. The computer-implemented method of claim 5, wherein the second request includes additional requests for additional services to perform tasks associated with the resource after having received the first request, each additional request in the additional requests digitally signed by an additional service of the additional services.

12. The computer-implemented method of claim 11, wherein each additional service of the additional services is further enabled to include additional metadata to be applied to the resource, each instance of additional metadata digitally signed by the additional service providing the additional metadata.

13. The computer-implemented method of claim 12, further comprising:

verifying a request chain for the second request, the request chain including a respective request for a source of the first request, the receiving component, and each additional service of the additional services.

14. The computer-implemented method of claim 13, further comprising:

verifying an order of the respective requests contained within the request chain.

15. The computer-implemented method of claim 13, further comprising:

analyzing at least one policy for the resource to determine whether the tagging metadata is authorized to be applied to the resource.

16. A system, comprising:

at least one processor; and

memory including instructions that, when executed by the at least one processor, cause the system to;

receive, from a first source to a receiving component of a computing resource environment, a first request to provision a resource, the first request comprising tagging metadata to be applied to the resource, the first request and the tagging metadata signed by the first source;

generate a second request signed by the receiving component, the second request including additional metadata and including the first request and the tagging metadata both signed by the first source;

receive the second request in a processing component of the computing resource environment;

analyze, the second request to determine that the second request is signed by the receiving component, the first request is signed by the first source, and the tagging metadata is signed by the first source;

validate a first signature for the first request and a second signature for the second request to verify contents of the second request;

process the second request to cause, the tagging metadata to be applied to the resource; and

provision the resource.

17. The system of claim 16, wherein the instructions when executed further cause the system to:

verify a request chain for the second request, the request chain including a respective request for a source of the first request, the receiving component, and each additional service associated with additional requests within the second request.

18. The system of claim 16, wherein the instructions when executed further cause the system to:

cause the tagging metadata to be stored to a metadata repository for the computing resource environment, the metadata repository searchable by a notation service to determine metadata currently applied to resources in the computing resource environment.

19. The system of claim 18, wherein the instructions when executed further cause the system to:

cause at least the first signature to be stored with the tagging metadata in the metadata repository, the first signature indicating a source of the tagging metadata for the resource.

20. The system of claim 16, wherein the second request includes additional requests for additional services having received the first request, each additional request in the additional requests digitally signed by an additional service of the additional services.