The Efficiency Hub

Go back

AWS Fargate

Behavioral Inefficiency

11

Commitment Misalignment

11

Contract Lifecycle Mismanagement

11

Excessive Data Retention

11

Excessive Recording Frequency

11

Excessive Retention Configuration

11

Excessive Retention of Non-Critical Data

11

Idle Resource

11

Idle Resource with Baseline Cost

11

Inactive Resource

11

Inactive Resource Consuming Baseline Costs

11

Inactive Storage Resource

11

Inactive and Detached Volume

11

Inefficient Architecture

11

Inefficient Configuration

11

Inefficient Configuration

11

Inefficient Data Ingestion

11

Inefficient Network Configuration

11

Inefficient Query Pattern

11

Inefficient Query Patterns

11

Inefficient Resource Usage

11

Inefficient Scheduling

11

Inefficient Storage Tiering

11

Inefficient Storage Usage

11

Misaligned Storage Tiering

11

Misconfiguration

11

Misconfiguration Leading to Future Orphaned Resource

11

Misconfigured Architecture

11

Misconfigured Logging

11

Misconfigured Performance Optimization

11

Misconfigured Redundancy

11

Misconfigured Reservation

11

Misconfigured Storage Tier

11

Missing Cost Control Configuration

11

Missing Lifecycle Policy

11

Missing Safeguard

11

Modernization

11

Orphaned Resource

11

Orphaned Storage Resource

11

Outdated Engine Version

11

Outdated Resource

11

Outdated Resource Selection

11

Over-Recording of Ephemeral Resources

11

Over-Retention of Data

11

Overcommitted Reservation

11

Overprovisioned Networking Resource

11

Overprovisioned Resource

11

Overprovisioned Resource

11

Overprovisioned Resource Allocation

11

Pricing Model Misalignment

11

Recursive Invocation Misconfiguration

11

Redundant Configuration

11

Retained Unused Resource

11

Retention

11

Retry Misconfiguration

11

Suboptimal Architecture Selection

11

Suboptimal Cluster Configuration

11

Suboptimal Configuration

11

Suboptimal Configuration and Usage

11

Suboptimal Data Layout

11

Suboptimal Data Layout or Format

11

Suboptimal Execution Model

11

Suboptimal Instance Family Selection

11

Suboptimal Instance Family Selection

11

Suboptimal Instance Selection

11

Suboptimal Lifecycle Configuration

11

Suboptimal Pricing Model

11

Suboptimal Query Routing and Warehouse Utilization

11

Suboptimal Recording Configuration

11

Suboptimal Storage Tier

11

Suboptimal Workload Distribution

11

Subscription Disruption Due to Billing Migration

11

Underutilization

11

Underutilized Commitment

11

Underutilized Compute Resource

11

Underutilized Resource

11

Unused Resource

11

Unused Resource

11

Version Sprawl

11

Visibility Gap

11

Clear filters

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Showing

1234

out of

1234

inefficiencis

Filter

:

Filter

x

Suboptimal Architecture Selection in AWS Fargate

Compute

Cloud Provider

AWS

Service Name

AWS Fargate

Inefficiency Type

Suboptimal Architecture Selection

AWS Fargate supports both x86 and Graviton2 (ARM64) CPU architectures, but by default, many workloads continue to run on x86. Graviton2 delivers significantly better price-performance, especially for stateless, scale-out container workloads. Teams that fail to configure task definitions with the `ARM64` architecture miss out on meaningful efficiency gains. Because this setting is not enabled automatically and is often overlooked, it results in higher compute costs for functionally equivalent workloads.

Learn more

Underuse of Fargate Spot for Interruptible Workloads

Compute

Cloud Provider

AWS

Service Name

AWS Fargate

Inefficiency Type

Pricing Model Misalignment

Many teams run workloads on standard Fargate pricing even when the workload is fault-tolerant and could tolerate interruptions. Fargate Spot provides the same performance characteristics at up to 70% lower cost, making it ideal for stateless jobs, batch processing, CI/CD runners, or retry-friendly microservices.

Learn more

There are no inefficiency matches the current filters.