Yes, you can use the AWS SDK to store objects within google storage.
From Simple migration:
In a simple migration from Amazon S3 to Google Cloud Storage, you can
use your existing tools and libraries for generating authenticated
REST requests to Amazon S3, to also send authenticated requests to
Google Cloud Storage. The changes you need to make to ...
Most of the AWS SDKs mentioned support constructing a custom endpoint, for example as described here for Node.JS.
Setting the endpoint to storage.googleapis.com and using your GCP access credentials should enable you to operate the Google storage backend service "like S3".
I don't know much about Redis/ElasticSearch, but GCS is not really a database-like solution, it is closer to a file storage solution.
If you're looking for database-like storage Google Cloud offers:
If you expect a modest app traffic or alternating high/low traffic it might be more cost-effective (and ...
We had the similar requirement as there needs to be a set of data cached in a server for serving the application (fast processing) and also by end of the day, we would need to sync the data from the cache server to the origin server.
In the longer run, I would suggest to go for Redis as you can have Redis as an intermediate database (caching) and it will ...
Before giving the answer I'd like to clarify that S3 is meant for object storage, meaning that there's no file system involved and thus there are not "directories" per se.
So, an "object" with the name "/avatars/user-123/xyz" might give you the impression that it's stored in the "/avatars/user-123" directory, but there's no directory involved, that's just a ...
Yes, your approach sounds okay to me. I am not sure how you "ship" machines but it is a good idea to use a service account per machine as you can delete the service account key if the machine ever becomes compromised.
You can, and should, fully automate the process of generating the credentials key files using the Google APIs or gcloud cli.
It is ...
It's not currently possible to list all the accessible buckets across all cloud projects, neither in the developer console browser nor via the gsutil command. Both of them only display buckets for one project at a time.
But if you specify a particular project (or stick with the one selected by default) you can list the accessible buckets inside that project ...