AWS S3 Plugin question

Hi, I’m using the S3 plugin for orthanc. In my logs, I’m getting these lines -

E0723 07:21:54.997797 MAIN PluginsManager.cpp:153] Aws::Config::AWSConfigFileProfileConfigLoaderInitializing config loader against fileName /var/lib/orthanc/.aws/credentials an>
E0723 07:21:54.997828 MAIN PluginsManager.cpp:153] Aws::Config::AWSConfigFileProfileConfigLoaderInitializing config loader against fileName /var/lib/orthanc/.aws/config and usi>
E0723 07:21:54.997889 MAIN PluginsManager.cpp:153] Aws::Config::AWSConfigFileProfileConfigLoaderUnable to open config file /var/lib/orthanc/.aws/credentials for reading.
E0723 07:21:54.997901 MAIN PluginsManager.cpp:153] Aws::Config::AWSProfileConfigLoaderBaseFailed to reload configuration.
E0723 07:21:54.997920 MAIN PluginsManager.cpp:153] Aws::Config::AWSConfigFileProfileConfigLoaderUnable to open config file /var/lib/orthanc/.aws/config for reading.
E0723 07:21:54.997926 MAIN PluginsManager.cpp:153] Aws::Config::AWSProfileConfigLoaderBaseFailed to reload configuration.

Am I supposed to add any config/credentials in /var/lib/orthanc/.aws? I don’t really understand why it’s trying to read a config file from this directory. I added all my bucket details in orthanc.json just like the documentation.

Hi,

I think the AWS plugin tries to find credentials in this file in case it does not have an AccessKey, SecretKey, … You should double check your configuration and have a look at this sample.

HTH,

Alain.

Hi, I am using the docker image but I’m still facing the same issue. I have correctly put the access key and secret key in the docker-compose.yml file and i enabled AwsSdkLogs but i get the same error. Just to confirm, this is not an error on Orthanc’s side right?

My instance has full access to the s3 bucket as well. I’ve set the hop limit to 2 (from another discussion I’d seen). I’m completely stuck.

You should check your startup logs for one of these 2 lines:

Hi Alain, thanks for the response! I wanted to let you know that the issue was resolved. For some reason, the IAM role was not attached properly so i reattached it and it’s all working good now.

1 Like