-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
aws_spot_instance_request doesn't assign key or subnetID #2919
Labels
Comments
mrdavidlaing
referenced
this issue
in logsearch/workspace
Aug 3, 2015
catsby
added a commit
that referenced
this issue
Aug 31, 2015
…s_to_aws_spot_request Pass key_name and subnetId to spot instance request - resolves issue #2919
I merged #2954, thanks for fixing it! |
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked and limited conversation to collaborators
May 1, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm attempting to launch a AWS spot instance into an existing VPC subnet using the following
aws_spot_instance_request
resource:A spot instance is created, but there are 2 important issues:
Looking at the debug output, it appears that the
subnetID
andkey_name
settings are not being added to the AWS spot request API call:Is this a bug?
The text was updated successfully, but these errors were encountered: