# AWS Disaster Recovery Calculator AI Agent Connect

> Deterministic RTO and RPO estimation for AWS disaster recovery strategies.

## Overview
- **Category:** infrastructure
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_6cf3fYmtL8DcXXTps9UuFOAfEft2QGjaKbM5LgUt/ai-agent-connect
- **Tags:** aws, rto, rpo, disaster-recovery, cloud-architecture

## Description

This MCP server provides precise calculations for disaster recovery planning on AWS. It allows AI agents to estimate Recovery Time Objective (RTO) and Recovery Point Objective (RPO) based on specific infrastructure parameters like RDS snapshot frequency, S3 replication latency, and Route 53 TTL. Use `calculate_dr_metrics` to determine cost ratios and testing frequencies, or `compare_rto_rpo_to_sla` to verify if your technical setup meets business requirements. It covers all major AWS DR patterns including backup-and-restore, pilot-light, warm-standby, and multi-site.

## Tools

### calculate_dr_metrics
Calculates the RPO, RTO, cost ratio, and testing frequency for a selected disaster recovery strategy

### validate_strategy_compatibility
Checks if the provided technical parameters are logically compatible with the chosen DR strategy

### compare_rto_rpo_to_sla
Compares calculated metrics against a provided Service Level Agreement (SLA)

## Prompt Examples

**Prompt:** 
```
Calculate DR metrics for a pilot-light strategy with 4 hour RDS snapshots, 15 minute S3 latency, 60 second Route 53 TTL, and 10 minute ASG warmup.
```

**Response:** 
```
For a pilot-light strategy, the RPO is 15 minutes and the RTO is 25 minutes. The estimated cost ratio is 0.2, and the recommended testing frequency is monthly.
```

**Prompt:** 
```
What is the RPO and RTO for a multi-site AWS setup?
```

**Response:** 
```
For a multi-site strategy, the RPO is 0 minutes and the RTO is effectively 0 seconds.
```

**Prompt:** 
```
Check if an RPO of 30 minutes and RTO of 60 minutes complies with an SLA of 45 minutes RPO and 120 minutes RTO.
```

**Response:** 
```
The status is Compliant.
```

## Frequently Asked Questions

**How is RPO calculated?**
RPO is determined by the maximum of the RDS snapshot frequency and the S3 cross-region replication latency. For multi-site strategies, RPO is zero.

**Can I check if my DR strategy meets my business SLA?**
Yes, you can use the `compare_rto_rpo_to_sla` tool to compare your calculated metrics against your specific business requirements.

**What DR strategies are supported?**
The server supports backup-and-restore, pilot-light, warm-standby, and multi-site strategies.