Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecated path-style request usage for AWS GovCloud #10824

Closed
cyberduck opened this issue Oct 1, 2019 · 7 comments
Closed

Deprecated path-style request usage for AWS GovCloud #10824

cyberduck opened this issue Oct 1, 2019 · 7 comments
Labels
enhancement fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

70c93aa created the issue

The old-style addressing will be deprecated:

Support for the path-style model continues for buckets created on or before September 30, 2020. Buckets created after that date must be referenced using the virtual-hosted model.
-- https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/

Does Cyberduck support the new virtual-hosted style addressing? As far as I understand, DNS buckets are disabled for all S3 host names that don't end with s3.amazonaws.com, for example GovCloud S3.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

We do not use the path-style API.

@cyberduck
Copy link
Collaborator Author

70c93aa commented

Is that true that when I put the bucket name into the Path field it's translated to virtual-host API? Across all regions? I ask because when I check the logs in the Log Drawer I see the requests like GET /{bucket}/?encoding-type=url&max-keys=...
The host is s3.us-gov-east-1.amazonaws.com.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

We use the path-style API in this case because the endpoint is not s3.amazonaws.com.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 9523997.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

d9b8c46 commented

Access to Ceph S3 is broken now.. Ceph doesn't support virtual-hosted style
Is there a chance to add an option for choosing the style?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:9 dimm00]:

Access to Ceph S3 is broken now.. Ceph doesn't support virtual-hosted style
Is there a chance to add an option for choosing the style?

Duplicate for #10888. Please comment there if you are still having issues. If possible provide a temporary test account.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

1 participant