AWS AmazonElastiCache: Document public endpoint connection for Valkey MCP
Summary
Adds guidance that Valkey serverless caches with a public endpoint can be connected to directly using the public endpoint as VALKEY_HOST, requiring TLS 1.3 and an IAM authentication token, and clarifies that other caches need an SSM tunnel.
Security assessment
The change documents connecting to a publicly exposed cache endpoint and explicitly requires TLS 1.3 and IAM authentication, which are security-relevant controls for public exposure. It is documentation of a feature rather than a fix for a specific vulnerability.
Evidence
+**Connecting to Amazon ElastiCache:** If your Valkey serverless cache has a public endpoint, use the public endpoint address as `VALKEY_HOST`. No tunnel is required. The connection requires TLS 1.3 and an IAM authentication token. For details on generating the token, see [Connect to a cache with a public endpoint](./connecting-public-endpoint.html).
Diff
diff --git a/AmazonElastiCache/latest/dg/agent-tools-valkey-mcp-getting-started.md b/AmazonElastiCache/latest/dg/agent-tools-valkey-mcp-getting-started.md index 4cd251a..944262a 100644 --- a//AmazonElastiCache/latest/dg/agent-tools-valkey-mcp-getting-started.md +++ b//AmazonElastiCache/latest/dg/agent-tools-valkey-mcp-getting-started.md @@ -33 +33,3 @@ Replace `<your-endpoint>` with the endpoint of your Valkey datastore. Your codin -**Connecting to Amazon ElastiCache:** ElastiCache Valkey clusters live in a private VPC and aren't reachable directly from your local machine. For SSM tunnel setup, IAM auth token generation, and TLS handling in tunnel mode, see the [ElastiCache connection guide](https://github.com/aws/agent-toolkit-for-aws/blob/main/skills/specialized-skills/database-skills/amazon-elasticache/references/setup/connection-guide.md) in the AWS Agent Toolkit, or install the [Amazon ElastiCache Skill](./agent-tools-skills.html) to let your agent handle the connection setup end-to-end. After the tunnel is established, use `VALKEY_HOST=127.0.0.1` in the config above. +**Connecting to Amazon ElastiCache:** If your Valkey serverless cache has a public endpoint, use the public endpoint address as `VALKEY_HOST`. No tunnel is required. The connection requires TLS 1.3 and an IAM authentication token. For details on generating the token, see [Connect to a cache with a public endpoint](./connecting-public-endpoint.html). + +For all other ElastiCache for Valkey caches, you cannot reach the cache directly from your local machine. For SSM tunnel setup, IAM auth token generation, and TLS handling in tunnel mode, see the [ElastiCache connection guide](https://github.com/aws/agent-toolkit-for-aws/blob/main/skills/specialized-skills/database-skills/amazon-elasticache/references/setup/connection-guide.md) in the AWS Agent Toolkit, or install the [Amazon ElastiCache Skill](./agent-tools-skills.html) to let your agent handle the connection setup end-to-end. After the tunnel is established, use `VALKEY_HOST=127.0.0.1` in the config above.