AWS amazonq documentation change
Summary
Removed standalone project rules section and added a reference to them in security measures
Security assessment
The change restructures documentation about project rules but maintains a security-focused reference. It does not address a specific vulnerability but continues to document security controls.
Diff
diff --git a/amazonq/latest/qdeveloper-ug/command-line-chat-security.md b/amazonq/latest/qdeveloper-ug/command-line-chat-security.md index b686f68fe..55646d0f2 100644 --- a//amazonq/latest/qdeveloper-ug/command-line-chat-security.md +++ b//amazonq/latest/qdeveloper-ug/command-line-chat-security.md @@ -63,17 +62,0 @@ This ensures that every new Amazon Q session starts with `fs_read` untrusted, re -### Using project rules - -Amazon Q supports project-level rules that can define security guidelines and restrictions. These rules are defined in Markdown files in the `.amazonq/rules` directory of your project. - -For example, you can create rules that specify: - - * Which directories Amazon Q should avoid accessing - - * Security requirements for generated code - - * Coding standards and best practices - - - - -For more information about creating and using project rules, see [Creating project rules for use with Amazon Q Developer chat](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/context-project-rules.html) in the IDE documentation. - @@ -91,0 +75,2 @@ For environments with highly sensitive information, consider these additional me + * Use project rules to define security guidelines and restrictions (see [Using project rules](./command-line-context-profiles.html#command-line-context-profiles-project-rules)) + @@ -127 +112 @@ Using chat -Using the editor command +Using MCP