[
https://issues.jboss.org/browse/JGRP-2109?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-2109:
--------------------------------
OK, [~keremkacel], a few weeks ago, I ported Zalando's natiev-s3-ping to JGroups 4,
and the result is in jgroups-extras [1].
This repo is also supported. The reason the new NATIVE_S3_PING is not in the JGroups repo
is that I don't want to have any dependencies in the JGroups core code. Implementing
NATIVE_S3_PING in jgroups-extras allowed me to use Amazon's AWS SDK as dependency.
I'm closing this issue. If you find issues in NATIVE_S3_PING, create separate new
issues.
Regards,
[1]
https://github.com/jgroups-extras/native-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....
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)