This repository has been archived by the owner on Jun 13, 2023. It is now read-only.
separate network resource and ec2 instance creation using data block #36
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
|
@ZacharyWills Please review/approve it when you have time. |
| To run the Terraform configuration, follow these steps: | ||
| ** Note that terraform configuration in network directory will setup initial VPC and subnets, only runs once by administrator. | ||
| To run the Terraform configuration as a user, follow these steps in user directory under terraform: | ||
| As a pre-requisite step, create a key-pair in AWS EC2 console, and place the key in user directory. |
There was a problem hiding this comment.
Might want to list the directory here as the users might not have a lot of experience with AWS.
ZacharyWills
suggested changes
Apr 17, 2023
added 2 commits
April 17, 2023 11:31
jameshalgren
approved these changes
Apr 17, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This change is related to #9.
TODO: find a way to mount S3 bucket into the docker container.