liveBook · Manning

AWS Fargate

As explained in Cloud Observability in Action

AWS Fargate is a managed AWS compute engine that runs containers without requiring users to manage the underlying servers.

AWS Fargate is a container-centric serverless compute offering that runs as the data plane for Amazon ECS or Amazon EKS, reducing the operational work of managing underlying infrastructure. section 3.2.4

Fargate simplifies operations and observability effort, but it also limits visibility: operating-system or virtual-machine signals are unavailable unless AWS explicitly exposes them. section 3.2.4

Choose the surrounding orchestrator and its available telemetry:

  • Use ECS on Fargate with CloudWatch monitoring and metrics available in Prometheus format. section 3.2.4
  • Use EKS on Fargate with Fluent Bit–based log routing and CloudWatch metrics. section 3.2.4
  • Track costs automatically and add alerts, especially when autoscaling can increase usage. section 3.2.4

How Cloud Observability in Action covers it

How deep it goes
Explains the deployment role and observability trade-off, but stops short of configuration or infrastructure internals.
Examples
Contrasts ECS and EKS deployments through their available CloudWatch, Prometheus, and Fluent Bit telemetry.
What it assumes
Assumes familiarity with containers, serverless compute, orchestration, observability, and autoscaling.
What you can do after
Operate container workloads through ECS or EKS while selecting exposed telemetry and controlling autoscaling costs.
How it connects
Connects container orchestration with Amazon ECS, Amazon EKS, CloudWatch, Prometheus, Fluent Bit, autoscaling, and observability.

Also explained in

Compare how 2 books explain AWS Fargate →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Cloud Observability in Action. The section links point to the parts of the book it draws on.