---
title: >-
  Bedrock interface VPC endpoints should be available, use private DNS, and have
  a least-privilege policy
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Datadog Security > OOTB Rules > Bedrock interface VPC endpoints should
  be available, use private DNS, and have a least-privilege policy
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Bedrock interface VPC endpoints should be available, use private DNS, and have a least-privilege policy
 
## Description{% #description %}

Interface VPC endpoints (AWS PrivateLink) for Amazon Bedrock should be available and have private DNS enabled, so calls to the standard Bedrock hostnames stay on the AWS private network, and should replace the default full-access policy with one scoped to the principals and actions the workload needs. The rule evaluates interface endpoints for every Bedrock PrivateLink service (for example `bedrock`, `bedrock-runtime`, `bedrock-agent`, `bedrock-agent-runtime`, `bedrock-agentcore.gateway`, and the FIPS variants); other endpoints are skipped, but an endpoint whose service name or type is missing fails. An endpoint also fails when a policy `Allow` statement grants a wildcard principal without a condition that restricts callers, grants every action the endpoint serves (such as `*`, `bedrock:*`, or `bedrock:??*`), or uses `NotAction` without excluding the endpoint's whole action prefix (for example `bedrock-agentcore:*` on an AgentCore endpoint). A wildcard principal counts as restricted only by an `aws:PrincipalOrgID`, `aws:PrincipalOrgPaths`, `aws:PrincipalAccount`, or `aws:PrincipalArn` condition that names a literal account or organization ID, without the `IfExists` or `ForAllValues` variants. A policy with no statements fails, and `Deny` statements are ignored. This is stricter than the CIS audit, which fails only the default policy: equivalent policies also fail, as does a policy that allows specific actions to `Principal: "*"` with no condition, as in the AWS example policy, so an AgentCore Gateway endpoint that uses OAuth inbound authorization cannot pass. The rule cannot detect a VPC that calls Bedrock without an endpoint, and it fails disabled private DNS even though CIS accepts it when callers use the endpoint-specific DNS name, because that cannot be verified from configuration.

## Remediation{% #remediation %}

Enable private DNS on the endpoint and replace its policy with one that names the required principals and Bedrock actions. For more information, see [Use interface VPC endpoints (AWS PrivateLink) to create a private connection between your VPC and Amazon Bedrock](https://docs.aws.amazon.com/bedrock/latest/userguide/vpc-interface-endpoints.html) in the Amazon Bedrock User Guide.

## References{% #references %}

- [Use interface VPC endpoints (AWS PrivateLink) to create a private connection between your VPC and Amazon Bedrock](https://docs.aws.amazon.com/bedrock/latest/userguide/vpc-interface-endpoints.html)
- [CIS Amazon Web Services Benchmarks](https://www.cisecurity.org/benchmark/amazon_web_services)
