1
00:00:02,240 --> 00:00:03,660
But wait a second,

2
00:00:03,660 --> 00:00:08,141
AWS EKS? Didn't we use that before already?

3
00:00:08,141 --> 00:00:11,850
Well, we used AWS ECS,

4
00:00:11,850 --> 00:00:14,297
which is another service offered by AWS.

5
00:00:15,670 --> 00:00:17,440
But there is an important difference

6
00:00:17,440 --> 00:00:19,140
between these two services,

7
00:00:19,140 --> 00:00:22,240
which is why we are using both.

8
00:00:22,240 --> 00:00:27,203
AWS EKS stands for Elastic Kubernetes Service.

9
00:00:28,060 --> 00:00:33,060
AWS ECS stands for Elastic Container Service.

10
00:00:33,330 --> 00:00:37,670
And the difference is that EKS is a service

11
00:00:37,670 --> 00:00:39,820
for Kubernetes deployments.

12
00:00:39,820 --> 00:00:42,430
So it's all set up for Kubernetes.

13
00:00:42,430 --> 00:00:44,830
It knows the Kubernetes concepts

14
00:00:44,830 --> 00:00:46,960
and it sets everything up such

15
00:00:46,960 --> 00:00:50,049
that you can use your existing Kubernetes configuration

16
00:00:50,049 --> 00:00:52,190
and apply it.

17
00:00:52,190 --> 00:00:57,190
AWS ECS on the other hand knows nothing about Kubernetes.

18
00:00:57,210 --> 00:01:00,530
Instead, it's a general service for container deployments,

19
00:01:00,530 --> 00:01:02,020
but it does not accept

20
00:01:02,020 --> 00:01:05,643
or want any Kubernetes configuration files for that.

21
00:01:06,760 --> 00:01:11,269
AWS EKS allows you to stay in the Kubernetes world

22
00:01:11,269 --> 00:01:14,750
and use the syntax and philosophy and approach

23
00:01:14,750 --> 00:01:16,050
as you learned there,

24
00:01:16,050 --> 00:01:21,050
and you don't need any AWS specific syntax or settings.

25
00:01:21,240 --> 00:01:24,320
Instead, you can apply what you learned about Kubernetes

26
00:01:24,320 --> 00:01:28,170
and just use static system configuration.

27
00:01:28,170 --> 00:01:31,130
With AWS ECS that's different.

28
00:01:31,130 --> 00:01:33,310
It has nothing to do with Kubernetes.

29
00:01:33,310 --> 00:01:35,690
It brings its own approach,

30
00:01:35,690 --> 00:01:36,950
its own philosophy,

31
00:01:36,950 --> 00:01:38,570
its own concepts.

32
00:01:38,570 --> 00:01:40,210
And you therefore have to embrace

33
00:01:40,210 --> 00:01:42,030
and use these concepts

34
00:01:42,030 --> 00:01:46,847
and set up everything as wanted by AWS ECS.

35
00:01:46,847 --> 00:01:48,630
Now that is what you saw

36
00:01:48,630 --> 00:01:51,830
in the deployment section earlier in the course.

37
00:01:51,830 --> 00:01:53,670
If you followed along there,

38
00:01:53,670 --> 00:01:56,290
you will notice that some concepts you saw

39
00:01:56,290 --> 00:02:00,120
in the ECS service actually also relate

40
00:02:00,120 --> 00:02:03,310
to certain concepts you know from Kubernetes,

41
00:02:03,310 --> 00:02:05,100
but that's just a coincidence

42
00:02:05,100 --> 00:02:08,479
or simply the case because it makes sense

43
00:02:08,479 --> 00:02:11,253
to solve a certain problem in a similar way.

44
00:02:12,140 --> 00:02:15,070
Besides that, there really is no connection.

45
00:02:15,070 --> 00:02:19,890
ECS does not want or understand Kubernetes configurations.

46
00:02:19,890 --> 00:02:21,390
And it's absolutely fine

47
00:02:21,390 --> 00:02:23,990
to use something like ECS if you want to,

48
00:02:23,990 --> 00:02:27,310
but if you wanna apply your Kubernetes knowledge,

49
00:02:27,310 --> 00:02:32,040
then a managed service like EKS is the better choice.

50
00:02:32,040 --> 00:02:34,770
Or of course you use neither of the two.

51
00:02:34,770 --> 00:02:37,760
And instead you set up everything on your own or

52
00:02:37,760 --> 00:02:41,850
with help of a tool like Kops as I mentioned before,

53
00:02:41,850 --> 00:02:46,300
we are however going to use AWS EKS

54
00:02:46,300 --> 00:02:47,413
in this section.