aws_ebs_default_kms_key returns invalid key_arn

[alekna]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

$ terraform version
Terraform v0.13.2
+ provider registry.terraform.io/hashicorp/aws v3.6.0

Affected Resource(s)

• aws_ebs_default_kms_key
• aws_ebs_volume

Terraform Configuration Files

As per example on https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/ebs_default_kms_key

data "aws_ebs_default_kms_key" "current" {}

resource "aws_ebs_volume" "example" {
  availability_zone = "us-west-2a"

  encrypted  = true
  kms_key_id = data.aws_ebs_default_kms_key.current.key_arn
}

Expected Behavior

• encrypted EBS volume is created

Actual Behavior

$ terraform apply
data.aws_ebs_default_kms_key.current: Refreshing state...

Error: "kms_key_id" (alias/aws/ebs) is an invalid ARN: arn: invalid prefix

  on ec2.tf line 21, in resource "aws_ebs_volume" "example":
  21:   kms_key_id = data.aws_ebs_default_kms_key.current.key_arn

Steps to Reproduce

1. terraform apply

[karnauskas]

Looks like AWS API which returns it: <kmsKeyId>alias/aws/ebs</kmsKeyId> if default key is managed by AWS.
You can work around this with:

data "aws_ebs_default_kms_key" "current" {}

data "aws_kms_key" "current" {
  key_id = data.aws_ebs_default_kms_key.current.key_arn
}

resource "aws_ebs_volume" "example" {
  availability_zone = "us-west-2a"

  encrypted  = true
  kms_key_id = data.aws_kms_key.current.arn
}

[anGie44]

Related #13860

[anGie44]

Hi @alekna, thank you for creating this issue! Given the upstream behavior @karnauskas mentioned above, we can plan to document this behavior in the data-source docs to capture this use case. In the meantime I've provided feedback to the EC2 service team's API documentation.

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[github-actions]

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.