Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Updates README to reflect strong password requirements for admin user #151

Merged
merged 2 commits into from
Feb 2, 2024
Merged

Updates README to reflect strong password requirements for admin user #151

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
31c66b5
Updates README to reflect strong password requirements for admin user
DarshitChanpura Feb 2, 2024
bfb5578
Applies PR feedback
DarshitChanpura Feb 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Applies PR feedback 
Signed-off-by: Darshit Chanpura <dchanp@amazon.com>
  • Loading branch information
@DarshitChanpura
DarshitChanpura committed Feb 2, 2024
commit bfb55784c4dd0e77f4bad578563686ef9a750426
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@ cluster_type: single-node

You should set the reserved users(`admin`, `kibanaserver`, and `logstash`) password using `admin_password`, `kibanaserver_password`, and `logstash_password` variables.

**Note**: Starting OpenSearch 2.12, a strong password is required for `admin` user, i.e. `myStrongPassword123!`. The cluster will fail to start with a weak password, i.e. `admin`
**Note**: Starting OpenSearch 2.12, a strong password is required for `admin` user, i.e. `myStrongPassword123!`. The cluster will fail to start with a weak password (i.e. admin) or no password.

If you define your own internal users (in addition to the reserved `admin`, `kibanaserver`, and `logstash`) in custom configuration
files, then passwords to them should be set via variables on the principle of `<username>_password`
Expand Down