AWS aws-mcp documentation change
Summary
Improved SigV4 authentication documentation and added AWS CLI login instructions
Security assessment
Clarified authentication methods and added guidance for AWS Management Console credentials. While security-related, this is routine documentation improvement rather than addressing a specific vulnerability.
Diff
diff --git a/aws-mcp/latest/userguide/getting-started-aws-mcp-server.md b/aws-mcp/latest/userguide/getting-started-aws-mcp-server.md index 0047af0a8..dffb17366 100644 --- a//aws-mcp/latest/userguide/getting-started-aws-mcp-server.md +++ b//aws-mcp/latest/userguide/getting-started-aws-mcp-server.md @@ -139 +139 @@ Before connecting to AWS MCP Server, you need to configure AWS credentials on yo -You can use the SigV4 via Proxy to authenticate the AWS MCP Server. SigV4 via Proxy your available AWS credentials and requires the [MCP Proxy for AWS](https://github.com/aws/mcp-proxy-for-aws). +You can use the SigV4 via Proxy to authenticate the AWS MCP Server. SigV4 via Proxy uses your available AWS credentials and requires the [MCP Proxy for AWS](https://github.com/aws/mcp-proxy-for-aws). @@ -144,0 +145,10 @@ You can use the SigV4 via Proxy to authenticate the AWS MCP Server. SigV4 via Pr +###### For users with AWS Management Console credentials (Recommended) + +From the AWS CLI, run the following command: + + aws login + +###### Note + +AWS Management Console credentials means that you have a username and password that allows you to sign in to the console. To use this method, you need the AWS CLI version `2.32.0` or later. +