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.

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

Obscure error when aws kinesis firehose delivery stream s3 buffer interval is too low #1122

Closed
jleclanche opened this issue Jul 11, 2017 · 2 comments · Fixed by #1881
Closed
Labels
enhancement Requests to existing resources that expand the functionality or scope.

Comments

@jleclanche
Copy link

I tried setting up a aws_kinesis_firehose_delivery_stream and set s3_configuration.buffer_interval to 30. This is below the minimum which is 60. I was greeted by this super unhelpful error:

* aws_kinesis_firehose_delivery_stream.deck_archetype_log_stream: 1 error(s) occurred:

* aws_kinesis_firehose_delivery_stream.deck_archetype_log_stream: [WARN] Error creating Kinesis Firehose Delivery Stream: "1 validation error(s) found.", code: "InvalidParameter"

It took me a while to figure out that the problem was with the buffer interval. I don't know if the problem is in terraform or AWS, but it'd be nice to check for the minimum at plan time either way.

@ApsOps
Copy link
Contributor

ApsOps commented Oct 13, 2017

+1 It gives a similar error when password field size is less than 6. Interestingly, updating the stream gives proper error:

* aws_kinesis_firehose_delivery_stream.kinesis_firehose_redshift: Error Updating Kinesis Firehose Delivery Stream: "test_stream"
InvalidParameter: 1 validation error(s) found.
- minimum field size of 6, UpdateDestinationInput.RedshiftDestinationUpdate.Password.

@radeksimko radeksimko added the enhancement Requests to existing resources that expand the functionality or scope. label Oct 14, 2017
@ghost
Copy link

ghost commented Apr 10, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants