Closed asambon closed 2 months ago
Hi @asambon, this appears to be an issue relating to the AWS provider and not Terraform Core. The individual providers are managed in their own repositories by separate teams. For AWS this is https://github.com/hashicorp/terraform-provider-aws. I will close the issue here, but you should reopen this directly with the relevant provider. Thanks!
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 Version
Terraform Configuration Files
Debug Output
Error: creating Secrets Manager Secret Rotation (): operation error Secrets Manager: RotateSecret, https response error StatusCode: 400, RequestID: f65503b7-1e21-49d1-9d26-22c8c6a78d2b, api error ValidationException: Invalid name. Must be a valid name containing alphanumeric characters, or any of the following: -/_+=.@! │ │ with module.backend.module.provisioned_aurora_0_virginia.aws_secretsmanager_secret_rotation.this[0], │ on .terraform/modules/backend.provisioned_aurora_0_virginia/main.tf line 374, in resource "aws_secretsmanager_secret_rotation" "this": │ 374: resource "aws_secretsmanager_secret_rotation" "this" {
Expected Behavior
The secret should be created successfully with the specified name and rotation configuration, as long as the name contains only valid characters (alphanumeric characters, or any of the following: -/_+=.@!).
Actual Behavior
The creation of the secret fails with a ValidationException, claiming the name is invalid despite containing only valid characters.
Steps to Reproduce
Additional Context
Automatic secret rotation was enabled, but the issue occurred in our production environment where we have provisioned Aurora instances. The error seems to happen when updates are made in addition to the automatic secret rotation. This behavior is not present in our non-production environments.
References
No response