IssueTracker

Hey there,

I will try to answer your questions in the fashion you asked:

A. What is the difference between V4 and V2
> The difference is mostly at implementation level, how the signature is constructed. Also, in v4 you cannot create signed urls whose expiration date goes beyond 7 days, whereas this can be set for years using v2. Something else is that v4 is now more suitable to carry out GCS-AWS operations, so if you need this option, this beta would be your only option for it. As this is the main purpose for v4, more details about the signature are left to the AWS documentation [1].

B. On both cases, Google Cloud Storage's Documentation contradicting the SIGNED URL functioning
> I am not sure what you mean by this, could you specify, or you have any specific questions about it?

C. Should I used GCS's provided Signed URL functionality or not for the project which is on production?
> As per any production environment using any technology, it is not recommended to use a Beta product in a production environment.


[1] https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html

Thanks for the answer, My following comment is, Since V4 is in Beta Mode,

A. we may use it as an experimental or testing purpose but not for production?

B. can we use V2 Signing Process for production (even it has some known issues ), As that's not in beta mode, ?, (and we are fine like we do not need to do GCS-AWS Stuff, and even It's possible to create longer duration signed URL)

C. later once we have V4 signing in an official release then we will use V4 signing process?

(and Yes I have tried to use signed URL from both V4 and V2 it works - by using func SignedURL(bucket, name string, opts *SignedURLOptions) available here go/src/cloud.google.com/go/storage at storage.go)

Hello,

Let's go through those:

A. we may use it as an experimental or testing purpose but not for production?
>Correct. You could use it for production if you have no other choice, but it is not recommended for the reason I specified previously. Beta products (of any kind) are subject to unexpected behaviors due the the development stage they are going through. However you can decide to use it under your own responsibility.

B. can we use V2 Signing Process for production (even it has some known issues ), As that's not in beta mode, ?, (and we are fine like we do not need to do GCS-AWS Stuff, and even It's possible to create longer duration signed URL)
>V2 is stable, not beta, but will be deprecated (no ETA). But yes, it can be used (and even better if you do not need to carry out any operations between GCS and AWS as you said).

C. later once we have V4 signing in an official release then we will use V4 signing process?
>Once V4 is in general availability, full support will be provided and its usage over V2 will be encouraged.

To sum up: being the situation as it is, seeing that they both work for you, it would be best using the stable version (V2) and wait for the V4 to be in general availability to change onto it.

Hello,

Due to inactivity of the past few days I assume that you don't need any further assistance regarding the differences with V4 and V2. I will proceed with closing the thread. In case you need any further help, you can reopen it later if needed or create a new Public Issue Tracker if needed.