[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Give me a comprehensive overview of agent instructions in AWS DevOps Agent.

[Assistant]
# Agent instructions

Use agent instructions to provide always-on guidance that AWS DevOps Agent applies to every session. A session is a single conversation or investigation with an agent. On the **Knowledge** page in your Agent Space Operator Web App, choose the **Instructions** tab to set instructions that apply to all agents, or set instructions for a specific managed agent such as Chat or Incident triage. These instructions are stored as an AGENTS.md file. Unlike DevOps Agent Skills, which load on demand when the agent matches a skill description to the current task, agent instructions are always present from the start of every session, regardless of what the agent is working on.

## What are agent instructions

Agent instructions provide unconditional, always-on guidance for your agents. At the start of every session, the agent service retrieves the instructions configured for your Agent Space and injects their content directly into the agent system prompt. The agent does not decide whether to load them; they are always present.

Each agent session receives instructions from both the global instructions and the relevant agent-specific instructions.

Agent instructions are stored as AGENTS.md files and differ from DevOps Agent Skills in several important ways:

| Aspect | Skill | Agent instructions (AGENTS.md) |
| --- | --- | --- |
| Name and description | Required | Not applicable |
| Content format | Markdown or ZIP bundle | Markdown only |
| Resource files | Supported | Not supported |
| Context injection | On demand (agent decides via skill description matching) | Always (unconditional, every session) |
| Uniqueness | Multiple per Agent Space | One per agent |

## Why use agent instructions

Agent instructions give you a reliable way to ensure certain guidance is always in context, without depending on the agent's skill-loading decisions.

**Key benefits:**
+ **Predictability:** Instructions are always present, regardless of what task the agent is working on.
+ **Guaranteed coverage:** Unlike Skills, which the agent may or may not load depending on task relevance, agent instructions are always injected at the start of every session.
+ **Standing policies:** Use agent instructions for standing operational policies, security guidelines, coding standards, or any guidance that must apply to every session without exception.
+ **Targeted scope:** You can apply instructions to all agent types at once using global instructions, or restrict instructions to a specific agent type.

## How agent instructions work

When a session starts, the agent service retrieves the instructions configured for your Agent Space and injects their content into the agent system prompt before the session begins. This happens automatically for every session.

Each new session loads the instructions fresh at startup. If you update your instructions, the change takes effect immediately for sessions that start after you save.

## Agent type scoping

Scoping controls which agent sessions receive a given set of instructions:
+ **Global instructions:** Applies to all agent types in your Agent Space.
+ **Agent-specific:** Applies only to sessions of the selected agent type.

The managed agents available for agent-specific instructions are:
+ **Chat** - Ad-hoc questions and requests during chat sessions.
+ **Incident triage** - Alarm filtering, severity classification, and initial scoping.
+ **Incident RCA** - Root cause analysis with evidence collection and validation.
+ **Incident mitigation** - Short-term remediation and long-term fix recommendations.
+ **Evaluation** - Agent performance scoring and policy compliance checks.

## Content size guidance

+ **Hard limit:** 25 KB
+ **Recommended size:** 120 lines

Focus your instructions on guidance that must be present in every session. For specialized investigation procedures, consider using DevOps Agent Skills instead.

## Example

```
# Agent Instructions

## Investigation approach
- Always check CloudWatch alarms and recent deployments before proposing a root cause.

## Response format
- Lead with a one-sentence summary of findings before listing details.
- Include the AWS region and resource identifier for any resource you reference.
- Use bullet points for lists of findings or recommendations.

## Security
- Never log, display, or suggest storing credentials or secrets in plaintext.
- When recommending IAM changes, follow least-privilege principles.
```

## Setting agent instructions

Each agent has exactly one set of instructions. When you save new content, it overwrites the existing content for that agent.

**To set global instructions (applies to all agents):**
1. Navigate to the **Knowledge** page in your Agent Space Operator Web App.
2. Choose the **Instructions** tab.
3. Choose **View** next to **All agents**.
4. Enter your markdown instructions in the editor.
5. Choose **Save**.

**To set instructions for a specific agent:**
1. Navigate to the **Knowledge** page in your Agent Space Operator Web App.
2. Choose the **Instructions** tab.
3. Choose **View** next to the agent you want to configure.
4. Enter your markdown instructions in the editor.
5. Choose **Save**.

## Managing agent instructions

**Viewing instructions:** Navigate to the **Knowledge** page, choose the **Instructions** tab, and choose **View** next to the agent.

**Editing instructions:** Open the agent, modify the content, and choose **Save**.

**Uploading instructions from a file:** Choose the **Upload** button to upload a markdown file.

**Downloading instructions:** Choose the **Download** button to download the current content.

**Deleting instructions:** Choose the **Delete** button and confirm the deletion.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is agent instructions?

[Assistant]
# Agent instructions

Use agent instructions to provide always-on guidance that AWS DevOps Agent applies to every session. A session is a single conversation or investigation with an agent. On the **Knowledge** page in your Agent Space Operator Web App, choose the **Instructions** tab to set instructions that apply to all agents, or set instructions for a specific managed agent such as Chat or Incident triage. These instructions are stored as an AGENTS.md file. Unlike DevOps Agent Skills, which load on demand when the agent matches a skill description to the current task, agent instructions are always present from the start of every session, regardless of what the agent is working on.

## What are agent instructions

Agent instructions provide unconditional, always-on guidance for your agents. At the start of every session, the agent service retrieves the instructions configured for your Agent Space and injects their content directly into the agent system prompt. The agent does not decide whether to load them; they are always present.

Each agent session receives instructions from both the global instructions and the relevant agent-specific instructions.

Agent instructions are stored as AGENTS.md files and differ from DevOps Agent Skills in several important ways:

| Aspect | Skill | Agent instructions (AGENTS.md) |
| --- | --- | --- |
| Name and description | Required | Not applicable |
| Content format | Markdown or ZIP bundle | Markdown only |
| Resource files | Supported | Not supported |
| Context injection | On demand (agent decides via skill description matching) | Always (unconditional, every session) |
| Uniqueness | Multiple per Agent Space | One per agent |

## Why use agent instructions

Agent instructions give you a reliable way to ensure certain guidance is always in context, without depending on the agent's skill-loading decisions.

**Key benefits:**
+ **Predictability:** Instructions are always present, regardless of what task the agent is working on.
+ **Guaranteed coverage:** Unlike Skills, which the agent may or may not load depending on task relevance, agent instructions are always injected at the start of every session.
+ **Standing policies:** Use agent instructions for standing operational policies, security guidelines, coding standards, or any guidance that must apply to every session without exception.
+ **Targeted scope:** You can apply instructions to all agent types at once using global instructions, or restrict instructions to a specific agent type.

## How agent instructions work

When a session starts, the agent service retrieves the instructions configured for your Agent Space and injects their content into the agent system prompt before the session begins. This happens automatically for every session.

Each new session loads the instructions fresh at startup. If you update your instructions, the change takes effect immediately for sessions that start after you save.

## Agent type scoping

Scoping controls which agent sessions receive a given set of instructions:
+ **Global instructions:** Applies to all agent types in your Agent Space.
+ **Agent-specific:** Applies only to sessions of the selected agent type.

The managed agents available for agent-specific instructions are:
+ **Chat** - Ad-hoc questions and requests during chat sessions.
+ **Incident triage** - Alarm filtering, severity classification, and initial scoping.
+ **Incident RCA** - Root cause analysis with evidence collection and validation.
+ **Incident mitigation** - Short-term remediation and long-term fix recommendations.
+ **Evaluation** - Agent performance scoring and policy compliance checks.

## Content size guidance

+ **Hard limit:** 25 KB
+ **Recommended size:** 120 lines

Focus your instructions on guidance that must be present in every session. For specialized investigation procedures, consider using DevOps Agent Skills instead.

## Example

```
# Agent Instructions

## Investigation approach
- Always check CloudWatch alarms and recent deployments before proposing a root cause.

## Response format
- Lead with a one-sentence summary of findings before listing details.
- Include the AWS region and resource identifier for any resource you reference.
- Use bullet points for lists of findings or recommendations.

## Security
- Never log, display, or suggest storing credentials or secrets in plaintext.
- When recommending IAM changes, follow least-privilege principles.
```

## Setting agent instructions

Each agent has exactly one set of instructions. When you save new content, it overwrites the existing content for that agent.

**To set global instructions (applies to all agents):**
1. Navigate to the **Knowledge** page in your Agent Space Operator Web App.
2. Choose the **Instructions** tab.
3. Choose **View** next to **All agents**.
4. Enter your markdown instructions in the editor.
5. Choose **Save**.

**To set instructions for a specific agent:**
1. Navigate to the **Knowledge** page in your Agent Space Operator Web App.
2. Choose the **Instructions** tab.
3. Choose **View** next to the agent you want to configure.
4. Enter your markdown instructions in the editor.
5. Choose **Save**.

## Managing agent instructions

**Viewing instructions:** Navigate to the **Knowledge** page, choose the **Instructions** tab, and choose **View** next to the agent.

**Editing instructions:** Open the agent, modify the content, and choose **Save**.

**Uploading instructions from a file:** Choose the **Upload** button to upload a markdown file.

**Downloading instructions:** Choose the **Download** button to download the current content.

**Deleting instructions:** Choose the **Delete** button and confirm the deletion.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is Agent instructions in AWS DevOps Agent?

[Assistant] Use agent instructions to provide always-on guidance that AWS DevOps Agent applies to every session. A session is a single conversation or investigation with an agent. On the **Knowledge** page in your Agent Space Operator Web App, choose the **Instructions** tab to set instructions that apply to all agents, or set instructions for a specific managed agent such as Chat or Incident triage. These instructions are stored as an AGENTS.md file. Unlike DevOps Agent Skills, which load on demand when the agent matches a skill description to the current task, agent instructions are always present from the start of every session, regardless of what the agent is working on.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about Agent instructions in AWS DevOps Agent.

[Assistant] Use agent instructions to provide always-on guidance that AWS DevOps Agent applies to every session. A session is a single conversation or investigation with an agent. On the **Knowledge** page in your Agent Space Operator Web App, choose the **Instructions** tab to set instructions that apply to all agents, or set instructions for a specific managed agent such as Chat or Incident triage. These instructions are stored as an AGENTS.md file. Unlike DevOps Agent Skills, which load on demand when the agent matches a skill description to the current task, agent instructions are always present from the start of every session, regardless of what the agent is working on.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is What are agent instructions in AWS DevOps Agent?

[Assistant]
Agent instructions provide unconditional, always-on guidance for your agents. At the start of every session, the agent service retrieves the instructions configured for your Agent Space and injects their content directly into the agent system prompt. The agent does not decide whether to load them; they are always present.

Each agent session receives instructions from both the global instructions and the relevant agent-specific instructions.

Agent instructions are stored as AGENTS.md files and differ from DevOps Agent Skills in several important ways:

| Aspect | Skill | Agent instructions (AGENTS.md) |
| --- | --- | --- |
| Name and description | Required | Not applicable |
| Content format | Markdown or ZIP bundle | Markdown only |
| Resource files | Supported | Not supported |
| Context injection | On demand (agent decides via skill description matching) | Always (unconditional, every session) |
| Uniqueness | Multiple per Agent Space | One per agent |


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about What are agent instructions in AWS DevOps Agent.

[Assistant]
Agent instructions provide unconditional, always-on guidance for your agents. At the start of every session, the agent service retrieves the instructions configured for your Agent Space and injects their content directly into the agent system prompt. The agent does not decide whether to load them; they are always present.

Each agent session receives instructions from both the global instructions and the relevant agent-specific instructions.

Agent instructions are stored as AGENTS.md files and differ from DevOps Agent Skills in several important ways:

| Aspect | Skill | Agent instructions (AGENTS.md) |
| --- | --- | --- |
| Name and description | Required | Not applicable |
| Content format | Markdown or ZIP bundle | Markdown only |
| Resource files | Supported | Not supported |
| Context injection | On demand (agent decides via skill description matching) | Always (unconditional, every session) |
| Uniqueness | Multiple per Agent Space | One per agent |


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is Why use agent instructions in AWS DevOps Agent?

[Assistant]
Agent instructions give you a reliable way to ensure certain guidance is always in context, without depending on the agent's skill-loading decisions.

**Key benefits:**
+ **Predictability:** Instructions are always present, regardless of what task the agent is working on.
+ **Guaranteed coverage:** Unlike Skills, which the agent may or may not load depending on task relevance, agent instructions are always injected at the start of every session.
+ **Standing policies:** Use agent instructions for standing operational policies, security guidelines, coding standards, or any guidance that must apply to every session without exception.
+ **Targeted scope:** You can apply instructions to all agent types at once using global instructions, or restrict instructions to a specific agent type.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about Why use agent instructions in AWS DevOps Agent.

[Assistant]
Agent instructions give you a reliable way to ensure certain guidance is always in context, without depending on the agent's skill-loading decisions.

**Key benefits:**
+ **Predictability:** Instructions are always present, regardless of what task the agent is working on.
+ **Guaranteed coverage:** Unlike Skills, which the agent may or may not load depending on task relevance, agent instructions are always injected at the start of every session.
+ **Standing policies:** Use agent instructions for standing operational policies, security guidelines, coding standards, or any guidance that must apply to every session without exception.
+ **Targeted scope:** You can apply instructions to all agent types at once using global instructions, or restrict instructions to a specific agent type.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is How agent instructions work in AWS DevOps Agent?

[Assistant]
When a session starts, the agent service retrieves the instructions configured for your Agent Space and injects their content into the agent system prompt before the session begins. This happens automatically for every session.

Each new session loads the instructions fresh at startup. If you update your instructions, the change takes effect immediately for sessions that start after you save.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about How agent instructions work in AWS DevOps Agent.

[Assistant]
When a session starts, the agent service retrieves the instructions configured for your Agent Space and injects their content into the agent system prompt before the session begins. This happens automatically for every session.

Each new session loads the instructions fresh at startup. If you update your instructions, the change takes effect immediately for sessions that start after you save.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is Agent type scoping in AWS DevOps Agent?

[Assistant]
Scoping controls which agent sessions receive a given set of instructions:
+ **Global instructions:** Applies to all agent types in your Agent Space.
+ **Agent-specific:** Applies only to sessions of the selected agent type.

The managed agents available for agent-specific instructions are:
+ **Chat** - Ad-hoc questions and requests during chat sessions.
+ **Incident triage** - Alarm filtering, severity classification, and initial scoping.
+ **Incident RCA** - Root cause analysis with evidence collection and validation.
+ **Incident mitigation** - Short-term remediation and long-term fix recommendations.
+ **Evaluation** - Agent performance scoring and policy compliance checks.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about Agent type scoping in AWS DevOps Agent.

[Assistant]
Scoping controls which agent sessions receive a given set of instructions:
+ **Global instructions:** Applies to all agent types in your Agent Space.
+ **Agent-specific:** Applies only to sessions of the selected agent type.

The managed agents available for agent-specific instructions are:
+ **Chat** - Ad-hoc questions and requests during chat sessions.
+ **Incident triage** - Alarm filtering, severity classification, and initial scoping.
+ **Incident RCA** - Root cause analysis with evidence collection and validation.
+ **Incident mitigation** - Short-term remediation and long-term fix recommendations.
+ **Evaluation** - Agent performance scoring and policy compliance checks.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is Content size guidance in AWS DevOps Agent?

[Assistant]
+ **Hard limit:** 25 KB
+ **Recommended size:** 120 lines

Focus your instructions on guidance that must be present in every session. For specialized investigation procedures, consider using DevOps Agent Skills instead.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about Content size guidance in AWS DevOps Agent.

[Assistant]
+ **Hard limit:** 25 KB
+ **Recommended size:** 120 lines

Focus your instructions on guidance that must be present in every session. For specialized investigation procedures, consider using DevOps Agent Skills instead.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is Investigation approach in AWS DevOps Agent?

[Assistant] - Always check CloudWatch alarms and recent deployments before proposing a root cause.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about Investigation approach in AWS DevOps Agent.

[Assistant] - Always check CloudWatch alarms and recent deployments before proposing a root cause.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is Response format in AWS DevOps Agent?

[Assistant]
- Lead with a one-sentence summary of findings before listing details.
- Include the AWS region and resource identifier for any resource you reference.
- Use bullet points for lists of findings or recommendations.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about Response format in AWS DevOps Agent.

[Assistant]
- Lead with a one-sentence summary of findings before listing details.
- Include the AWS region and resource identifier for any resource you reference.
- Use bullet points for lists of findings or recommendations.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] How does agent instructions work in AWS DevOps Agent?

