Google Cloud Storage
Google Cloud Storage is Google Cloud's managed object storage service. You put files and other data into buckets, then control where the data lives, who can access it, how long it stays, and what storage behavior you pay for.
itCloud computing | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Intro
Google Cloud Storage
Google Cloud Storage is a managed object storage service. You store data as objects inside buckets. An object combines bytes, a name, and metadata. A bucket supplies the shared location, access, protection, and lifecycle settings around those objects.
This model differs from a disk or shared file system. An application reaches Cloud Storage through an API, a client library, the Google Cloud CLI, or an HTTP endpoint. It does not receive raw blocks to format. It also does not receive a normal operating-system file system with arbitrary in-place writes.
That distinction guides every design decision. Cloud Storage fits data that your application can read or replace as whole objects. Common examples include media, documents, static web assets, backups, logs, data exchange files, and analytics input.
The resource model
Every bucket belongs to a Google Cloud project. The bucket has a globally unique name and a location. Objects live inside that bucket and have names such as reports/2026/july.csv.
The slash characters in that name can support a folder-like view. The object still has one name unless you use hierarchical namespace features. Do not assume that every object name maps to a directory on a mounted disk.
Cloud Storage assigns a generation number when it creates an object. If an upload replaces an object with the same name, the replacement receives a new generation. Generation and metageneration values also support request preconditions. A precondition lets you reject a write when the object changed after your application last observed it.
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://docs.cloud.google.com/storage/docs/introduction
Supports
- Cloud Storage is a managed object storage service
- Buckets contain objects and belong to projects
- APIs, client libraries, command-line tools, and HTTP endpoints provide access
- Buckets, objects, folders, and managed folders are Google Cloud resources
- https://docs.cloud.google.com/storage/docs/objects
Supports
- Objects have names, data, metadata, and generation identifiers
- Slash characters can support folder-like naming without ordinary file-system semantics
- Replacing an object is atomic
- Generation numbers identify versions of object data
- https://docs.cloud.google.com/storage/docs/bucket-locations
Supports
- Bucket location determines physical placement of object data
- Region, dual-region, and multi-region location types have different replication behavior
- Colocating data and compute can improve performance and lower total cost
- Location affects availability and price
- https://docs.cloud.google.com/storage/docs/storage-classes
Supports
- Storage class is object metadata that affects availability and pricing
- Standard, Nearline, Coldline, Archive, and Rapid address different access patterns
- New objects inherit the bucket default class unless another class is specified
- Changing a bucket default does not alter existing objects
- Autoclass can manage storage classes automatically
- https://cloud.google.com/storage/pricing
Supports
- Nearline, Coldline, and Archive have minimum storage durations
- Pricing includes stored data, operations, retrieval, replication, feature, and network-transfer dimensions
- Early deletion or rewrite can incur minimum-duration charges
- Retrieval and transfer fees depend on bytes accessed
- https://docs.cloud.google.com/storage/docs/access-control
Supports
- Cloud Storage supports IAM and access control lists
- Uniform bucket-level access creates an IAM-only access model
- Public access prevention blocks access through public principals
- Signed URLs provide another access path
- https://docs.cloud.google.com/storage/docs/uniform-bucket-level-access
Supports
- Uniform bucket-level access disables object access control lists
- IAM controls access to buckets and objects after the setting is enabled
- Uniform access supports a simpler policy model than mixed IAM and access control lists
- https://docs.cloud.google.com/storage/docs/access-control/signed-urls
Supports
- Signed URLs grant time-limited access to a specific Cloud Storage request
- Anyone possessing a valid signed URL can use its permission
- Signed URLs can support read, write, or delete access
- Signed URLs use XML API endpoints
- https://docs.cloud.google.com/storage/docs/protection-backup-recovery-overview
Supports
- Soft delete, Object Versioning, retention policies, Bucket Lock, and lifecycle management solve different protection needs
- Protection design depends on recovery and retention requirements
- https://docs.cloud.google.com/storage/docs/soft-delete
Supports
- Soft delete retains deleted buckets and objects during a retention duration
- Authorized users can restore data within that duration
- Soft-deleted data can add storage cost
- Lifecycle rules do not manage soft-deleted objects
- https://docs.cloud.google.com/storage/docs/object-versioning
Supports
- Object Versioning retains noncurrent generations after replacement or deletion
- Noncurrent versions remain accessible until removed
- Versioning and soft delete can be enabled together
- Retained versions incur storage charges
- https://docs.cloud.google.com/storage/docs/lifecycle
Supports
- Lifecycle configurations contain rules applied to current and future objects
- Matching rules can delete objects or change storage class
- Retention policies can prevent lifecycle deletion
- Lifecycle management can act on noncurrent versions
- https://docs.cloud.google.com/storage/docs/bucket-lock
Supports
- Retention policies prevent object deletion or replacement before retention age
- Locking a retention policy is irreversible
- A locked policy cannot be reduced or removed
- https://docs.cloud.google.com/storage/docs/consistency
Supports
- Cloud Storage provides strong global consistency for object reads and listings
- Bucket reads and listings are strongly consistent
- Successful writes are immediately available to reads and metadata operations
- Public cache behavior remains governed by cache settings
- https://docs.cloud.google.com/storage/docs/request-preconditions
Supports
- Generation and metageneration conditions prevent race conditions
- A generation-match value of zero supports create-only behavior
- Preconditions can make eligible operations safe to retry
- ETags can protect metadata requests on supported interfaces
- https://docs.cloud.google.com/storage/docs/retry-strategy
Supports
- Retry safety depends on the response and operation idempotency
- Transient failures should use exponential backoff
- Preconditions can make some mutations conditionally idempotent
- Unbounded, layered, or unconditional retries are anti-patterns
- https://docs.cloud.google.com/storage/docs/encryption
Supports
- Cloud Storage encrypts data on the server side before writing to disk
- Google manages default encryption keys
- Customer-managed, customer-supplied, and client-side options change key responsibility
- Lost customer-controlled keys can make data unreadable
- https://docs.cloud.google.com/storage/docs/encryption/customer-managed-keys
Supports
- Customer-managed keys use Cloud Key Management Service
- Customers control key location, rotation, permissions, and lifecycle
- A Cloud Storage service agent needs permission to use the key
- Disabling or destroying a required key can prevent object decryption
- https://docs.cloud.google.com/storage/docs/discover-object-storage-gcloud
Supports
- The Google Cloud CLI can create buckets and upload, list, download, and delete objects
- The official quickstart provides an ordered introductory practice path
- https://github.com/GoogleCloudPlatform/awesome-google-cloud
Supports
- The curated list is archived
- Its Storage and Databases section links to the official Cloud Storage product page without distinct storage tools