☁️ Google Cloud Storage

1. What is Cloud Storage?

Cloud Storage = Google Cloud's Object Storage service.

It is mainly used to store large amounts of data, especially files such as:

🖼️ Images
🎥 Videos
🎵 Audio
📄 Documents
💾 Backups
📦 Archived data

It is fully managed and scalable, so you don't have to manage physical disks or storage servers.

2. What is Object Storage?

There are 3 common ways to store data:

Storage type	How data is stored	Example
File Storage	Files + folders	`Documents/photo.jpg`
Block Storage	Blocks/chunks of a disk	VM disk
Object Storage	Objects	Image/video stored as an object

Simple example

Suppose you upload:

holiday.jpg

In object storage, the object contains:

Actual data
→ the image itself

Metadata
→ information about the image

For example:


File: holiday.jpg
Created: 2 Sept 2026
Type: image/jpeg
Author: Shivam
Permissions: Read

Unique ID
→ identifies the object.

So you can think:

Object = Data + Metadata + Unique Identifier

3. Why is Object Storage good for the Internet?

Each object can be identified using a unique key/URL.

For example:


https://storage.googleapis.com/my-bucket/photo.jpg

This makes object storage very useful for web applications.

For example:


User → Website → Cloud Storage → Image

A website can retrieve an image/video directly from Cloud Storage.

4. What is a Bucket?

Cloud Storage organizes objects inside buckets.

Think of:


Cloud Storage
     ↓
   Bucket
     ↓
 ┌───────────┐
 │ photo.jpg │
 │ video.mp4 │
 │ backup.zip│
 └───────────┘

Important:

Bucket = container for objects

A bucket has:

Globally unique name
Geographic location

Example:


Bucket name: my-company-backup-123
Location: Europe

5. Choosing Bucket Location

You should generally place storage close to your users/applications to reduce latency.

Example

If most users are in Europe:


Users → Europe
          ↓
    Cloud Storage
      Europe

This can provide better latency than putting the bucket far away.

Google Cloud provides different location choices, including:

Region
Dual-region
Multi-region

For the course example:

European users → Europe region or EU multi-region

6. What does Immutable mean?

Cloud Storage objects are immutable.

That sounds complicated, but the idea is simple:

You don't directly modify an existing object. A new version is written when the object's contents change.

Suppose:


photo.jpg
Version 1

You change the image:


photo.jpg
Version 2

Without versioning, the newer version normally replaces/overwrites the old one.

7. Object Versioning

You can enable Object Versioning on a bucket.

Without versioning:


photo.jpg V1
     ↓
photo.jpg V2
     ↓
V1 overwritten

With versioning:


photo.jpg
 ├── Version 1
 ├── Version 2
 └── Version 3

This allows you to:

See older versions
Restore an older version
Delete a particular version permanently

Example

You accidentally overwrite:


important.pdf

If versioning is enabled, you can potentially restore the previous version.

8. IAM and Access Control

Cloud Storage may contain sensitive information, so access control is important.

Google Cloud mainly uses IAM for controlling access.

Think:

IAM = Who can do what?

Example:


Developer → Read objects
Admin     → Read + Write + Delete
Viewer    → Read only

The goal is least privilege:

Give a user only the permissions they actually need.

9. IAM vs ACL

IAM

IAM is generally sufficient for most Cloud Storage access-control needs.

Example:


Project
   ↓
Bucket
   ↓
Object

Permissions can be inherited through this hierarchy.

ACL

If you need more granular control, you can use Access Control Lists.

An ACL has two important parts:

1. Scope = WHO?

Example:


user@example.com

or a group.

2. Permission = WHAT?

Example:


READ
WRITE

So:

ACL = Who + What they can do

10. Lifecycle Management

Storage costs money.

Imagine you have:


1 TB → useful today
2 TB → old backups
5 TB → old logs

You may not need all of this forever.

Cloud Storage provides Lifecycle Management to automatically perform actions on objects based on rules.

Example 1

Delete objects older than 365 days:


Object age > 365 days
        ↓
      DELETE

Example 2

Delete objects created before a particular date.

Example 3

If versioning is enabled:


Keep only latest 3 versions

Older versions can be removed according to the lifecycle rule.

⭐ Easy Real-Life Example

Imagine you run YouTube-like application.

Users upload:


video1.mp4
video2.mp4
video3.mp4

You store these videos in:


