[Docs]: resource/aws_cloudwatch_event_rule

[ericrichtert]

Documentation Link

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_event_rule

Description

We migrated all aws_cloudwatch_event_rule resources from "is_enabled=true" to "state=ENABLED_WITH_ALL_CLOUDTRAIL_MANAGEMENT_EVENTS". But that stopped all scheduled event_rules from being triggered.
AWS explained this as "works as designed" and will implement an error on the combination of a scheduled event_rule and ENABLED_WITH_ALL_CLOUDTRAIL_MANAGEMENT_EVENTS.

Is this something to:

• write down in the docs?
• add as validation?
• both?

References

#34510

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.

[acwwat]

Looks like the AWS API is now returning a 400 error for this scenario:

│ Error: creating EventBridge Rule (capture-aws-sign-in): ValidationException: ENABLED_WITH_ALL_CLOUDTRAIL_MANAGEMENT_EVENTS rule state is not supported with scheduled rule expressions.    
│       status code: 400, request id: c8f01078-41a9-4fc0-a7e3-76997c3189bc

For good measure, I will add a note in the resource doc.

[github-actions]

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