Closed prateekrastogi92 closed 5 months ago
Voting for Prioritization
Volunteering to Work on This Issue
Hey @prateekrastogi92 👋 Thank you for taking the time to raise this! That the configuration works with all other regions and the error is an AccessDeniedException
(relating to permissions) indicates that this is almost certainly not a bug with the provider itself. With that in mind, you'd be better served by raising this in one of the community forums, such as the AWS Provider forum. So that we can maintain focus on bugs and feature requests for the provider, I'll be closing this issue.
[!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.
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.
Terraform Core Version
1.7.5
AWS Provider Version
5.41.0
Affected Resource(s)
aws_config_organization_managed_rule
Expected Behavior
The aws_config_organization_managed_rule should create AWS Config rules in eu-central-2 region
Actual Behavior
The same configuration works for all other regions
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
terraform apply
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None