AWS solutions documentation change
Summary
Updated workflow commands from 'output' to 'log all', corrected step approval syntax, and enhanced explanation of multi-type mapping resolution
Security assessment
Changes involve command syntax updates and clarification of mapping-type handling during migration. No security vulnerabilities, mitigations, or security features are mentioned. The mapping-type change describes default behavior configuration without security implications.
Diff
diff --git a/solutions/latest/migration-assistant-for-amazon-opensearch-service/troubleshooting.md b/solutions/latest/migration-assistant-for-amazon-opensearch-service/troubleshooting.md index 149351528..98985caa4 100644 --- a//solutions/latest/migration-assistant-for-amazon-opensearch-service/troubleshooting.md +++ b//solutions/latest/migration-assistant-for-amazon-opensearch-service/troubleshooting.md @@ -21 +21 @@ Start with the simplest question: is this a deployment problem, an authenticatio - workflow output + workflow log all @@ -168,2 +168,2 @@ Do not plan around mTLS unless you have validated it in the exact version you ar - workflow output - workflow output --follow + workflow log all + workflow log all --follow @@ -193 +193 @@ Or approve the step directly: - workflow approve <STEP_NAME> + workflow approve step <STEP_NAME> @@ -221 +221 @@ Common causes: - * Elasticsearch 6.x mapping-type cleanup issues — set `multiTypeBehavior` to `NONE`, `UNION`, or `SPLIT` intentionally. + * Elasticsearch 6.x mapping-type cleanup issues — multi-type (multiple types per index) mappings from sources below Elasticsearch 7 are automatically resolved by the type-mapping sanitization transformer, which unions the types into a single mapping by default. To override the default behavior, configure the `TypeMappingSanitizationTransformerProvider` request transform (through its `regexMappings`/`featureFlags`). @@ -264 +264 @@ Collect the following before opening a support case: - * `workflow output` + * `workflow log all`