Cloud Storage Bucket
       ↓
 ┌─────────────┐
 │ video1.mp4  │
 │ video2.mp4  │
 │ video3.mp4  │
 └─────────────┘

Cloud Storage is good because:

Videos are objects
Storage can scale
Users can download content
IAM controls who can access videos
Versioning can preserve old versions
Lifecycle rules can remove old content
Bucket location can be selected close to users

🧠 Remember These 8 Points

For exams/interviews, remember:

Cloud Storage = Object Storage

Object = Data + Metadata + Unique ID
Bucket = Container for objects
Bucket name must be globally unique
Bucket has a location
Objects are immutable
Versioning keeps older object versions
IAM controls access; ACLs provide finer-grained control
Lifecycle policies automatically delete/manage old objects

One-line summary

Cloud Storage is Google's scalable object-storage service, organized into buckets, commonly used for images, videos, backups, archives, and other large binary objects.

Absolutely. This section is mainly about Cloud Storage classes, cost optimization, security, and ways to upload large data.

☁️ Cloud Storage Storage Classes

There are 4 main storage classes:

Storage Class	Best for	Typical access
Standard	Hot/frequently accessed data	Frequently
Nearline	Infrequently accessed data	About once a month or less
Coldline	Very infrequently accessed data	About once every 90 days or less
Archive	Long-term archive/DR	Less than once a year

Easy way to remember

Think of your data like clothes:


🔥 STANDARD
Clothes you wear every day
        ↓
🟡 NEARLINE
Clothes you wear once a month
        ↓
🔵 COLDLINE
Clothes you wear once every 3 months
        ↓
❄️ ARCHIVE
Winter clothes kept for almost the whole year

As access becomes less frequent → storage becomes cheaper, but accessing the data becomes relatively more expensive.

1. Standard Storage 🔥

Used for frequently accessed ("hot") data.

Example:

Website images
Frequently watched videos
Active application data


Application
    ↓
Frequently accesses data
    ↓
STANDARD

Also useful when data is stored only for a short period.

2. Nearline Storage 🟡

Used for infrequently accessed data.

Think:

"I probably need this about once a month or less."

Examples:

Backups
Long-tail multimedia content
Data archives


Access ≈ once a month or less
              ↓
          NEARLINE

It costs less to store than Standard, but access costs are higher.

3. Coldline Storage 🔵

Used for data accessed very rarely.

Think:

"I might need this once every 3 months."

Examples:

Disaster recovery data
Old backups
Infrequently accessed datasets


Access ≈ once every 90 days or less
              ↓
          COLDLINE

4. Archive Storage ❄️

This is the lowest-cost storage class for storing data.

Used when you expect to access data less than once a year.

Examples:

Long-term archives
Online backup
Disaster recovery

But there are trade-offs:

Higher data-access/operation costs
365-day minimum storage duration

So don't choose Archive for data you access frequently.

⭐ Storage Classes — Most Important Table


                    ACCESS FREQUENCY
                          ↓
             High --------------------> Very Low

             Standard → Nearline → Coldline → Archive
                ↑           ↑          ↑          ↑
             Hot data    Monthly    ~90 days   <1 year

And generally:


Storage cost:
Standard > Nearline > Coldline > Archive

Access cost:
Standard < Nearline < Coldline < Archive

So:

Frequent access → Standard
Rare access → colder storage class

5. Common Features of All Storage Classes

Regardless of which class you select, Cloud Storage provides several common characteristics.

Unlimited storage

You can store huge amounts of data without needing to provision a fixed capacity beforehand.

No minimum object size

You don't have to make every object a certain minimum size.

Worldwide accessibility

You can choose storage locations around the world.

High durability

Cloud Storage is designed to keep your data highly durable.

Low latency

Data can be accessed with low latency depending on the location and architecture.

Same experience

The security, tools, and APIs provide a consistent experience across storage classes.

6. Geo-Redundancy 🌍

This is important.

Suppose you store data in multiple geographically separated locations:


             Cloud Storage
                  |
        ┌─────────┴─────────┐
        ↓                   ↓
   Data Center A       Data Center B
      Europe             Europe

If one location experiences a major problem, another location can still have the data.

This is called geo-redundancy.

It helps protect against:

Natural disasters
Data-center failures
Other catastrophic events

Cloud Storage provides geo-redundancy when data is stored in a dual-region or multi-region.

7. Autoclass 🤖

