The google cloud platform can be used to perform simple storage management tasks for Google Cloud Storage. Other function which Cloud Platform Console can be used for include:
- Creating and deleting buckets.
- Enabling the Google Cloud Storage API for a project
- Uploading, downloading and deleting various objects
- Managing Identity and Access Management (IAM) policies
An overview about Cloud Platform Console is provided by this page, it also includes the tasks which you can accomplish with the aid of Cloud Platform Console to manage your data. For other tasks which are advanced, you can use the gstil command line tool or any of the client libraries which support Google Cloud Storage.
Various tasks which can be performed with the aid of Google Cloud Platform Console
Whenever you are browsing with data, you’ll be able to perform basic storage management tasks with the aid of Cloud Platform Console. So that you’ll be able to use the Cloud Platform Console, there is need for you to authenticate with Google and have an appropriate permission to complete a particular task. If you are the account owner and you personally create the project, there is likelihood that you’ll have all the permission that is needed to complete the task below. If not, you’ll be added as a project member or you will be given permission to perform actions on a bucket.
Creating a bucket
A flat namespace is used by Google Cloud Storage to store your data but a cloud platform console can be used to create folders and mimic a folder hierarchy. Your data is not stored physically in a hierarchical structure, but is displayed like that in the Cloud Platform Console.
Because there is no notion of folder in the Cloud Storage, the folder suffix and the object name delimiter can be seen when your folders are viewed with gsutil or other command-line tool that work effectively with the Cloud Storage.
You can visit Creating Storage Buckets so as to see a step-by-step guide by which you can create buckets by using the Cloud Platform Console.
Uploading data to a bucket
Data can be uploaded to your bucket by uploading one or more files or a folder which contains files. Whenever you upload a folder, the Google Cloud Platform Console maintains the same hierarchical structure of the folder, as well as all the files and folders contained. The process of upload can be tracked to the Cloud Platform Console with the aid of upload progress window. The progress window can also be minimized so that you can continue working with your bucket.
Visit Uploading Objects for a step-by-step guide for uploading objects to your buckets with the aid of Cloud Platform Console.
Objects can also be uploaded to the Cloud Platform Console by dragging and dropping files as well as folders from your desktop or file manager tool to a bucket or sub-folder which is in the Cloud Platform Console.
Downloading data from a bucket
You can also display an object in your browser by clicking it. If the object cannot be displayed, your browser will download the object instead (or prompt you to download it).
Object can also be displayed in the browser by clicking it. And the object will be displayed by your browser if it cannot be displayed.
Creating and using folders
Because there is no notion of folders in the Google Cloud Storage system, the folders which are created in the Cloud Platform Console provide a convenient way by which you can organize the objects in a bucket. As a visual aid, the Cloud Platform Console shows with a folder icon image so that you’ll be able to differentiate folders from objects.
From inside a bucket or a folder which is the bucket, a new folder can be created by clicking the Create Folder button. Rather than buckets, folders do not have to be unique globally. This means that while a bucket name can only be used if there are no buckets with the same name, the name of folder can be used repeatedly once they are not located in the same bucket or sub-folder.
Various objects which are added to a particular folder would reside inside the folder in the Cloud Platform Console. The reality is that all objects exist at the bucket level, and the directory structure is included in their name. For instance, if a folder is created with the name “pets” and add a file “cat.jpeg” to such folder, the Cloud Platform Console will make it possible for the folder to appear in the folder. However, there is no separate folder entity in reality: the file only exists in the bucket and has the name “pets/cat.jpeg”.
Whenever you are navigating folders in the Cloud Platform Console, a higher level of directory can be accesses by clicking the desired folder or bucket name in the breadcrumb trail above the file lists.
Working with folders in gsutil
When other tools are used to work with your data and buckets, the way the folder is presented may be different from the presentation in the Cloud Platform Console. For instance, so as to see how gsutil interprets folders, see how Subdirectories Work.
Deleting folders, objects, and buckets
Object or folder can be deleted in the Google Cloud Platform Console by selecting the checkbox which is next to it and then clicking the delete button. Whenever a folder is deleted, the object inside it will be deleted as well. It is also important for you to note that object which are marked as shared publicly would be deleted as well from the Cloud Storage to confirm your choice.
You can see Deleting Objects for a step by step instruction to removing objects from your buckets using the Cloud Platform Console.
Deleting buckets
So as to delete bucket, there is no need for you to delete all the folders as well as objects which are inside the bucket. When a bucket containing object is deleted, the Cloud Platform Console would show a dialog which will warn you that the content of the bucket will be deleted. In such situation, you can either chose to continue or cancel the delete.
Visit Deleting Buckets for a step-by-step guide on how to delete bucket from your project using the Cloud Platform Console.
Sharing your data publicly
You can also see Making Data Public for a gradual step on how to share your objects with others by making them accessible publicly. You can either make the individual objects or the entire contents of a bucket publicly accessible.
Whenever an object is shared publicly, a shareable link would appear in the shared publicly column. The shareable link makes references to your objects using the “storage.googleapis.com” domain, which is quite different from the domain used in the Cloud Platform Console to navigate in a bucket. For instance, for a bucket with name “example-bucket” and an object name “image1.JPG,” this will be the public link to share the object http://storage.googleapis.com/example-bucket/image1.JPG. You can visit Accessing Public Data for an example of accessing a publicly shared object.
To stop sharing an object publicly:
You can also stop publicly sharing an individual object in two different ways: one is by deselecting the checkbox in the SHARED PUBLICLY column or by editing the object permissions. When the latter approach is used, remove the anonymous users, which is the entry with allUsers in the column named.
Setting bucket permissions
The access to the Google Cloud Storage can be controlled with the aid of Identity and Access Management (IAM) permissions. For instance, you can set a bucket’s permission so as to allow an entity such as a user or group to view or create objects in your bucket. This can be done when it is inappropriate to add a user as a project team member.
Making a bucket readable to “allAuthenticatedUsers” does not imply that all its objects can be accessed publicly. To make object accessible publicly without Google authentication, just share the object publicly as shown in Making Data Public.
Setting object permissions and metadata
The object in a bucket can be easily and uniformly controlled with the aid of Identity and Access Management (IAM) permissions in the Cloud Platform Console. If you want to customize access for individual objects within a bucket, you can use Access Control Lists (ACLs) or Signed URLs. You can also see Using IAM Permissions for a guide on viewing and editing. Changing ACLs can be checked to see how to change permissions for individual objects.
An object metadata can be configured in the Cloud Platform Console. The metadata of an object controls various aspects on how requests are handled, including the type of content your data represents and the way your data is encoded. Metadata can be set only on one object at once by using the Cloud Platform Console. However gsutil setmeta can be used to set metadata on multiple objects at once.
Filtering objects to view
You can also filter the object you see in the Cloud Platform Console by specifying a prefix in the Filter by prefix text box which is located above the list of objects. The filter will display objects which are beginning with a particular prefix. The prefix only filters objects in your current bucket view; object contained in the folder is not selected.
Giving users project-level roles
Whenever a project is being created, you will be given the ownership role. Other kind of entities like collaborators must be given their personal roles so that they will be able to work with your project’s buckets and objects.
After giving you a role for a project, the name of the project will appear in your list of projects. If you are an existing project owner, you can add a member to your project.
Visit I AM with projects for a guide on how to add and remove access at the project level.