AWS bedrock-agentcore documentation change
Summary
Minor text updates including changing 'Using the console' to 'Using the AgentCore console', updating apostrophes in contractions (don't to don’t, won't to won’t, they're to they’re), and fixing code formatting for `ConsoleAccess`.
Security assessment
These changes are purely editorial and typographical. They do not introduce, modify, or remove any security policies, permissions, or vulnerability information. The updates are for clarity and consistency in documentation formatting.
Diff
diff --git a/bedrock-agentcore/latest/devguide/security_iam_id-based-policy-examples.md b/bedrock-agentcore/latest/devguide/security_iam_id-based-policy-examples.md index f3435301e..39bc9b6cf 100644 --- a//bedrock-agentcore/latest/devguide/security_iam_id-based-policy-examples.md +++ b//bedrock-agentcore/latest/devguide/security_iam_id-based-policy-examples.md @@ -5 +5 @@ -Policy best practicesUsing the consoleAllow users to view their own permissions +Policy best practicesUsing the AgentCore consoleAllow users to view their own permissions @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissions -By default, users and roles don't have permission to create or modify AgentCore resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. +By default, users and roles don’t have permission to create or modify AgentCore resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. @@ -47 +47 @@ For more information about best practices in IAM, see [Security best practices i -To access the Amazon Bedrock AgentCore console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the AgentCore resources in your AWS account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won't function as intended for entities (users or roles) with that policy. +To access the Amazon Bedrock AgentCore console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the AgentCore resources in your AWS account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won’t function as intended for entities (users or roles) with that policy. @@ -49 +49 @@ To access the Amazon Bedrock AgentCore console, you must have a minimum set of p -You don't need to allow minimum console permissions for users that are making calls only to the AWS CLI or the AWS API. Instead, allow access to only the actions that match the API operation that they're trying to perform. +You don’t need to allow minimum console permissions for users that are making calls only to the AWS CLI or the AWS API. Instead, allow access to only the actions that match the API operation that they’re trying to perform. @@ -51 +51 @@ You don't need to allow minimum console permissions for users that are making ca -To ensure that users and roles can still use the AgentCore console, also attach the AgentCore ``ConsoleAccess`` or ``ReadOnly`` AWS managed policy to the entities. For more information, see [Adding permissions to a user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_change-permissions.html#users_change_permissions-add-console) in the _IAM User Guide_. +To ensure that users and roles can still use the AgentCore console, also attach the AgentCore `ConsoleAccess` or `ReadOnly` AWS managed policy to the entities. For more information, see [Adding permissions to a user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_change-permissions.html#users_change_permissions-add-console) in the _IAM User Guide_.