How to Define Tasks for CloudThinker Autonomous Agent

Overview

This guide will help you create clear and effective task definitions for CloudThinker's autonomous agent. A well-defined task ensures the agent can properly understand and execute your requirements.

Task Template Structure

Every task should include these three essential components:

1. Mission: A clear statement of what needs to be done

2. Goal: The specific outcome you want to achieve

3. Instructions: Step-by-step guidance for the agent

How to Write Each Component

1. Mission Statement

• Keep it short and specific

• Start with an action verb (Example: Optimize, Reduce, Monitor)

• Include the target resource type

• Specify the location/region if applicable

Good examples:

• "Automate right-sizing of EC2 instances in Singapore"

• "Optimize EBS volumes in US-East region"

• "Monitor S3 bucket usage in all regions"

2. Goal Statement

• Define what success looks like

• Make it measurable when possible

• Include any specific criteria or thresholds

Good examples:

• "Ensure all instances are cost-optimized based on usage patterns"

• "Reduce unused EBS volume capacity by 30%"

• "Identify S3 buckets with no access in last 90 days"

3. Instructions

• List specific steps or requirements

• Include any important limitations or conditions

• Specify any required tags or filters

• Note any special permissions or restrictions

Good examples:

Instructions:
1. Identify all right-sizing opportunities for instances tagged 'Development'
2. Only analyze instances with less than 20% CPU utilization
3. You have permission to perform instance resizing without backups

Important Details to Include

1. Resource Targeting:

   • Environment tags (Production, Development, etc.)

   • Resource types

   • Regions or locations

   • Specific inclusion/exclusion criteria

2. Permissions:

   • What actions the agent can take

   • Whether human approval is needed

   • Any restricted operations

3. Constraints:

   • Time windows for actions

   • Cost thresholds

   • Performance requirements

Example Task Definitions

Example 1: EC2 Right-sizing

Mission: Perform right-sizing of EC2 instances in Singapore

Goal: Ensure all development instances are cost-optimized based on usage patterns

Instructions:
1. Analyze all EC2 instances tagged Environment=Development
2. Identify instances with average CPU usage below 30%
3. Perform right-sizing in the non-business hours of Singapore
4. Maintain current instance family type

Example 2: Storage Optimization

Mission: Optimize EBS volume usage in US-East region

Goal: Reduce costs by identifying and addressing underutilized EBS volumes

Instructions:
1. Scan all EBS volumes in US-East-1
2. Identify volumes with less than 30% utilization
3. Create report of unused volumes
4. Flag volumes not accessed in last 30 days
5. Do not modify any production volumes

Common Pitfalls to Avoid

1. Being too vague

   • Bad: "Optimize cloud resources"

   • Good: "Right-size EC2 instances tagged as Development in Singapore region"

2. Missing important constraints

   • Bad: "Delete unused resources"

   • Good: "Delete unattached EBS volumes older than 30 days in the Development environment"

3. Unclear permissions

   • Bad: "Update instances as needed"

   • Good: "You have permission to modify instance types within the same family"