data aws_launch_configuration throws Error: Invalid address to set: []string{"ebs_block_device", "0", "no_device"}

[datapromike]

Terraform Version

Terraform v0.12.29
+ provider.aws v3.0.0

Terraform Configuration Files

provider "aws" {
  profile = "default"
  secret_key = var.secret_key
  region     = var.aws_region
}

data "aws_launch_configuration" "launch_config" {
  name = "EA-cluster-LaunchConfig1-19A7XZL8FKR8A"
}

Debug Output

Debug Output

Crash Output

N/A

Expected Behavior

Retrieve launch configuration data

Actual Behavior

Returns Error:

data.aws_availability_zones.available: Refreshing state...
data.aws_launch_configuration.launch_config: Refreshing state...

Error: Invalid address to set: []string{"ebs_block_device", "0", "no_device"}

on marklogic-cf-with-tf-exist-vpc.tf line 40, in data "aws_launch_configuration" "launch_config":
40: data "aws_launch_configuration" "launch_config" {

Steps to Reproduce

terraform apply

Additional Context

There are two EBS devices in the launch configuration, both with encrypted set to false:

 <DescribeImagesResponse xmlns="http://ec2.amazonaws.com/doc/2016-11-15/">
     <requestId>2d9d0dd2-9c9c-42af-a290-31c8eea45ecc</requestId>
     <imagesSet>
         <item>
             <imageId>ami-0b08f9840dc6d5f9b</imageId>
             <imageLocation>aws-marketplace/release-MarkLogic-10.0-4.x86_64.rpm-52ce1567-c738-4208-be90-08b575f2c41d-ami-072912159b2174cd4.4</imageLocation>
             <imageState>available</imageState>
             <imageOwnerId>679593333241</imageOwnerId>
             <creationDate>2020-04-16T13:16:50.000Z</creationDate>
             <isPublic>true</isPublic>
             <productCodes>
                 <item>
                     <productCode>4whbpp8cq0qvbyg98jlvmjod9</productCode>
                     <type>marketplace</type>
                 </item>
             </productCodes>
             <architecture>x86_64</architecture>
             <imageType>machine</imageType>
             <sriovNetSupport>simple</sriovNetSupport>
             <imageOwnerAlias>aws-marketplace</imageOwnerAlias>
             <name>release-MarkLogic-10.0-4.x86_64.rpm-52ce1567-c738-4208-be90-08b575f2c41d-ami-072912159b2174cd4.4</name>
             <description>release-MarkLogic-10.0-4.x86_64.rpm</description>
             <rootDeviceType>ebs</rootDeviceType>
             <rootDeviceName>/dev/xvda</rootDeviceName>
             <blockDeviceMapping>
                 <item>
                     <deviceName>/dev/xvda</deviceName>
                     <ebs>
                         <snapshotId>snap-038f64149ad8b9993</snapshotId>
                         <volumeSize>8</volumeSize>
                         <deleteOnTermination>true</deleteOnTermination>
                         <volumeType>gp2</volumeType>
                         <encrypted>false</encrypted>
                     </ebs>
                 </item>
                 <item>
                     <deviceName>/dev/sdf</deviceName>
                     <ebs>
                         <snapshotId>snap-007fd7e86733caab0</snapshotId>
                         <volumeSize>10</volumeSize>
                         <deleteOnTermination>true</deleteOnTermination>
                         <volumeType>gp2</volumeType>
                         <encrypted>false</encrypted>
                     </ebs>
                 </item>
             </blockDeviceMapping>
             <virtualizationType>hvm</virtualizationType>
             <hypervisor>xen</hypervisor>
             <enaSupport>true</enaSupport>
             <platformDetails>Linux/UNIX</platformDetails>
             <usageOperation>RunInstances</usageOperation>
         </item>
     </imagesSet>
 </DescribeImagesResponse>

References

Appears similar to:

• Invalid address to set: []string{"root_block_device", "0", "encrypted"} #5108

[ghost]

This issue has been automatically migrated to hashicorp/terraform-provider-aws#14572 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-aws#14572.

[ghost]

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.