iSharkFly-Docs
/
opensearch-docs-cn
mirror of https://github.com/iSharkFly-Docs/opensearch-docs-cn
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Addressing Tar installation feedback (#4392) 

* updated step 2

Signed-off-by: Heather Halter <hdhalter@amazon.com>

* fixed capitalization

Signed-off-by: Heather Halter <hdhalter@amazon.com>

---------

Signed-off-by: Heather Halter <hdhalter@amazon.com>
This commit is contained in:
Heather Halter 2023-06-26 18:33:07 -07:00 committed by GitHub
parent 0b859900a1
commit 25e64f7f74
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
_install-and-configure/install-opensearch/tar.md
View File

@ -86,7 +86,7 @@ If you only want to verify that the service is properly configured and you inten
An OpenSearch node configured by the demo security script is not suitable for a production environment. If you plan to use the node in a production environment after running `opensearch-tar-install.sh`, you should, at a minimum, replace the demo TLS certificates with your own TLS certificates and [update the list of internal users and passwords]({{site.url}}{{site.baseurl}}/security/configuration/yaml). See [Security configuration]({{site.url}}{{site.baseurl}}/security/configuration/index/) for additional guidance to ensure that your nodes are configured according to your security requirements.
{: .warning}
### Option 1: Test your Opensearch settings with security enabled
### Option 1: Test your OpenSearch settings with security enabled
1. Change to the top directory of your OpenSearch installation.
```bash
@ -94,7 +94,7 @@ An OpenSearch node configured by the demo security script is not suitable for a
```
{% include copy.html %}
1. Run the demo security script.
1. Run the OpenSearch startup script with the security demo configuration.
```bash
./opensearch-tar-install.sh
```