Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id AEDEB200C01 for ; Thu, 5 Jan 2017 00:41:12 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id AD6CC160B44; Wed, 4 Jan 2017 23:41:12 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 021A5160B3A for ; Thu, 5 Jan 2017 00:41:11 +0100 (CET) Received: (qmail 86616 invoked by uid 500); 4 Jan 2017 23:41:11 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 86607 invoked by uid 99); 4 Jan 2017 23:41:11 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2017 23:41:11 +0000 Received: from [192.168.75.153] (c-73-222-138-29.hsd1.ca.comcast.net [73.222.138.29]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id BF9721A02F0 for ; Wed, 4 Jan 2017 23:41:10 +0000 (UTC) From: Denis Magda Content-Type: multipart/alternative; boundary="Apple-Mail=_895079DA-3DD4-4766-9F07-F213CC49A962" Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Old AWS SDK version, why? Date: Wed, 4 Jan 2017 15:41:09 -0800 References: <1483372752362-9824.post@n6.nabble.com> <1483387884027-9825.post@n6.nabble.com> <1483473319758-9855.post@n6.nabble.com> <43E5FB2D-63CA-45A3-9718-963AAAB80F1C@apache.org> <1483557260457-9879.post@n6.nabble.com> To: user@ignite.apache.org In-Reply-To: <1483557260457-9879.post@n6.nabble.com> Message-Id: <96DB8EA5-A78B-48A7-8ECE-2960651D5ECD@apache.org> X-Mailer: Apple Mail (2.3259) archived-at: Wed, 04 Jan 2017 23:41:12 -0000 --Apple-Mail=_895079DA-3DD4-4766-9F07-F213CC49A962 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Chandresh has just updated the SDK version and I=E2=80=99ve merged the = changes to Ignite=E2=80=99s master branch 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. =E2=80=94 Denis > On Jan 4, 2017, at 11:14 AM, zshamrock = wrote: >=20 > Thank you for pointing to the Github discussion, Denis. >=20 > 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: >=20 > Expiry Date: None > Expiration Rule: N/A >=20 > 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. >=20 > 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). >=20 >=20 >=20 > -- > View this message in context: = http://apache-ignite-users.70518.x6.nabble.com/Old-AWS-SDK-version-why-tp9= 824p9879.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. --Apple-Mail=_895079DA-3DD4-4766-9F07-F213CC49A962 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Chandresh has just updated the SDK version and I=E2=80=99ve = merged the changes to Ignite=E2=80=99s master branch

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.

=E2=80=94

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-vers= ion-why-tp9824p9879.html
Sent from the Apache Ignite = Users mailing list archive at Nabble.com.

= --Apple-Mail=_895079DA-3DD4-4766-9F07-F213CC49A962--