Agents on AWS

StratoNext agents are autonomous workers that execute tasks and scheduled jobs against your AWS environments. Today’s agents specialize in AWS troubleshooting: investigating errors, analyzing logs and metrics, producing reports, and proposing changes for approval.

Runtime: Amazon Bedrock AgentCore

Agents run as Amazon Bedrock AgentCore runtimes. When you create an agent, it is deployed to the StratoNext cloud and works on your behalf against your connected environments.

Deploying agents into your own AWS account uses the same AgentCore runtime, provisioned through the deployment and runtime roles in the onboarding template (see IAM roles reference). This keeps the agent’s execution inside your account boundary while StratoNext manages its lifecycle.

Protocol: A2A

Agents communicate with the StratoNext platform over the A2A (Agent2Agent) protocol. The platform dispatches tasks to agents as A2A messages and receives their results the same way. Because the interface is standard A2A, the platform is not tied to a single agent implementation. Support for importing your existing A2A agents is planned.

What agents can and cannot do

• Agents work with the permissions of the environment’s Operations Role, read-only by default.
• Write and sensitive operations require human approval per your automation policy. When an agent hits a permission or approval boundary, it stops, files an approval request with the exact scope it needs, and waits. It never retries or works around the gate.
• Agents cannot approve requests; only humans can.
• Every agent action is recorded with its identity and a correlation ID, and summarized in the workspace journal.

Dispatching work

• Tasks: one-off background work such as investigations, reports, and changes. Not interactive.
• Scheduled jobs: recurring tasks on a cron schedule, assigned to an agent for unattended execution.
• Interactive work: use a local agent with the skill for multi-turn conversations with full platform access.