> For the complete documentation index, see [llms.txt](https://docs.tuannvm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tuannvm.com/blog/reading/2025-11-25-amazon-eks-provisioned-control-plane-amazon-eks.md).

# Amazon EKS Provisioned Control Plane

This diagram illustrates the architecture of Amazon EKS Provisioned Control Plane, highlighting its components and interactions:

{% @mermaid/diagram content="graph TD
A\[Amazon EKS Cluster] --> B\[Control Plane Nodes]
B --> C\[API Server]
B --> D\[Scheduler]
B --> E\[etcd Database]
C --> F\[Client Requests]
D --> G\[Pod Scheduling]
E --> H\[Cluster State]
A --> I\[Control Plane Scaling Tier]
I --> J\[XL, 2XL, 4XL]
J --> K\[API Request Concurrency]
J --> L\[Pod Scheduling Rate]
J --> M\[Cluster Database Size]
K --> N\[Concurrent Requests Processed]
L --> O\[Pods Scheduled per Second]
M --> P\[Storage Space Allocated GB]
N --> Q\[Performance Metrics]
O --> Q
P --> Q
Q --> R\[CloudWatch Metrics]
R --> S\[Prometheus Endpoint]
S --> T\[Monitoring and Alerts]" %}

## Overview

Amazon EKS Provisioned Control Plane allows cluster administrators to pre-allocate control plane capacity, ensuring high and predictable performance. It operates alongside the default Standard mode, which dynamically scales based on workload demands.

## Key Features

* **Scaling Tiers**:
  * Available in XL, 2XL, and 4XL sizes.
  * Defined by API request concurrency, pod scheduling rate, and cluster database size.
* **Use Cases**:
  * Performance-critical workloads requiring minimal latency.
  * Massively scalable workloads like AI training and high-performance computing.
  * Anticipated high-demand events.
  * Environment consistency across staging, production, and disaster recovery.

## Control Plane Modes

* **Standard Mode**:
  * Automatically scales based on workload.
  * Recommended for most applications due to cost efficiency.
* **Provisioned Mode**:
  * Pre-allocated capacity for consistent performance.
  * Suitable for workloads intolerant of scaling variability.

## Monitoring and Management

* **Utilization Metrics**:
  * Available via Amazon CloudWatch and Prometheus.
  * Key metrics include API request concurrency, pod scheduling rate, and database size.
* **Tier Management**:
  * Requires explicit opt-in.
  * No automatic scaling between tiers; manual adjustments can be made.

## Considerations

* **Cost**:
  * Additional hourly charges for Provisioned mode.
  * Pricing varies by tier and region.
* **Database Limitations**:
  * Standard mode supports up to 8 GB of etcd storage.
  * Transition back to Standard mode requires reducing database size below this threshold.
* **Performance Optimization**:
  * Adherence to Kubernetes best practices is essential for achieving expected performance levels.

This architecture and summary provide a comprehensive understanding of Amazon EKS Provisioned Control Plane, its benefits, and considerations for implementation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tuannvm.com/blog/reading/2025-11-25-amazon-eks-provisioned-control-plane-amazon-eks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.