[
https://issues.apache.org/jira/browse/JCLOUDS-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561443#comment-17561443
]
Andrew Gaul commented on JCLOUDS-1610:
--------------------------------------
I believe that you only need to add a constant to
{{{}org.jclouds.s3.domain.ObjectMetadata.StorageClass{}}}. However, you will
need to run the integration tests to make sure that this works correctly via:
{noformat}
mvn integration-test -pl :aws-s3 -Plive
-Dtest.aws-s3.identity="${JCLOUDS_IDENTITY}"
-Dtest.aws-s3.credential="${JCLOUDS_CREDENTIAL}"{noformat}
Can you do this and submit a PR via GitHub?
> AWS S3 on outposts support
> --------------------------
>
> Key: JCLOUDS-1610
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1610
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-core
> Affects Versions: 2.5.0
> Reporter: Vincent Shi-Ming Huang
> Assignee: Andrew Gaul
> Priority: Major
>
> When jCloud work in the environment of AWS outposts, we noticed that a GET
> request to outposts S3 will get a response header `x-amz-storage-class:
> OUTPOSTS`. This causes an exception of unsupported storage class.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
