But wait a second,
AWS EKS? Didn't we use that before already?
Well, we used AWS ECS,
which is another service offered by AWS.
But there is an important difference
between these two services,
which is why we are using both.
AWS EKS stands for Elastic Kubernetes Service.
AWS ECS stands for Elastic Container Service.
And the difference is that EKS is a service
for Kubernetes deployments.
So it's all set up for Kubernetes.
It knows the Kubernetes concepts
and it sets everything up such
that you can use your existing Kubernetes configuration
and apply it.
AWS ECS on the other hand knows nothing about Kubernetes.
Instead, it's a general service for container deployments,
but it does not accept
or want any Kubernetes configuration files for that.
AWS EKS allows you to stay in the Kubernetes world
and use the syntax and philosophy and approach
as you learned there,
and you don't need any AWS specific syntax or settings.
Instead, you can apply what you learned about Kubernetes
and just use static system configuration.
With AWS ECS that's different.
It has nothing to do with Kubernetes.
It brings its own approach,
its own philosophy,
its own concepts.
And you therefore have to embrace
and use these concepts
and set up everything as wanted by AWS ECS.
Now that is what you saw
in the deployment section earlier in the course.
If you followed along there,
you will notice that some concepts you saw
in the ECS service actually also relate
to certain concepts you know from Kubernetes,
but that's just a coincidence
or simply the case because it makes sense
to solve a certain problem in a similar way.
Besides that, there really is no connection.
ECS does not want or understand Kubernetes configurations.
And it's absolutely fine
to use something like ECS if you want to,
but if you wanna apply your Kubernetes knowledge,
then a managed service like EKS is the better choice.
Or of course you use neither of the two.
And instead you set up everything on your own or
with help of a tool like Kops as I mentioned before,
we are however going to use AWS EKS
in this section.