- Newest
- Most votes
- Most comments
I have been able to rectify the issue partially by using the CLI to deploy an instance using the AMI. We were getting the same error when trying to create a launch template revision, but same deal using the cli it works.
The parameters are identical, in the web ui we locate the image click Launch Instance from AMI then set Instance Type, Key Pair and Network settings. When we hit Launch instance we received the error above. Using the CLI to perform the exact same thing:
aws ec2 run-instances --image-id ami-xxx --count 1 --instance-type t3.medium --key-name xxx --security-group-ids sg-xxx --subnet-id subnet-xxx
It works fine.
scratches head
We have the same issue, but when we try to create a new "launch template". We didnt have any problem until yesterday. Now, we create a new AMI, and when we try to create a new launch template, it asks for "Tenancy". We never had selected anything, only "not include in the template" and now it is mandatory to select something. We try to choose "Shared" but it says that "The selected instance type...". We need a solution, please
The AMI is trying to deploy to a dedicated host. Was this the intended behavior for the AMI or was that accidentally changed in the newer revisions?
No we were not trying to deploy to dedicated, not sure how the dedicated requirement has slipped into the mix. Ill post below on an interesting finding though.
Relevant content
- asked 5 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
Yeah this error appears to affect creating instances, creating launch templates and creating launch template revisions. Interestingly enough when you create a launch template/revision via CLI and it creates it, if you try and create a revision/version without actually touching a single thing you still get this warning. What region are you in ?
I didnt try using CLI, only web interface. I will try using CLI, to see what happens. Region Ireland.
Test done, and you are right! using de CLI everything is ok and I can create new templates without problems, and I can see the new configuration in the web interface, and interact with it. There is some kind of problem in the web interface. Please, fix it