AWS prescriptive-guidance documentation change
Summary
Reformatted important note, added list formatting to policy description, and fixed broken link
Security assessment
Changes improve readability and fix a broken link. Security content about VPC endpoint policies remains unchanged.
Diff
diff --git a/prescriptive-guidance/latest/data-perimeter-for-amazon-bedrock/vpc-endpoint-policies.md b/prescriptive-guidance/latest/data-perimeter-for-amazon-bedrock/vpc-endpoint-policies.md index 2d36284dd..6a78ee87d 100644 --- a//prescriptive-guidance/latest/data-perimeter-for-amazon-bedrock/vpc-endpoint-policies.md +++ b//prescriptive-guidance/latest/data-perimeter-for-amazon-bedrock/vpc-endpoint-policies.md @@ -17 +17,3 @@ Control which identities can access Amazon Bedrock through VPC endpoints by atta -**Important –** Replace `o-1234567890` with your AWS organization ID. +###### Important + +Replace `o-1234567890` with your AWS organization ID. @@ -46 +48,4 @@ Control which identities can access Amazon Bedrock through VPC endpoints by atta -**AllowOrganizationAccess** – Permits Amazon Bedrock API calls only from identities within your AWSorganization, creating an identity boundary at the VPC endpoint level. + * **AllowOrganizationAccess** – Permits Amazon Bedrock API calls only from identities within your AWSorganization, creating an identity boundary at the VPC endpoint level. + + + @@ -50 +55 @@ Control which identities can access Amazon Bedrock through VPC endpoints by atta -– For network-based VPC endpoint controls, see the Network Perimeter section. +For network-based VPC endpoint controls, see the [Network Perimeter](./network-perimeter.html) section.