Its a while from this thread but I am having the same issue. I host configuration file on S3 bucket. First I added this bucket to be publically accessible and everything works correctly. I simply pass https://s3.amazonaws.com/... link to my docker run command when I start ignite(I am using docker) and it works ok. But do not want for my s3 bucket to be public. I change this setting, and I add my ec2 instance the role which whom I give s3 full access to it. I also create vpc endpoint allowing access to s3 bucket. When I use aws-cli I am able to download s3 file to my ec2 instance. But I cannot start container providing http://s3.amazonaws.com/.. as configuration input source: It says access denied. Basically, I cannot access to my s3 bucket without using aws-cli. I tried using curl and I also get access denied.
Is there any workaround for this? Tnx -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
