AWS opensearch-service documentation change
Summary
Strengthened recommendation wording for console use and improved SCP policy clarification
Security assessment
Changed 'highly recommend' to 'strongly recommend' emphasizes best practices but doesn't address specific vulnerabilities. SCP policy wording clarification improves accuracy but doesn't introduce new security controls.
Diff
diff --git a/opensearch-service/latest/developerguide/saml.md b/opensearch-service/latest/developerguide/saml.md index f865cf56f..49a0161af 100644 --- a//opensearch-service/latest/developerguide/saml.md +++ b//opensearch-service/latest/developerguide/saml.md @@ -36 +36 @@ Consider the following when you configure SAML authentication: - * Due to the size of the IdP metadata file, we highly recommend using the AWS console to configure SAML authentication. + * Due to the size of the IdP metadata file, we strongly recommend using the AWS console to configure SAML authentication. @@ -42 +42 @@ Consider the following when you configure SAML authentication: - * Service Control Policies (SCP) will not be applicable or evaluated in case of non-IAM identities (like SAML in Amazon OpenSearch Serverless & SAML and basic internal user authorization for Amazon OpenSearch Service). + * Service Control Policies (SCP) will not be applicable or evaluated in the case of non-IAM identities (like SAML in Amazon OpenSearch Serverless & SAML and basic internal user authorization for Amazon OpenSearch Service).