diff --git a/_includes/downloads/logstash-oss-with-opensearch-output-plugin.markdown b/_includes/downloads/logstash-oss-with-opensearch-output-plugin.markdown
deleted file mode 100644
index a1b1f3bfcb..0000000000
--- a/_includes/downloads/logstash-oss-with-opensearch-output-plugin.markdown
+++ /dev/null
@@ -1 +0,0 @@
-This package includes open source Logstash bundled with the OpenSearch output plugin (v2.0.1). The output plugin is compatible with OpenSearch and Open Source versions of Elasticsearch (7.10.2 or lower). The output plugin is also available as a [Ruby Gem](https://rubygems.org/gems/logstash-output-opensearch).
diff --git a/_posts/2024-04-30-A-comprehensive-guide-to-setup-and-connect-self-managed-dashboards-with-Amazon-OpenSearch-domain.md b/_posts/2024-04-30-A-comprehensive-guide-to-setup-and-connect-self-managed-dashboards-with-Amazon-OpenSearch-domain.md
index b8a418cb33..98d28de0e4 100644
--- a/_posts/2024-04-30-A-comprehensive-guide-to-setup-and-connect-self-managed-dashboards-with-Amazon-OpenSearch-domain.md
+++ b/_posts/2024-04-30-A-comprehensive-guide-to-setup-and-connect-self-managed-dashboards-with-Amazon-OpenSearch-domain.md
@@ -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.