IssueTracker

Any update on an ETA to complete?

We tracked the problem down to an upstream component canonicalizing the request URI to the /bucket/object form, which was breaking the signature. We've plumbed the original URI down to use in the signature, so it should be working now.

I am still not able to access domain-based buckets directly (Works as storage.googleapis.com/domain.bucket.com/object, but not domain.bucket.com/object), I still just get a signature error.

Also, as a side note, AWS gives more debug output in their error that makes it much easier to debug this issue.

Thanks for checking Matt. The API should return the string to sign GCS calculated. We can also return the calculated Canonical Request, is there anything else that would be helpful?

I think the string to sign and the canonical request are what AWS returns when it throws the same error, and having the canonical request would be hugely helpful in this case. I don't have perms to see the 63114020 issue you added as a blocker, is that an issue for the domain buckets?

Just checking back on this.  Any status update?

We have the fix working in our test environment, but it's waiting for rollout to production. It's stacked up behind several other changes, but I'll update here once the rollout starts. We're looking at ~3 weeks.

The fix is finally live! I just tested with the aws python example, and the bucket.storage.googleapis.com form is working. Please let me know if it works for you.

Canonical Request:  GET
/

host:my-test-bucket.storage.googleapis.com
x-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date:20170815T171638Z

host;x-amz-content-sha256;x-amz-date
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
String To Sign:  AWS4-HMAC-SHA256
20170815T171638Z
20170815/us-east-1/ec2/aws4_request
3dde853f8dbfa9194c3a63df51a970ecf4cc782270ba38a50ed5928d9e6a1a21

BEGIN REQUEST++++++++++++++++++++++++++++++++++++
Request URL = https://my-test-bucket.storage.googleapis.com?

RESPONSE++++++++++++++++++++++++++++++++++++
Response code: 200

I'm just testing a basic GET, but I'm able to do that to a domain name bucket now as well, so looks better here.

Great, I'll mark this as fixed for now. Let me know if you hit any snags.