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/02 19:33:26 UTC

[jira] [Commented] (JCR-3914) Support default aws credential provider chain

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

Shashank Gupta commented on JCR-3914:
-------------------------------------

[~cziegeler] seems related to JCR-3886 where connector connects using IAM user used to spin ec2 instance. 

> 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)