AWS Security ChangesHomeSearch

AWS bedrock documentation change

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

File: bedrock/latest/userguide/getting-started-api.md

Summary

Fixed URL formatting by adding double slashes in documentation links and corrected a broken IAM Identity Center URL

Security assessment

The changes correct URL formatting and fix a broken link but do not introduce new security content or address specific vulnerabilities. The security best practice recommendations were already present; the changes only improve link accuracy.

Diff

diff --git a/bedrock/latest/userguide/getting-started-api.md b/bedrock/latest/userguide/getting-started-api.md
index 017e2ff27..d8e5fd67c 100644
--- a//bedrock/latest/userguide/getting-started-api.md
+++ b//bedrock/latest/userguide/getting-started-api.md
@@ -83,3 +83,3 @@ IAM users | Limit the duration of long-term credentials to sign programmatic req
-  * For the AWS CLI, see [Authenticating using IAM user credentials](https://docs.aws.amazon.com/cli/latest/userguide/cli-authentication-user.html) in the _AWS Command Line Interface User Guide_.
-  * For AWS SDKs and tools, see [Authenticate using long-term credentials](https://docs.aws.amazon.com/sdkref/latest/guide/access-iam-users.html) in the _AWS SDKs and Tools Reference Guide_.
-  * For AWS APIs, see [Managing access keys for IAM users](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html) in the _IAM User Guide_.
+  * For the AWS CLI, see [Authenticating using IAM user credentials](https://docs.aws.amazon.com//cli/latest/userguide/cli-authentication-user.html) in the _AWS Command Line Interface User Guide_.
+  * For AWS SDKs and tools, see [Authenticate using long-term credentials](https://docs.aws.amazon.com//sdkref/latest/guide/access-iam-users.html) in the _AWS SDKs and Tools Reference Guide_.
+  * For AWS APIs, see [Managing access keys for IAM users](https://docs.aws.amazon.com//IAM/latest/UserGuide/id_credentials_access-keys.html) in the _IAM User Guide_.
@@ -91,2 +91,2 @@ Workforce identity (Users managed in IAM Identity Center) | Use temporary creden
-  * For the AWS CLI, see [Configuring the AWS CLI to use AWS IAM Identity Center](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-sso.html) in the _AWS Command Line Interface User Guide_.
-  * For AWS SDKs, tools, and AWS APIs, see [IAM Identity Center authentication](https://docs.aws.amazon.com/sdkref/latest/guide/access-sso.html) in the _AWS SDKs and Tools Reference Guide_.
+  * For the AWS CLI, see [Configuring the AWS CLI to use AWS IAM Identity Center](https://docs.aws.amazon.com//cli/latest/userguide/cli-configure-sso.html) in the _AWS Command Line Interface User Guide_.
+  * For AWS SDKs, tools, and AWS APIs, see [IAM Identity Center authentication](https://docs.aws.amazon.com//sdkref/latest/guide/access-sso.html) in the _AWS SDKs and Tools Reference Guide_.
@@ -179 +179 @@ JSON
-When you no longer need this IAM user, we recommend that you remove it and align with the [AWS security best practice](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#lock-away-credentials), we recommend that you require your human users to use temporary credentials through [AWS IAM Identity Center](https://docs.aws.amazon.com/https://docs.aws.amazon.com/singlesignon/latest/userguide/getting-started.html) when accessing AWS.
+When you no longer need this IAM user, we recommend that you remove it and align with the [AWS security best practice](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#lock-away-credentials), we recommend that you require your human users to use temporary credentials through [AWS IAM Identity Center](https://docs.aws.amazon.com/singlesignon/latest/userguide/getting-started.html) when accessing AWS.