1
00:00:00,530 --> 00:00:05,720
In this video, we are going to talk about what is infrastructure as code.

2
00:00:06,890 --> 00:00:14,660
So infrastructure is code or IAC is the process of provisioning and managing infrastructure defined

3
00:00:14,660 --> 00:00:18,110
through the code instead of doing bit manual process.

4
00:00:19,430 --> 00:00:22,040
So as infrastructure is defined as code.

5
00:00:22,070 --> 00:00:28,370
It allows users to easily edit and distribute configurations while ensuring the desired state of the

6
00:00:28,370 --> 00:00:29,330
infrastructure.

7
00:00:29,900 --> 00:00:34,550
So this means you can create reproducible infrastructure configurations.

8
00:00:36,300 --> 00:00:36,810
InfoSec.

9
00:00:36,820 --> 00:00:42,300
Today's code is a process that automates the provisioning and management of the cloud resources.

10
00:00:43,530 --> 00:00:47,300
InfoSec code software takes some input secrets.

11
00:00:47,310 --> 00:00:55,230
This software is the software and take some input scripts describing the desired state and then communicates

12
00:00:55,230 --> 00:00:56,550
with the cloud vendors.

13
00:00:56,550 --> 00:01:02,760
Typically they are using through APIs in order to make the royalty match the desired state.

14
00:01:02,760 --> 00:01:09,900
So that means we are writing desired state as a script and we basically connect with any cloud vendors.

15
00:01:09,900 --> 00:01:18,810
It could be Azure and Google and we can communicate through the APIs and provision the desired state

16
00:01:18,810 --> 00:01:27,300
according to script and make it reality sometimes referred to as a programmable infrastructure.

17
00:01:27,510 --> 00:01:31,110
IAC configures infrastructure exactly like programming.

18
00:01:31,110 --> 00:01:36,060
So Face It uses descriptive coding language that automates the process.

19
00:01:37,300 --> 00:01:44,470
So with latest technologies like virtualization and the cloud, it is combined with the rise of the

20
00:01:44,470 --> 00:01:50,890
DevOps and Agile practices, and it makes shortening the software development lifecycle dramatically.

21
00:01:51,490 --> 00:01:56,020
As a result, there was a demand for better infrastructure management techniques.

22
00:01:56,230 --> 00:02:02,320
Organization could no longer afford to wait for hours or days for servers to be deployed.

23
00:02:02,560 --> 00:02:09,100
So infrastructure is code is the only way of raising standards of infrastructure management and time

24
00:02:09,100 --> 00:02:09,820
to deploy.

25
00:02:10,420 --> 00:02:17,020
By using a combination of tools, language, protocols and processes, infrastructure as code can safely

26
00:02:17,020 --> 00:02:20,230
create and configure infrastructure elements in a second.

27
00:02:22,050 --> 00:02:27,800
So we can talk about the benefits of infrastructure discord with automated process.

28
00:02:27,810 --> 00:02:30,990
IAC helps business manage their I.T.

29
00:02:31,020 --> 00:02:33,210
Infrastructure needs in several ways.

30
00:02:33,880 --> 00:02:39,700
And organization using the IAC experiments for kind of expert benefits.

31
00:02:39,700 --> 00:02:43,660
I would like to give some of the benefits and the first benefit is speed.

32
00:02:44,970 --> 00:02:51,150
Speed is alluding to manual intervention and infrastructure deployments are quickly unsafe.

33
00:02:51,330 --> 00:02:55,200
We can avoiding manual intervention model configuration.

34
00:02:55,200 --> 00:02:56,880
It makes us more speedy.

35
00:02:57,780 --> 00:03:00,050
And also IAC transform developers.

36
00:03:00,060 --> 00:03:06,390
Time consuming provisioning works into a simple script execution in order to have their infrastructure

37
00:03:06,390 --> 00:03:06,870
ready.

38
00:03:07,530 --> 00:03:13,530
So infrastructure as code enables you to quickly set up your complete infrastructure by running a script.

39
00:03:14,820 --> 00:03:21,390
You can do that for every environment, from development to production, pacing through, staging and

40
00:03:21,390 --> 00:03:21,840
more.

41
00:03:21,870 --> 00:03:28,560
We can define a parameter as an environment and we can run the same circuit for several environments.

