Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
sayden opened this issue Apr 7, 2020 · 7 comments · Fixed by #20887
Closed

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

sayden opened this issue Apr 7, 2020 · 7 comments · Fixed by #20887
Labels
bug Functionbeat Team:Services (Deprecated) Label for the former Integrations-Services team

Comments

@sayden
Copy link
Contributor

sayden commented Apr 7, 2020

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 😄
@andresrc andresrc added [zube]: Inbox Team:Services (Deprecated) Label for the former Integrations-Services team labels Apr 14, 2020
@elasticmachine
Copy link
Collaborator

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

@mgilgar
Copy link

mgilgar commented Jul 13, 2020

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
Copy link
Contributor

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.

@ravinaik1312 ravinaik1312 mentioned this issue Sep 1, 2020
Merged
4 tasks
kvch pushed a commit that referenced this issue Sep 21, 2020
@ravinaik1312
Additional bucket name validation for S3 bucket regex (#20887)
43354ff 
## What does this PR do?

This is a bug fix when functionbeat errors out with a blanket error message. According to me, this error can be mitigated pretty early by validating the S3 bucket name by creating the regex patterns from the rules for bucket naming. 
https://docs.aws.amazon.com/AmazonS3/latest/dev/BucketRestrictions.html#bucketnamingrules

## Why is it important?

This will restrict users from shooting themselves in their foot when they pass an incorrect bucket name in the functionbeat configuration. 

## Related issues

Closes #17572
kvch pushed a commit to kvch/beats that referenced this issue Sep 21, 2020
@ravinaik1312 @kvch
Additional bucket name validation for S3 bucket regex (elastic#20887)
02664c3 
## What does this PR do?

This is a bug fix when functionbeat errors out with a blanket error message. According to me, this error can be mitigated pretty early by validating the S3 bucket name by creating the regex patterns from the rules for bucket naming.
https://docs.aws.amazon.com/AmazonS3/latest/dev/BucketRestrictions.html#bucketnamingrules

## Why is it important?

This will restrict users from shooting themselves in their foot when they pass an incorrect bucket name in the functionbeat configuration.

## Related issues

Closes elastic#17572

(cherry picked from commit 43354ff)
@kvch kvch mentioned this issue Sep 21, 2020
Merged
4 tasks
kvch added a commit that referenced this issue Sep 21, 2020
@kvch @ravinaik1312
Additional bucket name validation for S3 bucket regex (#20887) (#21199)
c925f58 
## What does this PR do?

This is a bug fix when functionbeat errors out with a blanket error message. According to me, this error can be mitigated pretty early by validating the S3 bucket name by creating the regex patterns from the rules for bucket naming.
https://docs.aws.amazon.com/AmazonS3/latest/dev/BucketRestrictions.html#bucketnamingrules

## Why is it important?

This will restrict users from shooting themselves in their foot when they pass an incorrect bucket name in the functionbeat configuration.

## Related issues

Closes #17572

(cherry picked from commit 43354ff)

Co-authored-by: Ravi Naik <ravinaik1312@gmail.com>
@zube zube bot removed the [zube]: Done label Dec 21, 2020
@sunilmchaudhari
Copy link

What is the solution finally?
Sorry I don't know how to track issues and get to the solution from Github.

@ravinaik1312
Copy link
Contributor

This shows that the bugfix is now available in version 7.10.0

@sunilmchaudhari
Copy link

Hi,
Still same error in version 7.10.0 and 7.11

@sunilmchaudhari
Copy link

This is solved by installing and configuring AWS CLI. I could easily upload function in aws. Probably the document need to update for Windows users and add this step under https://www.elastic.co/guide/en/beats/functionbeat/current/functionbeat-installation-configuration.html#setup-assets

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Functionbeat Team:Services (Deprecated) Label for the former Integrations-Services team
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

additional bucket name validation for S3 bucket regex ravinaik1312/beats
6 participants
@andresrc @mgilgar @sayden @ravinaik1312 @elasticmachine @sunilmchaudhari