Victor Renan Covalski Junes

Hi @florian0410. I can't agree with you more on this issue. Until this gets fixed, I've modified my local copy of the module to include an input variable to override...

I'm getting the same error with Logstash 6.5.1 and plugin version v4.1.7. Below is my configuration `output { s3 { region => "us-east-1" bucket => "logstash-poc-logs" canned_acl => "private" rotation_strategy...

@J00MZ you can work around this issue if you use `aws sso get-role-credentials` and provide the access-token that gets stored in your `.aws` directory. https://aws.amazon.com/premiumsupport/knowledge-center/sso-temporary-credentials/