[Assistant]
- Never log, display, or suggest storing credentials or secrets in plaintext.
- When recommending IAM changes, follow least-privilege principles.
```


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What security features does AWS DevOps Agent provide for agent instructions?

[Assistant]
- Never log, display, or suggest storing credentials or secrets in plaintext.
- When recommending IAM changes, follow least-privilege principles.
```


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is Setting agent instructions in AWS DevOps Agent?

[Assistant]
Each agent has exactly one set of instructions. When you save new content, it overwrites the existing content for that agent.

**To set global instructions (applies to all agents):**
1. Navigate to the **Knowledge** page in your Agent Space Operator Web App.
2. Choose the **Instructions** tab.
3. Choose **View** next to **All agents**.
4. Enter your markdown instructions in the editor.
5. Choose **Save**.

**To set instructions for a specific agent:**
1. Navigate to the **Knowledge** page in your Agent Space Operator Web App.
2. Choose the **Instructions** tab.
3. Choose **View** next to the agent you want to configure.
4. Enter your markdown instructions in the editor.
5. Choose **Save**.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about Setting agent instructions in AWS DevOps Agent.

[Assistant]
Each agent has exactly one set of instructions. When you save new content, it overwrites the existing content for that agent.

**To set global instructions (applies to all agents):**
1. Navigate to the **Knowledge** page in your Agent Space Operator Web App.
2. Choose the **Instructions** tab.
3. Choose **View** next to **All agents**.
4. Enter your markdown instructions in the editor.
5. Choose **Save**.

