[Docs] aws_ecs_cluster: Correct documentation to use KMS ARN instead of KMS ID in Fargate Storage configuration #45590
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the library.
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
Description
According to the current acceptance test implementation,
configuration.managed_storage_configuration.fargate_ephemeral_storage_kms_key_idinaws_ecs_clusterresource is expected to be a KMS ARN, not a KMS ID, as #45545 reported.See:
terraform-provider-aws/internal/service/ecs/cluster_test.go
Lines 348 to 357 in a4196fb
The same applies to the
kms_key_idattribute in this block as well:terraform-provider-aws/internal/service/ecs/cluster_test.go
Lines 364 to 373 in a4196fb
This PR updates the documentation including the example and description of
fargate_ephemeral_storage_kms_key_idandkms_key_idinconfiguration.managed_storage_configurationblock.Relations
Closes #45545