I found an old post from Even that mentioned PKG_CONFIG_PATH so I added the
follow and everything works now:
ENV PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
Ashley Mort
Sr. Software Engineer
972-638-6317 office
814-571-3039 cell
From: Ashley Mort
Sent: Friday, November 18, 2022 5:17 PM
To: gdal-de
Using gdal_cp.py, it copies using IAM credentials (and using key credentials
from the curl call). Now I’m even more confused.
I was able to replicate with the docker image osgeo/gdal:latest, so its not
just my own docker image although it could be my own environment.
Will continue to debu
Le 19/11/2022 à 16:00, michael.smith.e...@gmail.com a écrit :
Correct, not a public bucket, which is why the IAM credentials are
needed. If I set them manually, it all works fine.
That's super weird if the result of a range request changes depending on
how credentials have been set... Perhaps
Correct, not a public bucket, which is why the IAM credentials are needed. If I set them manually, it all works fine.[ u02]$ export AWS_ACCESS_KEY_ID=x [ u02]$ gdalinfo /vsis3/grid-dev-publiclidar/estoni
Yes, a 206 response code means success here as we are requesting only
bytes 0-16383. So maybe the file is not a valid TIFF ?
( "grid-dev-publiclidar" must not be so public I guess, because when
trying with my credentials, I get a Access Denied)
Le 19/11/2022 à 15:40, michael.smith.e...@gmail.
I’m seeing that it’s getting a 206 response code, so wouldn’t that indicate
auth is working?
gdalinfo /vsis3/grid-dev-publiclidar/estonia/dtm/estonia_dtm_5m.tif
HTTP: Fetch(http://169.254.169.254/latest/api/token)
HTTP: libcurl/7.86.0 OpenSSL/3.0.7 zlib/1.2.13 libssh2/1.10.0 nghttp2/1.47.0
HTTP:
curl
http://169.254.169.254/latest/meta-data/iam/security-credentials/iam-grid-s3
{
"Code" : "Success",
"LastUpdated" : "2022-11-19T14:30:52Z",
"Type" : "AWS-HMAC",
"AccessKeyId" : "xxx",
"SecretAccessKey" : "x/1ssuwVLuUevA",
"Token" :
"xz6ZANv
Hi Mike,
could you send the output of
curl
http://169.254.169.254/latest/meta-data/iam/security-credentials/iam-grid-s3
Slightly redacted of course, but with the exact formatting. This part of
thee code currently uses a "simple JSON parser"
(https://github.com/OSGeo/gdal/blob/c61d116a469821
Just recently I’m seeing errors using iam profile authentication using /vsis3
drivers in gdal (over multiple versions).
gdalinfo /vsis3/grid-dev-publiclidar/estonia/dtm/estonia-dtm-5m.tif
HTTP: Fetch(http://169.254.169.254/latest/api/token)
HTTP: libcurl/7.86.0 OpenSSL/3.0.7 zlib/1.2.13 libssh2