**To set instructions for a specific agent:**
1. Navigate to the **Knowledge** page in your Agent Space Operator Web App.
2. Choose the **Instructions** tab.
3. Choose **View** next to the agent you want to configure.
4. Enter your markdown instructions in the editor.
5. Choose **Save**.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is Managing agent instructions in AWS DevOps Agent?

[Assistant]
**Viewing instructions:** Navigate to the **Knowledge** page, choose the **Instructions** tab, and choose **View** next to the agent.

**Editing instructions:** Open the agent, modify the content, and choose **Save**.

**Uploading instructions from a file:** Choose the **Upload** button to upload a markdown file.

**Downloading instructions:** Choose the **Download** button to download the current content.

**Deleting instructions:** Choose the **Delete** button and confirm the deletion.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about Managing agent instructions in AWS DevOps Agent.

[Assistant]
**Viewing instructions:** Navigate to the **Knowledge** page, choose the **Instructions** tab, and choose **View** next to the agent.

**Editing instructions:** Open the agent, modify the content, and choose **Save**.

**Uploading instructions from a file:** Choose the **Upload** button to upload a markdown file.

**Downloading instructions:** Choose the **Download** button to download the current content.

**Deleting instructions:** Choose the **Delete** button and confirm the deletion.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Give me a comprehensive overview of devops agent memories in AWS DevOps Agent.

