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

feat(s3): support generating endpoints from multi-region access point #2742

Merged
merged 6 commits into from
Sep 2, 2021

Conversation

AllanZhengYP
Copy link
Contributor

Description

Customizations required to support accessing S3 multi-region access point

Testing

Unit tests


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AllanZhengYP and others added 6 commits September 2, 2021 00:05
* feat(signature-v4): support CRT version of sigv4 signer

integrate with CRT for signing

Sigv4A

add yarn link and V4A presign unit test

yarn change

revert the change of dependencies

address comments from Allan

remove esModuleInterop

class name changed

remove a comment

* feat: add crtSuite, and change to optimise the code

format

formatting crtSutie

verify sigv4a signature

* feat(signature-v4-crt): create crt implementation of sigv4

* feat(client-s3): support MRAP and SigV4a signer

* feat(s3-request-presigner): support MRAP in presign

* chore(signature-v4-crt): update dependencies

* feat(middleware-bucket-endpoint): disable vpce for mrap

* chore: fix bucket endpoint test after rebase

* Revert "feat(middleware-bucket-endpoint): disable vpce for mrap"

This reverts commit acbc92aaafc0bccda9318e5ba11bc938e3447855.
Customer will get DNS error if the VPCE is not supported. But
it's expected behavior

* fix: address feedbacks

* chore: rebase onto upstream

Co-authored-by: Dengke Tang <dengket@amazon.com>
* feat(signature-v4-crt): update deps with latest upstream

* feat(signature-v4-crt): use public version of SigV4a signer

* feat(signature-v4-crt): skip crt signer dependency in non-Node.js runtimes
@github-actions
Copy link

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 and link to relevant comments in this thread.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants