ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@apache.org>
Subject Re: Old AWS SDK version, why?
Date Wed, 04 Jan 2017 23:41:09 GMT
Chandresh has just updated the SDK version and I’ve merged the changes to Ignite’s master
branch
https://issues.apache.org/jira/browse/IGNITE-4519 <https://issues.apache.org/jira/browse/IGNITE-4519>

You can build the project from sources and check if the SDK version was a cause of your issue.

—
Denis

> On Jan 4, 2017, at 11:14 AM, zshamrock <aliaksandr.kazlou@gmail.com> wrote:
> 
> Thank you for pointing to the Github discussion, Denis.
> 
> If I understood it correctly, it doesn't apply to my case (at least
> according to my understanding of the topic). I've checked the expire
> properties of the S3 objects, and they are not set:
> 
> Expiry Date: 	None
> Expiration Rule: 	N/A
> 
> Also I run another services using the same IAM role, and I don't see similar
> error happening for any of the other services in use.
> 
> Again, it still can be due to some IAM policy misconfiguration, but I would
> like to try with the latest AWS SDK to be sure (as I expect S3 SDK should
> handle instance profile token expiration by itself, which potentially it
> doesn't).
> 
> 
> 
> --
> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Old-AWS-SDK-version-why-tp9824p9879.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.


Mime
View raw message