[ 
https://issues.apache.org/jira/browse/HADOOP-18328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564037#comment-17564037
 ] 

Sotetsu Suzugamine commented on HADOOP-18328:
---------------------------------------------

I share a web page that summarizes the S3 on Outposts specification in a 
nutshell.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3OnOutpostsRestrictionsLimitations.html

Currently, storage classes are not implemented in S3A in such a way that they 
can be changed, and all defaults are used, so they are not expected to be 
affected.
The specifications for encryption are as follows.
> By default, all objects stored in the OUTPOSTS storage class are stored by 
> using server-side encryption with Amazon S3 managed encryption keys (SSE-S3). 
> You can also explicitly choose to store objects by using server-side 
> encryption with customer-provided encryption keys (SSE-C).
Also, it is available with the same API as s3.

> S3A supports S3 on Outposts
> ---------------------------
>
>                 Key: HADOOP-18328
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18328
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/s3
>            Reporter: Sotetsu Suzugamine
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, the endpoint for using S3 accesspoint is set as 
> "s3-accesspoint.%s.amazonaws.com" as follows.
> [https://github.com/apache/hadoop/blob/3ec4b932c179d9ec6c4e465f25e35b3d7eded08b/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/ArnResource.java#L29]
> However, "s3-outposts.%s.amazonaws.com" is the preferred endpoint when 
> accessing S3 on Outposts bucket by accesspoint.
> This ticket improves them.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to