-
Notifications
You must be signed in to change notification settings - Fork 501
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
docs: added guidance on how to setup acm private ca for istio #287
docs: added guidance on how to setup acm private ca for istio #287
Conversation
… mesh Signed-off-by: Lukonde Mwila <outlier.developer@gmail.com>
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.
As usual, your work read really well! I just have a few small suggestions.
content/security/docs/network.md
Outdated
|
||
|
||
#### Setup Instructions | ||
1. Start by following the same [setup instructions](https://aws.github.io/aws-eks-best-practices/security/docs/network/#setup-instructions) outlined above to complete the following: |
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.
Just an FYI, not required for you to do here: Instead of numbering each step "1.", "2.", "3." and so on, you can number each step "1." As long as you indent any sub-bullets or code blocks three spaces, each step will number sequentially. In the future, if you ever need to insert a step in the middle, you don't have to go through and renumber everything.
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.
Sure thing. Thanks @chrisnegus
Co-authored-by: Chris Negus <striker57@gmail.com>
Co-authored-by: Chris Negus <striker57@gmail.com>
Co-authored-by: Chris Negus <striker57@gmail.com>
Co-authored-by: Chris Negus <striker57@gmail.com>
/lgtm |
Issue #, if available:
Description of changes:
Added guidance on how to set up ACM Private CA as the root CA for Istio in an EKS cluster.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.