hashicorp / terraform-provider-aws

The AWS Provider enables Terraform to manage AWS resources.
https://registry.terraform.io/providers/hashicorp/aws
Mozilla Public License 2.0
9.85k stars 9.19k forks source link

[Docs]: Incorrect Attribute Usage on Verified Access Group #39769

Closed u-blavins closed 2 weeks ago

u-blavins commented 1 month ago

Documentation Link

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/verifiedaccess_group

Description

Within the example usage, it states that to enable SSE encryption through KMS, you need:

resource "aws_verifiedaccess_group" "test" {
  verifiedaccess_instance_id = aws_verifiedaccess_instance_trust_provider_attachment.test.verifiedaccess_instance_id

  server_side_encryption_configuration {
    kms_key_arn = aws_kms_key.test_key.arn
  }
}

but below the snippet (also showing in IDE), server_side_encryption_configuration is not the correct option and should be sse_configuration.

References

Terraform plan output:

│ Error: Unsupported block type
│ 
│   on modules/PayloadCMS/vpc.tf line 46, in resource "aws_verifiedaccess_group" "marketplace_payload_cms":
│   46:   server_side_encryption_configuration {
│ 
│ Blocks of type "server_side_encryption_configuration" are not expected here.

Would you like to implement a fix?

Yes

github-actions[bot] commented 1 month ago

Community Note

Voting for Prioritization

Volunteering to Work on This Issue

stefanfreitag commented 2 weeks ago

Hi @jar-b,

as #39768 is merged to main - any ToDo left here? I am asking because the PR did not contain the "Closes xyz...".

jar-b commented 2 weeks ago

Nothing else to do here, thanks for checking.

Closed via #39768

github-actions[bot] commented 2 weeks ago

[!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.