-
Notifications
You must be signed in to change notification settings - Fork 31
added CLI commands for the EC2 page #627
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
added CLI commands for the EC2 page #627
Conversation
Signed-off-by: Jaya Venkatesh <jjayabaskar@nvidia.com>
jacobtomlinson
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall this looks great. I ran into a few technical problems when running the commands, see the comments.
I also think we should include a quick copy/paste cleanup section at the end to delete everything that gets created in here.
Signed-off-by: Jaya Venkatesh <jjayabaskar@nvidia.com>
…ent into cli-instructions Signed-off-by: Jaya Venkatesh <jjayabaskar@nvidia.com>
jacobtomlinson
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried running through these again but ran into a couple more issues
Signed-off-by: Jaya Venkatesh <jjayabaskar@nvidia.com>
Co-authored-by: Jacob Tomlinson <jacobtomlinson@users.noreply.github.com>
Adds CLI commands to create and deploy a EC2 instance with the NVIDIA AMI
To fetch the
AMI_IDfor the NVIDIA GPU-Optimized AMI image, currently a wildcard string matching is being used with the wildcard being*NVIDIA*GPU*VMI*to fetch the latest version as different versions of this AMI have different names with this being the common wildcard string.If there is a better way to filter through all available AMIs to get the
AMI-IDof the latest NVIDIA AMI, that should be incorporated into this page.