Diagram
A top-down hierarchy from organization to project to bucket to object, showing folders as a real file system and managed folders as a permission overlay.
How Buckets Organize Objects and Connect to Other Services
Cloud Storage organizes resources in a fixed hierarchy that flows from organization to project to bucket to object. All buckets belong to a project, projects are grouped under an organization, and each project has its own set of Cloud Storage APIs. Resource names make this hierarchy explicit as projects/_/buckets/BUCKET_NAME for buckets and projects/_/buckets/BUCKET_NAME/objects/OBJECT_NAME for objects, where a trailing #NUMBER indicates a generation and #0 is the most recent version.
Within a bucket, folders and managed folders add directory-like control in different ways. Folders exist only in buckets with hierarchical namespace enabled and provide a real file system, so a folder and all objects inside it can be renamed atomically in one operation. Managed folders do not use a true directory tree; a managed folder is a resource overlay used only for permission checking that grants or revokes additional access beyond the Identity and Access Management (IAM) permissions set on the bucket.
Buckets also act as a primary data foundation for other Google Cloud services. Buckets can be connected as storage backends for services such as AI Hypercomputer, Vertex AI, and Google Kubernetes Engine (GKE), so analytics and AI workloads can read directly from object storage. You can work with buckets and objects through the Google Cloud console, the Google Cloud CLI, or client libraries in C++, C#, Go, Java, Node.js, PHP, Python, and Ruby.
Domain 3 of 6
27 practice questions
Practice this DomainLast updated