AWS incident-manager documentation change
Summary
Removed 'Grant programmatic access' section and related references throughout the document.
Security assessment
This change removes documentation about programmatic access methods but shows no evidence of addressing a specific security vulnerability or incident. Programmatic access is a standard AWS feature, and its removal appears to be documentation reorganization without security implications.
Diff
diff --git a/incident-manager/latest/userguide/setting-up.md b/incident-manager/latest/userguide/setting-up.md index d724954ef..fff2662b7 100644 --- a//incident-manager/latest/userguide/setting-up.md +++ b//incident-manager/latest/userguide/setting-up.md @@ -7 +7 @@ -Sign up for an AWS accountGrant programmatic accessRequired role for Incident Manager setup +Sign up for an AWS accountRequired role for Incident Manager setup @@ -19,2 +18,0 @@ We recommend setting up AWS Systems Manager Incident Manager in the account that - * Grant programmatic access - @@ -30,29 +27,0 @@ To get started with AWS, you need an AWS account. For information about creating -## Grant programmatic access - -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_. - - -