Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini menyediakan ringkasan Cloud Storage dan cara kerjanya.
Cloud Storage adalah layanan untuk menyimpan objek Anda di
Google Cloud. Object adalah bagian data yang tidak dapat diubah dan terdiri dari file dalam format apa pun. Anda menyimpan objek di container yang disebut bucket.
Semua bucket terkait dengan project, dan Anda dapat mengelompokkan project Anda di bawah organisasi. Setiap project, bucket, folder terkelola, dan objek di Google Cloud adalah resource di Google Cloud, begitu juga dengan hal-hal seperti instance Compute Engine.
Berikut cara struktur Cloud Storage dapat diterapkan pada kasus dunia nyata:
Organisasi: Perusahaan Anda, yang bernama Example Inc., membuat organisasi Google Cloud
bernama exampleinc.org.
Project: Example Inc. sedang membuat beberapa aplikasi, dan masing-masing terkait dengan sebuah project. Setiap project memiliki kumpulan Cloud Storage API sendiri, serta resource lainnya.
Bucket: Setiap project dapat berisi beberapa bucket, yang merupakan container untuk menyimpan objek Anda. Misalnya, Anda dapat membuat bucket photos untuk semua file image yang dihasilkan aplikasi Anda dan bucket videos terpisah.
Objek: Setiap bucket dapat berisi objek individual yang pada dasarnya tidak terbatas,
seperti gambar bernama puppy.png.
Folder terkelola: Setiap bucket juga dapat berisi beberapa
folder terkelola, yang memberikan akses tambahan di luar akses yang diberikan
ke bucket secara keseluruhan.
Akses tambahan ini berlaku untuk objek yang memiliki awalan yang cocok dengan
nama folder terkelola. Misalnya, Anda dapat membuat folder terkelola animals/, yang memberi pengguna yang ditetapkan akses tambahan ke objek seperti animals/puppy.png dan animals/kitten.png.
Bucket dengan namespace hierarkis yang diaktifkan: Bucket dapat mengaktifkan
namespace hierarkis. Bucket dengan namespace hierarkis yang diaktifkan dapat menyimpan data Anda dalam struktur sistem file logis. Operasi pengelolaan folder memberikan kemampuan pengelolaan dan keandalan, termasuk membuat, menghapus, mencantumkan, dan mengganti nama folder. Namespace hierarkis bermanfaat untuk tugas yang intensif data seperti beban kerja analisis, AI, dan ML karena menawarkan batas QPS awal hingga 8 kali lebih tinggi untuk membaca dan menulis objek dibandingkan dengan bucket tanpa namespace hierarkis yang diaktifkan.
Alat dasar untuk Cloud Storage
Berikut beberapa cara dasar untuk berinteraksi dengan Cloud Storage:
Konsol: Google Cloud console menyediakan antarmuka visual bagi Anda untuk mengelola data di browser.
Google Cloud CLI: Dengan gcloud CLI, Anda dapat berinteraksi dengan Cloud Storage melalui terminal menggunakan perintah gcloud storage.
Library klien: Dengan library klien Cloud Storage, Anda dapat mengelola data menggunakan salah satu bahasa pilihan, termasuk C++, C#, Go, Java, Node.js, PHP, Python, dan Ruby.
REST API: Kelola data Anda menggunakan JSON atau XML API.
Terraform: Terraform adalah alat Infrastructure as code (IaC) yang dapat Anda gunakan untuk menyediakan infrastruktur untuk Cloud Storage.
Cloud Storage FUSE: Cloud Storage FUSE memungkinkan Anda memasang bucket Cloud Storage ke sistem file lokal Anda. Hal ini memungkinkan aplikasi Anda membaca dari bucket atau menulis ke bucket dengan menggunakan semantik sistem file standar.
gRPC: gRPC memungkinkan Anda berinteraksi dengan Cloud Storage. gRPC adalah framework RPC universal open source berperforma tinggi yang dikembangkan oleh Google yang dapat Anda gunakan untuk menentukan layanan menggunakan Protocol Buffers.
Melindungi data Anda
Setelah mengupload objek ke Cloud Storage, Anda memiliki kontrol terperinci terkait cara mengamankan dan membagikan data. Berikut beberapa cara untuk mengamankan data yang Anda upload ke Cloud Storage:
Identity and Access Management: Gunakan IAM untuk mengontrol siapa saja yang memiliki akses ke resource di project Google Cloud Anda. Resource mencakup bucket dan objek Cloud Storage, serta entity Google Cloud lainnya seperti
instance Compute Engine. Anda dapat memberikan jenis akses tertentu ke bucket dan objek pada akun utama, seperti update, create, atau delete.
Hapus sementara: Mencegah kehilangan data secara permanen akibat penghapusan yang tidak disengaja atau berbahaya dengan mempertahankan objek dan bucket yang baru dihapus. Secara default, Cloud Storage mengaktifkan penghapusan sementara untuk semua bucket dengan periode retensi tujuh hari.
Pembuatan Versi Objek: Jika versi aktif sebuah objek diganti atau dihapus, objek tersebut dapat dipertahankan sebagai versi lama jika Anda mengaktifkan Pembuatan Versi Objek.
Pemfilteran IP bucket: Dengan pemfilteran IP bucket, Anda dapat membatasi akses ke bucket berdasarkan alamat IP sumber permintaan dan mengamankan data Anda dari akses tidak sah dari alamat IP atau Virtual Private Cloud (VPC) tertentu.
Nama resource
Setiap resource memiliki nama unik yang mengidentifikasinya, seperti nama file.
Bucket memiliki nama resource dalam bentuk projects/_/buckets/BUCKET_NAME, dengan BUCKET_NAME sebagai ID bucket. Objek memiliki nama resource dalam bentuk projects/_/buckets/BUCKET_NAME/objects/OBJECT_NAME, dengan OBJECT_NAME yang merupakan ID objek.
#NUMBER yang ditambahkan ke akhir nama resource
menunjukkan pembuatan objek tertentu. #0 adalah ID khusus untuk
versi terbaru suatu objek. #0 berguna untuk ditambahkan saat nama objek diakhiri dengan string yang akan ditafsirkan sebagai nomor pembuatan.
Panduan memulai
Untuk mempelajari dasar-dasar penggunaan Cloud Storage, baca panduan berikut:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-18 UTC."],[],[],null,["# Product overview of Cloud Storage\n\nThis page provides an overview of Cloud Storage and how it works.\n\nCloud Storage is a service for storing your [*objects*](/storage/docs/objects) in\nGoogle Cloud. An object is an immutable piece of data consisting of a file of\nany format. You store objects in containers called [*buckets*](/storage/docs/buckets).\n\nAll buckets are associated with a [*project*](/storage/docs/projects), and you can group your\nprojects under an [*organization*](/resource-manager/docs/cloud-platform-resource-hierarchy#organizations). Each project, bucket, managed folder,\nand object in Google Cloud is a *resource* in Google Cloud, as are things such\nas [Compute Engine instances](/compute/docs/instances).\n\nAfter you create a project, you can [create Cloud Storage buckets](/storage/docs/creating-buckets),\n[upload objects](/storage/docs/uploading-objects) to your buckets, and [download objects](/storage/docs/downloading-objects) from your\nbuckets. You can also grant permissions to make your data accessible to\nprincipals you specify or [accessible to everyone on the public internet](/storage/docs/access-control/making-data-public).\n\nThe Google Cloud hierarchy\n--------------------------\n\nHere's how the Cloud Storage structure can apply to a real-world case:\n\n- **Organization** : Your company, called Example Inc., creates a Google Cloud\n organization called `exampleinc.org`.\n\n- **Project**: Example Inc. is building several applications, and each one is\n associated with a project. Each project has its own set of\n Cloud Storage APIs, as well as other resources.\n\n- **Bucket** : Each project can contain multiple buckets, which are containers to\n store your objects. For example, you might create a `photos` bucket for all the\n image files your app generates and a separate `videos` bucket.\n\n- **Object** : Each bucket can contain essentially unlimited individual objects,\n such as an image called `puppy.png`.\n\n- **Managed folder** : Each bucket can also contain multiple\n [managed folders](/storage/docs/managed-folders), which grant additional access beyond the access granted\n to the overall bucket.\n This additional access applies to objects that have a prefix matching the\n managed folder name. For example, you might create an `animals/` managed folder,\n which gives designated users additional access to objects such as\n `animals/puppy.png` and `animals/kitten.png`.\n\n- **Hierarchical namespace enabled buckets** : Buckets can have\n [hierarchical namespace](/storage/docs/hns-overview) enabled. Buckets with hierarchical namespace\n enabled can store your data in a logical file system structure. The folder\n management operations provide reliability and management capabilities, including\n creating, deleting, listing, and renaming folders. Hierarchical namespace is\n beneficial for data-intensive tasks like analytics, AI, and ML workloads as they\n offer up to 8 times higher initial QPS limits for reading and writing objects\n compared to buckets without hierarchical namespace enabled.\n\nBasic tools for Cloud Storage\n-----------------------------\n\nHere are some basic ways you can interact with Cloud Storage:\n\n- **Console** : The [Google Cloud console](https://console.cloud.google.com/storage/browser) provides a visual interface for\n you to manage your data in a browser.\n\n- **Google Cloud CLI** : The [gcloud CLI](/sdk/gcloud) allows you to interact\n with Cloud Storage through a terminal using\n [`gcloud storage` commands](/sdk/gcloud/reference/storage).\n\n- **Client libraries** : The Cloud Storage [client libraries](/storage/docs/reference/libraries) allow\n you to manage your data using one of your preferred languages, including C++,\n C#, Go, Java, Node.js, PHP, Python, and Ruby.\n\n- **REST APIs** : Manage your data using the [JSON](/storage/docs/json_api) or [XML](/storage/docs/xml-api/overview) API.\n\n- **Terraform** : [Terraform](https://www.terraform.io/) is an infrastructure-as-code (IaC)\n tool that you can use to provision the infrastructure for\n Cloud Storage.\n\n- **Cloud Storage FUSE** : [Cloud Storage FUSE](/storage/docs/gcs-fuse) lets you mount Cloud Storage\n buckets to your local file system. This enables your applications to read from\n a bucket or write to a bucket by using standard file system semantics.\n\n- **gRPC** : [gRPC](/storage/docs/enable-grpc-api) lets you interact with Cloud Storage. gRPC\n is a high performance, open source universal RPC framework developed by Google\n that you can use to define your services using Protocol Buffers.\n\nSecuring your data\n------------------\n\nOnce you upload your objects to Cloud Storage, you have fine-grained\ncontrol over how you secure and share your data. Here are some ways to secure\nthe data you upload to Cloud Storage:\n\n- **Identity and Access Management** : Use [IAM](/storage/docs/access-control/iam) to control who has access to the\n resources in your Google Cloud project. Resources include Cloud Storage\n buckets and objects, as well as other Google Cloud entities such as\n [Compute Engine instances](/compute/docs/instances). You can grant principals certain types of access\n to buckets and objects, such as `update`, `create`, or `delete`.\n\n- **Data encryption** : Cloud Storage uses server-side encryption to\n [encrypt your data](/storage/docs/encryption) by default. You can also use supplemental data\n encryption options such as [customer-managed encryption keys](/storage/docs/encryption/customer-managed-keys) and\n [customer-supplied encryption keys](/storage/docs/encryption/customer-supplied-keys).\n\n- **Authentication** : Ensure that anyone who accesses your data has [proper\n credentials](/storage/docs/authentication).\n\n- **Bucket Lock** : Govern how long objects in buckets must be retained by\n [specifying a retention policy](/storage/docs/using-bucket-lock).\n\n- **Soft delete** : Prevent permanent loss of data against\n accidental or malicious deletion by retaining recently deleted objects and\n buckets. By default, Cloud Storage enables [soft delete](/storage/docs/soft-delete)\n for all buckets with a seven day retention period.\n\n- **Object Versioning** : When a live version of an object is replaced or\n deleted, it can be retained as a *noncurrent version* if you\n [enable Object Versioning](/storage/docs/using-object-versioning).\n\n- **Bucket IP filtering** : With [bucket IP filtering](/storage/docs/ip-filtering-overview), you\n can restrict access to a bucket based on the source IP address of the request\n and secure your data from unauthorized access from specific IP addresses or\n Virtual Private Cloud (VPC).\n\n### Resource names\n\n| **Note:** The use of resource names within Cloud Storage is limited to [Pub/Sub Notifications for Cloud Storage](/storage/docs/pubsub-notifications) and [Identity and Access Management](/storage/docs/access-control/iam).\n\nEach resource has a unique name that identifies it, much like a filename.\nBuckets have a resource name in the form of\n`projects/_/buckets/`\u003cvar translate=\"no\"\u003eBUCKET_NAME\u003c/var\u003e, where\n\u003cvar translate=\"no\"\u003eBUCKET_NAME\u003c/var\u003e is the ID of the bucket. Objects have a\nresource name in the form of\n`projects/_/buckets/`\u003cvar translate=\"no\"\u003eBUCKET_NAME\u003c/var\u003e`/objects/`\u003cvar translate=\"no\"\u003eOBJECT_NAME\u003c/var\u003e,\nwhere \u003cvar translate=\"no\"\u003eOBJECT_NAME\u003c/var\u003e is the ID of the object.\n\nA `#`\u003cvar translate=\"no\"\u003eNUMBER\u003c/var\u003e appended to the end of the resource name\nindicates a specific generation of the object. `#0` is a special identifier for\nthe most recent version of an object. `#0` is useful to add when the name of\nthe object ends in a string that would otherwise be interpreted as a generation\nnumber.\n\nQuickstart guides\n-----------------\n\nTo learn the fundamentals of using Cloud Storage, visit the following\nguides:\n\n- [Google Cloud console quickstart](/storage/docs/discover-object-storage-console)\n- [gcloud quickstart](/storage/docs/discover-object-storage-gcloud)\n- [Terraform quickstart](/storage/docs/terraform-create-bucket-upload-object)\n\nWhat's next\n-----------\n\n- Learn the fundamentals of Cloud Storage through the [Google Cloud console](/storage/docs/discover-object-storage-console) or [Google Cloud CLI](/storage/docs/discover-object-storage-gcloud).\n- Try [Google Cloud jump start solutions that use Cloud Storage](/architecture/storage).\n- Get started with [client libraries](/storage/docs/reference/libraries).\n- Quickly import online data into Cloud Storage or between Cloud Storage buckets using [Storage Transfer Service](/storage-transfer/docs/overview)."]]
