-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
[Enhancement]: aws_pipes_pipe
- Support self managed kafka as a source
#31330
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
aws_pipes_pipe
- Support self managed kafka as a source
This should be fixed by #28153 (comment) |
@jordanfinners Thanks for the quick work! |
This functionality has been released in v5.6.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Description
On the AWS EventBridge console you can configure a pipe to connect to a Self Managed Apache Kafka instance as a source. You can then choose an authentication type and specify a credentials secret in Secrets Manager so you can successfully connect to a private topic.
As far as I'm aware, this same functionality is not available in the TF
aws_pipes_pipe
resource.Affected Resource(s) and/or Data Source(s)
aws_pipes_pipe
Potential Terraform Configuration
References
https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-pipes-kafka.html
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: