What is a CircleCI runner?
To learn more about the CircleCI runner, visit: https://academy.circleci.com/runner-course/704320/scorm/38u8egtp3x93c
The latest News and Information on DevOps, CI/CD, Automation and related technologies.
To learn more about the CircleCI runner, visit: https://academy.circleci.com/runner-course/704320/scorm/38u8egtp3x93c
AWS Fargate provides a way to use AWS container orchestration services—Amazon Elastic Container Service (ECS) and Amazon Elastic Kubernetes Service (EKS)—without needing to provision and maintain the infrastructure that runs your containers. Fargate is similar to serverless container platforms from Google (Cloud Run) and Microsoft (AKS virtual nodes).
In Part 1 of this series, we showed you the key metrics you can monitor to understand the health of your Amazon ECS and Amazon EKS clusters running on AWS Fargate. In this post, we’ll show you how you can: You can use Amazon CloudWatch and related AWS services to gain visibility into your ECS clusters and the Fargate infrastructure that runs them.
In Part 1 of this series, we looked at the important metrics to monitor when you’re running ECS or EKS on AWS Fargate. In Part 2 we showed you how to use Amazon CloudWatch and other tools to collect those metrics plus logs from your application containers. Fargate’s serverless container platform helps users deploy and manage ECS and EKS applications, but the dynamic nature of containers makes them challenging to monitor.
Whenever I look broadly at my career in telecom, one area that always amuses me is the extent to which our collective business enjoys its peculiarities. Sort of like our own secret handshake society full of unique terms and abbreviations like AIN & ANI, DDI and CLID or CLECs and POTS. After all, the Bell System used to formally publish a list of abbreviations and acronyms. Maybe it is just in our DNA?