You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
terraform is able to create this launch configuration (and the snapshot_id is a valid snapshot) but the autoscaling group is unable to launch instances and the activity history for the autoscaling group shows failed launches with this error message:
Launching a new EC2 instance. Status Reason: Parameter encrypted is invalid. You cannot specify the encrypted flag if specifying a snapshot id in a block device mapping. Launching EC2 instance failed.
I believe that this is essentially the same bug as #1862, but with respect to the aws_launch_configuration resource rather than aws_instance.
The text was updated successfully, but these errors were encountered:
I have the same issue to create ASG from launch instance from template. I did not set any encryption while creating the launch template. any workaround this issue?
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.
ghost
locked and limited conversation to collaborators
Mar 30, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have an
aws_launch_configuration
with anebs_block_device
that looks like this:terraform
is able to create this launch configuration (and the snapshot_id is a valid snapshot) but the autoscaling group is unable to launch instances and the activity history for the autoscaling group shows failed launches with this error message:I believe that this is essentially the same bug as #1862, but with respect to the
aws_launch_configuration
resource rather thanaws_instance
.The text was updated successfully, but these errors were encountered: