AWS aurora-dsql documentation change
Summary
Added specific IAM permissions required for DSQL connections and expanded configuration examples
Security assessment
The change documents required IAM permissions (dsql:DbConnectAdmin and dsql:DbConnect) which are security-related access controls, but there's no evidence of addressing a specific security vulnerability.
Diff
diff --git a/aurora-dsql/latest/userguide/SECTION_aurora-dsql-mcp-server.md b/aurora-dsql/latest/userguide/SECTION_aurora-dsql-mcp-server.md index 10ce19d10..206bf862d 100644 --- a//aurora-dsql/latest/userguide/SECTION_aurora-dsql-mcp-server.md +++ b//aurora-dsql/latest/userguide/SECTION_aurora-dsql-mcp-server.md @@ -62 +62,5 @@ An AWS Labs Model Context Protocol (MCP) server for Aurora DSQL - * You need an AWS account with appropriate permissions + * You need an AWS account with a role including these permissions: + + * `dsql:DbConnectAdmin` \- Connect to DSQL clusters as the admin user + + * `dsql:DbConnect` \- Connect to DSQL clusters with custom database roles (only needed if using non-admin users) @@ -90 +94 @@ Configure the MCP server in your MCP client configuration (e.g., for Amazon Q De - "[your dsql cluster endpoint]", + "[your dsql cluster endpoint, e.g. abcdefghijklmnopqrst234567.dsql.us-east-1.on.aws]", @@ -94 +98 @@ Configure the MCP server in your MCP client configuration (e.g., for Amazon Q De - "[your dsql username]", + "[your dsql username, e.g. admin]", @@ -136,0 +141,4 @@ For Windows users, the MCP server configuration format is slightly different: +### Verifying Installation + +For Amazon Q Developer CLI, run `/mcp` to see the status of the MCP server. +