[jboss-jira] [JBoss JIRA] (JGRP-2109) S3_PING: add support for instance metadata

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405008#comment-13405008 ] 

Bela Ban edited comment on JGRP-2109 at 5/11/17 7:28 AM:
---------------------------------------------------------

Sorry, I cannot deprecate S3_PING, at least for the time being, as GOOGLE_PING depends on it. Until I haven't re-implemented GOOGLE_PING with an implementation that uses the GCP SDK, I have to rely on S3_PING.


was (Author: belaban):
Sorry, I cannot deprecate S3_PING, at least for the time being, as GOOGEL_PING depends on it. Until I haven't re-implemented GOOGLE_PING with an implementation that uses the GCP SDK, I have to rely on S3_PING.

> S3_PING: add support for instance metadata
> ------------------------------------------
>
>                 Key: JGRP-2109
>                 URL: https://issues.jboss.org/browse/JGRP-2109
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Kerem Kacel
>            Assignee: Bela Ban
>             Fix For: 4.1
>
>
> The AWS libraries used by S3_PING do not support authenticating into the AWS API via the EC2 instance profile (implicit credentials stored on the AWS EC2 instance).
> The AWS SDK for Java supports instance profile. This eliminates the need for storing AWS access keys in config files.
> Are there any plans to add official support for this in JGroups?
> Resources:
> http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/java-dg-roles.html
> http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html
> Example third-party protocols:
> https://github.com/tagbangers/jgroups-s3-client-ping
> https://github.com/mcacker/jgroups-native-s3-ping



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)