As per your docs here https://cloud.google.com/storage/docs/reference-uris#cname its not possible to use SSL when also using CNAME. It would be great if you guys could fix this limitation.

Would be a pretty cool feature :)

The Developers Console should have a column to show each bucket's current disk usage.

I'd like to give a service account access to write (upload) to a bucket, but not to delete files. This allows backups to run from the server being backed up to Google Cloud Storage, without concern that an attacker could login and then also destroy all backups from the compromised server itself. This particular example would also be resolved by allowing bucket data to be archived to a different bucket at certain intervals.

The ability to mount via NFS one bucket in a directory on a virtual machine

The Developers Console should allow us to view the existing configuration and change the configuration for lifecycle management and versioning.

The option for copy buckets data between different google accounts

So when you push changes to some git repo, they get automatically synced to GCS! Would be pretty cool.

There should be a way to specify a default cache-control header value of an entire bucket. Currently cache-control maxAge is hard coded to 3600 (1 hour). If you wish to change this, you have to manually specify a cache-control value for each object uploaded using the gcloud CLI.

I suggest a new global bucket preference that changes the default cache-control of all objects that DON'T have a custom cache-control value already provided. I.E. changing this bucket value changes all objects that have a null cache-control provided.

After adding storage write access to a compute engine access scope, gsutil still reported 403 Insufficient Permission.
The fix was to delete ~/.gsutil which then addressed the issue.
This is not obvious to the user. Can gsutil identify if the cache is dirty or at least provide a message to the user on what to do for this issue?

Have an option to archive data to another bucket after a certain age. This archival bucket could be a different class of storage and then permanently delete after a further number of days.

Currently, the Google Storage Transfer Service requires the following Amazon S3 permissions on the bucket:
List the Amazon S3 bucket
Get the location of the bucket
Read the objects in the bucket

I'd love it if there was S3 transfer and migration tooling that doesn't require FULL S3 bucket permissions.

https://cloud.google.com/storage/transfer/configure-access#s3_short_bucket
https://cloud.google.com/storage/transfer/
https://cloud.google.com/storage/docs/migrating