Operational Cost of OneLens

This page highlights the cost implicated with using key OneLens features. To begin with, here is a quick summary of cost components, structured in a way to help you estimate based on your own AWS infrastructure.

Feature
Unit of Usage
Estimated Cost

~10000 Resources

~$0.7 per day

100 GB CUR

~$2.30 per month

1 runbook execution (after free tier)

~$0.31 per execution

Monitoring 500 pods

~$35.94 per month

10,000 pods

~$2.73 per month

The sections below breaks down where charges may apply, and how they’re calculated:

Cost Optimization Policies

OneLens cost optimization policies targets to find cost optimization opportunities in your AWS resources with 3 types of datasets:

  1. Resource metadata that tells the resource configuration

  2. Resource metrics relevant to policy evaluation

  3. Cost and Usage Report (CUR) data

Few Examples to Understand This Better

  • Evaluating GP2 EBS volumes for migration to GP3, and identifying EC2 instances suited for Graviton, both rely entirely on resource configuration.

  • Evaluating underutilized instance in EC2, RDS, MSK requires resource configuration and metrics data.

  • Finding idle resources will combine resource configuration, metrics and cost data.

Understanding Cost for Resource and Metric Data Extraction

OneLens leverages the official AWS SDK to collect both resource and metric cost data. Currently, it onboarded 15 AWS services and gathers only the metadata and metrics related to these specific services.

Retrieving resource metadata is entirely free. However, the cost is incurred in getting the metrics information. OneLens collect CloudWatch metrics using the GetMetricData API, typically charged at $.01 for 1000 API calls.

Costs are primarily driven by the number of API calls, calculated using the following formula:

Total API Calls per day = Σ (#Metrics × Resources)

Where:

  • Metrics: The number of CloudWatch metrics collected per resource (varies by service).

  • Resource Count: The number of resources available in your accounts for each service.

NOTE

Sample Estimate

For simplicity, lets assume you have 10000 EC2 instances and 100 resources across 14 other services we observe. The table below simplifies the calculations for this infrastructure:

Service (Namespace)
# Metrics
# Resources
API Calls/Day
Cost/Day ($)

AWS/EC2

7

10,000

70,000

0.70

AWS/RDS

6

100

600

0.006

AWS/DynamoDB

3

100

300

0.003

AWS/ElastiCache

27

100

2,700

0.027

AWS/ApplicationELB

1

100

100

0.001

AWS/NetworkELB

1

100

100

0.001

AWS/GatewayELB

1

100

100

0.001

AWS/PrivateLinkEndpoints

1

100

100

0.001

AWS/Redshift

2

100

200

0.002

AWS/ES

13

100

1,300

0.013

AWS/S3

3

100

300

0.003

CWAgent

2

100

200

0.002

AWS/Lambda

4

100

400

0.004

LambdaInsights

1

100

100

0.001

AWS/NATGateway

5

100

500

0.005

Total

77

76,000

0.76

Cost Reporting

The cost you incur here is for storing the Cost and Usage Report (CUR) in your S3 bucket. You are charged for the storage of the CUR report before OneLens ingests the data for analysis and provides granular insights.

Cost Estimate Based on Storage Size

Storage Size

Approx. Cost per Month

100 GB -500 GB

$2.30 - $11.50

500GB – 1 TB

$11.50 - $23.00

1 TB – 2 TB

$23.00 - $46.00

Automated Remediation

When automated remediation is enabled, you are charged based on the AWS Systems Manager services used during runbook execution via Change Manager and Systems Manager Automation.

Charges Based on AWS Pricing
Components
Cost
Free Tier Limits

Change Request

$0.296 per request

30 days free trial per new account

Automation Steps

$0.002

Upto 100,000 steps/month

Script Duration

$0.00003 per second

Upto 5,000 seconds/month

Estimate Example: Cost for running EBS volumes migration from gp2 to gp3 runbook

After exhausting your free tier, here’s the breakdown of the charges for a runbook called migrating EBS volumes from gp2 to gp3:

Component
Units
Price Per Unit
Total Cost

Change Request

1 request

$0.296

$0.296

Automation Steps

7 steps

$0.002

$0.014

Script Duration

1-5 seconds

$0.00003

$0.00003 - $0.00015

Total

-

-

$0.31003 - $0.31015

K8s Visibility and Optimization

Cost Associated with Agent

The OneLens agent runs as a set of lightweight pods within the cluster. These pods monitor container-level metrics, resource limits, and usage trends. The cost structure is mainly influenced by the number of pods in the cluster.

Agent Cost based on Number of Pods

The agent incurs a variable cost per cluster, based on pod count:

Cluster Size (Pods)
CPU (Cores)
Memory (GB)
Total Monthly Cost ($)

< 100

0.237

1.33

$17.98

100-499

0.386

1.92

$35.94

500-999

0.587

3.70

$35.94

1000-1499

0.696

5.47

$71.88

1500-2000

0.805

7.25

$99.00

Refer to the Agent Setup for more details on how the agent works and how to deploy it.

Additional Cost for Split Allocation in EKS

You may incur an estimated $2.73/month per 10,000 pods due to increased CUR data size and processing overhead.

Refer to the Split Allocation Setup Guide for steps to enable this option and understand its cost implications.

Last updated