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(middleware-bucket-endpoint): arn supports fips & handles global regions #2392

Merged
merged 3 commits into from
May 14, 2021

Conversation

AllanZhengYP
Copy link
Contributor

3 formats of ARN s3 accepts is touched in this change: Outposts ARN, AccessPoint ARN,
and ObjectLambda ARN. Here are the changes:

  • All of the 3 ARN formats no longer accept s3 global region: s3-global("s3.amazonaws.com"),
    s3-external-1("s3-external-1.amazonaws.com").
  • Outposts ARN no longer support FIPS region, e.g. fips-us-gov-east-1
  • AccessPoint ARN accepts FIPS regions with a special endpoint format, e.g. {accesspoint-name}-{account-id}.s3-accesspoint[-fips][.dualstack].{region}.{partition}
  • ObjectLambda ARN accepts FIPS regions with a special endpoint format, e.g. {accesspointName}-{accountId}.s3-object-lambda[-fips].{region}.{dnsSuffix}

#JS-2608


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

All ARN-format bucket disallows global client region like s3-external-1
or s3 global endpoint(aws-global). Westeros and Output ARN allows
FIPS region as long as the pseudo region compliant with the arn region
… regions

3 formats of ARN s3 accepts is touched in this change: Outposts ARN, AccessPoint ARN,
and ObjectLambda ARN. Here are the changes:
* All of the 3 ARN formats no longer accept s3 global region: s3-global("s3.amazonaws.com"),
s3-external-1("s3-external-1.amazonaws.com").
* Outposts ARN no longer support FIPS region, e.g. fips-us-gov-east-1
* AccessPoint ARN accepts FIPS regions with a special endpoint format.
* ObjectLambda ARN accepts FIPS regions with a special endpoint format.
@codecov-commenter
Copy link

codecov-commenter commented May 14, 2021

Codecov Report

❗ No coverage uploaded for pull request base (main@597e689). Click here to learn what that means.
The diff coverage is n/a.

❗ Current head 35334b6 differs from pull request most recent head f7bf391. Consider uploading reports for the commit f7bf391 to get more accurate results
Impacted file tree graph

@@           Coverage Diff           @@
##             main    #2392   +/-   ##
=======================================
  Coverage        ?   59.00%           
=======================================
  Files           ?      484           
  Lines           ?    26077           
  Branches        ?     6193           
=======================================
  Hits            ?    15386           
  Misses          ?    10691           
  Partials        ?        0           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 597e689...f7bf391. Read the comment docs.

@AllanZhengYP AllanZhengYP requested a review from trivikr May 14, 2021 17:53
@AllanZhengYP AllanZhengYP merged commit 7b32494 into aws:main May 14, 2021
@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 May 29, 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.

3 participants