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

Remove logstash from downloads page and fix blog #3432

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −2
Open

Remove logstash from downloads page and fix blog #3432

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
1 change: 0 additions & 1 deletion _includes/downloads/logstash-oss-with-opensearch-output-plugin.markdown
View file
Open in desktop
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file cannot be safely deleted unless we find all the places its being used. Try running bundle exec jekyll serve from the root of the repo and going through the list of errors. It should give us some hints.

This file was deleted.

2 changes: 1 addition & 1 deletion ...e-to-setup-and-connect-self-managed-dashboards-with-Amazon-OpenSearch-domain.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -222,7 +222,7 @@ IK5Y04uMGfRjcE+cPA/vPCKPxh/sgB0n6GaJCIDI</ds:X509Certificate></ds:X509Data></ds:

* Replace the self-managed Dashboards URL in the security configuration file with the self-managed Dashboards endpoint. The purpose of this change is to guarantee that after the user is authenticated by IdP, they are redirected to the self-managed Dashboards instance instead of the managed Dashboards instance.

**IMPORTANT**: Users do not have access to modify the security configuration file, so you will need to raise a support case with AWS Support to request a change to the self-managed Dashboards URL endpoint. After AWS Support completes your request, you can check the new endpoint by running the API call **```_opendistro/_security/api/securityconfig```** and validate the **`kibana_url`** changes in the security configuration file.
**IMPORTANT**: Users do not have access to modify the security configuration file, so you will need to raise a support case with AWS Support to request a change to the self-managed Dashboards URL endpoint. After AWS Support completes your request, you can check the new endpoint by running the API call **```_opendistro/_security/api/securityconfig```** and validate the **`kibana_url`** changes in the security configuration file. Additionally, make sure that **`challenge`** is set to false for basic auth backend, and your idp has the appropriate basepath for your self-managed dashboards.

**Disclaimer**: When changes are made to the Security Configuration file (such as those related to Basic Auth or SAML) after altering the `kibana_url`, it initiates an update to the backend Security Configuration. This update results in the `kibana_url` being reverted to the Custom Domain endpoint. The managed service control plane component uses the PATCH security config API to carry out this process, underscoring the strong recommendation against making any modifications to the security configuration.

Expand Down
Loading