Docs · Connector reference

Amazon Web Services connector reference

Operations, inputs, troubleshooting, and questions for the Amazon Web Services connection. Policy decides each change before the credential is resolved, and the action record carries the result.

Set up and verify the Amazon Web Services connection

Choose one task and its account, and match the reads and actions on the overview page to it before granting provider permissions.
Prepare the connection settings from the overview page, connect the provider in Deixic, and choose which tools your agent can use.
Try a small task with a known result, and compare the returned identity and resource with what the account owner expects.
Configure approval for sensitive changes, review the destination and inputs, and check the result in the provider before expanding the workflow.

Information your agent can use

Resource	Record identity	Start with	Page coverage
Resources	`Arn`	Top level	Cursor in request body
Inventory coverage	`Id`	Top level	None configured
Security identity findings	`ProductArn` + `Id`	Top level	Cursor in request body
Security storage findings	`ProductArn` + `Id`	Top level	Cursor in request body
Security network findings	`ProductArn` + `Id`	Top level	Cursor in request body
Security logging findings	`ProductArn` + `Id`	Top level	Cursor in request body
Config security	`arn`	Top level	Cursor in request body
IAM credential report	`arn`	Top level	None configured

Record identity: Match on these fields before joining or deduplicating results; where none is specified, check the returned record first.
Start with: Resolve the parent identifier first.
Cursor in request body: Cursor pagination in the request body. Keep the query consistent when continuing to the next page.
None configured: No page continuation is configured for this resource. Check the response and any provider limits before treating it as a complete inventory.

Supported operations

Review the inputs before granting an action to an agent. Required inputs must be supplied, optional inputs narrow the request, and provider permissions apply in addition to Deixic policy.

Read: Retrieves information; check the returned scope and identifiers before use.
Action: Can change provider state; review the target and inputs, then retain the result to avoid repeating completed work.

Operation	Effect	Approval	Provider permissions	Inputs
S3 Public Access Block Get	Read	By policy	s3:GetBucketPublicAccessBlock	3
S3 Public Access Block Enable	Action	Approval required	s3:GetBucketPublicAccessBlock, s3:PutBucketPublicAccessBlock	4

Inputs by operation

S3 Public Access Block Get Read

Inputs for Aws S3 Public Access Block Get
Input	Requirement	Accepted value
`account_id`	Required	string
`bucket`	Required	stringMinimum characters: 3Maximum characters: 63
`region`	Required	stringMinimum characters: 5Maximum characters: 32

S3 Public Access Block Enable Action · approval required

Inputs for Aws S3 Public Access Block Enable
Input	Requirement	Accepted value
`account_id`	Required	string
`bucket`	Required	stringMinimum characters: 3Maximum characters: 63
`expected_configuration_sha256`	Required	string
`region`	Required	stringMinimum characters: 5Maximum characters: 32

When the Amazon Web Services task does not produce the expected result

Connected, but the expected data is missing

Check the identity behind the aws signature v4 connection and its access to the specific resource; a successful connection does not establish access to every object.

Compare the lookup against one known record first, and keep an empty response separate from a permissions error.

The answer covers only part of the data

Check the resource’s page coverage, query filters, and result limit, and have the agent state the account and time window it inspected, so a partial response yields a scoped answer.

The agent keeps doing the same work

Inspect the action history for repeated targets and inputs, keep the successful result’s identifiers with the task, and refresh a lookup only when the information changed.

A change is waiting or failed

Check whether the call awaits approval, was rejected by policy, lacks an input, or failed at the provider, and after a timeout inspect the destination before repeating a write.

See how an action proceeds and how to review an approval.

Questions about the Amazon Web Services connector

Can I use my existing agent with Amazon Web Services?

Yes: connect your agent to Deixic through MCP, choose which connected tools it can use, and Deixic checks calls routed through its gateway; Dex is available if your team also wants an agent.

Can an agent change data in Amazon Web Services?

This connector supports 1 action, listed on its overview page. Configure a connection and choose the tools and provider permissions your task needs; an available action is not permission for every agent to run it, and Deixic policy and any required approval still apply to calls through the gateway.

What do I need to connect Amazon Web Services?

Prepare AWS region; the connection uses AWS Signature v4, and the connected identity’s provider permissions determine which resources it can access.

Does connecting Amazon Web Services keep every answer up to date?

No: an earlier answer is still an earlier answer, so for a decision that depends on current state, have the agent refresh the source and retain the lookup time, and save stable instructions separately from facts that can change.

Amazon Web Services connector overview Docs All connectors