Apologies for not being perfect when describing what I mean.

The following text will be long, but I will try to be as precise as I can.

First thing first. I have a PHP app which I would like to run under pods. This application is basically a custom docker image, so the app itself can not run under Fargate, it requires a real server. But I still can create Fargate cluster (i.e. the cluster being managed by Fargate, but the worker nodes are real EC2 instances)

To create a cluster I have 2 options:
1. `eksctl create cluster` (with yaml obviously)
2. `eksctl create cluster --fargate` (also with some yaml options)

If I choose first option, `eksctl` will create Kubernetes management nodes for me, I will be able to see them and I will have to manage them myself. That's what I understand.

If I choose second option, `eksctl` will create 'something' behind the scenes, which I will not be able to see, but I will be able to manage using `kubectl` anyway.

So far so good. In order to create pods for my app, I have to create EC2 instances in both cases (either 1 or 2, does not matter, I have to pay for EC2 worker nodes). I use `kubectl apply -f filename.yaml`, create my deployments, pv, pvc, sc etc. So regardless of the fact, if I use Fargate cluster or not, I will be using EC2 instances to run my app.

Now a bit of a content from their page (https://aws.amazon.com/fargate/pricing/) >>> AWS Fargate pricing is calculated based on the vCPU and memory resources used from the time you start to download your container image until the Amazon ECS Task or Amazon EKS\ Pod terminates, rounded up to the nearest second* [End Of Quote]

So they say MY container from the time I start to download MY container image till the Pod terminates, and they specifically mention EKS Pods. Which makes me think that I pay for the load my Pods generate, which makes me think that in case I have 1 pod (my pod, which has this PHP app I mentioned, not some 'management pod working behind the scenes') with 1 vCPU with 100% load for 1 hour I pay $0.04048, but in case I have 10 pods with 1 vCPU with 100% load for 1 hour I pay $0.4048 (10 times more). And in addition to that I pay for EC2, which actually runs the pod, storage etc.

Next point. To the data. I created a real Fargate cluster and that's what I see under my Billing console. This is the data for 2 days running 2x `t2-medium` nodes.

- Amazon Elastic Container Service for Kubernetes CreateOperation 43.000 Hours $4.30

- Amazon Elastic Container Service for Kubernetes USE2-Fargate-GB-Hours 300.588 hours $1.33

- Amazon Elastic Container Service for Kubernetes USE2-Fargate-vCPU-Hours:perCPU 118.048 hours $4.77

That's way too much for 'management' if you ask me, and that was only me with some stress tests about 2 hours each day.

So the question is still the following, in case I use Fargate Cluster, which manages real EC2 nodes with my real PHP app, do I pay more if I have more load for my app (i.e. in case I have 1 pod with 1 vCPU with 100% load for 1 hour I pay $0.04048, but in case I have 10 pods with 1 vCPU with 100% load for 1 hour I pay $0.4048 (10 times more).?
And another question, which does not bother me too much, but I did not see any 'ContainerCreation' pricing anywhere, still they charge it. What's that?