
Argent with Amazon Web Services
Run Argent in your own AWS account, send Amazon Bedrock calls through it, and let Argent read your account to show whether AWS itself refuses AI calls that go around the gateway.
Argent across Amazon Web Services
Argent Strategic Intelligence is the gateway between your AI agents and the AI models they use. It meets Amazon Web Services in five places.
| Where | What Argent does |
|---|---|
| Runs in your account | One Helm chart on Amazon EKS. The AWS profile exposes only the gateway and the console, through AWS load balancers, and keeps every other service inside the cluster. |
| Governs Amazon Bedrock | Agents send Bedrock calls to the gateway. The gateway signs each upstream call itself with the one IAM credential it holds, so agents hold no AWS keys. See Amazon Bedrock. |
| Agents with no keys | A workload can prove who it is with its own AWS role (an EC2 instance profile, an ECS or EKS task role, or a Lambda role). Argent asks AWS who signed, and maps that role to an agent with a human owner. |
| Keys and evidence | AI keys can stay in AWS Secrets Manager. The signed evidence archive can live in Amazon S3 with Object Lock in compliance mode. |
| Checks the cloud | A read-only coverage scan reads your AWS account and reports whether AWS itself blocks Bedrock calls that skip Argent. The rest of this page is about that scan. |
Why the cloud matters. A gateway governs what goes through it. AWS can make it the only way: a service control policy sets "the maximum available permissions for the IAM users and IAM roles" in your organization, and it never grants any (AWS). One that lets only the gateway's role call Bedrock turns a policy on paper into a refusal from AWS.
What the scan checks in AWS
Every check is read-only. Each one ends in pass, fail or unknown, and the evidence says why.
| Check | Pass means |
|---|---|
| Only Argent's role may call Bedrock | A service control policy in force on the account (attached to it, its organizational units or the root) denies the Bedrock model-call actions to everyone except exactly the registered Argent role. |
| The Bedrock endpoint serves only Argent | Each bedrock-runtime VPC endpoint has a policy that admits only the Argent role. A region with no endpoint passes only when the service control policy check passed. |
| Bedrock model invocation logging | Per region, logging sends text data to a CloudWatch log group or an S3 bucket. Recorded for your auditors; it does not change the verdict. |
The management account is a fail, on purpose. AWS states that service control policies "don't affect users or roles in the management account" (AWS). So a policy there cannot stop anyone, and the scan says so. An account outside any organization reports unknown, with the reason named.
How a scan runs, and what you see
Argent reads the account, judges it, and signs the result.
- Argent signs in read-only. It fetches the scan credential from the Credential Broker by its reference.
- Argent runs every check. On its schedule, every 24 hours by default, or when an admin presses Scan now.
- Argent gives a verdict. Bypass blocked when every check that closes a path passes. Bypass possible when one fails. Unknown when none fails but one could not be read. The invocation-logging check is shown, but it does not change the verdict.
- Argent signs the result. Each scan writes a signed record, and every check whose result changed since the last scan writes another.
- Argent raises an alert on a drop. When an account falls from blocked to possible, an alert opens with the failing checks, and an admin acknowledges it. A return to blocked is signed too.
The scanner talks only to AWS. It signs every request with SigV4 and talks only to organizations.us-east-1, bedrock.<region> and ec2.<region> under amazonaws.com. A region must match a fixed pattern, so a registered value cannot steer a signed request anywhere else. AWS error text is never stored, only its error code.
What you enter in the Argent console
An admin adds the account under Integrations > Discovery > Cloud coverage, with Add account. The form asks for:
| Field | What it is |
|---|---|
| Cloud | AWS. |
| Name | Optional. Shown instead of the account id. |
| Account id (12 digits) | The AWS account to scan. |
| Regions | Where Bedrock is checked, separated by commas. |
| Argent gateway role ARN | The one IAM role allowed to call Bedrock. |
| Credential reference | Where the scanner's access key pair is kept in the Credential Broker, never the keys themselves. |
| Scan every (hours) / Scan on schedule | How often the scan runs on its own. The default is every 24 hours. |
- See every account at a glance. The page counts accounts by verdict, shows each account's last scan, lists open alerts and explains what each check reads and what a pass proves.
- Who can do what. SuperAdmins and tenant admins add accounts and run scans. Auditors can read every result.
- One switch, with a lock. Scanning has one switch per tenant: on, off or locked. Off skips the schedule and refuses Scan now, and deletes nothing. A higher level can lock the switch, and only that level can change or unlock it. Every change is signed, and so is every refused one.
What you set up on the AWS side
One read-only identity, once. Nothing on this list lets Argent change your cloud.
- A read-only IAM user for the scanner with exactly
organizations:Describe*,organizations:List*,bedrock:GetModelInvocationLoggingConfigurationandec2:DescribeVpcEndpoints, and one access key. - Organizations read access. Only the management account or a delegated administrator can list service control policies. Without that access, the policy check reports unknown, with the reason named.
- Its access key pair, saved as one reference. Store
{"access_key_id": ..., "secret_access_key": ...}in the Credential Broker and give Argent the reference. Delete the local copy. - The levers themselves are yours. Your AWS admins write the service control policy and the VPC endpoint policy. Test a service control policy on one organizational unit before the root, as AWS recommends.
Where it fits, and how you start
The scan is how a security team proves the gateway is the only way to the models, not just the easiest one.
- Capabilities: shadow AI discovery, model control, keyless agents, watch before you enforce and one-click audit evidence. All capabilities.
- Goals: see all AI in your company, model control and routing, threat defense, compliance evidence and sovereign AI. All goals.
- Use cases: AI coding agents, customer-facing assistants, enterprise copilots, agent tool access and regulated and air-gapped AI.
- Related integrations: Amazon Bedrock, Bedrock Mantle, AWS Secrets Manager, Kubernetes and Helm, and the scans for Microsoft Azure and Google Cloud.
- Where Argent runs: air-gapped on premises, private cloud or your public cloud VPC. Compare the options.
- Industries: financial services, insurance, healthcare, the public sector and retail. All industries.
- Install. Put the Helm chart in your EKS cluster with the AWS profile, and point Bedrock callers at the gateway.
- Watch. In Watch mode, Argent records what it would have stopped and changes nothing.
- Scan. Add the account under Integrations > Discovery > Cloud coverage and press Scan now. Each failing check is named, with its evidence.
- Enforce and prove. Switch on Enforce, have your admins pull the levers, and scan again until the account reads Bypass blocked. The signed records show when it got there.
Want this running on your own use cases?
Book a demo