[Assistant]
# DevOps Agent Memories

Memories are informational knowledge items that AWS DevOps Agent builds and maintains to supplement its capabilities with synthesized, high-signal context specific to your Agent Space. Unlike DevOps Agent Skills, which encode procedural knowledge and extend agent capabilities, memories encode informational knowledge that helps agents make faster and more accurate decisions during investigations.

## What are memories

A *memory* is a single markdown file that captures synthesized information relevant to your Agent Space. Examples include recurring root causes for a specific alarm, known environmental quirks, or user-specific preferences. Memories do not extend agent capabilities; they provide context the agent uses to make better decisions.

A *memory store* is a collection of related memory files. Each memory store has a name and description that agents use to decide whether to browse its contents. Memory stores are the organizational containers that group memories by topic.

Memories differ from other knowledge item types in key ways:

| Aspect | Skill | Agent instructions | Memory |
| --- | --- | --- | --- |
| Knowledge type | Procedural (instructions) | Procedural (always-on instructions) | Informational (synthesized context) |
| Content format | Markdown or ZIP bundle | Markdown only | Markdown only |
| Context injection | On demand (agent decides via description matching) | Always (every session) | On demand (agent decides via description matching) |
| Created by | User (UI, CLI), DevOps Agent | User (UI, CLI) | User (via Chat), DevOps Agent (Learning agent) |

## Why use memories

Memories give agents access to historical patterns and environmental knowledge that would otherwise be lost between sessions.

**Key benefits:**
+ **Faster investigations** - Agents recall recent root causes for specific monitors, avoiding redundant diagnostic steps when a recurring issue fires again.
+ **Environmental awareness** - Memories capture environment-specific details such as known noisy alarms, infrastructure quirks, or component relationships that are difficult to re-discover each session.
+ **Continuous improvement** - As the DevOps Agent resolves more incidents, it automatically builds a richer knowledge base of patterns and root causes specific to your infrastructure.
+ **User preferences** - Memories record communication preferences and directives so the agent consistently behaves according to your expectations.

## How memories work

When an agent session starts, the agent receives a list of memory stores with their names and descriptions. During an investigation, the agent evaluates whether a memory store is relevant to the current task. If it is, the agent lists the memories within that store and reads the specific memory files it needs. This progressive-disclosure pattern keeps context consumption low while making all relevant knowledge accessible.

Each memory is versioned. Every update creates a new immutable version, enabling audit trails and rollback to previous content.

## Managed memory stores

DevOps Agent creates and maintains the following managed memory stores automatically as it learns from sessions in your Agent Space:

### monitors

Per-monitor recurring root cause history. Each memory file corresponds to a specific monitor (alarm or metric) and lists the cause categories that have produced incidents for that alarm, with per-investigation evidence. Agents read the entry matching the firing alarm before triaging to quickly identify whether the current incident matches a known pattern.

When there are investigations in the past 2 weeks in the Agent Space, a Learning agent runs once per day to analyze recent investigations, then extract and store memories in this store. Memory items in this store are deleted when they have no updates for 2 weeks.

### directives

User-authored directives that steer agent behavior. Use this store to record standing instructions the agent should follow, such as infrastructure conventions or naming preferences.

Examples:
+ "Lambdas are no longer used. The service uses Fargate."
+ "The storage service is called Orders Storage Service."

## Viewing memories

You can view all memory stores and their contents from the **Knowledge** page in your Agent Space Operator Web App.

**To view memory stores:**
1. Navigate to the **Knowledge** page in your Agent Space Operator Web App.
2. Choose the **Memories** tab.
3. Browse the list of managed memory stores.

**To view memories within a store:**
1. On the **Memories** tab, choose **View** next to the memory store you want to explore.
2. The store detail page lists all memories with their name, description, version number, and last modified date.

**To view a specific memory:**
1. From the store detail page, choose **View** next to the memory you want to read.
2. The memory detail page displays the rendered markdown content along with creation date, last modified date, and a version selector.

## Activating and deactivating memories

You can toggle individual memory stores or individual memories active or inactive without deleting them.

**To toggle a memory store:**
1. On the **Memories** tab, use the toggle switch next to the memory store.
2. When inactive, agents do not access any memories within that store.

**To toggle an individual memory:**
1. Navigate into a memory store to see its list of memories.
2. Use the toggle switch next to the memory you want to activate or deactivate.

## Editing memories with Chat

You can create, update, or delete memories by chatting with the DevOps Agent in the Chat interface.

**Examples of Chat commands:**
+ "Remember that the storage service is called Orders Storage Service"
+ "Update the memory for the canary alarm to note that it is flaky during deployments"
+ "Delete the memory about the old database connection string"

## Memory limits

| Resource | Limit |
| --- | --- |
| Memory stores per Agent Space | 50 |
| Memories per memory store | 200 |
| Individual memory content size | 100 KB |


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is devops agent memories?

[Assistant]
# DevOps Agent Memories

Memories are informational knowledge items that AWS DevOps Agent builds and maintains to supplement its capabilities with synthesized, high-signal context specific to your Agent Space. Unlike DevOps Agent Skills, which encode procedural knowledge and extend agent capabilities, memories encode informational knowledge that helps agents make faster and more accurate decisions during investigations.

## What are memories

A *memory* is a single markdown file that captures synthesized information relevant to your Agent Space. Examples include recurring root causes for a specific alarm, known environmental quirks, or user-specific preferences. Memories do not extend agent capabilities; they provide context the agent uses to make better decisions.

A *memory store* is a collection of related memory files. Each memory store has a name and description that agents use to decide whether to browse its contents. Memory stores are the organizational containers that group memories by topic.

Memories differ from other knowledge item types in key ways:

| Aspect | Skill | Agent instructions | Memory |
| --- | --- | --- | --- |
| Knowledge type | Procedural (instructions) | Procedural (always-on instructions) | Informational (synthesized context) |
| Content format | Markdown or ZIP bundle | Markdown only | Markdown only |
| Context injection | On demand (agent decides via description matching) | Always (every session) | On demand (agent decides via description matching) |
| Created by | User (UI, CLI), DevOps Agent | User (UI, CLI) | User (via Chat), DevOps Agent (Learning agent) |

## Why use memories

Memories give agents access to historical patterns and environmental knowledge that would otherwise be lost between sessions.

**Key benefits:**
+ **Faster investigations** - Agents recall recent root causes for specific monitors, avoiding redundant diagnostic steps when a recurring issue fires again.
+ **Environmental awareness** - Memories capture environment-specific details such as known noisy alarms, infrastructure quirks, or component relationships that are difficult to re-discover each session.
+ **Continuous improvement** - As the DevOps Agent resolves more incidents, it automatically builds a richer knowledge base of patterns and root causes specific to your infrastructure.
+ **User preferences** - Memories record communication preferences and directives so the agent consistently behaves according to your expectations.

## How memories work

When an agent session starts, the agent receives a list of memory stores with their names and descriptions. During an investigation, the agent evaluates whether a memory store is relevant to the current task. If it is, the agent lists the memories within that store and reads the specific memory files it needs. This progressive-disclosure pattern keeps context consumption low while making all relevant knowledge accessible.

Each memory is versioned. Every update creates a new immutable version, enabling audit trails and rollback to previous content.

## Managed memory stores

DevOps Agent creates and maintains the following managed memory stores automatically as it learns from sessions in your Agent Space:

### monitors

Per-monitor recurring root cause history. Each memory file corresponds to a specific monitor (alarm or metric) and lists the cause categories that have produced incidents for that alarm, with per-investigation evidence. Agents read the entry matching the firing alarm before triaging to quickly identify whether the current incident matches a known pattern.

When there are investigations in the past 2 weeks in the Agent Space, a Learning agent runs once per day to analyze recent investigations, then extract and store memories in this store. Memory items in this store are deleted when they have no updates for 2 weeks.

### directives

User-authored directives that steer agent behavior. Use this store to record standing instructions the agent should follow, such as infrastructure conventions or naming preferences.

Examples:
+ "Lambdas are no longer used. The service uses Fargate."
+ "The storage service is called Orders Storage Service."

## Viewing memories

You can view all memory stores and their contents from the **Knowledge** page in your Agent Space Operator Web App.

**To view memory stores:**
1. Navigate to the **Knowledge** page in your Agent Space Operator Web App.
2. Choose the **Memories** tab.
3. Browse the list of managed memory stores.

**To view memories within a store:**
1. On the **Memories** tab, choose **View** next to the memory store you want to explore.
2. The store detail page lists all memories with their name, description, version number, and last modified date.

**To view a specific memory:**
1. From the store detail page, choose **View** next to the memory you want to read.
2. The memory detail page displays the rendered markdown content along with creation date, last modified date, and a version selector.

## Activating and deactivating memories

You can toggle individual memory stores or individual memories active or inactive without deleting them.

**To toggle a memory store:**
1. On the **Memories** tab, use the toggle switch next to the memory store.
2. When inactive, agents do not access any memories within that store.

**To toggle an individual memory:**
1. Navigate into a memory store to see its list of memories.
2. Use the toggle switch next to the memory you want to activate or deactivate.

## Editing memories with Chat

You can create, update, or delete memories by chatting with the DevOps Agent in the Chat interface.

**Examples of Chat commands:**
+ "Remember that the storage service is called Orders Storage Service"
+ "Update the memory for the canary alarm to note that it is flaky during deployments"
+ "Delete the memory about the old database connection string"

## Memory limits

| Resource | Limit |
| --- | --- |
| Memory stores per Agent Space | 50 |
| Memories per memory store | 200 |
| Individual memory content size | 100 KB |


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is DevOps Agent Memories in AWS DevOps Agent?

[Assistant] Memories are informational knowledge items that AWS DevOps Agent builds and maintains to supplement its capabilities with synthesized, high-signal context specific to your Agent Space. Unlike DevOps Agent Skills, which encode procedural knowledge and extend agent capabilities, memories encode informational knowledge that helps agents make faster and more accurate decisions during investigations.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about DevOps Agent Memories in AWS DevOps Agent.

[Assistant] Memories are informational knowledge items that AWS DevOps Agent builds and maintains to supplement its capabilities with synthesized, high-signal context specific to your Agent Space. Unlike DevOps Agent Skills, which encode procedural knowledge and extend agent capabilities, memories encode informational knowledge that helps agents make faster and more accurate decisions during investigations.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is What are memories in AWS DevOps Agent?

[Assistant]
A *memory* is a single markdown file that captures synthesized information relevant to your Agent Space. Examples include recurring root causes for a specific alarm, known environmental quirks, or user-specific preferences. Memories do not extend agent capabilities; they provide context the agent uses to make better decisions.

A *memory store* is a collection of related memory files. Each memory store has a name and description that agents use to decide whether to browse its contents. Memory stores are the organizational containers that group memories by topic.

Memories differ from other knowledge item types in key ways:

| Aspect | Skill | Agent instructions | Memory |
| --- | --- | --- | --- |
| Knowledge type | Procedural (instructions) | Procedural (always-on instructions) | Informational (synthesized context) |
| Content format | Markdown or ZIP bundle | Markdown only | Markdown only |
| Context injection | On demand (agent decides via description matching) | Always (every session) | On demand (agent decides via description matching) |
| Created by | User (UI, CLI), DevOps Agent | User (UI, CLI) | User (via Chat), DevOps Agent (Learning agent) |


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about What are memories in AWS DevOps Agent.

[Assistant]
A *memory* is a single markdown file that captures synthesized information relevant to your Agent Space. Examples include recurring root causes for a specific alarm, known environmental quirks, or user-specific preferences. Memories do not extend agent capabilities; they provide context the agent uses to make better decisions.

A *memory store* is a collection of related memory files. Each memory store has a name and description that agents use to decide whether to browse its contents. Memory stores are the organizational containers that group memories by topic.

Memories differ from other knowledge item types in key ways:

| Aspect | Skill | Agent instructions | Memory |
| --- | --- | --- | --- |
| Knowledge type | Procedural (instructions) | Procedural (always-on instructions) | Informational (synthesized context) |
| Content format | Markdown or ZIP bundle | Markdown only | Markdown only |
| Context injection | On demand (agent decides via description matching) | Always (every session) | On demand (agent decides via description matching) |
| Created by | User (UI, CLI), DevOps Agent | User (UI, CLI) | User (via Chat), DevOps Agent (Learning agent) |


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is Why use memories in AWS DevOps Agent?

[Assistant]
Memories give agents access to historical patterns and environmental knowledge that would otherwise be lost between sessions.

**Key benefits:**
+ **Faster investigations** - Agents recall recent root causes for specific monitors, avoiding redundant diagnostic steps when a recurring issue fires again.
+ **Environmental awareness** - Memories capture environment-specific details such as known noisy alarms, infrastructure quirks, or component relationships that are difficult to re-discover each session.
+ **Continuous improvement** - As the DevOps Agent resolves more incidents, it automatically builds a richer knowledge base of patterns and root causes specific to your infrastructure.
+ **User preferences** - Memories record communication preferences and directives so the agent consistently behaves according to your expectations.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about Why use memories in AWS DevOps Agent.

[Assistant]
Memories give agents access to historical patterns and environmental knowledge that would otherwise be lost between sessions.

**Key benefits:**
+ **Faster investigations** - Agents recall recent root causes for specific monitors, avoiding redundant diagnostic steps when a recurring issue fires again.
+ **Environmental awareness** - Memories capture environment-specific details such as known noisy alarms, infrastructure quirks, or component relationships that are difficult to re-discover each session.
+ **Continuous improvement** - As the DevOps Agent resolves more incidents, it automatically builds a richer knowledge base of patterns and root causes specific to your infrastructure.
+ **User preferences** - Memories record communication preferences and directives so the agent consistently behaves according to your expectations.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is How memories work in AWS DevOps Agent?

[Assistant]
When an agent session starts, the agent receives a list of memory stores with their names and descriptions. During an investigation, the agent evaluates whether a memory store is relevant to the current task. If it is, the agent lists the memories within that store and reads the specific memory files it needs. This progressive-disclosure pattern keeps context consumption low while making all relevant knowledge accessible.

Each memory is versioned. Every update creates a new immutable version, enabling audit trails and rollback to previous content.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about How memories work in AWS DevOps Agent.

[Assistant]
When an agent session starts, the agent receives a list of memory stores with their names and descriptions. During an investigation, the agent evaluates whether a memory store is relevant to the current task. If it is, the agent lists the memories within that store and reads the specific memory files it needs. This progressive-disclosure pattern keeps context consumption low while making all relevant knowledge accessible.

Each memory is versioned. Every update creates a new immutable version, enabling audit trails and rollback to previous content.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is Managed memory stores in AWS DevOps Agent?

[Assistant] DevOps Agent creates and maintains the following managed memory stores automatically as it learns from sessions in your Agent Space:


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about Managed memory stores in AWS DevOps Agent.

[Assistant] DevOps Agent creates and maintains the following managed memory stores automatically as it learns from sessions in your Agent Space:


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is monitors in AWS DevOps Agent?

[Assistant]
Per-monitor recurring root cause history. Each memory file corresponds to a specific monitor (alarm or metric) and lists the cause categories that have produced incidents for that alarm, with per-investigation evidence. Agents read the entry matching the firing alarm before triaging to quickly identify whether the current incident matches a known pattern.

When there are investigations in the past 2 weeks in the Agent Space, a Learning agent runs once per day to analyze recent investigations, then extract and store memories in this store. Memory items in this store are deleted when they have no updates for 2 weeks.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about monitors in AWS DevOps Agent.

[Assistant]
Per-monitor recurring root cause history. Each memory file corresponds to a specific monitor (alarm or metric) and lists the cause categories that have produced incidents for that alarm, with per-investigation evidence. Agents read the entry matching the firing alarm before triaging to quickly identify whether the current incident matches a known pattern.

When there are investigations in the past 2 weeks in the Agent Space, a Learning agent runs once per day to analyze recent investigations, then extract and store memories in this store. Memory items in this store are deleted when they have no updates for 2 weeks.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is directives in AWS DevOps Agent?

