Hi Daniel Hug , seen this post and remember wanting to respond straight away but got distracted.  I've checked again this morning and is working for me.  Do you get any error, maybe visible from the logs?

Patrick Andrew Hartnett 

I should have posted this right away:

Hi Daniel Hug , ahh I see, this is possibly related to the AWS region name you have defined in the plugin settings, can you check?

Note: I am able to reproduce the same exception response from the server when I insert the incorrect name for the AWS region name

Patrick Andrew Hartnett Your guess is correct. It used to work, and it stopped working without any changes on my side, but I guess there is quite a lot of movement in the world of AWS. I am surprised how precise AI (Google Gemini Pro 1.5 in this case) could point out the possible sources for this error. Should have gone that way right away! ;)

Patrick Andrew Hartnett Your guess is correct. It used to work, and it stopped working without any changes on my side, but I guess there is quite a lot of movement in the world of AWS. I am surprised how precise AI (Google Gemini Pro 1.5 in this case) could point out the possible sources for this error. Should have gone that way right away! ;)