High network bandwidth usage by eks fargate

We have an EKS cluster and we are deploying cronjobs using fargate. The cronjobs runs every 15 minutes. My NAT gateway costs skyrocketed because every 15 minutes it was an amount of 1GB BytesOutToSource. Previously we had this cronjobs running in EC2 instances and never used this amount of internet. What could be causing this? For example, I would think that downloading the image from ECR has no costs (They are even in the same region)

主題

無伺服器容器

標籤

AWS Fargate Amazon Elastic Container Registry(ECR)Amazon Elastic Kubernetes Service

語言

English

ignacio

已提問 5 個月前檢視次數 246 次

1 個回答

最新
最多得票
最多評論

這些答案是否有幫助？支持正確答案，以幫助社區從您的知識中受益。

已接受的答案

Hello.

If you are using Fargate, pulling the container image in ECR will require communication to the NAT Gateway, which should increase costs.
The blog below is for ECS, but I believe the same situation will occur even for EKS.
https://andrew-larse514.medium.com/aws-nat-gateway-ecr-cost-gotcha-a0865d0edd4
https://pierreraffa.medium.com/cost-reduction-using-ecr-vpc-endpoints-ff87316f36a8

專家

Riku_Kobayashi

已回答 5 個月前

專家

Giovanni Lauria

已審閱 2 個月前

ignacio
5 個月前
Thank you. That would explain a lot. There are like 20 pods pulling a new ECR image every time. I would have to investigate a way to not download the image on each run of the pod
Riku_Kobayashi 專家
5 個月前
Using the EC2 launch type instead of Fargate allows container images to be cached within EC2, potentially reducing costs. The blog below is in Japanese, but it states that changing from Fargate to EC2 led to cost reductions. https://techblog.zozo.com/entry/reconfigure-eks-workflow-infrastructure
This AWS blog may also be helpful. https://aws.amazon.com/jp/blogs/containers/start-pods-faster-by-prefetching-images/

High network bandwidth usage by eks fargate

相關內容