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
However, I was wondering why it was removed.
I actually wanted to use a different AMI (since I wanted to deploy for inference on a cheaper ARM-based CPU machine on ec2, and the deep learning AMI is an x86 AMI, so I can't use it). Would adding this functionality back be possible? Or alternatively being able to pass in the ID of one of the public AWS AMI's would also be even nicer instead of needing to create our own.
The text was updated successfully, but these errors were encountered:
Via aws ssm get-parameters --names /aws/service/ecs/optimized-ami/amazon-linux-2/arm64/recommended you can find the amiId of the recommended AMI for Arm64-based CPU and put it into your spotty.yaml file.
I think the docs should be updated at https://spotty.cloud/docs/providers/aws/instance-parameters.html
since
spotty aws create-ami
no longer works since it looks like the create-ami command was removed.However, I was wondering why it was removed.
![image](https://user-images.githubusercontent.com/1156974/112708388-1d1bf500-8e88-11eb-9329-5745f8467837.png)
I actually wanted to use a different AMI (since I wanted to deploy for inference on a cheaper ARM-based CPU machine on ec2, and the deep learning AMI is an x86 AMI, so I can't use it). Would adding this functionality back be possible? Or alternatively being able to pass in the ID of one of the public AWS AMI's would also be even nicer instead of needing to create our own.
The text was updated successfully, but these errors were encountered: