[
https://issues.apache.org/jira/browse/JCR-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942576#comment-14942576
]
Carsten Ziegeler commented on JCR-3914:
---------------------------------------
Sorry, ignore my comment from above, I didn't read the source code correctly.
So, yes the default provider chain is already in use.
I think the only thing missing is:
if ( region == null ) {
region = Regions.getCurrentRegion().getName();
}
in Utils.openService
> Support default aws credential provider chain
> ---------------------------------------------
>
> Key: JCR-3914
> URL: https://issues.apache.org/jira/browse/JCR-3914
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Reporter: Carsten Ziegeler
> Priority: Blocker
>
> 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)