This is a very useful feature.

Normally, you have to decide which storage class your data should use.

But with Autoclass, Cloud Storage automatically changes an object's storage class based on its access pattern.

Example

Suppose:


video.mp4
   ↓
Frequently accessed
   ↓
Standard

After some time nobody accesses it:


video.mp4
   ↓
Not accessed
   ↓
Colder storage class

Later people start accessing it again:


video.mp4
   ↓
Frequently accessed again
   ↓
Standard

So:

Autoclass = Automatically moves data between storage classes to optimize cost.

Very useful when you don't know how frequently each object will be accessed.

8. Do I need to reserve storage?

No.

Cloud Storage follows a pay-for-what-you-use model.

You don't need to say:

"I need to reserve 10 TB."

Instead:


You use 100 GB
      ↓
Pay for what you use

There is no need for prior capacity provisioning.

9. Encryption 🔐

Cloud Storage encrypts your data on the server side before it is written to disk, without an additional charge for this default encryption.

Think:


Your data
   ↓
Google Cloud
   ↓
Encryption 🔐
   ↓
Disk

Also, data traveling between your device and Google is encrypted using:

HTTPS / TLS

For example:


Your Laptop
     ↓
   HTTPS 🔐
     ↓
Google Cloud Storage

So remember:

At rest → encrypted by Cloud Storage
In transit → HTTPS/TLS

10. How can you upload data?

There are several ways.

Method 1 — gcloud storage

You can use the Google Cloud CLI.

For example:


gcloud storage cp myfile.txt gs://my-bucket/

Think:


Your computer
      ↓
gcloud storage
      ↓
Cloud Storage bucket

11. Cloud Console Drag & Drop

You can also upload files through the Google Cloud Console.

Simple:


Cloud Console
     ↓
Bucket
     ↓
Upload
     ↓
Drag & Drop

Good for normal/manual uploads.

12. Storage Transfer Service

What if you have TBs or PBs of data?

Manually uploading everything isn't practical.

That's where Storage Transfer Service comes in.

It is designed for transferring large amounts of online data into Cloud Storage.

Data can come from:


Another cloud provider
        ↓
Different Cloud Storage region
        ↓
HTTP/HTTPS endpoint
        ↓
Cloud Storage

You can also schedule and manage batch transfers.

Remember:

Storage Transfer Service = Large-scale ONLINE data transfer

13. Transfer Appliance 📦

Now imagine you have 1 PB of data sitting in your company's data center.

Uploading it over the internet could take a very long time.

Google provides Transfer Appliance.

Think of it like a giant physical storage server:


Your Data Center
      ↓
Load data onto
Transfer Appliance
      ↓
Ship appliance to Google
      ↓
Google uploads data
      ↓
Cloud Storage

A single appliance can handle up to a petabyte of data according to the course.

Remember:

Transfer Appliance = Physical device for massive data migration

14. Cloud Storage Integrates With Other Google Cloud Services

Cloud Storage isn't isolated.

It works closely with other Google Cloud services.

For example:

BigQuery

You can import/export data between:


BigQuery ↔ Cloud Storage

Cloud SQL


Cloud SQL ↔ Cloud Storage

App Engine

Cloud Storage can store:

App Engine logs
Firestore backups
Images and other application objects

Compute Engine

Cloud Storage can store:

Startup scripts
VM images
Application objects

🧠 Very Important Exam Revision

Remember this flow:


              CLOUD STORAGE
                    │
       ┌────────────┼─────────────┐
       ↓            ↓             ↓
 Storage Classes   Security     Data Transfer
       │            │             │
       ↓            ↓             ↓
 Standard        Encryption    gcloud storage
 Nearline        HTTPS/TLS     Console
 Coldline                      Transfer Service
 Archive                       Transfer Appliance
       │
       ↓
   Autoclass

🔥 One-line definitions

Standard: Frequently accessed data.

Nearline: Accessed roughly once a month or less.

Coldline: Accessed roughly once every 90 days or less.

Archive: Accessed less than once a year; lowest storage cost, but higher access costs and 365-day minimum duration.

Autoclass: Automatically moves objects between storage classes based on access patterns.

Storage Transfer Service: Transfers large amounts of online data.

Transfer Appliance: Physically moves massive amounts of data to Google.

HTTPS/TLS: Encrypts data while traveling between your device and Google.

Server-side encryption: Protects data before it is written to disk.