AWS bedrock documentation change
Summary
Updated documentation to use consistent capitalization of 'Region' in placeholder variables across multiple database integration sections
Security assessment
Changes only correct capitalization of 'region' to 'Region' in placeholder variables without altering security content. No evidence of addressing vulnerabilities or security incidents.
Diff
diff --git a/bedrock/latest/userguide/kb-permissions.md b/bedrock/latest/userguide/kb-permissions.md index b3e98c084..901b6ba4f 100644 --- a/bedrock/latest/userguide/kb-permissions.md +++ b/bedrock/latest/userguide/kb-permissions.md @@ -399 +399 @@ If you created an Amazon Kendra GenAI index for your knowledge base, then attach -If you created a vector database in OpenSearch Serverless for your knowledge base, attach the following policy to your Amazon Bedrock Knowledge Bases service role to allow access to the collection. Replace `${Region}` and `${AccountId}` with the region and account ID to which the database belongs. Input the ID of your Amazon OpenSearch Service collection in `${CollectionId}`. You can allow access to multiple collections by adding them to the `Resource` list. +If you created a vector database in OpenSearch Serverless for your knowledge base, attach the following policy to your Amazon Bedrock Knowledge Bases service role to allow access to the collection. Replace `${Region}` and `${AccountId}` with the Region and account ID to which the database belongs. Input the ID of your Amazon OpenSearch Service collection in `${CollectionId}`. You can allow access to multiple collections by adding them to the `Resource` list. @@ -417 +417 @@ If you created a vector database in OpenSearch Serverless for your knowledge bas -If you created a vector database in OpenSearch Managed Cluster for your knowledge base, attach the following policy to your Amazon Bedrock Knowledge Bases service role to allow access to the domain. Replace `<region>` and `<accountId>` with the region and account ID to which the database belongs. You can allow access to multiple domains by adding them to the `Resource` list. For more information about configuring permissions, see [Prerequisites and permissions required for using OpenSearch Managed Clusters with Amazon Bedrock Knowledge Bases](./kb-osm-permissions-prereq.html). +If you created a vector database in OpenSearch Managed Cluster for your knowledge base, attach the following policy to your Amazon Bedrock Knowledge Bases service role to allow access to the domain. Replace `<region>` and `<accountId>` with the Region and account ID to which the database belongs. You can allow access to multiple domains by adding them to the `Resource` list. For more information about configuring permissions, see [Prerequisites and permissions required for using OpenSearch Managed Clusters with Amazon Bedrock Knowledge Bases](./kb-osm-permissions-prereq.html). @@ -448 +448 @@ If you created a vector database in OpenSearch Managed Cluster for your knowledg -If you created a database (DB) cluster in Amazon Aurora for your knowledge base, attach the following policy to your Amazon Bedrock Knowledge Bases service role to allow access to the DB cluster and to provide read and write permissions on it. Replace `${Region}` and `${AccountId}` with the region and account ID to which the DB cluster belongs. Input the ID of your Amazon Aurora database cluster in `${DbClusterId}`. You can allow access to multiple DB clusters by adding them to the `Resource` list. +If you created a database (DB) cluster in Amazon Aurora for your knowledge base, attach the following policy to your Amazon Bedrock Knowledge Bases service role to allow access to the DB cluster and to provide read and write permissions on it. Replace `${Region}` and `${AccountId}` with the Region and account ID to which the DB cluster belongs. Input the ID of your Amazon Aurora database cluster in `${DbClusterId}`. You can allow access to multiple DB clusters by adding them to the `Resource` list. @@ -479 +479 @@ If you created a database (DB) cluster in Amazon Aurora for your knowledge base, -If you created an Amazon Neptune Analytics graph for your knowledge base, attach the following policy to your Amazon Bedrock Knowledge Bases service role to allow access to the graph. In the policy, replace `${Region}` and `${AccountId}` with the region and account ID to which the database belongs. Replace `${GraphId}` with the values for your graph database. +If you created an Amazon Neptune Analytics graph for your knowledge base, attach the following policy to your Amazon Bedrock Knowledge Bases service role to allow access to the graph. In the policy, replace `${Region}` and `${AccountId}` with the Region and account ID to which the database belongs. Replace `${GraphId}` with the values for your graph database. @@ -502 +502 @@ If you created an Amazon Neptune Analytics graph for your knowledge base, attach -If your vector database is configured with an AWS Secrets Manager secret, attach the following policy to your Amazon Bedrock Knowledge Bases service role to allow AWS Secrets Manager to authenticate your account to access the database. Replace `${Region}` and `${AccountId}` with the region and account ID to which the database belongs. Replace `${SecretId}` with the ID of your secret. +If your vector database is configured with an AWS Secrets Manager secret, attach the following policy to your Amazon Bedrock Knowledge Bases service role to allow AWS Secrets Manager to authenticate your account to access the database. Replace `${Region}` and `${AccountId}` with the Region and account ID to which the database belongs. Replace `${SecretId}` with the ID of your secret.