{"version":"2.1.207","anchor":"aws-credential-validation-in-mcp-server-config","canonical_anchor":"aws-credential-validation-in-mcp-server-config","heading":"AWS Credential Validation in MCP Server Config","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.207\/e\/aws-credential-validation-in-mcp-server-config","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.207","markdown":"### AWS Credential Validation in MCP Server Config\n\nMCP server definitions using AWS auth now validate that:\n\n- `aws_access_key_id` and `aws_secret_access_key` must be set together (not one without the other).\n- `aws_session_token` requires `aws_access_key_id` and `aws_secret_access_key` to be present.\n\nEmpty-string values are also now rejected (fields require `min(1)` length). Clear error messages are surfaced on config parse.\n\n**Evidence**\n\nAWS credential pair refinements (search for `\"aws_access_key_id and aws_secret_access_key must be set together\"`)"}