Skip to content

Use V4 signature with london s3 region#28283

Merged
PVince81 merged 1 commit into
masterfrom
s3-london-region
Jul 10, 2017
Merged

Use V4 signature with london s3 region#28283
PVince81 merged 1 commit into
masterfrom
s3-london-region

Conversation

@tomneedham

Copy link
Copy Markdown
Contributor

Description

Forces the use of V4 style AWS signature when using the london region.

Also, consider updating of the AWS library in core: #28282

Motivation and Context

  • Usage of london region is broken without this

How Has This Been Tested?

Tested creating a london s3 external mount

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@tomneedham tomneedham added this to the development milestone Jul 3, 2017
@tomneedham tomneedham self-assigned this Jul 3, 2017
@tomneedham tomneedham requested a review from PVince81 July 3, 2017 08:54

@PVince81 PVince81 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 please also test a non-london location

@PVince81

PVince81 commented Jul 4, 2017

Copy link
Copy Markdown
Contributor

the jenkins needs the boot

@PVince81

PVince81 commented Jul 5, 2017

Copy link
Copy Markdown
Contributor

rebased ⛏

@PVince81 PVince81 force-pushed the s3-london-region branch from f85c300 to 15c5159 Compare July 5, 2017 11:12
@tomneedham

Copy link
Copy Markdown
Contributor Author

This is a hotfix, and the more I see issues around this I think we should look at fixing it properly. I think we may also have a signature issue with the frankfurt region.

@PVince81 PVince81 force-pushed the s3-london-region branch from 15c5159 to c921e2e Compare July 7, 2017 06:24
@PVince81

PVince81 commented Jul 7, 2017

Copy link
Copy Markdown
Contributor

Rebased 🔨

@tomneedham or do you want to abandon this hotfix and go for a cleaner fix ?

I think I'd rather have this in first

@PVince81

Copy link
Copy Markdown
Contributor

stable10: #28349
stable9.1: #28350

@lock

lock Bot commented Aug 3, 2019

Copy link
Copy Markdown

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock Bot locked as resolved and limited conversation to collaborators Aug 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants