-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[Bug]: aws_chime_voice_connector
errors with ForbiddenException
in new AWS accounts
#33633
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
I updated our pipeline to try this today with the 5.19.0 that came out this morning, and now we have a more descriptive error that confirms suspicion of a deprecated API:
|
Relevant github issue on Chime SDK |
This functionality has been released in v5.22.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. |
Terraform Core Version
1.5.7
AWS Provider Version
5.17.0
Affected Resource(s)
Expected Behavior
Voice Connector should have been provisioned successfully
Actual Behavior
AWS API throws 403 ForbiddenException, despite the IAM user having full
AdministratorAccess
policy directly attached.Relevant Error/Panic Output Snippet
Terraform Configuration Files
main.tf
:variables.tf
Steps to Reproduce
terraform apply
to attempt creatingaws_chime_voice_connector
Error: creating Chime Voice connector: ForbiddenException: Not authorized to call Chime SDK with Account Id xxxxxxxxxxxx
Debug Output
No response
Panic Output
No response
Important Factoids
The AWS Chime team working with us to set up this new service suspects that this issue is because the AWS Terraform Provider is still using the legacy Chime API that has been deprecated and no longer accepts requests from new accounts. I would love to put someone from the provider dev team in touch with them to help resolve.
References
No response
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: