Chat with the AWS DevOps Agent

AgentSpace routing (SigV4 only): If list_agent_spaces is available in your tool list and the multi-space orchestration skill has NOT been invoked yet this session, invoke it first to determine which agent_space_id to use. Then pass agent_space_id on all tool calls below. For bearer token auth this is unnecessary — the token is already scoped to one space.

Chat is the default. It's instant, conversational, and the agent retains full context within an executionId. Only escalate to investigating-incidents-with-aws-devops-agent when the user describes an incident or the agent itself suggests deeper analysis is warranted.

How to send messages

Primary — use the chat tool:

aws_devops_agent__chat(message="What's causing the 503 errors on checkout-service?")
→ {"executionId": "uuid", "answer": "Based on my analysis..."}

One call, full answer. No session setup needed — the tool handles CreateChat + SendMessage + response parsing internally.

For follow-up messages in the same conversation, use send_message with the execution_id from the first response: