Update ec2_create.yaml #8
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Was trying to create same ec2 instance but it was giving error, the missing part in scrip was vpc_subnet_id
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This pull request updates ec2_create.yaml to include a placeholder for the vpc_subnet_id. Previously, the absence of this parameter was causing EC2 instance creation failures. The added placeholder guides users to insert the appropriate subnet ID based on their AWS region.
Changes Made
Added a comment in ec2_create.yaml to specify where to provide the vpc_subnet_id.
Reason
The update prevents creation issues by clarifying where to enter the vpc_subnet_id, improving setup clarity for new users.
Thank you!