In an embodiment, the resource container service 406 receives an API request 430 to attach a resource, specified by BucketPhobos, to a resource container, specified by ProjectPhobosURN, determines if the resource exists, and utilizes an internal API request to the platform data store 412 to attach the resource to the resource container. In some examples, the internal API request may be configured as the following request: LinkResourceToResourceContainer(ProjectPhobosURN, BucketPhobos), in which ProjectPhobosURN specifies the resource container, and BucketPhobos specifies the resource. The platform data store 412 may locate the storage space allocated for the resource container, and store a link to the resource, which may be a URN such as BucketPhobos, and/or variations thereof.
The customer B 402B may have access to various services and resources associated with the Account 456, but not associated with the Account 123 of customer A 202A. Consequently, the customer A 402A may not normally have access to any of the resources associated with Account 456. The customer B 402B may desire to add such resources to a resource container in order to allow the customer A 402A to access such resources. The customer B 402B may desire to attach a resource, specified by a URN “TablePhobos,” to a resource container, specified by a URN, ProjectPhobosURN. In an embodiment, an owner of the resource container (e.g., the customer A 402A) may have associated a policy with the resource container that grants the customer B 402B access to add or remove resources from the resource container from Account 456 of the customer B 402B.