-
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
aws_sagemaker_domain sharing settings s3 kms key id fails with kms id expecting kms arn #23429
Comments
I think it's related to this: https://github.com/hashicorp/terraform-provider-aws/blob/main/internal/service/sagemaker/domain.go#L108 I don't think there should be an ARN check, since the expected input is an id. |
This same thing is also happening in the s3 resource. e.g.
That code applies fine, but you end up with weirdo behaviour, like ACM Private CA trying to call for that key-id on an AccountId that belongs to AWS. Correct application needs to be .arn, but you can apply with .key_id and it shows up "correct" inside of the S3 properties console. So it also looks like there isn't field validation there, too? |
The same error is true for the |
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. |
Community Note
Terraform CLI and Terraform AWS Provider Version
Providers:
Affected Resource(s)
aws_sagemaker_domain
(maybe aws_sagemaker_user_profile too)Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
Panic Output
Plan output:
Expected Behavior
The KMS Key ID to be accepted.
Actual Behavior
See plan output error.
Steps to Reproduce
Important Factoids
It errors when I provide the KMS key ID. Terraform, the CLI and the console they all point to the KMS key ID, and not the ARN, so not sure why it expects the ARN.
The text was updated successfully, but these errors were encountered: