You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Shashank Gupta (JIRA)" <ji...@apache.org> on 2015/10/16 08:49:05 UTC
[jira] [Commented] (JCR-3914) Support default aws region
[ https://issues.apache.org/jira/browse/JCR-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960252#comment-14960252 ]
Shashank Gupta commented on JCR-3914:
-------------------------------------
[~cziegeler] one AWS S3 region can have multiple endpoints and externalized endpoint takes precedence over derived one. see JCR-3732 & [1]
I will provide a patch and you check it out if its works as expected.
[1]http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region
> Support default aws region
> --------------------------
>
> Key: JCR-3914
> URL: https://issues.apache.org/jira/browse/JCR-3914
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Affects Versions: 2.11.1
> Reporter: Carsten Ziegeler
> Priority: Blocker
> Fix For: 2.11.2
>
> Attachments: patch.txt
>
>
> The aws s3 support (jackrabbit-aws-ext module) only supports providing the credentials through a file and through an OSGi configuration. However, in general all aws related services provide more configuration values, especially when running aws it makes sense to support the metadata service.
> I suggest therefore to use com.amazonaws.auth.DefaultAWSCredentialsProviderChain.
> Similar goes for the region, when running in aws,
> Region region = Regions.getCurrentRegion();
> provides automatically the correct region.
> An OSGi configuration can be used for compatibility or testing to override things
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)