# OPS07-BP06 - Create support plans for production workloads

Best practice: OPS07-BP06
Pillar: Operational Excellence
Source: https://wellarchitected.cloudvisor.eu/docs/operational-excellence/ops07-bp06.html

## Implementation Guidance

"Create support plans for production workloads" should be delivered as a standard operating capability with explicit scope, controls, and validation checkpoints. Embed it into day-to-day engineering and operations workflows.

For the question "How do you know that you are ready to support a workload?", define measurable outcomes, assign owners, and review execution regularly. Integrate this practice into delivery and operations processes so improvements persist as workloads and requirements evolve.

### Key Steps

1. **Define implementation scope and outcomes**:
   - Set explicit success criteria for "Create support plans for production workloads"
   - Identify dependencies, prerequisites, and sequencing constraints
   - Assign accountable owners for execution and maintenance

2. **Implement with standards and validation**:
   - Use reusable templates and runbooks for consistent execution
   - Validate implementation with tests, checks, or controlled rollouts
   - Capture telemetry to confirm adoption and effectiveness

3. **Operate and iterate**:
   - Review outcomes against KPIs on a recurring schedule
   - Fix recurring failure modes and process bottlenecks
   - Update implementation guidance based on operational learning

## Risk / Impact

**Level of risk if not implemented**: Medium

**Impact**: Without this best practice, workloads typically accumulate inefficiencies and execution drift that increase failure probability over time. Problems often surface during traffic spikes, major releases, or dependency failures.

**Benefits of implementation**:
- More predictable operational and engineering outcomes
- Better alignment between architecture decisions and business goals
- Continuous improvement through measurable feedback loops

## AWS Services to Consider

<div class="aws-service">
  <div class="aws-service-content">
    <h4>AWS Systems Manager</h4>
    <p>Provides automation, inventory, and operational runbooks for day-2 management.</p>
  </div>
</div>

<div class="aws-service">
  <div class="aws-service-content">
    <h4>AWS Systems Manager Incident Manager</h4>
    <p>Coordinates incident response with predefined plans, contacts, and timelines.</p>
  </div>
</div>

<div class="aws-service">
  <div class="aws-service-content">
    <h4>Amazon CloudWatch</h4>
    <p>Collects metrics, logs, and alarms that support operational insight and performance management.</p>
  </div>
</div>

<div class="aws-service">
  <div class="aws-service-content">
    <h4>AWS Config</h4>
    <p>Tracks configuration changes and compliance state to detect drift and enforce standards.</p>
  </div>
</div>

## Related Resources

<div class="related-resources">
  <h2>Related Resources</h2>
  <ul>
    <li><a href="https://docs.aws.amazon.com/wellarchitected/latest/framework/ops-07.html">OPS07: How do you know that you are ready to support a workload?</a></li>
    <li><a href="https://docs.aws.amazon.com/wellarchitected/latest/operational-excellence-pillar/welcome.html">AWS Well-Architected Framework - Operational Excellence Pillar</a></li>
    <li><a href="https://docs.aws.amazon.com/wellarchitected/latest/operational-excellence-pillar/design-principles.html">Operational Excellence Design Principles</a></li>
  </ul>
</div>