It should be noted that, in various embodiments, access to a resource that is assigned to multiple resource containers may be constrained by one or more policies of the policies of the multiple resource containers. In some examples, all of the policies of the multiple resource containers may be utilized to constrain access to the resource. In some examples, only certain policies of the multiple resource containers may be utilized to constrain access to the resource. For example, in an embodiment, the particular project that an entity requesting access to the resource is a factor that determines which policy of the policies of the multiple resource containers is applied to the entity. In another example, the resource containers may have a hierarchy, whereby the governing policy for a resource is determined by where the resource container associated with the policy falls in the hierarchy (e.g., policies of a parent resource container may trump conflicting policies of a child resource container, or vice-versa). In various examples, the entity requesting access to the resource, the context surrounding the request to access the resource, and/or variations thereof, may be utilized determine which resource policy of the multiple resource policies of the multiple resource containers is utilized to constrain access to the resource.
Alternatively, in some embodiments, a service or resource associated with a first resource container may be disallowed from being associated with a second resource container unless the service or resource is first disassociated (e.g., by the resource owner or by the resource container owner) from the first resource container. In some examples, a resource container owner refers to a customer (e.g., the customer A 202A) that created and/or administrates the particular resource container.