Updating language to reflect sigv4 connection to S3. #1838
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jamesls
reviewed
Feb 4, 2019
jamesls
reviewed
Feb 11, 2019
S3 is deprecating sigv2, and so moving forward, the only way to connect to S3 will be with sig v4.
jschwarzwalder
force-pushed
the
patch-2
branch
from
85ec501
to
1d65273
Compare
jamesls
added a commit
that referenced
this pull request
Feb 12, 2019
PR #1838. * jschwarzwalder-patch-2: Updating language to reflect sigv4 connection to S3.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
S3 is deprecating sigv2, and so moving forward, the only way to connect to S3 will be with sig v4.
We can also remove the code sample entirely if desired.