[
https://issues.apache.org/jira/browse/IGNITE-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15805876#comment-15805876
]
Aliaksandr Kazlou commented on IGNITE-4530:
-------------------------------------------
According to IAM Best Practices, it is a recommended way to launch EC2
instances where application running there needs to talk to AWS services
http://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#use-roles-with-ec2.
And assuming that most of the people are following the best practices from the
above, and Apache Ignite is running on those EC2 instances in the clustered
mode using S3 as an IP finder source, then it is pretty common issue people
will encounter.
> Passing AWSCredentialsProvider to TcpDiscoveryS3IpFinder
> --------------------------------------------------------
>
> Key: IGNITE-4530
> URL: https://issues.apache.org/jira/browse/IGNITE-4530
> Project: Ignite
> Issue Type: Bug
> Reporter: Denis Magda
>
> {{TcpDiscoveryS3IpFinder}} accepts credentials in a form of
> {{AWSCredentials}} only. This might not be enough for all the cases. In a
> situation when the credentials get expired a special instance of
> {{AWSCredentialsProvider}} can renew them automatically.
> However, the credentials will not be updated if {{StaticCredentialsProvider}}
> is used. This provider is created automatically if user provides raw
> {{AWSCredentials}}.
> We need to add new method to {{TcpDiscoveryS3IpFinder}} that will accept
> {{AWSCredentialsProvider}}:
> {code}
> public void setAwsCredentialsProvider(AWSCredentialsProvider provider) {
> {code}
> A new test has to be added to {{TcpDiscoveryS3IpFinderSelfTest}} as well.
> For more details refer to a discussion on the user list:
> http://apache-ignite-users.70518.x6.nabble.com/Old-AWS-SDK-version-why-td9824.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
