Close this search box.

Cloud8 features for containers

Cloud8 features for containers

Cloud8 has several tools to extend the management and optimization of your containers.

From a FINOPS perspective, we cover all aspects:

  • individual costs per Fargate and ECS container IDs
  • usage and allocation details
  • anomalies
  • reports and alerts
  • tags with chargeback, untagged monitoring and others
  • bulk tag fixes
  • markups para MSPs

We monitor best practices for compliance, security and cost reduction recommendations:

  • ECR repositories that are scan enabled
  • vulnerability alerts for these repositories
  • outdated agents
  • network ports open unnecessarily
  • monitoring the tags created and whether it is appropriately following the defined standards
  • Type migration opportunities and Graviton compatibility

Automations and Workflows to reduce costs:

  • changes in the number of servers in Auto Scaling Groups. When considering ‘zero’ it is the equivalent of stopping an ASG
  • we support ASGs mapped to pure ECS, EKS and any other equivalent services
  • support for AKS (Azure Kubernetes Services) with shutdown/deallocation of nodes or scalability of the number of instances (more or less)
  • Google Instance Group support with increasing and decreasing instances
  • support scaling Fargate services
  • Fargate upgrade/downgrade support via changing Task Definitions

It is worth highlighting the extensive support we have for Fargate. We were able to identify the cost of each container with its tasks and carry out business apportionment. Once you have identified containers that use a lot, you can use the workflow scheduler to turn off certain services and/or update a task definition so that it runs with less CPU and memory on weekends and holidays.

It is very common to find Fargate tests that are connected all the time or environments with lower usage on weekends – these are ideal candidates for having a Task Definition changed and reducing costs. The main advantage is that AWS deploys transparently without incurring downtime (unlike upgrading / downgrading an EC2 instance where an on / off takes the server offline for a few seconds).

Share if you liked


Leave a Reply

Your email address will not be published. Required fields are marked *