42
00:03:29,040 --> 00:03:34,320
Also, infrastructure as code can make the entire software development lifecycle more efficient.

43
00:03:34,410 --> 00:03:40,860
As a result, application deployments no longer have to wait for the infrastructure, and new software

44
00:03:40,860 --> 00:03:42,700
can be released much more quickly.

45
00:03:42,720 --> 00:03:45,420
It becomes us comes with the speed.

46
00:03:46,260 --> 00:03:48,810
The second benefit is the consistency.

47
00:03:49,260 --> 00:03:56,010
So deploying identical infrastructure across the board, avoiding edge cases and one of configurations

48
00:03:56,010 --> 00:04:01,660
make comes with the consistency and manual processes result in mistakes.

49
00:04:01,680 --> 00:04:05,910
At some period you can get mistakes with the manual processing.

50
00:04:06,030 --> 00:04:10,450
Humans are can get fails when deploying the applications.

51
00:04:10,470 --> 00:04:15,510
Our memory is faultless, so communication is hard and we are in general pretty bad.

52
00:04:16,290 --> 00:04:22,620
So infrastructure is code solves that kind of problems by having the config files themselves to be a

53
00:04:22,620 --> 00:04:24,240
single source of truth.

54
00:04:24,570 --> 00:04:31,500
So by that way, you guarantee the same configuration will be deployed over and over again without any

55
00:04:31,500 --> 00:04:32,640
getting exception.

56
00:04:33,780 --> 00:04:37,350
So that means the third benefit is reusability.

57
00:04:37,470 --> 00:04:43,590
Infrastructure is code, makes it easy to create reusable models, for example, to replicate development

58
00:04:43,590 --> 00:04:45,180
and production environments.

59
00:04:45,720 --> 00:04:48,150
And another benefit is reduced.

60
00:04:48,150 --> 00:04:55,410
The cost infrastructure is code ALOS virtual machines to be managed programmatically and eliminating

61
00:04:55,410 --> 00:04:58,800
the need of manual hardware configurations and updates.

62
00:04:59,630 --> 00:05:05,850
One operator can deploy and manage one machine or a thousand machine using the same set of code.

63
00:05:05,870 --> 00:05:12,170
So that means that people, staff are needed and purchasing new hardware is no longer necessary.

64
00:05:12,200 --> 00:05:18,410
Reducing cost is significantly and another benefit is source control.

65
00:05:18,470 --> 00:05:23,480
Code can be checked in the source control for increased transparency and accountability.

66
00:05:24,290 --> 00:05:29,750
Infrastructure is called can improve consistency and reduce errors that often happen during the manual

67
00:05:29,750 --> 00:05:30,680
configuration.

68
00:05:30,920 --> 00:05:37,700
It also eliminates any configuration drift that might occur during the manual process by codifying and

69
00:05:37,700 --> 00:05:40,490
documenting your configuration specifications.

70
00:05:40,580 --> 00:05:45,890
Infrastructure as code helps you to avoid undocumented and adult configuration chains.

71
00:05:47,010 --> 00:05:54,030
And the last one, of course, Agility DevOps has made software delivery more efficiently, and infrastructure

72
00:05:54,030 --> 00:05:58,080
as code brings agility to the realm of the infrastructure management.

73
00:05:59,500 --> 00:06:06,590
P.S. In the image on the slide, how infrastructure is called works infrastructure is quote can be explained

74
00:06:06,590 --> 00:06:13,250
from the high level in three simple steps and visualize with the diagram you can see the diagram.

75
00:06:13,250 --> 00:06:15,550
We have three steps and four.

76
00:06:15,590 --> 00:06:21,740
First step is developers write the infrastructure specification in the domain specific language.

77
00:06:21,770 --> 00:06:26,570
You can write secret templates in the domain specific language.

78
00:06:27,110 --> 00:06:35,150
And second step is the resulting files are sent to master server and management API or code repository.

79
00:06:35,480 --> 00:06:39,170
You can manage these scripts into the these tools.

80
00:06:39,170 --> 00:06:46,160
And the last one is the platform takes all the necessary steps to create and configure provisioned your

81
00:06:46,160 --> 00:06:47,630
desired infrastructure.
