Re: [gdal-dev] Gdal.Open on S3 using IAM roles

2021-04-14 Thread Patrick Young
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 set

Re: [gdal-dev] Gdal.Open on S3 using IAM roles

2021-04-14 Thread Jeannie May
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)

Re: [gdal-dev] Gdal.Open on S3 using IAM roles

2021-04-14 Thread Patrick Young
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 d

[gdal-dev] [ gdal ImportError undefined symbol ]

2021-04-14 Thread 박소원
I use the python 3.8 in cluster server. In this server richdem (0.3.4) and GDAL (2.4.3) is installed. But this function do not work probably due to the gdal import error. (when using richdem.LoadGDAL()) Exception: richdem.LoadGDAL() requires GDAL. But when I import gdal, I got this error message