### What you need to know (be aware of) when using ECS on Fargate.

- **Limitation** Fargate do not support all of the task definition parameters. [ref](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/AWS_Fargate.html)
  - Cannot use provilaged mode
  - Should use `awsvpc` mode -> Task will have ENI and a primary private IP address
  - Cannot use _gpu_
  - No placement constraint
  - Task CPU and memory (min: 0.25 vCPU, 0.5GB RAM, max: 4 vCPU, 30 GB RAM)
  - Logging: awslogs, splunk, firelens, and fluentd
- Optional need Amazon ECS task execution IAM role for call other AWS service, e.g. ECR
- Fargate platform version realease will provides update on kernel or operating system updates, new features, bug fixes, or security update
- Task automated scheduled-retirement: you will be notified by email
  - Task is stopped or terminated by AWS. If it is part of the service, it will be updated automatically.
  - Reason:
    - Irreparable failure of the underlying hardware
    - Task has a security vulnerability
- Fargate task recycling
  - When a security or infrastructure update is needed
  - No notification before recycling process
  - Only affect task that part of service (not standalone task)
- Fargate makes no network throughput guarantees, nor does it guarantee equal CPU performance among tasks,
- [Expose Fargate using API gateway, VPC Link & NLB](https://medium.com/swlh/deploy-container-in-ecs-fargate-behind-api-gateway-nlb-for-secure-optimal-accessibility-with-95542d5867c3)