- Newest
- Most votes
- Most comments
Hello,
Can you provide details about the Storage (volumes) section of your template?
Do you specify any mount points?
Thank you
The error you're encountering suggests that there might be an issue with the storage configuration in your launch template, specifically related to the "NoDevice" parameter. This error can occur when trying to launch an instance directly from a template, even if the template works fine within an Auto Scaling group.
The "NoDevice" parameter is typically used to suppress devices mapped in the AMI's block device mapping. In your case, it seems that the value "true" for this parameter is causing issues when launching instances outside of an Auto Scaling group context.
To resolve this issue, you can try the following steps:
-
Review the storage configuration in your launch template. Pay special attention to any block device mappings.
-
Look for any "NoDevice" settings in the block device mappings and remove them or set them to a valid value.
-
If you can't find the issue in the console, you might want to use the AWS CLI or SDK to get a more detailed view of the template configuration.
-
Create a new version of the launch template with the corrected storage configuration.
-
If you're still unable to identify the problem, you could try creating a new launch template from scratch, copying over the essential configurations from the working template, but omitting any complex storage configurations initially.
-
Test the new template version or new template by launching a single instance before using it in your Auto Scaling group.
It's worth noting that sometimes, configurations that work in an Auto Scaling group context might need slight adjustments when used for launching individual instances. This could be due to how Auto Scaling interprets and applies certain parameters compared to the EC2 instance launch process.
If the problem persists after these steps, you may need to contact AWS support for more detailed troubleshooting, as there might be an underlying issue with how the template is being interpreted outside of the Auto Scaling group context.
Sources
Create a launch template for an Auto Scaling group - Amazon EC2 Auto Scaling
Troubleshoot Amazon EC2 Auto Scaling: Launch templates - Amazon EC2 Auto Scaling
Relevant content
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago

I only have one volume, using the aws cli i can get the json template description, it has the following excerpt: "EbsOptimized": true, "BlockDeviceMappings": [ { "DeviceName": "/dev/sda1", "Ebs": { "Encrypted": false, "DeleteOnTermination": true, "SnapshotId": "snap-015f004792626a72d", "VolumeSize": 15, "VolumeType": "gp3" } }, { "DeviceName": "/dev/sdp", "NoDevice": "true" } ]
from the console i can not access that 2th volume definition to delete it
According to that doc if you want to omit the device from the block device mapping you should specify an empty string for the NoDevice parameter. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-launchtemplate-blockdevicemapping.html
Thanks!!, Never edited this launch template in any way other than the web console so that value ended there by a bug in the template editor