AWS ses documentation change
Summary
Simplified setup instructions by removing 'Grant programmatic access' section and consolidating AWS account sign-up information.
Security assessment
Removal of programmatic access guidance and credential management details reduces security documentation coverage but doesn't fix a specific vulnerability. The change focuses on simplification rather than security remediation.
Diff
diff --git a/ses/latest/dg/setting-up.md b/ses/latest/dg/setting-up.md index a1f12562d..7962c73cf 100644 --- a//ses/latest/dg/setting-up.md +++ b//ses/latest/dg/setting-up.md @@ -7 +7 @@ -Sign up for AWSSet up your SES accountGrant programmatic access (To interact with SES outside of the console)Download an AWS SDK (For using the SES APIs) +Sign up for an AWS accountSet up your SES accountDownload an AWS SDK (For using the SES APIs) @@ -15 +15 @@ Before you start using Amazon SES, you must complete the following tasks. - * Sign up for AWS + * Sign up for an AWS account @@ -19,2 +18,0 @@ Before you start using Amazon SES, you must complete the following tasks. - * Grant programmatic access (To interact with SES outside of the console) - @@ -26,15 +24 @@ Before you start using Amazon SES, you must complete the following tasks. -## Sign up for AWS - -If you do not have an AWS account, complete the following steps to create one. - -###### To sign up for an AWS account - - 1. Open [https://portal.aws.amazon.com/billing/signup](https://portal.aws.amazon.com/billing/signup). - - 2. Follow the online instructions. - -Part of the sign-up procedure involves receiving a phone call or text message and entering a verification code on the phone keypad. - -When you sign up for an AWS account, an _AWS account root user_ is created. The root user has access to all AWS services and resources in the account. As a security best practice, assign administrative access to a user, and use only the root user to perform [tasks that require root user access](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#root-user-tasks). - - +## Sign up for an AWS account @@ -41,0 +26 @@ When you sign up for an AWS account, an _AWS account root user_ is created. The +To get started with AWS, you need an AWS account. For information about creating an AWS account, see [Getting started with an AWS account](https://docs.aws.amazon.com//accounts/latest/reference/getting-started.html) in the _AWS Account Management Reference Guide_. @@ -58,29 +42,0 @@ _The_ SES account set up _wizard will only be presented if you have not yet crea -## Grant programmatic access (To interact with SES outside of the console) - -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_. - - -