- 新しい順
- 投票が多い順
- コメントが多い順
, it's possible that you're seeing the total memory available to the underlying infrastructure (the EC2 instance) rather than the memory limit set for your specific Fargate task. Fargate abstracts the underlying server infrastructure, but when you run commands like free or top inside a container, they report information about the underlying host, not the individual container.
The memory value that you set in the task definition is used by AWS to allocate resources and to enforce memory limits, but it might not be directly visible inside the container using tools like free or top.
To investigate further, you might consider monitoring the memory usage of your task using CloudWatch, or looking into container-level monitoring tools which are designed to report metrics in a containerized environment.
関連するコンテンツ
AWS公式更新しました 9ヶ月前
I said " it's possible that you're seeing the total memory available to the underlying infrastructure (the EC2 instance) ", but I don't understand the "infrastructure (the EC2 instance)" part, so I have an additional question. Can you say that infrastructure (the EC2 instance) is the server that actually operated fargate? fargate is confusing me as it doesn't use ec2 services.