AWS Security ChangesHomeSearch

AWS amazonq high security documentation change

Service: amazonq · 2025-09-10 · Security-related high

File: amazonq/latest/qdeveloper-ug/command-line-custom-agents-configuration.md

Summary

Added detailed configuration options for built-in tools including execute_bash, fs_read, fs_write, and use_aws with security controls for allowed/denied commands, paths, and services

Security assessment

The changes document security controls for restricting command execution, file system access, and AWS service usage. The added configuration options allow administrators to define allow/deny lists and permission rules that directly impact system security by limiting potential attack surfaces and unauthorized operations.

Diff

diff --git a/amazonq/latest/qdeveloper-ug/command-line-custom-agents-configuration.md b/amazonq/latest/qdeveloper-ug/command-line-custom-agents-configuration.md
index e53403f8a..a59253f03 100644
--- a//amazonq/latest/qdeveloper-ug/command-line-custom-agents-configuration.md
+++ b//amazonq/latest/qdeveloper-ug/command-line-custom-agents-configuration.md
@@ -38,0 +39,2 @@ Every custom agent can include basic metadata for identification and documentati
+  * **Prompt** \- High-level context for the agent, similar to a system prompt
+
@@ -65,0 +68,121 @@ Configures specific behavior for individual tools, such as allowed file paths or
+### Built-in tool settings
+
+Built-in tools can be configured through the `toolsSettings` section to control their behavior and permissions. Each tool supports specific configuration options that allow you to pre-approve certain operations or restrict access to specific resources.
+
+#### execute_bash tool
+
+Controls which bash commands can be executed without user confirmation:
+    
+    
+    {
+      "toolsSettings": {
+        "execute_bash": {
+          "allowedCommands": ["git status", "git fetch"],
+          "deniedCommands": ["git commit .*", "git push .*"],
+          "allowReadOnly": true
+        }
+      }
+    }
+
+allowedCommands
+    
+
+Array of specific commands allowed without prompting. Supports regex formatting with anchors `\A` and `\z`.
+
+deniedCommands
+    
+
+Array of commands to deny. Supports regex formatting. Deny rules are evaluated before allow rules.
+
+allowReadOnly
+    
+
+Boolean (default: `true`) - Whether to allow read-only commands without prompting.
+
+#### fs_read tool
+
+Controls which files and directories can be read without user confirmation:
+    
+    
+    {
+      "toolsSettings": {
+        "fs_read": {
+          "allowedPaths": ["~/projects", "./src/**"],
+          "deniedPaths": ["/some/denied/path/", "/another/denied/path/**/file.txt"]
+        }
+      }
+    }
+
+allowedPaths
+    
+
+Array of paths that can be read without prompting. Supports glob patterns with gitignore-style behavior.
+
+deniedPaths
+    
+
+Array of paths to deny access. Supports glob patterns. Deny rules are evaluated before allow rules.
+
+#### fs_write tool
+
+Controls which files and directories can be written to without user confirmation:
+    
+    
+    {
+      "toolsSettings": {
+        "fs_write": {
+          "allowedPaths": ["~/projects/output.txt", "./src/**"],
+          "deniedPaths": ["/some/denied/path/", "/another/denied/path/**/file.txt"]
+        }
+      }
+    }
+
+allowedPaths
+    
+
+Array of paths that can be written to without prompting. Supports glob patterns with gitignore-style behavior.
+
+deniedPaths
+    
+
+Array of paths to deny write access. Supports glob patterns. Deny rules are evaluated before allow rules.
+
+#### use_aws tool
+
+Controls which AWS services can be accessed without user confirmation:
+    
+    
+    {
+      "toolsSettings": {
+        "use_aws": {
+          "allowedServices": ["s3", "lambda", "ec2"],
+          "deniedServices": ["eks", "rds"]
+        }
+      }
+    }
+
+allowedServices
+    
+
+Array of AWS services that can be accessed without prompting.
+
+deniedServices
+    
+
+Array of AWS services to deny access. Deny rules are evaluated before allow rules.
+
+#### Tool permissions and defaults
+
+Built-in tools have different default permission behaviors:
+
+  * **Trusted by default:** `fs_read`, `report_issue`
+
+  * **Require permission by default:** `execute_bash`, `fs_write`, `use_aws`
+
+  * **No configuration options:** `introspect`, `knowledge`, `thinking`, `todo_list`
+
+
+
+
+Tools can be explicitly allowed in the `allowedTools` section, or configured with specific permissions through `toolsSettings`. If a tool is not in the `allowedTools` list, users will be prompted for permission unless an appropriate `toolsSettings` configuration is set.
+
@@ -106,0 +230 @@ A simple custom agent that provides basic file operations with pre-approved read
+      "prompt": "You are a helpful assistant specialized in basic file operations",
@@ -124,0 +249 @@ An custom agent configured for AWS infrastructure management with specific tool
+      "prompt": "You are an expert AWS infrastructure specialist",
@@ -154,0 +280 @@ An custom agent that includes project context through both static files and dyna
+      "prompt": "You are a project development assistant with access to git information",
@@ -187,0 +314 @@ An custom agent that integrates external tools through MCP servers:
+      "prompt": "You are a development assistant with access to git and web fetching capabilities",