I'll try to get to this this afternoon. What gdalinfo commands would be
best to reveal the issue?
On Thu, Apr 15, 2021 at 9:28 AM Patrick Young <
patrick.mckendree.yo...@gmail.com> wrote:
> AWS_REGION shouldn't cause problems.
>
> If it was me, I'd just hop onto the box and test by running
AWS_REGION shouldn't cause problems.
If it was me, I'd just hop onto the box and test by running gdalinfo
/vsis3/... with verbose curl config options set and so on and make sure I
could get that working as a sanity check.
On Wed, Apr 14, 2021 at 3:21 PM Jeannie May wrote:
> This is the gdal
This is the gdal setup. None of the AWS keys are set excep region (could
that be an issue). Where would I expect to see the logging - none is
showing up in our logs. Do we need to configure the output to our log?
public GdalClient(IConfigurationStore configStore, ILoggerFactory
loggerFactory)
That should be the behavior, and I use it all the time so I am confident it
works...
Is it possible you have set any of the AWS_* variables in your
EC2/container environment? I think that could spoil it for you.
You can set CPL_CURL_VERBOSE to YES and get an idea of the network requests
GDAL is
See
https://aws.amazon.com/premiumsupport/knowledge-center/iam-assume-role-cli/ ,
they describe how to assume a role and set the usual AWS_*
environment variables that GDAL should pick up.
There's discussion on vsis3 related stuff (e.g. authentication) here:
I'm new to using Gdal. How do I configure gdal to use an IAM role, rather
than defining an aws-Profile?
I get a timeout doing a gdal.Open() on a tiff file on S3 using vsis3, while
trying to use an IAM role.
I'm using MaxRev.Gdal.Core 3.2.0.250. Netcore 3.1 c#, running in a Linux
container.
Note
