AWS Security ChangesHomeSearch

AWS sagemaker documentation change

Service: sagemaker · 2025-11-22 · Documentation low

File: sagemaker/latest/dg/sms-workforce-management-private-api-dualstack.md

Summary

Fixed URL formatting by adding double slashes in API documentation links

Security assessment

Changes only correct URL syntax (added double slashes) without altering security-related content. No evidence of addressing vulnerabilities or security weaknesses.

Diff

diff --git a/sagemaker/latest/dg/sms-workforce-management-private-api-dualstack.md b/sagemaker/latest/dg/sms-workforce-management-private-api-dualstack.md
index 38b6b4d1c..df3799023 100644
--- a//sagemaker/latest/dg/sms-workforce-management-private-api-dualstack.md
+++ b//sagemaker/latest/dg/sms-workforce-management-private-api-dualstack.md
@@ -9 +9 @@ Create a dual-stack workforceUpdate a dual-stack workforce
-You can enable a dual-stack workforce by using the [CreateWorkforce](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_CreateWorkforce.html) and [UpdateWorkforce](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_UpdateWorkforce.html) API operations. Creating a dual-stack workforce, updating an existing workforce to dual-stack, and changing a workforce from dual-stack back to IPv4 are not supported in AWS Management Console.
+You can enable a dual-stack workforce by using the [CreateWorkforce](https://docs.aws.amazon.com//sagemaker/latest/APIReference/API_CreateWorkforce.html) and [UpdateWorkforce](https://docs.aws.amazon.com//sagemaker/latest/APIReference/API_UpdateWorkforce.html) API operations. Creating a dual-stack workforce, updating an existing workforce to dual-stack, and changing a workforce from dual-stack back to IPv4 are not supported in AWS Management Console.
@@ -17 +17 @@ A workforce without a defined `IpAddressType` defaults to `IPv4`.
-The process for creating a dual-stack workforce is similar to creating an IPv4-only workforce, with the exceptions noted below. For more information, see [CreateWorkforce](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_CreateWorkforce.html).
+The process for creating a dual-stack workforce is similar to creating an IPv4-only workforce, with the exceptions noted below. For more information, see [CreateWorkforce](https://docs.aws.amazon.com//sagemaker/latest/APIReference/API_CreateWorkforce.html).
@@ -25 +25 @@ The process for creating a dual-stack workforce is similar to creating an IPv4-o
-  * Your identity provider authentication endpoint supports dual-stack. For more information, see [Authentication flow](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/listener-authenticate-users.html#authentication-flow).
+  * Your identity provider authentication endpoint supports dual-stack. For more information, see [Authentication flow](https://docs.aws.amazon.com//elasticloadbalancing/latest/application/listener-authenticate-users.html#authentication-flow).
@@ -53 +53 @@ For more information, see [create_workforce](https://boto3.amazonaws.com/v1/docu
-When updating an existing workforce to be dual-stack, note the following. For more information, see [UpdateWorkforce](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_UpdateWorkforce.html) and [IPv6 support for your VPC](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-migrate-ipv6.html).
+When updating an existing workforce to be dual-stack, note the following. For more information, see [UpdateWorkforce](https://docs.aws.amazon.com//sagemaker/latest/APIReference/API_UpdateWorkforce.html) and [IPv6 support for your VPC](https://docs.aws.amazon.com//vpc/latest/userguide/vpc-migrate-ipv6.html).
@@ -61 +61 @@ When updating an existing workforce to be dual-stack, note the following. For mo
-  * Your identity provider authentication endpoint supports dual-stack. For more information, see [Authentication flow](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/listener-authenticate-users.html#authentication-flow).
+  * Your identity provider authentication endpoint supports dual-stack. For more information, see [Authentication flow](https://docs.aws.amazon.com//elasticloadbalancing/latest/application/listener-authenticate-users.html#authentication-flow).