Authorize the Secrets Manager endpoint separately from choosing a private route

A private Secrets Manager connection still needs an endpoint access policy that matches the intended callers and secrets.

A controlled technology lifecycle progressing from assessment to approved production.
DSE visual intelligenceManaged IT operationsGuide · 2 min read
Executive summary

What you need to know

A private Secrets Manager connection still needs an endpoint access policy that matches the intended callers and secrets.

Potentially affected

This concerns the Secrets Manager interface endpoint. Review endpoint access policies for application and Lambda rotation callers.

DSE recommendation

DSE recommends mapping each application and rotation function that should use the endpoint.

A private Secrets Manager connection still needs an endpoint access policy that matches the intended callers and secrets.

Source facts

Secrets Manager supports interface VPC endpoints through AWS PrivateLink. With private DNS enabled, applications can use the Region’s normal Secrets Manager hostname through the endpoint. AWS documents a default endpoint policy allowing full Secrets Manager access through that endpoint and allows a custom policy specifying principals, actions and resources. Endpoint routing and endpoint-policy scope are therefore separate configuration choices.

Source: AWS — Using an AWS Secrets Manager VPC endpoint.

Applicability

This concerns the Secrets Manager interface endpoint. Review endpoint access policies for application and Lambda rotation callers.

DSE recommendation

DSE recommends mapping each application and rotation function that should use the endpoint. Define a narrow endpoint policy using the required actions and secret identifiers, then review it alongside the rest of the access design. Check DNS behavior from the actual workload network. Preserve an approved administrative recovery path before enforcing conditions that could exclude legitimate service calls. Require the network and secret owners to approve the same workload-to-secret access matrix. Keep an endpoint-specific denial in the test plan and identify the recovery contact before tightening policy, so a connectivity incident does not prompt an unreviewed full-access exception.

Verification

Proposed verification: from an authorized test workload, resolve the regional hostname and inspect the selected endpoint path. Verify retrieval of a permitted test secret and rejection of a secret outside the intended scope. Exercise rotation dependencies separately, retaining metadata and access outcomes while keeping secret values out of the evidence.

Official reference

AWS — Using an AWS Secrets Manager VPC endpoint. Reviewed October 20, 2026.

Primary reference

Review the official source

AWS — Using an AWS Secrets Manager VPC endpoint · Verified October 20, 2026

Open official reference ↗
Plan the next step

Need help applying this guidance safely?

DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.

Talk with DSE