Fargate provisioning is tied to AWS, unlike Kubernetes or other systems that aren't Cloud Vendor specific. If I build tooling around Kubernetes, I can move fro

Fargate provisioning is tied to AWS, unlike Kubernetes or other systems that aren't Cloud Vendor specific. If I build tooling around Kubernetes, I can move from Google to EKS without needing to change it. However, if I build tooling around Fargate, it's useless outside of AWS. Keep in mind, this doesn't make it bad or impossible to move out. Just more work. That all being said, I still like Fargate even with it tying me to using AWS. I think the pros out-weight the cons.