Mechanism to manage group of resources using virtual resource containers
摘要
說明書
In embodiments, the customer A 202A may specify in the resource policy 218 that the customer B 202B may add resources from his/her own account (e.g., Account 456) to the resource container 216. The customer B 202B may attach the table 224 and VM 228 to the resource container 216 via various API requests. The table 224 may be attached with the following API request: AttachResource(ProjectPhobosURN, TablePhobos) to attach the table 224; in the example 200, the table 224 is specified by the URN: “TablePhobos.” The VM 228 may be attached with the following API request: AttachResource(ProjectPhobosURN, VMInstancePhobos) to attach the VM 227; in the example 200, the VM 228 is specified by the URN: “VMInstancePhobos.”
In this manner, the resource container 216 may be configured to allow different customers of a computing resource service provider to share resources with each other and collaborate on a common project. Furthermore, the policies (e.g., the resource policy 218) associated with the resource container 216 may be written to automatically apply to multiple resources, or to certain types of resources, associated with the resource container 216. In this manner, managing policies for resources associated with the resource container 216 is simplified from otherwise having to associate separate policies from different accounts with individual resources.
In some examples, the customer A 202A may configure the resource policy 218 such that the customer B 202B may access the resource container 216. The customer A 202A may configure the resource container policy with the following high-level code:
{
