AWS Bedrock and AgentCore

Keep Bedrock agents powerful in the cloud and limited in permissions.

Agents on Bedrock and AgentCore touch real resources with IAM roles. AvertGate passes the APIs and tools the agent calls through a second security gate on top of the role.

Request a DemoHow the architecture works
AvertGate · Session trails
AvertGate · Session trailsAvertGate · Session trails
AWS · S3 read passedS3 · bucket delete stoppedCluster · scale change awaiting approval

Runs in front of the AWS and infrastructure tools Bedrock agents reach

AWSAmazon S3KubernetesDockerPostgreSQLSnowflakeCloudflareSlackGitHub
Isolation

An IAM role is not enough; give every call a policy too.

The role defines what can be done; the policy defines what should be done. AvertGate evaluates every API call, arguments included, against your rules.

  • Rules per resource and per argument
  • Destructive actions stop before they run
  • A tool that is not listed is never called
Bedrock agent · AWS calls
  • s3:GetObject raporlar/q3.pdfOpen
  • ec2:RunInstances × 40In approval
  • s3:DeleteBucket muhasebeStopped
Network boundary

Keep data from leaving your cloud.

The gateway runs in your VPC or company network. Tool results and queries stay inside; only redacted events reach the dashboard.

  • Option to run the AI review on your own server
  • Metadata addresses and internal network egress are blocked
  • Works on air-gapped networks too

Your network

Bedrock agent→AvertGate→S3RDS
Only redacted events reach the dashboard. Your data never leaves your network.
Trail

Every agent session on record, start to finish.

What was read, what was run and who approved it in each session. Events are chained, so any backdated change is detected.

  • SHA-256 chained audit log
  • Redacted arguments per event
  • One view for incident review
Audit chainverified
Session startedbedrock-agent-7a3f9…c21e
S3 readreports/q3.pdf7be1…09aa
Approval requestedec2:RunInstancesc4d8…71f0

Frequently asked

Does it work with Bedrock Agents and AgentCore?

If tool calls pass over MCP or HTTP, AvertGate steps in. The agent’s own code does not change.

Is our data sent to AvertGate?

No. The gateway runs on your network. Tool arguments, results and file contents never leave it; only redacted event data reaches the dashboard.

Will it slow our agents down?

Everyday reads and queries flow with a few milliseconds of added latency on average. Only risky actions are put to a person.

More

Irreversible ActionsStop deletes, deployments and money movement before they run.MCP GatewayOne checkpoint for every MCP server and tool.

Take your agents to production with confidence.

Every rollout starts with a demo and a POC on your own agents.

Request a Demo