[Functionbeat] Wrong error message when using a bucket which doesn't exists in AWS

[sayden]

When using cloudwatch Functionbeat with a non existing bucket, you get the following error message:

Function: cloudwatch, could not deploy, error: bucket 'sdfja;sdlkfja;lsdkjfa;lsdkfjalksdjhfg928y3zs' already exist and you don't have permission to access it

Obviously, bucket sdfja;sdlkfja;lsdkjfa;lsdkfjalksdjhfg928y3zs does not exists 😄

[elasticmachine]

Pinging @elastic/integrations-services (Team:Services)

[mgilgar]

I have the same issue, just following the example in the documentation, nothing fancy https://www.elastic.co/guide/en/beats/functionbeat/current/functionbeat-configuration.html

[ravinaik1312]

I think this is coming from the catch all error here, I believe we can stop something like this pretty early on where we are validating the configuration, can send in a PR soon.