AWS Security ChangesHomeSearch

AWS AWSSimpleQueueService documentation change

Service: AWSSimpleQueueService · 2026-06-19 · Documentation medium

File: AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-setting-up.md

Summary

Restructured setup documentation: removed IAM/programmatic access details, simplified to AWS account signup and example code preparation

Security assessment

Removal of IAM/programmatic access guidance could reduce security awareness, but no evidence of security vulnerability being addressed. Change appears organizational rather than security-focused.

Diff

diff --git a/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-setting-up.md b/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-setting-up.md
index 7ba73eb68..c86c5800d 100644
--- a//AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-setting-up.md
+++ b//AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-setting-up.md
@@ -7 +7 @@
-Step 1: Create an AWS account and IAM userStep 2: Grant programmatic accessStep 3: Get ready to use the example codeNext steps
+Sign up for an AWS accountGet ready to use the example codeNext steps
@@ -13,7 +13 @@ Before you can use Amazon SQS for the first time, you must complete the followin
-## Step 1: Create an AWS account and IAM user
-
-To access any AWS service, you first need to create an [AWS account](https://aws.amazon.com/), an Amazon.com account that can use AWS products. You can use your AWS account to view your activity and usage reports and to manage authentication and access.
-
-To avoid using your AWS account root user for Amazon SQS actions, it is a best practice to create an IAM user for each person who needs administrative access to Amazon SQS.
-
-### Sign up for an AWS account
+## Sign up for an AWS account
@@ -23,36 +17 @@ To get started with AWS, you need an AWS account. For information about creating
-## Step 2: Grant programmatic access
-
-To use Amazon SQS actions (for example, using Java or through the AWS Command Line Interface), you need an access key ID and a secret access key.
-
-###### Note
-
-The access key ID and secret access key are specific to AWS Identity and Access Management. Don't confuse them with credentials for other AWS services, such as Amazon EC2 key pairs.
-
-Users need programmatic access if they want to interact with AWS outside of the AWS Management Console. The way to grant programmatic access depends on the type of user that's accessing AWS.
-
-To grant users programmatic access, choose one of the following options.
-
-Which user needs programmatic access? | To | By  
----|---|---  
-IAM | (Recommended) Use console credentials as temporary credentials to sign programmatic requests to the AWS CLI, AWS SDKs, or AWS APIs. |  Following the instructions for the interface that you want to use.
-
-  * For the AWS CLI, see [Login for AWS local development](https://docs.aws.amazon.com//cli/latest/userguide/cli-configure-sign-in.html) in the _AWS Command Line Interface User Guide_.
-  * For AWS SDKs, see [Login for AWS local development](https://docs.aws.amazon.com//sdkref/latest/guide/access-login.html) in the _AWS SDKs and Tools Reference Guide_.
-
-  
-Workforce identity (Users managed in IAM Identity Center) | Use temporary credentials to sign programmatic requests to the AWS CLI, AWS SDKs, or AWS APIs. |  Following the instructions for the interface that you want to use.
-
-  * 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_.
-
-  
-IAM | Use temporary credentials to sign programmatic requests to the AWS CLI, AWS SDKs, or AWS APIs. | Following the instructions in [Using temporary credentials with AWS resources](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_use-resources.html) in the _IAM User Guide_.  
-IAM | (Not recommended)Use long-term credentials to sign programmatic requests to the AWS CLI, AWS SDKs, or AWS APIs. |  Following the instructions for the interface that you want to use.
-
-  * 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_.
-
-  
-  
-## Step 3: Get ready to use the example code
+## Get ready to use the example code