[Enhancement]: Add logging configuration for the event bridge pipe

[srilavanyapaleti]

Description

Logging is supported for Event bridge pipes since Nov, 2023. How ever, in the current terraform event bridge pipe configuration, the logging is not supported. This enhancement request should add the logging configuration support so that the logging settings are configurable via terraform

Affected Resource(s) and/or Data Source(s)

No response

Potential Terraform Configuration

No response

References

No response

Would you like to implement a fix?

No

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[andreswebs]

Hello, I'm interested in working on this feature.

[Wool3673]

Has this issue been resolved else where? The latest docs suggest it has been, but it doesn't seem to work.

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/pipes_pipe#cloudwatch_logs_parameters

Sample error:
Error: updating Amazon EventBridge Pipes Pipe (foo): operation error Pipes: UpdatePipe, https response error StatusCode: 400, RequestID: foo, ValidationException: {"ValidationErrorFields":[{"Name":"CloudWatchLogsParameters","Message":"Invalid target parameter provided for target."}]}

[andreswebs]

Actually no, it's still pending. The docs you linked refer to using CloudWatch logs as a target. This issue is to enable logging from the pipe, but not as a target.

…

On Monday, April 22nd, 2024 at 5:28 AM, Wool3673 ***@***.***> wrote: Has this issue been resolved else where? The latest docs suggest it has been, but it doesn't seem to work. https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/pipes_pipe#cloudwatch_logs_parameters Sample error: Error: updating Amazon EventBridge Pipes Pipe (foo): operation error Pipes: UpdatePipe, https response error StatusCode: 400, RequestID: foo, ValidationException: {"ValidationErrorFields":[{"Name":"CloudWatchLogsParameters","Message":"Invalid target parameter provided for target."}]} — Reply to this email directly, [view it on GitHub](#35216 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AHFPRTXF2POIGQQADYFFE4TY6TCZHAVCNFSM6AAAAABBUGKCN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRYG44TONRXHA). You are receiving this because you commented.Message ID: ***@***.***>

[Wool3673]

Actually no, it's still pending. The docs you linked refer to using CloudWatch logs as a target. This issue is to enable logging from the pipe, but not as a target.
…
On Monday, April 22nd, 2024 at 5:28 AM, Wool3673 @.> wrote: Has this issue been resolved else where? The latest docs suggest it has been, but it doesn't seem to work. https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/pipes_pipe#cloudwatch_logs_parameters Sample error: Error: updating Amazon EventBridge Pipes Pipe (foo): operation error Pipes: UpdatePipe, https response error StatusCode: 400, RequestID: foo, ValidationException: {"ValidationErrorFields":[{"Name":"CloudWatchLogsParameters","Message":"Invalid target parameter provided for target."}]} — Reply to this email directly, [view it on GitHub](#35216 (comment)), or unsubscribe. You are receiving this because you commented.Message ID: @.>

Hello Andres, thanks for replying. I'm sorry but I dont quite understand your response (my fault). I don't understand what you mean by "logging from the pipe but not as the target", is there other means of logging available without using a target? I see different destinations/services, but they seem to be targets.

Slightly off topic question, do you happen to know if due to the cloudwatch_logs_parameters being listed in the documents it should work (seems like that is the case)? I'm trying to figure out if I'm doing something wrong or if there's an issue with this being a relatively new AWS Service to Terraform. I've found issues raised with the sources being a problem, but not for CW as a target.

Edit: I've score out the comment as I realise the error now. I've left it here as I've mentioned it else where.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions]

This functionality has been released in v5.53.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!

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.