Why I ask. It is not only matter of depending on the latest version, but for AWS, in the specific case, it probably even causes the error.
When EC2 instance is configured with instance profile, as described here, http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html, so new credentials are issued and periodically are renewed. And this is the error we see in the log from time to time (when running Ignite in the clustered mode): /ERROR [tcp-client-disco-reconnector-#5%%] o.a.i.s.d.t.TcpDiscoverySpi [null] - Failed to get registered addresses from IP fi nder on start (retrying every 2000 ms). org.apache.ignite.spi.IgniteSpiException: Failed to list objects in the bucket: at org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.getRegisteredAddresses(TcpDiscoveryS3IpFinder.java:168) ~[ignite-aws-1.7.0.ja r!/:1.7.0] at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.registeredAddresses(TcpDiscoverySpi.java:1600) ~[ignite-core-1.7.0.jar!/:1.7.0] at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.resolvedAddresses(TcpDiscoverySpi.java:1549) ~[ignite-core-1.7.0.jar!/:1.7.0] at org.apache.ignite.spi.discovery.tcp.ClientImpl.joinTopology(ClientImpl.java:475) [ignite-core-1.7.0.jar!/:1.7.0] at org.apache.ignite.spi.discovery.tcp.ClientImpl.access$900(ClientImpl.java:118) [ignite-core-1.7.0.jar!/:1.7.0] at org.apache.ignite.spi.discovery.tcp.ClientImpl$Reconnector.body(ClientImpl.java:1175) [ignite-core-1.7.0.jar!/:1.7.0] at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) [ignite-core-1.7.0.jar!/:1.7.0] Caused by: com.amazonaws.services.s3.model.AmazonS3Exception: The provided token has expired. (Service: Amazon S3; Status Code: 400; Error Code: ExpiredToken; Request ID: EFDFC0BD8F4421AA) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1307) ~[aws-java-sdk-core-1.10.50.jar!/:na] at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:894) ~[aws-java-sdk-core-1.10.50.jar!/:na] at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:597) ~[aws-java-sdk-core-1.10.50.jar!/:na] at com.amazonaws.http.AmazonHttpClient.doExecute(AmazonHttpClient.java:363) ~[aws-java-sdk-core-1.10.50.jar!/:na] at com.amazonaws.http.AmazonHttpClient.executeWithTimer(AmazonHttpClient.java:329) ~[aws-java-sdk-core-1.10.50.jar!/:na] at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:308) ~[aws-java-sdk-core-1.10.50.jar!/:na] at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3595) ~[aws-java-sdk-s3-1.10.29.jar!/:na] at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3548) ~[aws-java-sdk-s3-1.10.29.jar!/:na] at com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:647) ~[aws-java-sdk-s3-1.10.29.jar!/:na] at com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:626) ~[aws-java-sdk-s3-1.10.29.jar!/:na] at org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.getRegisteredAddresses(TcpDiscoveryS3IpFinder.java:128) ~[ignite-aws-1.7.0.ja r!/:1.7.0] ... 6 common frames omitted/ Which probably could be due to S3 library is not being worked properly with EC2 instance profile. So, using the latest S3 AWS SDK, would be a good thing to try, whether this indeed was fixed in the new version. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Old-AWS-SDK-version-why-tp9824p9855.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
