AWS bedrock-agentcore documentation change
Summary
Formatting changes including removal of preview notice, header punctuation cleanup, example phrasing updates, and addition of tagging documentation link
Security assessment
Changes are primarily grammatical/formatting improvements and documentation structure updates. The added tagging reference improves resource organization guidance but doesn't explicitly introduce security controls. Existing security considerations section remains unchanged in substance.
Diff
diff --git a/bedrock-agentcore/latest/devguide/agent-identity-directory.md b/bedrock-agentcore/latest/devguide/agent-identity-directory.md index a0efab778..c623d89ab 100644 --- a//bedrock-agentcore/latest/devguide/agent-identity-directory.md +++ b//bedrock-agentcore/latest/devguide/agent-identity-directory.md @@ -7,2 +6,0 @@ Directory concepts and structureDirectory management best practicesListing and v -Amazon Bedrock AgentCore is in preview release and is subject to change. - @@ -30 +28 @@ Understanding the fundamental concepts and organizational structure of the agent -**Key characteristics:** +**Key characteristics** @@ -32 +30 @@ Understanding the fundamental concepts and organizational structure of the agent - * **Single directory per account:** Each AWS account has exactly one agent identity directory + * **Single directory per account** – Each AWS account has exactly one agent identity directory @@ -34 +32 @@ Understanding the fundamental concepts and organizational structure of the agent - * **Automatic creation:** The directory is automatically created when the first workload identity is created in your account + * **Automatic creation** – The directory is automatically created when the first workload identity is created in your account @@ -36 +34 @@ Understanding the fundamental concepts and organizational structure of the agent - * **Centralized management:** All workload identities, regardless of how they were created, are stored in this directory + * **Centralized management** – All workload identities, regardless of how they were created, are stored in this directory @@ -38 +36 @@ Understanding the fundamental concepts and organizational structure of the agent - * **Cross-service visibility:** The directory provides visibility into identities created by Runtime, Gateway, and manual processes + * **Cross-service visibility** – The directory provides visibility into identities created by Runtime, Gateway, and manual processes @@ -43 +41 @@ Understanding the fundamental concepts and organizational structure of the agent -**Directory structure:** +**Directory structure** @@ -57 +55 @@ Following established best practices for directory management helps maintain org -**Naming conventions:** +**Naming conventions** @@ -59 +57 @@ Following established best practices for directory management helps maintain org - * Use descriptive names that indicate the agent's purpose (e.g., "customer-support-agent", "data-analysis-agent") + * Use descriptive names that indicate the agent's purpose (such as "customer-support-agent", "data-analysis-agent") @@ -61 +59 @@ Following established best practices for directory management helps maintain org - * Include environment indicators for multi-environment deployments (e.g., "prod-chatbot", "dev-chatbot") + * Include environment indicators for multi-environment deployments (such as "prod-chatbot", "dev-chatbot") @@ -63 +61 @@ Following established best practices for directory management helps maintain org - * Consider team or project prefixes for large organizations (e.g., "marketing-content-agent") + * Consider team or project prefixes for large organizations (such as "marketing-content-agent") @@ -68 +66 @@ Following established best practices for directory management helps maintain org -**Organization strategies:** +**Organization strategies** @@ -74 +72 @@ Following established best practices for directory management helps maintain org - * Implement consistent tagging strategies for workload identities when available + * Implement consistent tagging strategies for workload identities when available. For more information, see [Tagging AgentCore Identity resources](./identity-tagging.html). @@ -81 +79 @@ Following established best practices for directory management helps maintain org -**Security considerations:** +**Security considerations** @@ -98 +96 @@ You can view all workload identities in your directory using the AWS CLI: -**List all workload identities:** +**List all workload identities** @@ -116 +114 @@ This command returns information about all workload identities in your account, -**Example output:** +**Example output** @@ -136 +134 @@ This command returns information about all workload identities in your account, -**Get details about a specific workload identity:** +**Get details about a specific workload identity** @@ -146 +144 @@ The agent identity directory integrates with IAM to provide fine-grained access -**Directory-level permissions:** +**Directory-level permissions** @@ -148 +146 @@ The agent identity directory integrates with IAM to provide fine-grained access - * **List permissions:** Control who can view the directory contents + * **List permissions** – Control who can view the directory contents @@ -150 +148 @@ The agent identity directory integrates with IAM to provide fine-grained access - * **Create permissions:** Control who can create new workload identities + * **Create permissions** – Control who can create new workload identities @@ -152 +150 @@ The agent identity directory integrates with IAM to provide fine-grained access - * **Read permissions:** Control who can view specific workload identity details + * **Read permissions** – Control who can view specific workload identity details @@ -154 +152 @@ The agent identity directory integrates with IAM to provide fine-grained access - * **Delete permissions:** Control who can remove workload identities + * **Delete permissions** – Control who can remove workload identities @@ -159 +157 @@ The agent identity directory integrates with IAM to provide fine-grained access -**Example IAM policy for directory access:** +**Example IAM policy for directory access**