: Amazon S3 Based Discovery NOT USING BasicAWSCredentials
I’m still seeing this error even when passing a value via ‘ref’.
Looks like there’s some ignite lib not getting loaded that can resolve the
awsCredentials property, when running in a spark cluster.
Is there any comprehensive guidance for
if you replace `ref` with just a value?
> Like
>
>
>
>
> Stan
>
> From: Max Barrios
> Sent: 12 декабря 2018 г. 23:51
> To: user@ignite.apache.org
> Subject: Amazon S3 Based Discovery NOT USING BasicAWSCredentials
>
> I am running Apache Ignite 2.6.0
//issues.apache.org/jira/browse/IGNITE-4530.
>
> Does it work if you replace `ref` with just a value?
> Like
>
>
>
>
> Stan
>
> From: Max Barrios
> Sent: 12 декабря 2018 г. 23:51
> To: user@ignite.apache.org
> Subject: Amazon S3 Based Discovery NOT U
@ignite.apache.org
Subject: Amazon S3 Based Discovery NOT USING BasicAWSCredentials
I am running Apache Ignite 2.6.0 in AWS and am using S3 Based Discovery,
However, I DO NOT want to embed AWS Access or Secret Keys in my ignite.xml
I have AWS EC2 Instance Metadata Service for my instances so that the creds
I am running Apache Ignite 2.6.0 in AWS and am using S3 Based Discovery,
However, I DO NOT want to embed AWS Access or Secret Keys in my ignite.xml
I have AWS EC2 Instance Metadata Service for my instances so that the creds
can be loaded from there.
However, there's no guidance or documentation