Addition of aws_prometheus_workspace_configuration & aws_prometheus_resource_policy support

[Sudokamikaze]

Is your request related to a new offering from AWS?

Is this functionality available in the 5.100.0 & 6.16

• Yes ✅: aws_prometheus_workspace_configuration Since 5.100.0: https://github.com/hashicorp/terraform-provider-aws/blob/release/5.x/CHANGELOG.md#51000-june-12-2025
• Yes ✅: aws_prometheus_resource_policy Since 6.16: https://github.com/hashicorp/terraform-provider-aws/blob/main/CHANGELOG.md#6160-october-9-2025

Is your request related to a problem? Please describe.

I'd like to include support of aws_prometheus_workspace_configuration and aws_prometheus_resource_policy for example usecases:

aws_prometheus_workspace_configuration:

• Gives an ability to set metrics retention on workspace
• Limits per labels set

aws_prometheus_resource_policy:

• Adds ability to attach policy for cross-account access

Describe the solution you'd like.

• Adds variable to set retention as retention_period_in_days, not required, no default value (to inherit AWS default, share your opinion)
• Adds variable to allow user to pass limits_per_label_set in a map, then creates multiple blocks by for_each + dynamic
• Allows to attach a policy with a switch attach_policy bool, and a variable policy to attach custom user defined policy

Describe alternatives you've considered.

Not applicable

Additional context

I'm willing to open a PR for these changes, their size isn't big and not problematic to implement, I'm opening this FR first to hear maintainers opinion about these features

[bryantbiggs]

sounds great! once #24 lands we can proceed with a PR if you are willing

[Sudokamikaze]

I'll start working on the PR, will let you know once its ready for a review

[Sudokamikaze]

Hey guys, I been wondering should I implement the same thing:

• Workspace resource policy allows addition of custom policy to the prometheus, means theres a clear usecase of cross-account policy attachment

This policy will refer ARN of the prometheus itself, and to avoid circular dependency
Should I implement same approach as terraform s3 module? https://registry.terraform.io/modules/terraform-aws-modules/s3-bucket/aws/latest#bucket-with-a-custom-policy-attached

[antonbabenko]

This issue has been resolved in version 4.2.0 🎉