Background
RealTheory can use AWS Stock Keeping Units (SKUs) to calculate cost data when your environment uses non-standard or negotiated pricing (for example, Enterprise Discount Programs or specific negotiated rates) rather than standard pricing plans (on-demand, 1-Year reserved, a simple discount rate on standard pricing, etc.).
SKU names categorize services and map them to their associated pricing, including compute nodes, storage options, networking, etc. You provide SKU names using exact strings or wildcards (*) in a comma-separated list. If multiple SKUs could match a resource, RealTheory applies the first matching SKU in the table. Use the drag-and-drop handle to reorder rows and control matching priority.
The rest of this topic provides guidance on how to specify SKU names for the various sections of the SKU rate card:
Node SKUs
Storage SKUs
Network SKUs
Load Balancer SKUs
Kubernetes Management Service SKUs
Node SKUs
Node SKUs must reference valid EC2 instance types. Use wildcards to match entire instance families or specific processor architectures.
Examples:
| SKU Name | Matches |
|---|---|
| m6i.large | Only m6i.large instance types |
| c7* | All C7 family instance types |
| c8g* | All Graviton-based C8g instance types |
| r7*large | r7.large and larger instance types |
| r8g*large | r8g.large and larger instance types |
Storage SKUs
Storage SKUs match the underlying AWS storage technology backing your Kubernetes Persistent Volumes (PVs).
Examples:
| SKU Name | Matches |
|---|---|
| Standard | Magnetic |
| GP2 | GP2 General Purpose SSD |
| GP3 | GP3 General Purpose SSD |
| GP* | GP2 and GP3 General Purpose SSD (and future generations) |
| IO1 | IO1 Provisioned IOPS SSD |
| IO* | IO1, IO2, and IO2 Block Express Provisioned IOPS SSD (and future generations) |
| SC1 | Cold HDD |
| ST1 | Throughput optimized HDD |
Network SKUs
Network SKUs represent the pricing categories used for data transfer.
Configuration Requirement:
When using the InterRegion Inbound or InterRegion Outbound SKUs, you can optionally specify the following key/value pairs in Properties:
source=<region>destination=<region>
where <region> is the AWS region code (for example, us-east-1, eu-west-1) that corresponds to the source or destination of the cross-region traffic.
Examples:
| SKU Name | Applies to... |
|---|---|
| IntraRegion | All internal traffic moving between Availability Zones in the same region |
| InterRegion Inbound | All inbound cross-region traffic |
| InterRegion Outbound | All outbound cross-region traffic |
| Internet Inbound | All inbound traffic arriving from the public internet |
| Internet Outbound | All outbound traffic leaving the AWS network for the public internet |
Load Balancer SKUs
Load Balancer SKUs match the Application or Network Load Balancers provisioned by your Kubernetes Service objects.
Examples:
| SKU Name | Applies to... |
|---|---|
| Load Balancer-Application | Application Load Balancers |
| Load Balancer-Network | Network Load Balancers |
Kubernetes Management Service SKUs
Kubernetes Management Service SKUs account for the managed control plane fee and any serverless (Fargate) resources consumed by your cluster.
Examples:
| SKU Name | Tier |
|---|---|
| Amazon EKS | Standard cluster fee |
| Amazon EKS - AWS Outposts | Hybrid cluster fee |
| AWS Fargate - vCPU | Serverless compute |
| AWS Fargate - Memory | Serverless memory |
| AWS Fargate - Ephemeral Storage | Serverless storage |
Configuration Tip: If your environment uses serverless workloads, ensure you have entries for all three Fargate components (vCPU, Memory, and Ephemeral Storage). As Fargate is billed based on requested resources rather than actual consumption, these SKUs enable RealTheory to accurately calculate your Reserved vs. Used cost efficiency.