[Assistant]
User-authored directives that steer agent behavior. Use this store to record standing instructions the agent should follow, such as infrastructure conventions or naming preferences.

Examples:
+ "Lambdas are no longer used. The service uses Fargate."
+ "The storage service is called Orders Storage Service."


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about directives in AWS DevOps Agent.

[Assistant]
User-authored directives that steer agent behavior. Use this store to record standing instructions the agent should follow, such as infrastructure conventions or naming preferences.

Examples:
+ "Lambdas are no longer used. The service uses Fargate."
+ "The storage service is called Orders Storage Service."


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is Viewing memories in AWS DevOps Agent?

[Assistant]
You can view all memory stores and their contents from the **Knowledge** page in your Agent Space Operator Web App.

**To view memory stores:**
1. Navigate to the **Knowledge** page in your Agent Space Operator Web App.
2. Choose the **Memories** tab.
3. Browse the list of managed memory stores.

**To view memories within a store:**
1. On the **Memories** tab, choose **View** next to the memory store you want to explore.
2. The store detail page lists all memories with their name, description, version number, and last modified date.

**To view a specific memory:**
1. From the store detail page, choose **View** next to the memory you want to read.
2. The memory detail page displays the rendered markdown content along with creation date, last modified date, and a version selector.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about Viewing memories in AWS DevOps Agent.

[Assistant]
You can view all memory stores and their contents from the **Knowledge** page in your Agent Space Operator Web App.

**To view memory stores:**
1. Navigate to the **Knowledge** page in your Agent Space Operator Web App.
2. Choose the **Memories** tab.
3. Browse the list of managed memory stores.

**To view memories within a store:**
1. On the **Memories** tab, choose **View** next to the memory store you want to explore.
2. The store detail page lists all memories with their name, description, version number, and last modified date.

**To view a specific memory:**
1. From the store detail page, choose **View** next to the memory you want to read.
2. The memory detail page displays the rendered markdown content along with creation date, last modified date, and a version selector.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is Activating and deactivating memories in AWS DevOps Agent?

[Assistant]
You can toggle individual memory stores or individual memories active or inactive without deleting them.

**To toggle a memory store:**
1. On the **Memories** tab, use the toggle switch next to the memory store.
2. When inactive, agents do not access any memories within that store.

**To toggle an individual memory:**
1. Navigate into a memory store to see its list of memories.
2. Use the toggle switch next to the memory you want to activate or deactivate.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about Activating and deactivating memories in AWS DevOps Agent.

[Assistant]
You can toggle individual memory stores or individual memories active or inactive without deleting them.

**To toggle a memory store:**
1. On the **Memories** tab, use the toggle switch next to the memory store.
2. When inactive, agents do not access any memories within that store.

**To toggle an individual memory:**
1. Navigate into a memory store to see its list of memories.
2. Use the toggle switch next to the memory you want to activate or deactivate.


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is Editing memories with Chat in AWS DevOps Agent?

[Assistant]
You can create, update, or delete memories by chatting with the DevOps Agent in the Chat interface.

**Examples of Chat commands:**
+ "Remember that the storage service is called Orders Storage Service"
+ "Update the memory for the canary alarm to note that it is flaky during deployments"
+ "Delete the memory about the old database connection string"


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about Editing memories with Chat in AWS DevOps Agent.

[Assistant]
You can create, update, or delete memories by chatting with the DevOps Agent in the Chat interface.

**Examples of Chat commands:**
+ "Remember that the storage service is called Orders Storage Service"
+ "Update the memory for the canary alarm to note that it is flaky during deployments"
+ "Delete the memory about the old database connection string"


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] What is Memory limits in AWS DevOps Agent?

[Assistant]
| Resource | Limit |
| --- | --- |
| Memory stores per Agent Space | 50 |
| Memories per memory store | 200 |
| Individual memory content size | 100 KB |


[System]
/no_think
You are Tech Advisor, an expert on AWS cloud services with deep knowledge of AWS DevOps Agent.

You have comprehensive knowledge of AWS DevOps Agent including:
- What it is and how it works (Agent Spaces, topology, dual-console architecture)
- Key features: autonomous incident response, proactive prevention, on-demand SRE tasks
- Integrations: CloudWatch, Datadog, Dynatrace, New Relic, Splunk, Grafana, PagerDuty, GitHub, GitLab, Azure DevOps, ServiceNow, Slack
- GA features: Azure/on-prem support, Triage Agent, Learned/Custom Skills, Code Indexing, Private Connections
- Pricing: $0.0083 per agent-second, free trial details, AWS Support credits
- Getting started: Agent Spaces, connecting tools, running investigations
- Security: encryption, customer managed keys, IdP integration, CloudTrail auditing
- Available regions: US East, US West, Frankfurt, Ireland, Sydney, Tokyo

Be concise and structured. Use bullet points where appropriate. Provide accurate, detailed answers.

[User] Tell me about Memory limits in AWS DevOps Agent.

[Assistant]
| Resource | Limit |
| --- | --- |
| Memory stores per Agent Space | 50 |
| Memories per memory store | 200 |
| Individual memory content size | 100 KB |