# AWS Fargate

Sedai continuously tunes AWS Fargate task CPU, memory, and Spot eligibility — configuring the optimal Spot/On-Demand blend without sacrificing availability.

## Right-Size Fargate Tasks Without the Guesswork

With Fargate, you pay for exactly what you request, which means over-provisioned task definitions cost you directly, every hour. Sedai continuously tunes CPU and memory allocations, Spot eligibility, and auto scaling to cut waste without sacrificing availability.

## Fargate Removes Infrastructure Management. It Doesn't Remove Inefficiency.

Serverless compute shifts the operational burden off your team, but the decisions that drive cost don't disappear. Task CPU and memory are still yours to configure, Spot still requires judgment to use safely, and scaling minimums set at launch tend to stay wherever they were set.

### Task configuration is set at deployment and rarely revisited.

CPU and memory get defined based on launch-time estimates that may not reflect actual behavior. Unlike EC2, there's no gradual drift signal — you're either correctly sized or you're not, and the bill doesn't tell you which.

### Spot adoption requires per-service judgment that most teams skip.

Fargate Spot can cut compute costs significantly, but whether a service can tolerate interruptions depends on architecture, criticality, and traffic patterns. Assessing that across every service consistently gets deprioritized.

### Conservative scaling minimums run as idle cost indefinitely.

Minimum task counts get set to safe-feeling numbers at launch and rarely come back down — even when the services they were protecting no longer need them.

## How We Help

### Task & Container Rightsizing

Sedai observes actual utilization and incrementally adjusts CPU and memory allocations — accounting for Fargate's specific resource combinations — to eliminate over-provisioning at the task level.

### Intelligent Fargate Spot

Sedai evaluates restart tolerance, traffic patterns, and environment type to identify Spot candidates, then configures an optimal Spot/On-Demand blend automatically.

### Auto Scaling Optimization

Sedai analyzes load patterns to right-size task minimums and scaling policies, so you stop paying for idle capacity during low-demand periods.

## Stop Funding Worst-Case Scenarios.

## Frequently Asked Questions

### Does Sedai support Fargate Spot?

Yes. Sedai analyzes each service's characteristics, including restart time, traffic patterns, and whether it's production or non-production, to determine Spot suitability and configure the right Spot/On-Demand mix automatically.

### How does Sedai handle Fargate's fixed CPU/memory combinations?

Fargate requires CPU and memory to be selected from a specific set of valid combinations. Sedai's optimization model understands these constraints and only recommends configurations that are valid for Fargate — it won't suggest arbitrary values that can't be applied.

### Will task rightsizing cause service interruptions?

Applying new CPU and memory allocations requires tasks to be replaced. Sedai manages this process incrementally and respects your service's minimum healthy task count to maintain availability throughout.

### Does Sedai work with both ECS on Fargate and EKS on Fargate?

Yes. Sedai supports Fargate as a launch type for both ECS services and EKS pods, with optimization logic adapted to each orchestration model.

### How is auto scaling handled if we already have scaling policies configured?

Sedai evaluates your existing policies and only recommends changes when it identifies a more efficient configuration. It won't override a policy simply to make a change — only when the data supports an improvement.