-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to Increase Default Root Device from AWS Launch Template #4774
Comments
This appears to be a duplicate of #4553. |
I agree looks similar |
Bug fix pull request submitted: #5632 |
The fix for this has been merged into master and will release with version 1.34.0 of the AWS provider, likely later today. |
This has been released in version 1.34.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
@bflad thanks! |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
I'm testing out creating Launch Templates with aws_launch_template and I'm unable to reproduce a result that I achieved manually through the GUI. Using the GUI I was able to override the default block device for the AMI listed below (see describe image) and give it a larger volume. The GUI shows "Default" for this (see image).
However, when I try & recreate the same thing with terraform it doesn't seem to be possible because even if I omit
delete_on_termination
&encrypted
terraform provides default values for this. When I create a spot request I get errors from the console sayingthe encrypted flag cannot be specified since device /dev/xvda has a snapshot specified.
aws ec2 describe-images --image-ids ami-04351e12
Here is the sample terraform config I am working with.
Community Note
Expected Behavior
I should be able to omit encrypted & delete_on_termination from the block/ebs block and terraform will omit the values to the API and AWS will use Defaults for these blocks.
Actual Behavior
Terraform forces the value when it's omitted to a default value it has stored internally resulting in being unable to overwrite the root device.
The text was updated successfully, but these errors were encountered: