This repository was archived by the owner on Nov 15, 2022. It is now read-only.
Add AMI docs #79
Merged
Add AMI docs #79
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
Co-authored-by: devlucassantos <[email protected]> Co-authored-by: gaabrieljesuss <[email protected]>
Co-authored-by: gaabrieljesuss <[email protected]> Co-authored-by: devlucassantos <[email protected]>
Co-authored-by: gaabrieljesuss <[email protected]> Co-authored-by: devlucassantos <[email protected]>
camposer
suggested changes
Mar 14, 2022
ami-variables-user-data.sh.example
Outdated
| @@ -1,5 +1,8 @@ | |||
| #!/bin/bash | |||
|
|
|||
| # Template: | |||
| # echo "MY_VAR=value" >> /etc/sysconfig/log-export-container | |||
|
|
|||
| echo "LOG_EXPORT_CONTAINER_OUTPUT=mongo" >> /etc/sysconfig/log-export-container | |||
There was a problem hiding this comment.
Change this 2 (by default) values to be:
LOG_EXPORT_CONTAINER_INPUT=syslog-jsonLOG_EXPORT_CONTAINER_OUTPUT=stdout
docs/HOW_TO_CREATE_AMI.md
Outdated
|
|
||
| 6. Add tags if you want and click on **Next: Configure Security Group**. | ||
|
|
||
| 7. Now, with the option "Create a new security group" selected, click on **Add Rule** and configure it as follows: |
There was a problem hiding this comment.
Don't go into the details about how to configure the Security Group. Just say that we need to configure it and leave it til there.
docs/HOW_TO_CREATE_AMI.md
Outdated
| This step will take a while and you will know that it has finished when the "PLAY RECAP" message appears (see image below). | ||
|  | ||
|
|
||
| After that Log Export Container should be up and running. |
There was a problem hiding this comment.
You can also mention, that -at this point- LEC can be tested with SDM in case it's needed.
docs/HOW_TO_USE_AMI.md
Outdated
|
|
||
| 6. Add tags if you want and click on **Next: Configure Security Group**. | ||
|
|
||
| 7. In this step you can select an existing security group (if you have already created one from the previous tutorial on [How to create an AMI](docs/HOW_TO_CREATE_AMI.md)) or you can create a new security group as follows: |
There was a problem hiding this comment.
You can remove the reference to the other AMI doc
docs/HOW_TO_USE_AMI.md
Outdated
|
|
||
| 7. In this step you can select an existing security group (if you have already created one from the previous tutorial on [How to create an AMI](docs/HOW_TO_CREATE_AMI.md)) or you can create a new security group as follows: | ||
|
|
||
| With the option "Create a new security group" selected, click on **Add Rule** and configure it as follows: |
There was a problem hiding this comment.
Make a safe comment saying that you need to be careful with the SSH default config, and say that the user might want to change that to an specific IP address.
camposer
approved these changes
Mar 14, 2022
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.
Related #56