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.

Sign up for GitHub

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

Jump to bottom

Add notice about AWS2 signature version usage not recommended for AWS #484

Closed
dkocher opened this issue Mar 4, 2024 · 0 comments · Fixed by #508
Closed

Add notice about AWS2 signature version usage not recommended for AWS #484

dkocher opened this issue Mar 4, 2024 · 0 comments · Fixed by #508
Assignees
@Cassie205
Labels
s3

Comments

@dkocher
Copy link
Contributor

dkocher commented Mar 4, 2024

The connection profiles 1 using legacy AWS2 signature authentication are not recommended to be used with AWS S3. The use of AWS2 is not supported 2 for AWS-only features such as

  • Key Management Service
  • CloudFront configuration

Footnotes

  1. https://docs.cyberduck.io/protocols/s3/#generic-s3-profiles ↩

  2. Choosing AWS2 profile causes signature mismatch errors with AWS S3 cyberduck#15556 ↩
@dkocher dkocher added the s3 label Mar 4, 2024
@Cassie205 Cassie205 linked a pull request Mar 25, 2024 that will close this issue
Add warning for AWS2 signature authentication #508
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Cassie205 Cassie205

Labels
s3
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add warning for AWS2 signature authentication iterate-ch/docs
2 participants
@dkocher @Cassie205