AWS Tutorial for Beginners - AWS Crash Course | Learn AWS in 5 Hours | AWS Training | Edureka

Aug 16, 2023

AWS Tutorial for Beginners - AWS Crash Course | Learn AWS in 5 Hours | AWS Training | Edureka

🔥Edureka AWS Certification Training (Use Code: YOUTUBE20) - https://www.edureka.co/aws-certificat…

This AWS tutorial is brought to you by Edureka. This AWS Crash Course is a quick way to prepare for AWS Certifications, be it AWS Certified Cloud Practitioner or AWS Certified Developer–Associate.
Beginners who opt for this Crash Course are also professionals from Sales \u0026 Marketing background who need an understanding of how AWS platform works.

This AWS tutorial will help you learn AWS from scratch with practical Hands-on. Various AWS Services like:
- AWS EC2
- AWS S3
- AWS IAM
- AWS Lambda
- AWS Elastic Beanstalk
- AWS VPC
- AWS CloudFormation, etc..

Below are the timelines of concepts covered in this AWS Crash Course for Beginners:
00:00 Introduction to AWS Crash Course
03:19 AWS Tutorial for Beginners
05:57 What is Cloud?
08:17 Why AWS?
09:55 What is AWS?
10:30 Domains in AWS
10:58 Security Management in AWS
11:43 AWS IAM Service
12:39 IAM Components
16:42 Managing Users with IAM
39:42 IAM Best Practices
47:43 Key Management System
52:01 What are AWS Alerts?
53:15 Demo - Create Budget
56:13 AWS EC2 Tutorial for Beginners
57:14 What is EC2?
1:00:27 Understand Amazon Machine Image(AMI)
1:02:36 Security Groups, Key Groups, Tenacy
1:22:29 Elastic IP vs Public IP
1:28:37 AWS S3 Tutorial for Beginners
1:29:12 AWS Storage Services
1:32:42 What is Amazon S3?
1:43:29 Buckets \u0026 Objects
1:46:37 Versioning and Cross Region Replication
1:48:07 AWS S3 Demo
2:03:22 AWS Elastic Bean Stalk
2:04:13 What is Elastic Bean Stalk?
2:27:16 Features of Elastic Bean Stalk
2:39:51 Components of Bean Stalk
2:43:34 Architecture of Bean Stalk
2:48:52 AWS VPC Tutorial
2:50:04 Subnet, Subnet Mask
3:06:05 VPC Wizard
3:27:08 AWS Lambda Tutorial
3:27:44 What is AWS Lambda?
3:28:50 AWS Compute Domains
3:36:43 Why AWS Lambda?
3:37:53 AWS SDKs
3:38:37 AWS Lambda with Eclipse
3:52:41 AWS Data Pipeline
3:53:05 Need for Data Pipeline
3:57:09 What is AWS Data Pipeline?
4:00:01 AWS Data Pipeline Components
4:03:05 Demo: AWS Data Pipeline
4:17:26 AWS CloudFormation
4:19:00 Need for CloudFormation
4:20:44 What is CloudFormation?
4:20:53 CloudFormation Components
4:22:18 Templates in CloudFormation
4:26:11 Sample Template to Create EC2
4:26:42 Stack in CloudFormation
4:34:44 AWS OpsWork Services
4:45:40 Demo: AWS OpsWork Stack

🔴Subscribe to our channel to get video updates. Hit the subscribe button above: https://goo.gl/6ohpTV

Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Instagram: https://www.instagram.com/edureka_lea…
Facebook: https://www.facebook.com/edurekaIN/
SlideShare: https://www.slideshare.net/EdurekaIN
Castbox: https://castbox.fm/networks/505?count…
Meetup: https://www.meetup.com/edureka
----------------------------------------------------------------------------------------------------------

Got a question on the topic? Please share it in the comment section below and our experts will answer it for you.

For more information, please write back to us at [email protected] or call us at IND: 9606058406 / US: 18338555775 (toll-free).

Content

7.006 -> Cloud Computing has become quite a buzz word

9.5 -> these days it evolved from a personal cloud storage

13.052 -> to organizations move in their entire data

15.965 -> to the cloud ecosystem.

17.9 -> Now, we can obviously see an acceleration in the adoption

22.189 -> of Cloud Computing Services every year a trend

25.635 -> that doesn't seem to seize anytime soon.

29.1 -> Hi all I welcome you to this crash course by Edureka

33.34 -> and today we are going to talk about one of the most

36.2 -> popular cloud service provider the Amazon web services and

41.1 -> what follows is hopefully

43.1 -> everything you need to know to get started with AWS.

47.1 -> But before we begin,

48.433 -> let's look at our agenda for today.

51 -> First of all,

51.844 -> we are going to start by introducing you to AWS.

54.9 -> Why is it required?

56.349 -> What is it exactly?

57.8 -> What are the advantages of using the sort of an architecture?

61.7 -> So on and so forth

63 -> and then we're going to move on to Security Management in aw.

67 -> Yes followed by which we are going to talk about AWS ec2

72 -> or the elastic compute Cloud,

74.3 -> which is a web service

75.9 -> that provides secure resizable compute capacity in the cloud.

81.2 -> It's designed to make

82.589 -> web-scale cloud computing easier for developers.

86.3 -> Then we're going to move on to AWS S3,

89.6 -> which is the only object storage service which maintains

93.6 -> compliance programs data protection directive.

96.9 -> And hope to meet

98.066 -> regulatory requirements in the fifth module.

101.9 -> We're going to talk about AWS elastic Beanstalk,

105.4 -> which is an orchestration service offered by

108.3 -> Amazon web services for deploying apps moving on.

111.9 -> We're going to talk about the Amazon

114 -> virtual private Cloud,

115.456 -> which lets you provisional logically isolated section

118.9 -> of the AWS Cloud

120.09 -> where you can launch AWS resources in a virtual Network

124.109 -> that you define.

125.5 -> Then we shall discuss AWS Lambda which is a service

129.5 -> that lets you run your code without provisioning

132.3 -> or managing servers.

134.8 -> RF module covers AWS data pipeline,

138.2 -> which is a web service

139.422 -> that you can use to automate the movement and transformation

142.7 -> of data using data pipeline.

144.6 -> You basically Define data-driven workflows.

147.412 -> So that tasks can be dependent on the successful completion

151.295 -> of previous tasks.

153.03 -> And finally the last module discusses

155.8 -> cloud formation in AWS,

158.5 -> which is a service that helps you model and set

161.4 -> up your Amazon Web Services resource.

163.747 -> Asses so that you can spend less time managing these resources

167.845 -> and more time focusing on your application

170.6 -> that you run with this.

172.218 -> I come to the end of my agenda.

174.5 -> Also kindly take up this time to go ahead

176.899 -> and subscribe to us.

178.1 -> And don't forget to hit

179.452 -> that Bell icon to never miss an update

181.4 -> from the Edureka YouTube channel also to learn more

185.7 -> about AWS ec2 S3 and Lambda.

188.8 -> Don't forget to check out our certification training

191.9 -> the link to which is given in the description.

194.1 -> Box below.

194.9 -> So without Much Ado, let's get started.

203.5 -> So good morning,

204.299 -> good afternoon and good evening guys Bay is

206.4 -> on the time zones you all are coming

208.1 -> from the main agenda

209.8 -> for today's session is will be discussing on

212.7 -> what exactly is cloud platform.

214.6 -> What are different service models available

216.7 -> in Cloud platform?

218.2 -> Why exactly we need Cloud platforms?

221.3 -> And what exactly is AWS as an Amazon web services,

225.5 -> what are different domains available in AWS?

228.9 -> All right.

230.1 -> Now first of all,

231.026 -> let's understand the basics of cloud computing.

233.447 -> Ring why exactly we need cloud computing.

235.8 -> Now, for example,

236.852 -> let's suppose we want to host a static website,

239.7 -> right then we get now

241.093 -> when we are hosting a static website

243.556 -> or any kind of application both for web or mobile base.

247.059 -> If we want to do support

248.627 -> or deploy any particular application or website

251.537 -> then traditionally we had to buy a stack of servers

254.7 -> which will be holding up the entire data

257.1 -> and we should be working as a main competition environment

260.7 -> in which this application will be up and running.

263.3 -> If we have now,

264.182 -> once we buy the stack of servers

265.871 -> that means we have to invest a good amount

268.132 -> of money in buying those types of servers,

270.4 -> right and plus you have to invest in monitoring

272.91 -> and maintenance of these servers

274.792 -> on our own right that means here.

276.631 -> We have take care of everything from buying the infrastructure

280.229 -> to making sure

281.096 -> that the entire infrastructure is updated in the current

284.5 -> software department.

285.6 -> And again, making sure

286.7 -> that these entire servers are up and running all the time.

289.798 -> That means taking care of the entire deployment

292.3 -> as well as meeting show.

293.7 -> That the entire process as well monitored

296.3 -> and the maintenance is also done from I our own and by

300.01 -> when we deploy something traditionally and now

303.266 -> the main drawback of this one is

305.41 -> that this entire setup is expensive because again

308.5 -> here we have to now

309.7 -> when we are purchasing such stack of servers.

312.066 -> Obviously, we need infrastructure in order

314.28 -> to store those saves to store those physical servers as well.

317.588 -> Try we need to make sure

318.801 -> that we are investing a good amount of time

321.272 -> and as well as money in making sure the the entire system is up

324.8 -> and running without facing any kind of issues right

328.6 -> and depending upon the orb on the incoming traffic suppose.

332.5 -> If he's for some time.

333.9 -> We see the traffic getting increase and sometimes we

336.501 -> see the traffic getting they can decrease as well.

339.089 -> That means we need to have the entire application scale up

342.1 -> and scale down

343 -> and traditionally we have to take care of these scaling up

346 -> and scaling down.

347.7 -> Matt early today,

349.3 -> but again these things are required when we

351.869 -> deploy any particular application out there.

356 -> And then after introduction of cloud computing again

359.2 -> basically cloud computing is what the entire infrastructure

363.2 -> that is required to deploy the application remains

366.2 -> as it is,

366.723 -> right because again,

367.9 -> they are again it needs

369.33 -> any application needs to have a server any application needs

372.961 -> to have a database created the other it does servers

376.1 -> also need to be maintained

377.444 -> and everything needs to be done.

379.1 -> Right?

379.7 -> That means they has no Ben

381.474 -> and they hasn't been any kind of of it

384 -> can say any kind of Technologies.

386.2 -> Overwritten here.

387.262 -> But again, the main setup of the environment has changed

390.693 -> that means instead

391.752 -> of us taking care of everything now.

393.814 -> Everything is deployed on cloud.

395.7 -> That means now today

397.048 -> if we have to deploy a web site

399.048 -> and we go now instead of buying servers

401.504 -> on our own instead of taking care of the server deployment

405.189 -> on our own.

405.9 -> We cannot give it will take almost a week

408.6 -> in order to buy the servers set up Eda operating system

411.9 -> so that the entire environment nowadays,

414.218 -> we if we want to launch a website Site,

416.526 -> we can launch it within 15 minutes.

418.539 -> We can launch it with within 15 minutes

420.934 -> if you want,

421.7 -> right that's how fast it has been all thanks

424.6 -> to cloud computing

426 -> because here we already have these tag

428.298 -> of servers already available,

430.7 -> which we can simply hire which we can subscribe to

434.2 -> and then we can simply get started on top

436.78 -> of it right whether it

438.2 -> whether we need a server whether we need a storage service

441.816 -> whether we need any database services

444.1 -> or everything is now Able

446.1 -> to us as a solution as a software itself,

448.8 -> which we can subscribe and which and again

451.334 -> that means we don't have to take care of any kind of man

454.6 -> on implementation maintenance taking care of scalability.

458.309 -> Everything is start

459.5 -> taking care by the cloud computing platforms.

464.1 -> And that's why these all services I be

466.329 -> on cloud computing.

467.475 -> We get the entire pile

468.6 -> of stick with the complete pile of services

470.7 -> including computation database storage networking everything

474.9 -> every kind of service

476.224 -> that we need for the application deployments,

479 -> right and even for data analysis

481.263 -> for data science for handling large volume of data.

484.8 -> These all services are now available as a cloud service

488.85 -> on these different platform providers here.

494.2 -> All right.

496.5 -> Now let's understand.

498 -> Why exactly we need a wher

500.4 -> not AWS is basically the main cloud computing platform

504.5 -> that is owned by Amazon it is again,

506.97 -> it is one of the

508.1 -> you can see the the first the first most

510.9 -> popular cloud computing platform that was ever deployed.

514.4 -> So it started in 2006

516.661 -> and now it is having

518.2 -> the biggest market share the biggest market share

521.5 -> in the entire cloud computing providers.

523.7 -> So Adams has the biggest market share market.

526.9 -> Then followed by Microsoft Azure

530 -> and Then followed by Google Cloud platform All right,

534.7 -> so that's it down infrastructure of AWS here.

539.5 -> So because the AWS as compared to other platforms right

542.9 -> as compared to other platforms AWS here offers,

546.438 -> six times better capacity

548.5 -> that means six times better performance as compared to all

551.6 -> the platforms combined all the flat forms combined

554.5 -> and that's why AWS is much is the most

557.2 -> popular cloud computing platform for every kind of tree

561.2 -> for every team globally, right?

563.8 -> And that's the market

565.042 -> and that's why this is a market share of the of AWS

568 -> as compared to other players.

569.6 -> Earlier, it was even higher earlier.

571.857 -> It was more than 45% but now it has been reduced

574.757 -> or even person because of

576.3 -> multiple small players also coming up in the market here,

579.8 -> but still AWA AWA still governs the highest amount

582.824 -> got okay highest amount

584.243 -> of market share for different cloud computing Cloud forms

587.7 -> and offering flexible pricing on top of it.

591.1 -> All right, and now let's understand.

594 -> What exactly is AWS.

595.9 -> So AWS is simply a cloud computing platform

598.791 -> offered by a Amazon

600.1 -> where air embolus is a collection

602.2 -> of more than 90 plus Services

604.383 -> AWS is a collection of more than 90 plus Services ranging

608.6 -> from computation databases store Services analytics iot

614 -> machine learning data science big data.

616.6 -> So there are multiple data

618.075 -> warehousing there multiple services available try

620.8 -> and that Phoebe look

622.211 -> that be at that we will be looking at step by step

625.67 -> as we move further in either Bristow main platform.

629.3 -> Now let's explore

630.3 -> the different domains available in AWS here are AWS

633.8 -> as we had discussed AWS is a collection

636.737 -> of more than 90 plus Services,

639 -> right?

640.2 -> So here we have multiple services on computation

643.2 -> on storage databases

644.9 -> migration networking management tool security

648.4 -> and identity compliance and messaging right.

651.1 -> So there are multiple Services here that we can use

653.6 -> as we can get started with.

661.1 -> Security Management in AWS.

663.3 -> So in this module,

664.525 -> we will be talking about I am

666.432 -> which is identity and access management will see

669.5 -> how this can be implemented

671.204 -> within your AWS account to manage your users

673.964 -> and groups and they're relevant permissions will talk

677.4 -> through various M components

679.3 -> and also recognize the best practices

681.757 -> of I am in the second part.

683.6 -> We'll be talking about KMS, which is Key Management Service.

687.2 -> So this is a service that helps you.

689.581 -> Create and manage your encryption Keys

692.082 -> which are subsequently used to encrypt your data on AWS.

695.8 -> And lastly.

696.533 -> We'll see how do we create billing alerts

699.2 -> or cost management options that are available on AWS.

703 -> So I am is an abbreviation for identity and access management

707.5 -> where it allows to manage your AWS users groups

711.038 -> and roles and their access to AWS accounts and services

715.453 -> and I am is a service

717.1 -> which is global in nature,

718.7 -> which effectively means

720.168 -> that we have to create a user only once

722.516 -> and that user is applicable to across all these so William,

726.1 -> you can provide access and access permissions

728.7 -> to AWS resources such as ec2 or S3 or RDS service

733.3 -> for that matter any aw service

735.28 -> that you consume.

736.411 -> So there are three components that I'll be talking about.

740.076 -> So you're familiar with active directory,

742.603 -> which is a largely used as an ldap service in most

745.7 -> of the organization's the service is very similar

749.1 -> to Active directory

750.278 -> wherein you get to Define users

752.2 -> that need similar set of privileges you would grope them

755.5 -> and then additionally Amazon has a custom implementation

758.8 -> in form of prose.

760.123 -> Let's talk about various components of I am so

763.584 -> the first component is I am user.

766.5 -> So when you create an IM user by default,

769.9 -> I am user has a non-explicit deny for all the AWS services.

775.1 -> So which means

775.961 -> when you create a user the user is not associated.

779.236 -> With any permissions at all.

780.883 -> So you'll have to explicitly Grant permissions to

783.707 -> that particular user and also you can specify which services

786.933 -> that you want Grant him access to so let's say you want

789.946 -> to Grant permissions to a developer.

791.9 -> So you might want to give him access only to ec2 service

795.643 -> where and he only has the access to Virtual servers or instances.

800.04 -> You may not want to give him access permissions

803.2 -> to S3 storage service or probably a network services

807.117 -> that are available

808.5 -> so you can All the permissions at a very very granular level

813 -> and I am uses receive unique access credential

816.4 -> so we don't have to share them with other users

819.4 -> and user can have multiple lime policies applied to them.

823.2 -> So policy actually is set of permissions

826.2 -> that you specify you specify permissions to the user

830.043 -> by using policies.

831.4 -> So policies are document

832.902 -> that formally States one or more permissions

835.689 -> and by default and explicit deny always overrides

838.8 -> and it allowed

839.805 -> so there are pre-built policy templates for every service.

843.817 -> So you have either full access or you have read only access

847.9 -> and then at the account level also you can specify

851.234 -> whether a user can have admin access

853.615 -> or not in case you're looking at building up a custom policy.

857.7 -> So that option is also available

859.833 -> within I am wearing you can specify

862.181 -> let's say you want to deny a user to terminate

865.216 -> a specific resource

866.497 -> so you can actually specify that in the policy.

869.6 -> So essentially policy is a document

871.3 -> that formally States

872.589 -> one or more permissions to need to write a Json document.

876.2 -> So Amazon also provides you access to a policy generator.

880.4 -> So for those

881.212 -> who are not familiar with Json the policy generator,

884.6 -> you just have pizza web interface,

886.746 -> you will specify what permissions you want to apply

889.8 -> or what permissions you want to die

891.8 -> against a specific AWS resource.

894.2 -> The generator would actually generate a Json template

897.74 -> for you then we have I am groups so groups.

900.7 -> It's actually collection of users having

903.248 -> similar access needs.

904.6 -> So for example,

905.502 -> you have project team that is working

907.62 -> on a specific project and they need to have similar permission.

911.2 -> So you rather

911.912 -> than managing permissions at the individual level.

914.6 -> It is always advise to manage the permissions

917.4 -> at the group level.

918.606 -> So that's the first advisory note from Amazon

921.4 -> that don't manage permission at the user level

924.277 -> but manage them at the group level lastly.

926.9 -> We have I am rolls so Roll is something that another entity

931.2 -> can assume and in doing so

932.9 -> it requires the specific permissions defined to the role.

936.5 -> So a very good example would be lets say we're

939.485 -> in we were trying to create a bucket from the CLI interface.

943.4 -> I had to pass on the access key and the secret access key,

946.708 -> which is synonymous to username and password.

949.375 -> So the second piece

950.527 -> of advice from Amazon is never within your applications

953.8 -> use the username and password to access the service.

956.9 -> So, how does the service actually Access

959.6 -> the target service,

960.89 -> which is S 3 in this case so you can do it by virtue of trolls.

965.1 -> So I log into the portal and since I am is a global Service,

969.225 -> so it is not specific to any region

971.727 -> which means any user

973.2 -> that I create you can apply that user

975.888 -> across all the region in which AWS operates.

979.1 -> So for example,

980.154 -> I have asked to work with ec2 service.

982.659 -> So easy to is a region specific service.

985.3 -> So this would mean that the resources

987.7 -> that I provision in this case or So you have a root user

991.595 -> at the top level.

992.8 -> So root user is the one it is actually the credentials

996.3 -> that you supply

997.478 -> when you create your AWS account

1000 -> that would typically be your email address

1002.918 -> and your password.

1004.188 -> So root user has a limited privileges

1006.862 -> over here account.

1008.2 -> So it is highly recommended by WS

1010.8 -> that never use your root user credentials or share them

1014.4 -> because if they are compromised any user

1016.769 -> who has the access can do whatever you want.

1019.375 -> On your specific account.

1021.015 -> So root user is

1022 -> at the top level hierarchy and has unlimited privileges.

1026 -> So essentially it is the details that you are supplied

1028.994 -> which is in the form of email

1030.7 -> and password during the account signup process.

1033.8 -> This is actually the root user.

1036 -> The second type of users

1038.061 -> that you can create is admin users.

1040.7 -> So admin users to an extent they have permission similar to as

1045.2 -> that of a root user but with some limitation,

1048 -> so for example,

1048.8 -> let's say Normal chain these support plan

1050.8 -> or admins won't have the access to the billing console.

1054.7 -> So admins typically won't have these permissions.

1057.6 -> The admins will not have the ability to modify

1060.3 -> root user details change the support plan change

1063.6 -> or delete your payment options or close an AWS account.

1067.046 -> So essentially admin user can do whatever root user can do

1070.697 -> and except for the limitations

1072.698 -> that we just discussed third type of the user.

1075.949 -> You have power users.

1077.381 -> So power users they have Have similar permissions as that

1081.2 -> of admin The Only Exception is

1083.9 -> that whatever limitations

1085.457 -> are applicable to admin be applicable

1087.7 -> to power users as well.

1089.233 -> But another limitation is

1090.893 -> that they don't have access to I am which means they

1094.386 -> don't have the ability to manage users groups

1097.371 -> and their permissions and the

1099.412 -> for type and the final type is generally referred to

1103 -> as I am users.

1104.665 -> So I am users designer Customs users,

1107.5 -> either you can make them admin

1109.3 -> or Power in case you decide not to give them admin

1112.6 -> or power users.

1113.7 -> You can specify custom permissions

1116.182 -> and most of the times you will be using the IM users

1120.019 -> with custom policies.

1121.6 -> So four types root

1123.4 -> unlimited access permissions admin slightly lower

1127.177 -> than root user and Bauer slightly less than admin.

1130.593 -> And lastly.

1131.408 -> I am user starts with no permission.

1133.979 -> It is up to so once you log into your account go to I

1137.83 -> am you see global Ball out here.

1140.128 -> So services that are actually Global it's

1143 -> always a great idea to check the security status dashboard

1146.7 -> and there are five items listed out here.

1148.9 -> First one is delete your root access keys.

1151.9 -> That is something that Amazon takes care

1154.3 -> of it right now earlier.

1155.823 -> It was use a responsibility.

1157.645 -> So that means not allowing the root user to connect

1160.9 -> either SDK or CLI interface.

1163.7 -> So that is something

1164.954 -> that is being handled by Amazon earlier.

1167.4 -> It was used as the The second aspect is activate MFA

1171.8 -> on root account.

1172.925 -> So MFA is multi-factor authentication wherein you

1176.3 -> are introducing a second factor to authenticate against AWS.

1180.6 -> So if you recall when I log into my AWS account,

1184.515 -> I Supply username and password.

1186.9 -> That's simply because I have disabled the MFA

1189.1 -> because I had to swap my phone

1191.2 -> but usually for root user admin users are any priority users

1195.8 -> who have higher level

1197.262 -> of privileges it is always Advisable

1199.7 -> that you activate MFA on those then you have create individual.

1203.6 -> I'm users.

1204.249 -> So if you have created and users in your account,

1207.233 -> so this would be green

1208.6 -> since you have very recently signed.

1210.519 -> This would be orange then Jews group.

1212.736 -> So if you have created groups,

1214.501 -> this would again be green and lastly apply

1217 -> an IM password policy.

1218.5 -> So this is very similar to password policy

1221.097 -> that you set up on active directories are

1223.7 -> in you set up password complexity requirements then

1227 -> go to manage password policy.

1228.889 -> So You can specify the minimum length.

1231.3 -> So this is applicable at the account level any settings

1234.632 -> that you specify here would be applicable

1237.1 -> to all the users.

1238.2 -> So minimum password length should be 6 then

1240.72 -> complexity requirements

1242.1 -> like uppercase lowercase number alpha numeric

1245.028 -> allow users to change their password enable expiration.

1248.44 -> So this is again a great feature.

1250.555 -> We're in almost every organization has

1253 -> an expiration policy like 30 days 60 days

1255.804 -> or 90 days and you're forced to actually change.

1259.1 -> Words, so for the users who have access to AWS,

1262.4 -> you can actually force them to change their passwords

1265 -> depending upon your organization policy in terms of duration,

1268.629 -> then prevent password reuse again, pretty similar.

1271.592 -> You cannot keep

1272.5 -> the previous three passwords as your current password

1275.1 -> and then password admin expiration requires.

1277.9 -> Admin reset.

1278.7 -> The password has expired

1280.2 -> in many times many applications will see request

1283.06 -> as actually go to the admin for setting that up.

1285.916 -> So we'll go to users add user give it a name.

1288.614 -> So I am Being in by the named everyone.

1290.89 -> So assuming that is part of the developer group and visuals

1294.465 -> in the developer group would have similar access needs.

1297.7 -> Let's call it as Dev one and there are two types of access

1301.197 -> that you can grant to the user.

1303.095 -> The first one is programmatic access.

1305.383 -> So in this case,

1306.4 -> if you want to Grant user the CLI Axis

1309.052 -> or you want sdks

1310.206 -> that is working with to make API calls to AWS will have

1314.005 -> to generate a access key and a secret scheme.

1317.1 -> So that is typically referred to

1319.095 -> as As programmatic access the second type of access is

1322.5 -> AWS Management console access.

1324.499 -> So in this case,

1325.548 -> the user would be actually be able to log on to AWS console.

1329.3 -> So let's say

1330.001 -> if you are creating an admin user so then naturally

1332.635 -> you will have to condemn console access as well.

1335.5 -> So if you are doing it for a developer,

1337.869 -> you can simply do away with programmatic access.

1340.8 -> So for now we'll run console access.

1343.082 -> We'll just apply a custom password.

1345.3 -> So I'm on checking these but Diamond as

1347.376 -> a good security measure you should Marching them.

1350.2 -> I'm not adding the user

1351.441 -> to any group at this point of time just to demonstrate

1354.6 -> that when a user starts with no permissions.

1357.205 -> This user would be able to do is simply login to the AWS portal

1362 -> that's about it.

1363.053 -> So for I am users will have to use

1365.229 -> a different user sign in link.

1367.275 -> So the root user actually goes through the process that I do

1371.3 -> which is aws.amazon.com.

1373.36 -> I actually sign in with Google user credentials

1376.387 -> so that I have requisite access.

1378.593 -> So otherwise sighs all I am users

1380.8 -> that includes admin and power users

1383.214 -> and other I am users.

1384.7 -> They will have to go through the I am signing.

1387.7 -> So just go to customize

1389.2 -> and you can replace the account number with name

1392.2 -> of your choice just grab this.

1394.3 -> So I'm using a different browser

1395.9 -> because I am already signed in as a root user in this account.

1398.8 -> I'm using Mozilla right now and say the username

1401.802 -> and then the password so I'm logged in as

1404.558 -> Dev one and let's see

1405.9 -> if I have access to any service.

1410.021 -> So it says not authorized any service

1412.8 -> that I actually go ahead

1414.514 -> and check user would not be having permissions.

1419.3 -> So it's access denied.

1420.6 -> So rather than applying permissions at the user level.

1423.25 -> So what I'll do is I'll go ahead and create a group

1425.688 -> and I'll be setting permissions

1427.2 -> at the group level rather than at the user level.

1429.8 -> So the impact will be the same.

1431.8 -> So now we have an option to attach the policy so policy

1435.301 -> what we said was it set of permissions

1437.7 -> that we are going to apply to the specific group

1440.575 -> that we are creating

1441.8 -> so we can do it during the group creation process

1444.8 -> or else we can always go back

1446.7 -> and then attach a policy to the group.

1449.3 -> As you see we have admin access.

1451.7 -> So this is admin access at the account level.

1454.7 -> Then you have our user access.

1456.7 -> So game this is applicable

1458 -> at the account level and for rest of the services

1461.6 -> if you see so for example ec2.

1464.4 -> So in this case,

1465.2 -> you will have easy to full access

1467.492 -> or easy to read only access.

1469.5 -> So we're looking at two extremes either default templates

1472.884 -> can grant you full access permissions.

1475.167 -> If you're talking at the specific service level

1477.873 -> or read-only Burmese.

1479.1 -> Ins if you want to do something in between,

1481.346 -> you'll have to create a custom policy.

1483.358 -> And for the user

1484.28 -> if you want to make them admin power users,

1486.59 -> we can always do that.

1487.8 -> So what I will do is I learned I see two full access

1490.549 -> to this user this group rather.

1492.26 -> So I'll add that user to this particular group.

1494.8 -> So if I was to take a look at this user it will clearly

1498.3 -> indicate what policy is applied to this user and from

1501.686 -> where it is inheriting that policy.

1504.1 -> So first check we have granted.

1506 -> I am easy to access.

1507.4 -> So now the user is able to Says the ec2 service.

1511 -> Let's try with another service.

1512.972 -> The user should not have the access.

1515.2 -> So this is the correct Behavior.

1517.4 -> Also if I was to switch over to some other region

1520.8 -> the user would still have the access to easy to

1523.314 -> because we haven't put any restrictions or at

1525.682 -> this point of time,

1526.7 -> but for rest of the services again,

1528.7 -> the user will see the same impact.

1530.7 -> So I'll come back to the root user browser window.

1534 -> So what I'll do is I'll create another group.

1536.865 -> Let's say project leads so for Eject leads.

1539.6 -> Let's say we are going to ding access to S3 service.

1542.1 -> So we'll gaming m is threefold Axis.

1544.6 -> So there are no users towards will add the user to it

1548 -> that the group level you can see the permissions

1550.5 -> by using the permissions Tab.

1552.096 -> And now if you want to check

1553.568 -> that Dave is part of two groups at this point of time

1556.333 -> and you will see in the permissions tab

1558.444 -> what on permissions are the user is inheriting.

1561 -> So now the user has full access to ec2 and S3

1563.854 -> and that tool is inheriting it from two different groups.

1567.594 -> So now the user has access To S3 Service as well.

1571 -> So if the user is

1572.161 -> in editing permissions from multiple groups,

1575.1 -> the overall impact would be

1576.86 -> cumulative sum total of all the permissions

1579.494 -> that is being inherited.

1581 -> So I will talk about an exception.

1582.9 -> Also, we're in let's say in one group.

1585.366 -> The user was specified access to a service

1588.138 -> and in some other group,

1589.713 -> the user was denied access to that service.

1592.475 -> So whenever they will be a conflict

1594.766 -> that deny would always override and allow so let's say

1598.39 -> if this user I was to leave the organization.

1601.4 -> So one way is to manually go and delete the user.

1605.1 -> So many a times you need the user account still

1607.576 -> active for a variety of reasons.

1609.3 -> You simply want

1610.182 -> that the user should not be able to do anything just in case so I

1613.947 -> do have a denial group

1615.305 -> and I've already specified deny all policy.

1617.98 -> So in this case,

1619 -> I am denying the access user to any service.

1622 -> So now the user is the narrating the permissions

1624.5 -> from three groups

1625.5 -> and the third one actually denies the access

1627.781 -> to any service so even

1629.169 -> though Has full access to ec2

1631 -> and S3 the deny would actually superseded all the allows.

1634.805 -> So in case of conflict

1636.3 -> or deny would always supersede explicit law.

1643 -> This is true for all the regions

1645.097 -> so you can just flip around the regions and see the impact.

1648.673 -> The impact will be the same.

1650.4 -> So one takeaway here is the moment.

1652.585 -> I change the permissions the results are immediate.

1656.2 -> So there is no lag.

1657.392 -> You see scenario based questions.

1659.4 -> We're in change the permissions of what would happen.

1662.2 -> So the impact would be immediate you were guarding access

1665.244 -> the access would be grounded on immediate basis.

1667.8 -> So as long as there is there a law the resultant

1670.9 -> Will be cumulative

1672.284 -> if there is Adlai deny

1673.939 -> or a conflict then I would always supersede

1677.1 -> so I've already created a admin group

1679.5 -> so I can actually go ahead

1681.029 -> and detach and let's attach it again.

1683.147 -> I'm using the pre-built templates administrative access.

1686.3 -> So any user who becomes a part

1688.114 -> of this group now we'll have admin level privileges.

1691.2 -> So day one is now part of admin group.

1694.1 -> So let's go back to the dev One browser window.

1697.081 -> So now the user has access

1698.845 -> to all the services we also Also said

1701.7 -> that this admin user has some limitations

1704.5 -> predominantly in form

1706.1 -> of changing the support plan closing the account access

1709.412 -> to billing dashboard.

1710.7 -> So let's hear this user has access

1712.527 -> to the billing dashboard or not.

1714.3 -> So by default behavior is that the access is denied

1717.8 -> if I was to actually go ahead and check it withdrew to use

1721.3 -> the credentials time able to access likewise.

1724.157 -> You can set up a power user group.

1726.3 -> Simply attach a power user access.

1728.5 -> So now this user is part of power user.

1730.815 -> Effectively has all the permissions that admin had

1733.8 -> except on this would still be applicable

1735.949 -> because I had means did not have this privilege in addition.

1739.307 -> This user would not have access to I

1741.3 -> which means this users

1743 -> in the Power Group won't have the ability to manage users

1746.6 -> and groups or their permissions.

1748.394 -> We have the desired Behavior.

1750.1 -> So in order to activate MFA,

1752.056 -> so you could either use a software application

1755.34 -> or a hardware token.

1756.8 -> So if you want to use a virtual MFA So based

1760.8 -> on On the platform.

1762.187 -> If you have an Droid iPhone or Windows Phone,

1765.4 -> you could either use Google Authenticator

1768.3 -> or two Factor authentication.

1770.7 -> So any one of these

1771.891 -> so most commonly used as the Google Authenticator

1774.959 -> so you can just simply go ahead and download it

1777.9 -> from the play store or App Store

1780.4 -> as if you decide to use a hardware token.

1783.2 -> So hardware token would look something like this.

1786.4 -> So the process to set up MFA is pretty straightforward.

1790.9 -> Tell you want to set up an MFA for Dev one go

1794.122 -> to security credentials Tab

1796.1 -> and then you have an option assigned MFA device

1799.1 -> the same manage specify what type of a you want to use.

1803 -> So we are using virtual MFA

1804.787 -> and using your smartphone scan the QR code

1807.5 -> and there's another step subsequent stuff and doing

1810.523 -> that it would Google Authenticator

1812.518 -> would become your second Factor authentication.

1815.376 -> So let's try this out on the root user.

1818.3 -> So for the root user

1819.5 -> in your case, it would be the equivalent.

1821.2 -> Account number just go to my security credentials

1823.7 -> and activate MFA.

1824.9 -> So I already have a Google authenticator with me.

1827.8 -> So I'm scanning this so

1830.5 -> on the Google Authenticator application I get two codes

1834.117 -> will have to punch in

1835.529 -> that so wait for 30 seconds.

1837.411 -> It would generate the second set as well.

1840.053 -> Let's say Devin already member of power users.

1843.017 -> So if you're logged in you'll be logged in.

1845.655 -> So this user will still

1847.1 -> have access to all the services for the purposes of Des Moines.

1851.2 -> Taking all to services ec2 and S3.

1853.7 -> So this user has access to all the services

1856.175 -> which is very similar to admin.

1858 -> So now admin did not have access to the billing console.

1861.2 -> So this user will also not have access to the billing console

1864.7 -> also power users don't have access to I am so I am

1868.8 -> we know it is used to manage your users.

1871.4 -> You can create them Grant permissions to them.

1874.173 -> So you don't actually have access to the I

1876.624 -> am service per se.

1877.718 -> So now what I will do is I will remove this user

1880.599 -> from the the power user group.

1882.474 -> So now this user is now a member

1884.474 -> of admin so earlier he was member of power.

1887.1 -> So now this user should have access to I am which means

1890.9 -> as I admin you have the ability to create users manage them

1894.8 -> Grant specific permissions the way you like.

1897.7 -> Let's say we want to build

1899.386 -> custom policies rather than granting access as a whole

1902.925 -> to a service we want to restrict

1905.018 -> to some specific set of permissions.

1907.3 -> So in the first part of the demo,

1909.207 -> what I'll do is I'll create a

1911.017 -> In policy template just to make you familiar

1913.7 -> with how the policy template looks like

1916.2 -> and we'll take it Forward

1917.726 -> where it will go stick this user from accessing

1920.666 -> regarding easy to access

1922.2 -> but only to a specific region

1924.3 -> and then enabling only specific set of actions.

1928.1 -> So we have a policy generator available.

1930.9 -> We'll just use that to create our Json template.

1936.7 -> Select the type of policy that we want to create.

1939.1 -> So in this case,

1940.1 -> we are creating a im policy

1941.933 -> and the fact this is essentially stating

1944.5 -> whether we want to allow or deny the access.

1947.366 -> So in this case by saying allow the access and in the drop-down

1951.5 -> that you see is set of all the AWS services

1954.315 -> that are available.

1955.6 -> So I'll check all the services

1957.73 -> since I'm creating an admin policy

1960.081 -> and I'll just simply hit add statement

1962.599 -> and then generate policy.

1964.357 -> So this is how your Statement would look

1967.1 -> like S ID is more like a description optional action

1971.423 -> or we'll start with effect.

1973.5 -> In this case.

1974.3 -> We have said allow and actions by default.

1976.995 -> We said allow to all the services

1979.1 -> and action is every action applicable to each service.

1982.9 -> So this is your admin policy.

1984.9 -> If you were to actually compare it with the admin template.

1988.9 -> This is what we have

1990.094 -> so you can create your own policies the way you like.

1993.2 -> So now let's create a custom policy now,

1995.67 -> We're in let's say whosoever this policy is applied.

1998.9 -> So we are applying it to the developer group

2001.3 -> and they'll have access to ec2 service

2004.146 -> and that will be specific only to a one region.

2007.6 -> So let's say Oregon.

2009.1 -> So in this case,

2010.166 -> we'll select ec2 then within easy to these

2012.9 -> are the set of actions that you could actually perform.

2015.711 -> So to keep it simple at this point of time

2017.87 -> and select all the actions

2019.4 -> which is equivalent to easy

2021.2 -> to full access a RN is Amazon resource name.

2024.8 -> We're in a Resource

2026.4 -> that you create on Amazon generates a URL

2029.8 -> so you can actually specify which specific resource you

2033.6 -> want to control access to

2035.3 -> so let's give it as tricks out here any resource within easy to

2039.5 -> and now I'm adding a condition.

2041.566 -> So these are the operators

2043.3 -> that I can use as a string like and I'll use region

2047.2 -> since this is what we want to achieve

2049.8 -> and this case I will say u.s. West to

2052.8 -> so this is the Oregon region so for the,

2055.253 -> Oregon Agent you'll see

2056.7 -> u.s. - vest -

2058 -> to if I was to change it and that's the quickest way.

2061.2 -> There are other ways also.

2062.7 -> So for example, North Virginia would be u.s.

2065.1 -> - East - 1 so

2066.9 -> what essentially we are saying is lying access

2069.6 -> to ec2 service to perform all the actions on ec2 service

2073.013 -> and you're putting in a condition

2075 -> that the region has to be uswest to add

2078.1 -> the condition and statement and generate a policy.

2081.241 -> So this is what it generates.

2083.1 -> The first part is pretty much the same as we saw.

2085.764 -> In the previous case,

2087 -> but with the condition just copy this.

2093.3 -> I'll just simply paste this policy will name it as

2096.648 -> easy to region District policy

2098.7 -> which was a policy has been created.

2100.573 -> We can filter it with customer manage.

2102.538 -> So this is the policies that you create custom policies.

2105.5 -> They are being referred to as customer manage policy.

2108.558 -> So this is the one that we created

2110.4 -> so you create a policy.

2111.8 -> Let's say easy to Allowed the user to this group.

2123.284 -> So let's try this out

2124.9 -> since we have granted access only to ec2.

2127.798 -> So rest of the services should not be available

2130.375 -> to this user so which is good

2132.081 -> since we aren't in the Oregon region,

2134.1 -> which is u.s. Rest too.

2135.4 -> So the user is able to access.

2137.4 -> So if I try to actually go ahead and try to access easy

2140.576 -> to any other region the access would be denied.

2143.1 -> So it is always good to have these kind of policies

2145.7 -> in place else users can provision resources

2148.366 -> in any of the regions

2149.7 -> and it will become an administrative nightmare

2152.347 -> for the ad.

2153.089 -> Vince to see

2153.9 -> where the resources are being Persian

2156.128 -> and the last part for the demo for custom is just

2159.1 -> to Regina ec2 instance quickly.

2161.3 -> So the idea here is

2162.761 -> that not to restrict

2164.3 -> the user from terminating the instance so many times

2168.7 -> when you don't need virtual server or instance,

2171.227 -> you can actually go ahead and terminate that resource.

2174.344 -> So we are restricting the abilities of the developers.

2177.462 -> They should not be in a position to terminate

2179.9 -> so only admins should be able to terminate that.

2182.8 -> So we already have this policy bill.

2184.669 -> So I'll just simply add rather than let's do it again.

2187.523 -> So this time rather than selecting all actions.

2190 -> I'll start off with allow all the actions.

2192.5 -> So this is pretty much the same that we adjusted

2195.476 -> and now I'm adding a second condition to it.

2198.2 -> And this time I will say deny ec2 and I am specifically saying

2202.5 -> that the user should not have the ability

2204.8 -> to terminate the instance.

2206.372 -> So in the first part I said the law to all the I actions

2209.7 -> and the second part I said deny to one of the action

2212.809 -> And I would supersede the allow

2214.7 -> and then renders the first part is the pretty much the same

2217.7 -> that we saw in the previous demo in the second part.

2220.65 -> What we are saying is the fact is deny service is easy

2223.5 -> to action is terminate sources

2225.8 -> any resource just copy this simply go ahead

2229.176 -> and edit the existing policy and Sarah.

2232.1 -> So user still does not have

2233.872 -> access to easy to in any other region,

2236.295 -> except, Oregon.

2237.277 -> I'll switch over to the Oregon region.

2239.7 -> I actually Vision the instance in North Region.

2243 -> Harry so,

2243.8 -> what I will do is I'll just move over to the Oregon

2246.3 -> the just to demonstrate

2247.713 -> that resource created by

2249.188 -> the root user cannot be deleted by the devil user in this case.

2253 -> So now I'm logged in as Dev one and let's go TC.

2256.8 -> So I'll try to terminate this resource.

2258.9 -> So it has generated an error.

2261 -> So thereby restricted the user from termination.

2265.6 -> So specifically for higher environments.

2268.149 -> Let's say production or uat environment.

2270.7 -> You really want to put these kind of rest.

2273.1 -> Shenzhen Place,

2274.1 -> whereas if I do it with the root user credentials,

2276.923 -> so there are no limitations out there.

2279.017 -> I can simply go ahead and terminate managing users

2281.9 -> with I am we have already seen users in the console group

2285.575 -> than can always go ahead and delete them.

2288.2 -> You can rename your users using the CLI the users we have seen

2293 -> this already seen managing permissions using policies

2297 -> and policies are essentially your Json documents

2300.7 -> and you already have a policy generator.

2303.081 -> Later, you can take itself to generate the Json policies.

2306.454 -> So from a SS perspective

2307.9 -> another security restriction always follow the principle

2311.1 -> of least religious only Grant permissions

2313.1 -> that are required by the user to perform

2315.9 -> their specific job function.

2317.9 -> So we have all seen these in the demo create

2320.9 -> groups attached policies use managed policies.

2324.6 -> So marriage policies are the ones

2326.482 -> that are created by Amazon and customer manage.

2328.972 -> So there could be a legitimate business need

2331.258 -> as we saw in the later demos.

2332.964 -> That we actually want to go ahead and put additional levels

2336 -> of the restrictions.

2337.2 -> These are the various elements of IM policy affect allow

2340.884 -> or deny action specific to a resource resource

2343.9 -> could be easy to principle is basically the username

2347.408 -> if you want to specify so the sample Json

2350.36 -> that we have on the screen is related to S3 service

2353.8 -> so effect it says allow on which servicer is S3

2357.9 -> and we are specifying us only one action,

2360.3 -> which is list pocket which means listings.

2362.794 -> On the contents of the bucket

2364.345 -> and to which resource are we applying in?

2366.511 -> This case?

2367.1 -> The name of the bucket is example underscore bucket.

2370.1 -> So the way we have done it for easy to same logic

2372.9 -> can be extended across any service

2375.4 -> or all the services

2376.8 -> that me going to cover to the program

2379.073 -> that we have already seen creating policies

2381.2 -> for news having admin

2382.586 -> or limited images best practices use

2385.296 -> I am access and permission management delegation

2388.4 -> and audit and just cover

2389.7 -> so you are the best practices that we

2391.667 -> have already spoken about.

2393.1 -> You can go up

2393.871 -> to the very finest level of tolling permissions

2396.714 -> with respect to a service in question.

2399 -> Then benefits strong password policy

2401.5 -> where you set up your complexity requirements and way to expire

2405.6 -> the passwords based on your organization's policy.

2408.798 -> So we have already seen

2410.3 -> how do we create access for users to login

2413.27 -> to AWS console.

2414.304 -> So now what I will do is just create a user

2417.2 -> and this time we will grant them the programmatic access.

2419.8 -> So this would enable the user to access

2422.622 -> the the AWS Services via the CLI

2425 -> or the sdks for the service has generated the access ID

2428.946 -> and the secret access key.

2430.77 -> So this is the only time

2432.526 -> that you have to capture both the access ID

2435.481 -> and the secret key else

2437.1 -> the secret access key is never available.

2439.6 -> So we have downloaded the credential so I can go ahead

2442.327 -> and close this.

2443.1 -> So this is essentially the username and password

2445.4 -> for this and we'll have to assign permissions that

2448.1 -> which this user has access to which service

2450.8 -> so we can make this user a part of Pacific group will make

2454.4 -> this user part of project leads

2456.3 -> and project leads have already permissions assigned to it

2459.7 -> where and we have granted s three-fold axis.

2462.545 -> So this is how you do it.

2464.2 -> You need to have the CLI installer in place first.

2467.085 -> And once you have installed the installer,

2469.5 -> the first step is to issue a WS configure where you

2472.8 -> are authenticated against AWS.

2474.888 -> Let's grab the access ID.

2477 -> So now I have authenticated

2478.769 -> against the SS and the permission

2480.918 -> that this user has full access.

2483.003 -> Permissions to S3.

2484.6 -> So you WS s 3MB.

2488.723 -> Let me see the right syntax.

2491 -> So the user has been able to create the bucket

2493.6 -> so you can actually go ahead and check it out.

2495.99 -> So this is the bucket that we created using the CLI.

2498.7 -> Let me create a bucket.

2500.3 -> So let's say demo.

2502.2 -> Let's give it some name so specify the region

2505.687 -> in which to set up your bucket.

2507.9 -> So make sure

2508.7 -> that when you create a bucket just uncheck

2511.4 -> these options all these.

2513.05 -> Block statements so just

2514.7 -> make sure that you don't enable them so this does not mean

2518.246 -> that the bucket has become public.

2520.3 -> So we just created a bucket bucket treated as a container.

2524.1 -> And now when I upload any data into this bucket,

2527.571 -> so roles are typically another way of granting

2530.8 -> commission's and it is something that another entity can assume

2535.646 -> and in doing so

2536.8 -> requires the specific permissions defined by the roll

2540.8 -> so you can use roll.

2542.7 -> For variety of purposes.

2543.9 -> Let's say you want to integrate your existing ldap services

2548 -> with I am or you want one service to interact

2551.8 -> with other services.

2552.8 -> So the target service you need permissions.

2555.509 -> So you create a rule

2556.8 -> that is sitting in Silo and The Source service.

2559.584 -> We would assume that role

2561.062 -> and in doing so it would get the permissions

2563.591 -> that are applied to roll and

2565.291 -> that raised it will be able to access the target service.

2568.7 -> So for example,

2569.692 -> if you are using a ec2 instance and it needs access

2573 -> To S3 bucket.

2574.361 -> So in this case instance would assume a role from I am

2578.5 -> with proper required permissions

2580.622 -> and then the instance can perform actions based

2583.607 -> on the roles it resumes

2585.138 -> but we should never pass a store credentials

2588 -> into ec2 instance.

2589.22 -> So roles are pretty important in that context.

2592.2 -> So by default in this demo that will see ec2 instance

2595.6 -> by default can have only one rolled assigned to them.

2598.8 -> So that role can have multiple permissions assigned

2601.822 -> to it in the Background so we'll go to roles.

2605.086 -> So we are creating a role for AWS service

2607.6 -> and this case ec2.

2612.7 -> Can just simply pick up S3 full access policy

2616.4 -> that is being applied to this role.

2627.9 -> So this is the role that we created

2630.5 -> and it allows the ec2 service to assume the role,

2634.7 -> but we'll have to actually apply it at the instance level

2638.2 -> so that can assume this role.

2640.3 -> So just let me quickly provision.

2642.5 -> I instance.

2654.9 -> You have one of the configuration parameters

2657.3 -> during the provisioning process wherein you can assign I am road

2661 -> to the instance.

2662.1 -> In this case.

2662.934 -> We will assign the demo S3 access road to the instance.

2697.2 -> So now this instance has a role attached to it there

2701.258 -> in that role has a permission to Grant access to S3.

2705.4 -> So I really don't have to pass

2707.8 -> on the credentials to 28 against the S3 service.

2712.2 -> So if I straight away go ahead

2714.3 -> and want to list the contents of S3.

2717.2 -> I can do that.

2718.4 -> I actually had to pass on the access key

2720.98 -> and the secret access key for not just take it

2724 -> and I had access to ec2 instance and from that.

2727.1 -> Instance by virtue of role.

2729.4 -> I was able to access S3 servers.

2733.2 -> Also.

2733.7 -> There are a number of types of roles

2735.927 -> that you can create.

2737.2 -> So let's say you can create a role

2739.58 -> between another AWS account.

2741.8 -> So now you cannot have users maintaining multiple identities

2745.595 -> that in one account you have username and password

2748.7 -> in the second account with different and likewise.

2751.827 -> So how do we mitigate that kind of a situation

2754.7 -> so we will create roles across Multiple AWS accounts

2758.7 -> and in the Target account you will be creating the role

2761.9 -> that would have permissions and from The Source account

2765.3 -> where your users are defined

2767.1 -> that users would assume that role in the another account.

2770.7 -> Then you have web identity.

2772.211 -> So a lot of applications allow authentication

2774.99 -> via third party platforms like authenticate with Google

2778.5 -> or Facebook or LinkedIn

2780.257 -> so you can set up web identity as well using roles

2784.006 -> and lastly saml 2.0 Federation.

2786.5 -> So this Is

2787 -> where you can integrate your active directories

2789.951 -> with I am so that way

2791.3 -> is we will maintain a single identity store

2793.983 -> that is your active directory.

2795.9 -> You will Define your users groups

2798.361 -> in active directory.

2800 -> And on the AWS side,

2801.653 -> you will be simply creating the roles.

2804.5 -> So the user she have to feed rate or active directory

2808.2 -> stablish SSO between your identity store and I am

2812.1 -> so that Waze users will have single credentials so

2815.434 -> for logging on to Gary.

2817 -> Email or to their endpoints desktops or laptops.

2820.406 -> They have only one set

2821.996 -> of credentials to play with principle

2824.6 -> of least privilege has manage permissions with group

2828 -> and then restrict privileged access further with conditions.

2832 -> So let's say even

2833 -> if you are giving easy to full access,

2834.9 -> so in the demo,

2835.702 -> we said we are not relying

2837.231 -> the users to terminate the resources something

2839.7 -> like this then enable cloud trail to be aware

2842.7 -> of API call logs.

2843.936 -> So in this case,

2844.9 -> how do I keep a track that which you It is provisioning

2847.6 -> water source is making changes to those resources.

2850.6 -> So there's another service called Cloud train.

2853.247 -> So that actually keeps a track

2855.2 -> of all the APA calls being made to your AWS resources.

2859.4 -> So that concludes I am.

2862.3 -> So we'll move on to the next service

2864.1 -> which is Key Management Service of commonly referred to as KMS.

2868.003 -> So again, KMS is a region-specific hosted service

2871.74 -> that makes it easy to create and control encryption keys on AWS,

2876.6 -> which are used to encrypt data.

2878.8 -> So the background KMS uses Hardware security modules

2882.3 -> referred to as hsms commonly to protect the security

2885.9 -> and integrity of the keys.

2887.8 -> So before we get into the service,

2889.8 -> so there are two types of encryption that you can perform.

2892.4 -> One is symmetric and one is a symmetric.

2895 -> So KMS uses a symmetric encryption.

2897.7 -> So in symmetric encryption

2899.495 -> use the same key to perform both encryption and decryption.

2903.7 -> So that's principally because symmetric encryption is

2906.758 -> much faster as compared to a symmetric encryption.

2909.534 -> So in asymmetric encryption

2911.129 -> one part of the key pair is used to encrypt

2913.612 -> and the second part is used to decrypt

2915.8 -> so that's a pretty slow.

2917.418 -> I also not any kind

2918.7 -> of an encryption comes up with an overhead.

2921.184 -> So that's going to to kind of slow your performance.

2924.2 -> So with respect to data security

2926.523 -> two important aspects one is data security in transit

2930.3 -> so that you can meet by implementing SSL

2933.5 -> and data at rest meaning security for data at rest.

2937.4 -> You'll have to use a specific Key Management Service.

2941 -> So you can generate

2942.258 -> your own Keys within KMS service organum boat your keys.

2945.9 -> You can specify which I'm users or roles can manage those keys

2950.3 -> and then you can set up our L4 K zh as well,

2954.2 -> which tells you

2955.319 -> that which user has been using the keys so for predicting

2959.5 -> your data on cloud environment

2961.636 -> or for that matter in any environment

2964.2 -> that more likely to use a service similar to KMS

2967.7 -> and services similar to KMS

2969.6 -> would help you create your encryption keys

2972.516 -> and manage them store them rotate them at a periodic intro.

2976.538 -> So there are two types of keys in KMS one is CM case

2980.499 -> which is customer master keys.

2982 -> He's and the second one is data keys.

2984.425 -> So data keys are actually used to encrypt and decrypt

2987.966 -> whereas CM case which is the customer master keys used

2991.575 -> to protect the Integrity of the data key.

2994.9 -> So refer to this illustration

2996.745 -> that we have so it is actually a two-fold process

2999.8 -> where into the plain text your data key

3001.994 -> is applied along with the encryption algorithm.

3004.7 -> So it is AES 256-bit encryption algorithm.

3008 -> So combination of both these two is applied

3010.758 -> to your plain Text data.

3012.335 -> The resultant is your encrypted data.

3014.7 -> So we said that this is a symmetric key encryption

3018.2 -> and the same key is used to decrypt the data

3021.3 -> so I can push this data to any storage of my choice.

3026.3 -> And now how do I decipher this data?

3029.3 -> So I'll need the access

3030.652 -> to the same data key to decrypt this.

3032.7 -> So either I keep the data key along with this

3035.092 -> but then the entire purpose gets defeated.

3037.337 -> So the second part

3038.31 -> of the process is to protect the Integrity of the data key,

3041.6 -> what you do is

3042.4 -> if you encrypt the data itself using the Mastery

3045.466 -> and more commonly referred as CM case and apply

3048.339 -> the encryption algorithm.

3049.9 -> So the resultant that you get is the encrypted data key

3053.2 -> + this encrypted data key is stored

3055.338 -> along the the encrypted data.

3057.207 -> So whenever you have to decrypt it,

3059.4 -> your cmk is applied to the data key

3062 -> that gets decrypted and that decrypted data key is the again

3065.898 -> applied to the encrypted data.

3067.8 -> So this is the workflow

3069.209 -> that actually happens in the background.

3071.7 -> So Game gays never leave became a service

3075 -> are encrypted data key scan.

3077.7 -> So two types of keys customer master keys and data keys,

3081.9 -> so you can see your spend summary

3084.154 -> and based on which services that you have spent money on.

3088.1 -> So I have spend almost 39 cents on Route 53 rest are negligible.

3093 -> So it will give you the spend of previous month's

3096.1 -> and additionally your top free tier Services by usage.

3099.576 -> So in order to set up

3100.905 -> notifications The first step is to go to preferences

3104.1 -> and you have to check these options receive billing alerts.

3107.6 -> So this is first part of the process

3109.658 -> that you have to check this option receive billing alerts

3112.9 -> and in terms of setting up our actual or which is

3115.8 -> actually a notification in form of an email.

3118.338 -> We actually set it up in another servers.

3120.81 -> So in this case,

3121.8 -> we are talking about AWS alerts.

3124 -> So alerts is way of notification to a set of users.

3127.7 -> So in this case, our focus is on building a lot,

3130.2 -> but otherwise alerts could be

3132 -> About anything about monitoring the performance of your system

3135.804 -> and generating alerts out of it.

3137.8 -> You can set up alerts for your services going down

3140.927 -> or your additional resources being provisioned

3143.82 -> for you can set up alerts for any kind

3146.2 -> of action within AWS.

3147.6 -> So in this case since the focus is purely on billing

3150.487 -> so you can set up billing alerts.

3152.3 -> They said first part of the process

3154.3 -> has received billing alerts.

3156.1 -> So in order to actually receive the billing alert,

3158.9 -> you'll actually have to go to another service

3161.1 -> which is cloudwatch.

3162.147 -> Ouch, so cloudwatch is a monitoring service.

3164.388 -> So in the cloud wat dashboard

3165.9 -> on the left hand side of the pain you have billing.

3168.4 -> So UV actually have to be

3169.665 -> in the North Virginia region to set up the billing alert.

3172.5 -> So it does not really matter where your resources are,

3174.944 -> but you have to be in the North Shore Jeannie region

3177.149 -> to set up the building alert.

3178.418 -> So this is where you will create your alarm,

3180.307 -> but you will be only able to create the alarm

3182.328 -> once you have checked the option in the billing dashboard

3184.9 -> under preferences.

3186.1 -> So let's say

3187 -> when your total charges exceed let's say $1,000

3189.9 -> just type in your address and we'll send Alarms

3192.833 -> probably the last topic

3194.3 -> of discussion for today is AWS budgets.

3197.1 -> So with respect to cost Management on AWS,

3200.3 -> we have already seen billing alerts budgets are another way

3204.133 -> that give you the ability to set custom budgets

3207.3 -> that alert you

3208.3 -> when your cost or usage has exceeded your budgeted amount

3212.8 -> so you can track it on either at monthly

3215.3 -> or quarterly or yearly basis.

3217.5 -> So in this case you have created seven budgets.

3220.5 -> So let's say you want to Set up budgets

3223.013 -> across variety of projects.

3224.826 -> So in this case,

3225.9 -> you have project Nemo and you have budgeted $45

3229.312 -> for this project.

3230.547 -> So this is your current level and forecast.

3233.6 -> It is 56.

3234.6 -> That means you are exceeding your budget by some percentage.

3238.3 -> So you could set up the budget

3240.3 -> on two three types rather one is cost second one is usage

3244.9 -> and the third one is based on reservations.

3247.9 -> So on your billing dashboard,

3249.505 -> you can go to budgets create a budget so

3252.066 -> For the free tier the limit

3253.7 -> as you can create two budgets free of cost.

3256.343 -> But otherwise, I believe you can create thousands

3259.243 -> so nothing to worry about.

3260.8 -> So as I said,

3261.578 -> you could create the budget based on cost or usage.

3264.6 -> So let's say you're worried about the cost

3267.2 -> that we incur growing by using radio services within AWS.

3271.5 -> We will create a cost budget.

3273.281 -> If you are more concerned about the usage.

3275.877 -> There are a lot of variable factors in costs

3278.6 -> when using services,

3280.8 -> so if you want To track them

3282.6 -> by usage some parking reservation right now

3285.3 -> because this is something that we have not touched.

3288.005 -> So this is essentially

3289.3 -> that you're reserving capacities with AWS

3291.783 -> and you get significant discounts in this model.

3294.7 -> So we'll just simply go ahead and create a budget.

3297.3 -> So in this case,

3298.389 -> let's say monthly see to budget.

3301.323 -> So let's keep it to monthly.

3303.5 -> She could set it up as a recurring budget

3306 -> or monthly basis or for one time.

3308.153 -> You can specify the start and end dates.

3310.67 -> You can set up filters by default.

3312.8 -> It is included all based on the service.

3315.394 -> Let's say elastic compute.

3317.064 -> In this case.

3317.9 -> Then you have configure alerts you can say it up on the basis

3321.8 -> of actual cost and forecasted.

3323.937 -> So let's say in this case, I'll specify it P

3326.944 -> so I will be notified

3328.4 -> when the costs are nearing about 800 so just set

3331.604 -> up my email contact

3332.9 -> and you're good.

3333.8 -> So I have this virtual server is running

3336.1 -> so I can go ahead and create a system alarm

3338.6 -> or I can create another type of envelope based on the condition

3342.2 -> that I want to specify.

3343.6 -> So in this case CPU utilization and these are the measures

3347 -> that are available

3347.85 -> so you can choose either one of them Pro trigger out an alarm.

3350.9 -> So you want to set up aggregate CPU utilization

3354.129 -> of your let's say 50 servers exceeding safety person

3357.8 -> so you can trigger an alarm

3359.8 -> so that Can notify we will also you get introduced automation

3364.438 -> by using this Salam

3365.9 -> where and you can add more resources to it.

3368.1 -> Also additionally

3369.1 -> in auto-scaling alarms play a very important role.

3378.7 -> So today we have gathered to discuss on Amazon ec2.

3382.491 -> So the main agenda for this entire session

3385.6 -> will be will be discussing on what exactly easy to is

3389.2 -> how how it is.

3390.3 -> Structure and how we can get started on using ec2 as a as one

3394.915 -> of the main services offered by AWS as a as a part

3399.8 -> of elastic Cloud compute

3401.6 -> and then we'll be having a quick understanding

3404.3 -> of what exactly is.

3405.771 -> Am I as an Amazon machine image

3408.3 -> how to define the security groups keep ears

3411.127 -> and didn't see what is the main difference

3414 -> between elastic IP

3415.3 -> and public IP

3416.4 -> and different types of ec2 Boss configurations available.

3420.3 -> And what are different database server services available and

3424.218 -> how we can optimize the costing in ec2?

3426.7 -> That will be our main agenda

3428.668 -> for this entire session today itself.

3432.4 -> Let's get started

3433.515 -> on our discussion on ec2 as an elastic Cloud compute.

3436.9 -> So easy to is a web service

3438.564 -> that provides servers in the cloud

3440.578 -> which are customized as per the requirement.

3443.174 -> So when as we know

3444.317 -> if we want to deploy any particular application,

3447.268 -> they are two ways, or of it.

3449.025 -> We can deploy the application in two ways.

3452.8 -> We can either buy our own servers we

3455.6 -> can buy a stack of servers

3457.522 -> and then we have to perform all the the entire solution

3461.613 -> of all the insults the operating system.

3464.473 -> The network drivers is the colonel everything

3467.7 -> that we have along with the entire databases.

3470.359 -> Everything has to be done at our own ain't right

3473.5 -> or we can use the services already deployed over Cloud.

3477.5 -> So again here we have already deployed

3479.7 -> and pre-configured server then we can Use the began on top of

3483.307 -> as we can simply deploy applications automatically as

3486.367 -> a part of cloud servers and easy to itself

3489.088 -> is a just like we have we create multiple servers we

3492.1 -> create multiple VMS as

3493.8 -> in virtual machine

3495 -> the same way here we have easy to so these are begin.

3498.3 -> These are again the servers

3499.8 -> that we deploy over the cloud platform

3502 -> and that can be initiated in a couple of minutes

3505.5 -> as compared to Deployment on the under my service.

3510.1 -> So here it can be it can be configured.

3512.759 -> It can be it can be up

3514.3 -> and running in less than 15 minutes.

3516.9 -> That's how fast it is and in here it is highly scalable.

3521.3 -> So now I'm now when we talk about scalability suppose

3523.9 -> if we want to increase the capacity of these servers we

3526.957 -> want to increase the capacity

3528.534 -> of these servers from two cores of ram to 8 cores.

3531.2 -> We want to increase to add more RAM here.

3533.1 -> We want to increase the storage capacity as

3535.2 -> well so we can do that.

3536.615 -> Easily we can do

3537.642 -> that easily using the cloud computing platform as compared

3541.3 -> to the on-premise server, right?

3543.4 -> So that's the main advantage of again going

3546.006 -> for cloud platform as compared to on premises.

3549.9 -> Are the main advantages we get on top of cloud services?

3553.3 -> It is highly scalable.

3554.855 -> Plus it works on pay-as-you-go model.

3557.4 -> So here we don't have to pay any upfront costs

3560.1 -> because as compared to traditional we can say as

3562.968 -> compared to on-premise servers

3564.8 -> because in on-premise servers we have to pay we have to pay

3567.8 -> for setting up the servers.

3569.401 -> We have to pay an upfront amount

3571.302 -> for the infrastructure for the servers

3573.5 -> that will be buying right.

3575.143 -> Whereas the cloud services fish specially

3577.7 -> if you talk about a hour easy to it works

3580.386 -> on a monthly billing cycle.

3582.124 -> So we don't have to pay any upfront costs

3584.702 -> or any fixed costs every month.

3586.681 -> And here we have to pay only for the amount of amount

3590 -> of time we have used for sources

3591.711 -> and the duration for which we have used them.

3595.3 -> That's it mean that's the main advantage

3597.4 -> that we get as a part of ec2 deployment.

3600.6 -> And in terms of ec2

3602.2 -> or again here we have last except scale Computing again.

3605.3 -> It is highly scalable.

3606.7 -> It is highly flexible as well plus again.

3609.7 -> It is scalable.

3610.582 -> That means if you want to add up resources we can do

3613.5 -> that easily as compared to the optimizer was opposed

3616.7 -> if you want to increase the capacity here

3618.75 -> if you want to add more number of servers

3620.8 -> and that is done easily as compared to compromise.

3625.1 -> Now next is be happy.

3626.7 -> Am I we have a mi mi simply

3629 -> Amazon machine image now just to understand this

3632.7 -> in simple layman terms here.

3634.6 -> If we are deploying any virtual machine

3637 -> if we are deploying any virtual image machine,

3639.722 -> we do have to choose

3640.932 -> the operating system right operating system or suppose.

3644.4 -> It's even we are taking backups.

3646.3 -> For example,

3647 -> if you want to take the entire backup

3649.1 -> of our entire system here

3650.82 -> what we do we take a backup which contains not only Li Na

3654.672 -> this backup file suppose if this is a backup,

3657.9 -> then what it contains is it not only contains

3660.488 -> the entire operating system,

3662.1 -> but it also contains all the configuration

3664.671 -> that we have done.

3666.3 -> Right?

3667.1 -> It also contains all the files

3669.017 -> that we that is available on our entire system

3671.896 -> here all the files all the configuration all these settings

3675.626 -> that means entire particular

3677.411 -> system itself is being will be replicated

3680.26 -> if you are using this particular

3683.2 -> Is it is

3683.6 -> this particular snapshot or this particular image

3686 -> that we are currently created right and suppose

3688.5 -> if we create an image out of it,

3690.293 -> right suppose if we create an image

3692.208 -> out of a supposed to say we have a disk image for is oh, right.

3695.7 -> If we share this image to anyone then using this image suppose

3699.961 -> if they have a bland system

3701.784 -> if they have a blank system they can use this image to make

3705.7 -> a copy of whatever is present

3707.439 -> in this a damaged then tie the entire configuration files

3710.9 -> and operating system can be replicated.

3713.4 -> In on their own system using the concept of images,

3716.856 -> right and that's what images so

3719 -> images are now there are some predefined images

3721.7 -> which contains the pre the predefined configurations

3724.8 -> that we can choose to get started with

3726.8 -> like we can choose the windows incense

3728.696 -> and where Windows am I

3730 -> we can choose Ubuntu

3731.3 -> we can choose Debian Centos depending upon our use cases.

3735.452 -> We can choose these predefined images

3737.9 -> that we can simply use to install and setup our VM

3742 -> of against it stall.

3743 -> L've and set up our servers as an easy to that we want on top

3746.8 -> of which we can get started

3748.5 -> and start customizing on top of it.

3750.9 -> Right?

3751.4 -> That is what we mean by am I Amazon machine image?

3754.282 -> Sure.

3755.8 -> Alright next is we have Security Group.

3757.8 -> So security groups is

3758.984 -> when we're deploying servers obviously as a part of server

3762.2 -> as a server will be required to have a connection to as well.

3766 -> Right?

3767.5 -> Because when we're deploying a server,

3769.5 -> we also need to have a connection because suppose

3772.064 -> if we had a private server now

3773.668 -> in order to manipulate in order to work on the server.

3776.523 -> We need to establish

3777.714 -> a connection to the server itself, right?

3781.5 -> So which all pores will be used

3783.7 -> for setting up the connection here TCP ports HTTP https

3787.9 -> or SSL Sports here.

3789.1 -> So visual pores will be used as a part of connection

3792.3 -> that we haven't defined as a part of security group, right?

3797.8 -> So in networking, we have multiple ports.

3800.152 -> So which Port will be using

3801.694 -> for stablishing our connection with the server?

3804.4 -> That is what we Define as a part of Security Group suppose

3807.752 -> if you want this to be a suppose

3809.646 -> if we are using a TCP Port, right?

3811.6 -> And now in TCP we want the we want the axis of this one

3815.4 -> on port 8080 on port 8080.

3818.1 -> Then we can Define this as a part of security group.

3821.1 -> We want to access the server through

3823.7 -> through the HDMI port here.

3825.3 -> Right suppose here.

3826.4 -> We wanted to do to Define this as a part of HTTP so that

3829.8 -> if we type in the IP and the SUV and the HTTP post here again,

3834.705 -> they will be able to allow us the access to the server.

3838.5 -> So whatever Port we whatever port beam.

3841.272 -> Want to add we want the access to we have my own the assets

3845.2 -> from we can Define this as a part of security groups

3848.2 -> in easy to so now let's erase this up.

3851.8 -> Now.

3852.5 -> Let's do one thing now,

3854.2 -> let's move on to our hands on

3856.374 -> so that we can so now we can discuss

3859 -> on each and every topic seeing

3860.5 -> how exactly to get started on top of AWS ec2.

3865.3 -> So now let's log into a console first.

3869.6 -> In case we don't have the account or in KC

3872.1 -> or either we are having the account in both scenarios

3875.5 -> we can use this link as console dot AWS.com.

3881.9 -> So here we can use consoled or database or amazon.com

3885.8 -> which will take us to the login screen

3888 -> where we can start.

3891.2 -> We can where we can start registering for it was in case

3895.078 -> we don't have account yet

3896.659 -> or in case we already have the account

3899 -> then we can login to our portal here using the AWS portal.

3906.4 -> So here we not suppose if you don't know here

3908.6 -> if you don't have the account here,

3910 -> we can click on create

3911.2 -> a new AWS account in case we don't have the account yet.

3915.401 -> We can click on create a new a cc account

3918.8 -> and this will take us to the sign up page

3921.2 -> where we can get started on signing up as a new user just

3924.808 -> like we sign up for other websites.

3927 -> So here we can sign up for a new account here guys.

3930.1 -> And once we move onto the next screen,

3932.5 -> we have to know as a part of successfully.

3934.983 -> Elation of the signup process.

3936.8 -> We also have to pay you also have to add a car card details.

3940.814 -> It can be debated can be good card both

3943.6 -> and it again in order to start

3946.1 -> in order to activate our account for AWS.

3948.7 -> We do need the we do need these details

3951.5 -> and it has a double simply charger or card

3954.746 -> for a nominal fee of one i&r

3956.9 -> that will be reverse as

3958.31 -> well after it has been charged us to validate the car

3961.5 -> that we have added is working fine or not.

3964.9 -> Right so we can use any of a card.

3967.358 -> It is in order to enter this in and to that in AWS

3971.008 -> and get started.

3975.4 -> So here once we have the account created we can login

3978.8 -> to our console.

3980.58 -> Let's go right back.

3990.63 -> Here we can enter our credentials.

4000.2 -> Just a moment guys.

4001.305 -> We just said be setting of The MFE again

4003.6 -> because the again there's as a part of the of making sure

4006.9 -> the entire account is set up properly.

4009.42 -> We do need to enter we did we do need to set up the MFA

4013.055 -> or just a moment.

4014.8 -> Now once we log in to either

4016.4 -> because this will be our home dashboard that we

4018.7 -> will be looking at.

4019.811 -> So this is a home dashboard

4021.4 -> on which we can get started the in here we can find

4025.072 -> in here we have done in order to start with ec2.

4027.865 -> We have to search for the service called as ec2

4030.6 -> or we can use a search tab to find for any flu find

4033.9 -> any services on top of AWS

4036.2 -> because AWS as we know is a collection

4038.78 -> of more than 90 plus Services ranging from computation

4042.942 -> to management and governance.

4045 -> Services database analytics Media Services mobile a are iot.

4051.3 -> So these are all different services in total

4053.953 -> of more than 90 plus services offered by A diversity

4057.5 -> of so here we had to start with ec2.

4060.1 -> So here we can simply select ec2 here and this will show the list

4064.4 -> of all the active Services into our account.

4068.1 -> So that is open up.

4069.168 -> So as you can see a kanay any

4070.8 -> in order to start creating the instances,

4072.8 -> we have to click on this option,

4074.7 -> which says running

4075.927 -> in sensor years using this we can we can go ahead

4079.2 -> and we can go to the incense

4081.3 -> that is currently being deployed.

4083.2 -> There is currently being of recurrently up

4085.425 -> and running into our account.

4087.1 -> And again,

4087.7 -> if you want to get started on creation of a new instance,

4090.95 -> we can click

4091.65 -> on launch instance available on the table option here.

4094.919 -> We have launch instance.

4096.4 -> Let's click on it.

4099.2 -> Now as a father just like we deploy just

4101.8 -> like we create

4103.269 -> any virtual machine using the VK a secret any VM.

4106.8 -> First of all,

4107.684 -> we have to choose the base image as an Amazon machine image.

4111.7 -> Am I so they are

4112.9 -> multiple predefined Ami is available as a part

4116.242 -> of our a divorce account.

4118.1 -> So the so that we don't have to worry

4120.917 -> about using our own am I

4122.8 -> so we can use these as a base Ami

4125.261 -> we can say we can use these as a as a base.

4129 -> Application also gives a base operating system

4131.3 -> and configuration on top of which we can get started

4134.7 -> on deploying our own application on top of these.

4137.8 -> So here we can choose from simple Amazon Linux server.

4141.5 -> We can choose red hat Sue's or 1/2 server.

4145.1 -> Again.

4145.782 -> We can also choose multiple instances

4148.1 -> of Windows servers Ubuntu again,

4150.3 -> there are multiple a why is it from which we can choose

4153.5 -> and get started?

4155.2 -> Right so we can choose any of these am I here now as a part

4159.6 -> of a handsome will be choosing the Ubuntu Server.

4162 -> Am I we can click on select Now in here in this screen,

4168.1 -> we have to choose the instance type

4170.1 -> and you say and since time we simply mean the server type

4173.2 -> that means water is that configuration?

4175.1 -> We are looking for in order to deploy this entire server here.

4178.8 -> So as you can see currently we have died here.

4181.9 -> We have t to micro selected as a part of a new AWS account.

4187.058 -> We get selective services

4189.023 -> that we can use under limitation for free.

4192.5 -> Right, so they add some see as a new account.

4195.127 -> If you register for a new account on AWS.

4197.599 -> Then we are given a Selective Service couple of services

4201 -> that we can use for free under certain limitations right

4205.385 -> where T2 micro is all is one of those free services and

4209.2 -> as you can see are currently we can see the list of the name

4212 -> of all these different Services as an instances

4214.7 -> and how many cores of see could they have

4217.4 -> how much of gram

4218.439 -> of ram they have again these different storage side

4221.634 -> that they are.

4222.447 -> As a part of this entire deployment here.

4227.1 -> Suppose we want one core

4228.8 -> of CPU and Vivant 1GB of ram we've or we

4232.1 -> if we want suppose if we want the 48 goes of CPU V

4235.869 -> and we 192 MB of ram we can choose again again.

4239.407 -> We want to 900 Emmys.

4242.691 -> MV SSD is as a part of the storage options here.

4246.4 -> Then we can choose these accordingly.

4248.7 -> So depending upon our depending

4251.042 -> upon our configuration the cost will also change accordingly

4255.3 -> because the higher the amount of resources we use the

4257.9 -> higher the the building would be because again,

4260.773 -> these resources will be expensive and

4262.8 -> that's why we have to pay a high amount of money

4265.7 -> as compared to as compared to the lower

4269.5 -> of against a low resources as in 1GB of RAM and 1/4 of CPU.

4275.6 -> So as I example here,

4276.989 -> we want to deploy the application on a free account

4280.137 -> here having one score of CPU

4281.9 -> and 1GB of ram we can click on configure and sense detail.

4287.3 -> So here we can choose the T to Mike road.

4289.5 -> Now next is we have to click

4291.324 -> on next configure instance Z tail here.

4293.8 -> We can choose the incident number

4295.623 -> of instances animals Harmony instance.

4297.729 -> We mounted it right here.

4299.241 -> We cannot hear this part is mainly focus

4301.6 -> on the networking suppose.

4303.474 -> If we want to create our own own bpc.

4305.986 -> We wanted to create this

4307.694 -> on our own bpc own virtual private Cloud here,

4310.894 -> then we can deploy this easily.

4314.5 -> I know in this party.

4315.9 -> I will be focusing

4316.958 -> once we start our discussion on BBC itself so we can leave this

4320.2 -> as it is for by default.

4321.8 -> Next is here.

4322.69 -> We can add storage as and how what is this

4325.5 -> what it means in server.

4327.2 -> We also need to work on servers,

4329.186 -> right and what kind of storage we will need

4331.793 -> in order to deploy the server instance here

4334.4 -> that we had a defined as a part of As a part

4337.7 -> of storage services.

4338.8 -> So here we can Define

4340.1 -> how much of space we require for this entire V and

4342.9 -> that we're trying to create here we want to do use

4345.962 -> we want to use a GB of storage.

4347.9 -> We want to use 10 GB of storage you want to use hundreds maybe

4351.488 -> thousands GB depending upon a use case suppose.

4354.274 -> He wanted to deploy this with 15 GB of storage

4357.2 -> and here we can in here we can choose a so each type.

4360.4 -> We mainly use general-purpose SSD for 4.

4364.7 -> People can be conceived out of balance.

4367 -> for a balanced Okay, baby from someone.

4374.1 -> Yeah, so basically we

4375.3 -> use we use different purpose SEC for a balanced performance

4378.2 -> where we can get good performance as compared

4380.5 -> to other storage devices

4382.307 -> because ssds are generally faster in read and write access

4386.6 -> and read and write speed as compared to other services right

4390.1 -> so here we can choose here we can choose general purpose SSG

4394.3 -> and then we can choose the pro version iops specially

4397.6 -> when we have any data center application

4400.063 -> if you have any database applications,

4402.4 -> then we can choose Or we can say provision iops

4406.6 -> and then in terms of any cold storage

4408.63 -> if you are using this and just as a backup,

4411 -> we are not using this for an active insulation.

4414.27 -> Then we can go ahead and use magnetic.

4416.9 -> So for our hands on here, we'll be using general purpose.

4422.3 -> Then we can send and in here.

4424.5 -> Once we are storag then in here we can add tasks we can leave

4428.677 -> this blank for now.

4430.3 -> And then we can you find Security Group.

4432.5 -> If we are not out by default.

4434.5 -> We will be trying to access this via SSH portal.

4438.8 -> And now if you want to add to access this instance

4441.894 -> This Server also suppose

4443.484 -> if we are deploying a website then website

4446.2 -> will be open up using the HTTP HTTP host itself.

4449.9 -> Try HTTP or https, right?

4452.5 -> So if you are deploying a website,

4454.3 -> then we have to do to choose the HTTP and https.

4458.9 -> Ports as a part of as a part of protocol as a part

4462.1 -> of security group that we have discussed.

4464.6 -> So here we can click on review and launch.

4467.7 -> Once we are done we can launch it and as a part

4470.949 -> of configuration followed by AWS each and every

4474.2 -> and senses highly secured using the concept of of encryption.

4479.5 -> So the entire data available on the server

4482.2 -> that we deployed here is highly encrypted and for and

4486.1 -> if you are trying to access this

4487.65 -> if you are trying to make Changes to the store

4490.2 -> doesn't sense then.

4491.5 -> We have to we have to use the key that means until

4495 -> unless we have the key that has

4497.015 -> that that we has been generated by it 'll burst we

4500.2 -> won't be allowed to connect to the instance.

4502.508 -> We won't be allowed to do any changes on these sense

4505.211 -> until unless we have the right key selected

4507.541 -> and deployed here.

4510.6 -> Right.

4511.1 -> So here we can simply here.

4512.8 -> If you want we can go ahead and create a new key pair.

4516.5 -> We can click on create a new key pair suppose.

4519.1 -> We want to name this as now 21,

4521.4 -> we can create a new KP here.

4523.5 -> We can download this keep here and click on launch instance.

4527.7 -> Now remember to save this keep a

4529.583 -> that is downloaded as a format of in the format of dot p.m.

4532.9 -> Because we will be needing this this key file

4535.502 -> in order to connect to this

4537.1 -> into this instance without which

4539.2 -> he won't be allowed to Says so without this key

4542.2 -> that we are currently downloaded.

4543.8 -> We won't be allowed the access

4545.3 -> in any case so we have to make sure

4547.3 -> that we do end up

4549.5 -> saving this entire authentication code itself.

4556.1 -> And once we are done,

4557.488 -> we can simply click on view in sensors.

4566.2 -> So as you can see now we have the incense up

4568.5 -> and running here, right?

4570.4 -> So now here we can now once we have the put dog.

4573.2 -> Let's see how we can connect

4574.635 -> to the instance that we have currently deployed here.

4577.4 -> So here we can simply go ahead and open up pretty first

4580.8 -> of all we do now if you are using for TV2,

4584.6 -> first of all,

4585.599 -> we do need to convert that out p.m. File as a this is

4589.443 -> what a simple key

4590.7 -> that we have collected downloaded which we will need

4593.552 -> in order to connect to this instance, right so

4596.273 -> To fall in order to use it with Petit we have to convert

4599.6 -> this dot p.m. File to dot P PK as pretty public key

4603.8 -> because put he needs pbk five key files

4606.8 -> and not PPK format.

4608.261 -> Not m dot P so here for converting dot p.m.

4612 -> And into dot P PK,

4613.4 -> we can simply use a tool called last call last footage

4616.6 -> and Dot exe,

4617.7 -> which we can download which we can download

4620.5 -> from the link that I have shared with everyone.

4623.1 -> So here we can download pretty dot exe and for

4626.3 -> regen dot exe as well.

4628 -> Right?

4628.592 -> So here we can use we can open up region dot exe

4632.78 -> and here we have to click on load.

4636.3 -> Once you click on load here here we have to go to the folder

4639.7 -> where we have downloaded the current key file

4643.4 -> in dot p.m. Format.

4646.3 -> So if we choose all files in downloads

4650.479 -> if we search for DOT bem we can now this is a key that we

4654.8 -> have currently downloaded.

4656.3 -> The director that we have currently used for the instance

4659.1 -> that we have currently deployed here right for this instance.

4663.1 -> So now what we can do we can simply go ahead

4665.4 -> and open this up click on open.

4668.7 -> And now we have to click on save Private key.

4673.292 -> And let's save this on desktop

4675.6 -> with the same name as love 21 dot PPK we can save it up.

4681.8 -> Now must we have saved the key as dot PPK.

4684.518 -> We don't we no longer need this case

4686.839 -> so we can close it.

4688.7 -> And now we can open up pretty dot exe.

4691.6 -> We can open up for E dot exe.

4694.2 -> Now.

4694.451 -> Once we have converted the key here,

4696.622 -> then we can simply open a pretty dot exe

4699.04 -> where first of all we have to enter the in order to connect.

4702.5 -> First of all here.

4703.4 -> We have to enter the hostname

4705.471 -> so we can enter so now we can enter both the public DNS

4709.328 -> or public ipv4.

4710.4 -> We can under both we can copy this.

4716.4 -> We can cope with this on the Hosiery over IP address.

4719 -> We can enter this IP port name vote novel regular the remain

4723.542 -> as it is as 422 then under connection.

4726.4 -> We have data so under data,

4728.414 -> we have to enter something as Ubuntu.

4731.8 -> And under one to the under SSH here.

4734.223 -> We have two here.

4735.383 -> We can expand SSH and under oath.

4737.8 -> We can Define the key

4739.1 -> that we are currently trying to create here.

4741.6 -> So we have we can use a key that we have currently converted.

4744.9 -> That is November 21 dot PPK we can open this up.

4749.1 -> And now if you don't want to do the same step each

4752.2 -> and every time we are trying to connect to the instance,

4755 -> then you can save this as a profile.

4757.1 -> So let's name this as now pretty one itself.

4760.261 -> Let's save it.

4761.5 -> And now if we double-click here,

4763.305 -> we would be either credentials are correct

4765.52 -> if the key that we have chosen is correct.

4767.894 -> We would be able to log into the instance here.

4771.5 -> As you can see now we have got the access to the incense

4774.535 -> and now we can start communicating and as a part

4777.3 -> of CLI as a part of CLI,

4780.3 -> let's improve let's increase the font size

4783.1 -> as we don't want the to strain our eyes here.

4786.5 -> Let's increase the font size.

4791.9 -> That's how we can get started

4793.8 -> and get connected on top of easy to now

4796.3 -> once we have the connection we can start manipulating

4798.9 -> ec2 service exactly as per our requirement.

4801.7 -> So in here we can now

4803.1 -> if you want on this works like a simple shell scripting, right?

4807 -> So if we are clear

4807.926 -> if we are comfortable with shell scripting this works just

4810.859 -> like a shell scripting here.

4813.5 -> So in here we can out in order to get the complete access we

4817.4 -> can convert ourselves to the root user using sudo SU.

4822 -> If in case,

4822.8 -> we have chosen the default Linux environment,

4825.5 -> then we could have chosen Jam right around here

4828.505 -> since we are in essence.

4829.986 -> We are interacting with Ubuntu.

4831.946 -> So then we can start using all the Sudoku bonds.

4834.71 -> Right?

4835.8 -> So the first double here we have converted our son

4838.1 -> to the root user.

4839.132 -> We can clear this all out and then suppose

4842.556 -> if you want to update

4843.9 -> or three sing all the services we can use apt-get update.

4848.9 -> Each and every packages will be updated.

4856.4 -> Suppose if you want to install a party tools,

4859.2 -> we can simply go any gaped head install apache2.

4869.9 -> So here we can simply

4871.4 -> as join and set up the party to here.

4873.714 -> So once we are done,

4875.1 -> so since we have also chosen HTTP Port as well

4878.1 -> for this entire instance, right?

4879.7 -> So once we are done installing a party to

4882.398 -> if we open the same IP into the web browser,

4885.3 -> we would be able to see the default

4887.9 -> apache2 default apart Etude.

4891.3 -> Page being opened up in the browser.

4894.6 -> So let's wait

4895.6 -> for this entire instance to be executed.

4901 -> This which may take a couple of seconds.

4904.5 -> As you can see now this entire setup is done.

4906.9 -> Sophie come back

4908.054 -> if we copy the public IP here if you copy this

4911.3 -> and and face this and browser as you can see here,

4915.6 -> since we are since we are done with insulation

4918.599 -> of Apache server now,

4920 -> we can see the Apache to Ubuntu default page being opened up

4923.7 -> in the browser in the instance in the ec2 instance

4926.828 -> that we have quality deployed here.

4929.6 -> And that's how we can start manipulating it.

4931.8 -> That's how we can start working on top of it.

4934.1 -> Right?

4935.2 -> Let's also discuss shortly

4937.143 -> on top of the IP address is basically now basically

4940.9 -> what we have is in AWS,

4942.8 -> we have something as public and elastic IPS were

4946.6 -> so we also have something as public elastic IP.

4950.4 -> So when we are deployed when we deploy ec2 instance

4953.8 -> where we Harvest as you can see here,

4955.6 -> we have VIP being

4956.6 -> as automatically assigned to the instance

4958.6 -> that we have currently created.

4960.1 -> Right but this IP suppose if we'd know if you want

4963.5 -> if you no longer need this and senses,

4965.9 -> we can simply click on actions

4967.899 -> in state and then we can terminate these as well.

4971.1 -> When we say terminal that means we are simply killing

4973.8 -> of the servers that means we cannot restart this

4976.702 -> if we have killed her

4977.829 -> if we have stopped this if you have terminated That's right.

4981.4 -> If we stop if we stop their services,

4983.996 -> then we can restart them.

4985.8 -> But again, if you terminate them then again these

4988.7 -> and that servers you have will be terminated

4991.387 -> as I think we have to terminate at it.

4993.9 -> So here once you click on launch or the instance

4996.8 -> if we choose to launch another instance here click

5000.4 -> on select review and launch.

5012.5 -> Against these two have been terminated.

5020.1 -> Let's remove these.

5028 -> Now we have one instance up and running here.

5029.8 -> So as you can see curly this IP address

5031.7 -> has automatically been assigned to this instance.

5034.2 -> Right?

5034.9 -> And now if we suppose if we stop this instance here,

5038.2 -> if you are currently we can no doubt.

5040.5 -> It is one 3.23 2.1 or eight point one three six

5045.3 -> if you stop this and again,

5047.5 -> if you restart the same instance,

5049.6 -> then a new IP will be assigned here.

5051.8 -> So every time we start and stop

5054.1 -> and restart at the service here will be assigned a new.

5057 -> To the servers to the instant

5058.9 -> that we are currently deployed on top of AWS, right?

5062.2 -> And so this entire so this entire public IP that is

5065.9 -> that gets reassigned every time we restart the service.

5069.904 -> This is referred as a public IP.

5072.1 -> This is referred as a public IP in easy to wear

5076.007 -> as if we want suppose if you want to

5078.8 -> if you don't want this is IP to be changed every time we

5082.338 -> are restarting it then we can choose something as elastic IP.

5086.361 -> We can choose.

5087.3 -> Something as elastic IPO.

5089.6 -> So if we click on start here again,

5092.4 -> if we start the instance again

5095.642 -> again a new IP a new IP a new Fresh IP will be assigned here.

5101.5 -> So that's great for a second

5103.338 -> for this fun to be up and running again.

5111.9 -> As you can see here now fresh IP has been assigned

5114.5 -> here and basically the use case for the

5116.879 -> and again and if we do not wish to change we figure out

5120.201 -> if you don't wish to change the

5122.028 -> or have the IP change every time we are starting

5124.8 -> and research starting or stopping the server's starting

5127.676 -> or stopping the instances here,

5129.5 -> then we can use something as elastic IP.

5131.888 -> We can use something else elastic IP here.

5134.4 -> So the main so I will gain a simple use case

5137.227 -> for this one would be suppose.

5139.163 -> We have an office right and and any office

5141.72 -> Or suppose they're using an Enterprise solution now,

5144.9 -> they're using a server solution,

5146.841 -> which is used by the workforce from 9 a.m. In the morning.

5150.9 -> And kindly excuse for this beautiful calligraphy guys.

5154.065 -> That's what happens

5155.2 -> when we try to write using our Mouse pointer, right?

5158.9 -> So again in the office guys again,

5160.549 -> they are they are they are planning to use

5162.69 -> the application from 9 a.m.

5164.1 -> In the morning till 6 p.m.

5165.9 -> And that means from 6 p.m.

5167.9 -> In the morning 6:00 p.m.

5169.6 -> Till next morning 9 a.m.

5171.225 -> The application will not be used right.

5173.8 -> The application will not be used at me is here.

5176.4 -> We are simply wasting 15 hours

5178.48 -> of our work time here I so forth.

5180.7 -> Tina straight doesn't application will not be used

5184.106 -> that means in that servers will not be in use your right.

5188 -> So instead of keeping the server on and adding

5191.4 -> when we should be adding to our billing

5193.4 -> because this works on a pay-as-you-go model

5195.5 -> what we can do we can turn off the we can turn off

5198.151 -> or we can say we can stop the servers

5200.1 -> in this time period right

5201.9 -> but whenever we are stopping it the IP attached to this instance

5206.2 -> that we have currently using your will be changed

5208.8 -> every time we restart them.

5210.734 -> Right supposedly same application is used

5213.469 -> by thousand users.

5214.764 -> Then again.

5215.498 -> We have to reshare a new IP

5217.3 -> to those thousand users everyday becoming an increasing

5220.883 -> that we can see making it a more tedious tasks, right?

5225.2 -> So instead of doing that what we can do

5227 -> we can simply assign something as elastic IP,

5229.4 -> which will remain static which will not get change.

5231.9 -> Even though we stopped the server's right.

5234.016 -> So then in that case,

5235.156 -> even though we have stopped the service again,

5237.6 -> if we restart the IP address

5239.4 -> will not be changed and that exactly is

5242.25 -> what we mean by elastic IP o--

5244.502 -> being one of the use cases and

5246.9 -> now in order to issue a CIP we can simply Google elastic IP.

5251.9 -> We can just we can allocate

5253.632 -> a new one on Obviously lastic IP is a charger

5256.5 -> is a piece a paid service offered by AWS and maybe

5259.8 -> when we say paid Service as dog has that IP,

5263.3 -> does this elastic IP is being used

5265.5 -> we don't have to pay but if we generate

5268.018 -> when I pee and elastic IP and we are not using it

5271.5 -> that means we have not associated that IP

5274.282 -> with any particular instance,

5276.3 -> then we have to pay for the unused elastic IP.

5279.5 -> That's a concept here.

5281.9 -> So here we can just simply click on allocate advances

5285.2 -> IP has been located.

5287.984 -> We can close it.

5289.8 -> And now if you want to associate we can click

5292 -> on associate address.

5293.9 -> We can choose the instance

5295.452 -> that is up and running click on associate.

5298.3 -> And now if we come back if you close it.

5301.7 -> If you come back to instance now,

5304.2 -> even the IP now has been converted into blue,

5306.9 -> right and it means even though we start

5308.8 -> and stop the services this IP will not be changed at all.

5318.4 -> So the main agenda for today's session

5320.5 -> here would be will be discussing on AWS storage services will see

5324.491 -> how what like what exactly is

5326.3 -> or service is offered by a wh what is Amazon S3?

5329.9 -> What do we mean by buckets and objects how we can take care

5333.6 -> of versioning and cross region replication in S3

5336.6 -> how we can take care of transfer acceleration

5339.35 -> and then we'll see the S3 demo

5341.26 -> and it's multiple use cases has a part of our hands on.

5344.7 -> All right.

5345.4 -> First of all, let's get started

5347.478 -> on understanding the social services offered by AWS, right?

5351.377 -> So AWS offers multiple storage Services.

5354 -> The first of all, we have elastic block storage.

5356.6 -> Then we have file storage.

5358.2 -> Then we have Glacier, right?

5359.933 -> So here we are

5360.8 -> multiple storage Services of and then we have storage Gateway

5363.7 -> and then we have S 3 if we switch Gateway

5366.54 -> and then we have S3 right now

5368.6 -> when we talk about block storage now of lessons

5370.969 -> and these one by one

5372.023 -> if we talk about block storage and block storage

5374.5 -> is basically used for For for storing

5377.3 -> of multiple files as a block

5379.505 -> right now block storage is will be obviously.

5383.7 -> Be used in can be used for storing unformatted

5386.4 -> or suppose we can say unprocessed raw data, right?

5389.141 -> We have multiple data set are being stored as

5391.602 -> a complete block right in different regions, right?

5394.4 -> So that's why we can store

5396.048 -> these components as a block right file system are used

5399.407 -> for storing of files that we said.

5401.8 -> Let's suppose here we have now here.

5403.858 -> We have multiple file system

5405.4 -> that we need on a frequent basis, right?

5407.781 -> Then we can use EFS for that.

5409.63 -> Then we can use a face for storing those files

5412.5 -> which can be used which Need on a frequent basis,

5415.928 -> right Glacier is basically a service offered by Amazon

5419.7 -> where Glacier is basically focus on storing archive files try

5423.8 -> that means those files

5425.218 -> which we do not need on a regular basis.

5427.877 -> For example say

5428.9 -> if if a company has has

5431.9 -> records Forest Financial has its Financial records

5435.1 -> for supposed from five years back, right?

5437.417 -> So obviously company doesn't need those five years

5440.3 -> old financial data on a regular basis, correct,

5443.3 -> so that National Data may be required in ears

5446.4 -> or any particular use case, especially

5448.9 -> in multiple years, right?

5450.5 -> That's why the down this kind

5452.2 -> of data does not need to be accessed on a regular basis

5454.9 -> or not even months, right?

5456.6 -> So this can be stored as a part of Glacier service

5459.5 -> where these data can be stored not the cost of storing.

5463 -> These data will be much lower involved

5465.3 -> because these are not access frequently, correct,

5468.63 -> and then we can store them in this was in as a part

5472.1 -> of s as a part of S 3 Glacier all right.

5476.8 -> Now next we have

5477.913 -> storage gateways right now storage gateways are mostly

5481.6 -> used which gateways does switch gateways are mostly used

5484.928 -> for when we are transferring files from an on-premise

5487.987 -> server supposed to say we have on-premise server here, right?

5491.264 -> And now we've now we suppose here.

5493.279 -> We have 50 GB of data

5494.562 -> that needs to be transferred to AWS.

5496.7 -> Right?

5497.3 -> So now instead

5498.6 -> of transferring these files directly to AWS, right?

5502.5 -> So what we do we do

5503.4 -> You have something called a storage Gateway

5505.5 -> in between it's an again the main the main purpose of storage

5509.083 -> Gateway is it simply make sure the data is transferred smoothly

5513.133 -> and without any breaks

5514.5 -> and been uploaded to AWS servers to AWS servers here, right?

5519.3 -> And again here it contains multiple protocols.

5522.32 -> Like we had TCP we have multiple years multiple switches

5525.9 -> and Gates present here so that it makes sure

5528.8 -> that the data is transferred smoothie from on-premise

5531.5 -> to AWS as a part of switch kick.

5534.3 -> All right.

5535.9 -> And S3 is a part

5537.456 -> of the object storage that we have seen earlier correct?

5542 -> Object storage is a part

5543.2 -> of the SPs apart of the objects ways

5545.7 -> where we can store multiple files as a part

5548.2 -> of S3 object as the power

5549.855 -> of S3 storage that will be exploring step by step.

5553.9 -> Alright, so now let's proceed further.

5557.5 -> Now let's understand.

5558.996 -> What exactly is Amazon S3.

5560.848 -> What do we mean by Amazon S3 here?

5563.2 -> Right.

5563.7 -> So S3 has a simple interface

5565.631 -> that we can use to store and drive files of a

5568.665 -> of any size at any time from anywhere, right?

5571.7 -> So whenever we have a modest

5573.3 -> or any kind of file suppose, we want to store documents.

5575.7 -> You want to host a static website.

5577.786 -> We want to store the backups you want to store logs.

5581.1 -> So all of these things can be stored inside S3 bucket

5584.5 -> inside Amazon S3 storage right now

5587 -> when we talk about What S 3 S 3 simply now

5589.8 -> as we simply means simple storage service S3s

5593.546 -> what simple storage service simple storage service cell

5597.7 -> service offered by AWS, right?

5600.7 -> So it contains three it so it contains 3 S

5603.6 -> and that's why it has been abbreviated to S3.

5606.856 -> Right?

5607.3 -> So this area 3s here and that's why we call

5610.1 -> it as Amazon S3 storage simple storage service.

5615.7 -> Right.

5616.3 -> So now S3 is can be used

5618 -> as we can be used for storing any kind of data.

5620.4 -> It can be used for storing any kind of data.

5622.6 -> It is more durable.

5623.829 -> It is flexible.

5624.8 -> We can have in our vehicles

5626.382 -> always available at any given point of time durable as

5629.5 -> in because here we can encrypt the data

5631.7 -> and make sure our data security is intact flexible

5634.898 -> because we can scale up

5636.2 -> and scale down the resource exactly as we require

5638.6 -> but exactly as required,

5640.285 -> right and we can access the data anywhere

5642.979 -> from any time it is available.

5645 -> It is at that.

5645.827 -> As we can access this data at any point of time.

5648.591 -> So there is no restriction on the retrieval

5650.759 -> and storage of data

5651.919 -> that can be done at any point of time.

5654.2 -> Right?

5654.6 -> It is cause efficient that means obviously

5656.8 -> as compared to other providers for the for the block

5659.7 -> so it is much cost efficient as compared to the other one

5662.7 -> free then it is highly scalable as well.

5665.2 -> It cannot we can it can meet the requirement for us suppose.

5668.773 -> If we want to scale up the resources.

5670.618 -> If you want to scale down

5671.9 -> that means if you want to increase the storage

5674.1 -> or decrease then we can do that.

5675.9 -> Easily using S3,

5677.5 -> right again is more secure because of multiple encryption

5681.3 -> methods already put in place as a part of S3 storage.

5685.569 -> All right now in S3, we have multiple classes.

5689.288 -> We have standard infrequent axis and Glacier, right?

5693.211 -> For example.

5693.917 -> Now, let's understand this in a much better way and for

5697.093 -> understanding this let's go back.

5698.9 -> Let's move to our Picasso mode.

5701.4 -> Let's move to our Picasso mode here now in storage.

5705.6 -> We have three classes in storage options.

5708.167 -> We have three glasses here.

5711.1 -> We have standard we have in frequent access Scholars IA.

5716.489 -> And then we have Glacier, right?

5719 -> So standard in in standard class

5721.4 -> what we do we store all the files

5723.335 -> which we reach we require on a frequent basis

5726 -> on a frequent basis,

5727.282 -> right for example is opposed

5729.122 -> when we are now suppose if we have a website,

5732.038 -> right if we have a website now in their website,

5735.738 -> we are showcasing the gallery of the recent event.

5738.956 -> We are showcasing a gallery of the An adventure right

5742.351 -> now these files needs to be access needs.

5744.868 -> These files are needs to be shown to the users

5747.7 -> who are on the website on a regular basis, right?

5750.247 -> Since these are recent files.

5751.953 -> That means not now week what we can do in the website.

5754.8 -> We can store all

5755.7 -> of these images as a part of standard class in S3,

5758.849 -> right as a part of standard class in S3,

5761.3 -> right because this needs to be accessed

5763.6 -> these needs to be accessed on a frequent basis.

5766.1 -> That's why we can store this in standard

5768.4 -> because in standard the data can be A fish quickly

5771.9 -> because it is available 99.99% Right?

5775.3 -> So the availability of these standard are really high

5778.593 -> and it can be fetched within milliseconds

5781.067 -> within milliseconds as well.

5782.8 -> So if we need if we do need to access these files,

5785.425 -> it can be fished in milliseconds and these are highly available.

5789 -> Right so all those files and this can be PDF documents

5791.957 -> is can be static files.

5793.247 -> This can be any kind of file and there is

5795.422 -> no limitation as well that we

5797 -> there is no limitation in terms of the file

5799.1 -> that we can store the power of s and Right

5802.2 -> and we can understand it we can store files

5804.745 -> as low as so there is no minimum requirement as

5807.519 -> whether that means we need to have files only

5810.296 -> for suppose 1 MB ourselves.

5812 -> Also, we can store files as low as 1 KP as well.

5816.1 -> Right so you can store files as as small as one key be as well,

5820.3 -> right and all those frequent files.

5822.5 -> If you do in there that we need on a regular basis

5825.2 -> that can be stored as a part of standard class.

5828.3 -> All right.

5829.3 -> Now next is we have In frequent access next

5831.9 -> is we have in frequent access, right?

5834.163 -> So in in frequent access

5835.74 -> what we do we simply store those kind of files

5839 -> which we do not need frequently.

5841.227 -> But if we need frequently then it can be fetched

5844.7 -> at a then you can we fetch quickly right?

5847.7 -> For example suppose here.

5849.038 -> We are stored in on let's take the same example

5851.5 -> for gallery right now.

5853.3 -> This Gallery is for 2019.

5855.8 -> So obviously this will be required to to be

5857.9 -> fish frequently more frequently than any other.

5861.1 -> glasses, right

5862.5 -> And he's supposed to have you have a gallery

5864.8 -> for 2018 or 2018 or 17 right or 17 here.

5870.8 -> Now again, we have the images here stored.

5873.393 -> Correct.

5873.897 -> Now these images are not that in you

5876.192 -> or not that much induce

5877.7 -> or they're not requested as high as 2019 correct.

5881.5 -> So what we can do we can store these as a part

5884.072 -> of infrequent access

5885.3 -> so that this can be stored in a separate class

5888.023 -> for infrequent taxes right now.

5889.927 -> This will not be not the availability.

5892.2 -> Thirty of these of these images will be 99.9% Right?

5896.2 -> Not 9 9 but 9 percent right,

5898.661 -> but whenever we require to whenever we need

5901.892 -> to access these images we can again we can fetch them easily

5906.3 -> by using millisecond here.

5908.119 -> Right?

5908.572 -> So this can help us in again

5910.622 -> making entire storage more structured, right?

5913.8 -> So these are not available as high as as

5916.693 -> frequently as standard,

5918.357 -> but in any case if we do need to fetch these data.

5921.9 -> That can be done as quickly as possible as well.

5924.9 -> All right,

5925.5 -> and all of those five which are not required frequently,

5927.7 -> we can store this as a part of infrequent access here.

5930.7 -> All right now

5931.8 -> and there is a limitation also available guys.

5934.078 -> So in standard we there

5935.3 -> is no minimum duration for which we want to store the file,

5938.2 -> which we need to show the file

5939.6 -> for we can store the file for suppose

5941.571 -> for one minute and then we can remove it as well.

5944.4 -> Right but infrequent a says there is a requirement

5947.8 -> that means in which if we move the files to infrequent

5950.8 -> axis then we Have to keep the file

5952.977 -> in if we can access as these for 30 days at least for 30 days,

5957.299 -> right?

5957.679 -> That means we can fetch the files we can do that,

5960.503 -> but we cannot remove the files.

5962.164 -> Once we have moved them do infrequent like says at least

5965.4 -> for 30 days, right?

5966.7 -> So that's that mediation for infrequent axis.

5969.796 -> So now let's move to Glacier now in Glacier.

5973.5 -> Let's say if you go back to Glacier here now

5976.5 -> in Glacier we can now let's suppose here.

5978.988 -> We have some files or suppose if we have the files.

5982.1 -> Now you may have seen this also in our practical example.

5985.8 -> Now if we want to download

5987.7 -> our entire historical data from Facebook from Facebook, right?

5992.2 -> If you don't do download our entire history for on Google

5996.2 -> on Google fright right from Google self, right,

5999.2 -> then it now then it now even if we request the access

6002.6 -> of our off for downloading entire historical data,

6005.662 -> it simply says,

6006.6 -> okay, we are preparing your entire historical data

6009.3 -> and it will be available within next few hours, right?

6012.174 -> Right.

6012.5 -> So now what happens not since these data

6015.001 -> are not required on a regular basis.

6017.059 -> So what we can do we can store this as a part

6019.4 -> of Glacier as a part of Glacier service right there.

6022.5 -> We do not need to finish these data

6024.5 -> on a regular basis, right?

6026.2 -> And that's why

6026.9 -> if now we can store this as a part of Glacier right

6030 -> so that when we move something to Crazy obviously here we

6033.4 -> can store files on on like on a bigger volume,

6036.2 -> but the access will be much lower.

6038.2 -> For example,

6038.852 -> if you want to fetch something from Glacier we have It at least

6042.7 -> for four hours or four hours

6044.7 -> as the is it really is

6046.4 -> a normal waiting period for the for fetching

6049.477 -> and files from firm pressure back to our own storage.

6053.2 -> Right and there is a minimum duration for 90 days.

6057.1 -> That means we have if we move any files for Glacier service,

6060.216 -> then we have to store them at least for 90 days,

6062.7 -> right and again,

6064.553 -> although we can increase

6066.4 -> increase the speed of fetching the data.

6068.3 -> But again, we have to pay for that particular.

6071.8 -> Each right we have to pay extra for increased

6074 -> by increasing the speed of fishing process,

6076.5 -> right and here again,

6077.93 -> we cannot store the files lower than any standard

6081.3 -> we can now we had seen we can store files as low as as

6084.7 -> small as 1 KB current.

6086.2 -> But again, they have we have storage

6088.347 -> via a we have limitations on the file storage as well.

6091.6 -> Right and here they are

6093.6 -> they are additional fees for every table here.

6096.279 -> For example here we have to pay fees for a GB

6098.9 -> of free travel right suppose.

6100.421 -> They say we are retrieving data.

6102.1 -> I suppose 5gb, right then.

6103.664 -> There's a price attached to per GB of data

6106.2 -> that we can retrieve from the glacier and as well as

6109.4 -> from infrequent access.

6111.4 -> All right.

6113.7 -> Alright, so now let's remove our kindergarten drawing here.

6117.2 -> It's look like a Kindergarten kid had drawn something.

6120.615 -> So now let's remove this and let's get right back.

6125.7 -> And as you can see in here now the durability the each

6129.2 -> and every service is highly durable,

6131.619 -> but in terms of availability here,

6133.7 -> it is available.

6134.5 -> 99.99% of time here is the infrequent access is

6138 -> available idea and put nine percent of time

6140.352 -> and Glacier is not available

6142 -> because here we have to fetch here.

6144.1 -> We have to manually request the retrieval of data.

6146.982 -> That's why it is not available right now.

6149.335 -> Here we there is no limit on the in standard days.

6152.1 -> No limit on the minimum amount

6153.938 -> of size of file that we can have.

6156 -> And if you can access we need to have fights as

6158.9 -> at least for 128kb,

6160.412 -> right and there's no limit for Glacier as well

6164.1 -> say maybe in terms of minimum storage duration.

6166.787 -> There is no minimum period required for standard whereas

6169.884 -> for in frequently required to store the file status

6172.7 -> for 30 days and English.

6174.7 -> We need to store them at least for 90 days,

6177.3 -> right and again first bite latency

6179.5 -> that means in case we are trying to try the files.

6182.6 -> It can be fetched in milliseconds, right

6185.3 -> and Infrequent as standard

6187.2 -> but in a Chevy it is at least for us,

6190.1 -> right and there is no travel fee for standard.

6193.016 -> But there is a travel fee per GB for infrequent and for Glacier.

6197.6 -> All right.

6199.423 -> Now, let's discuss on buckets and objects.

6203.5 -> Right.

6204.5 -> So in S3 what we have here,

6207 -> we have multiple concepts of buckets,

6209.769 -> right so bucket is

6211.2 -> simply we can say a storage bucket of storage bucket

6214.1 -> right babies to have multiple multiple objects

6217.058 -> with their metadata

6218.247 -> with the metadata as a part of bucket, right?

6221 -> So for examples of now here we can create multiple buckets.

6224.082 -> For example here we can create multiple buckets here, right?

6227.553 -> So bucket we can say we can say it was like a container

6230.6 -> for bucket here works like a container.

6233.3 -> Go where all the media files for example,

6235.9 -> let's suppose here.

6236.917 -> We have we have we have audio files here.

6239.27 -> We have video files here.

6240.6 -> We have some some PDFs here.

6242.273 -> We have suppose.

6243.246 -> I have any website for the entire HTML file.

6245.884 -> So the website, right?

6247.341 -> So all of these all

6248.566 -> of these are referred as objects here, right?

6251.4 -> So bucket we can say bucket is referred as a container

6254.7 -> which will house all the objects stored

6257.1 -> inside that particular container itself on Insider bucket itself,

6261.7 -> right and N 1 S 3 So

6263.3 -> as we can have multiple containers we can have

6265.784 -> multiple buckets, right?

6267.204 -> So as a limitation here now

6268.793 -> in now one account here is offered hundred buckets.

6271.535 -> That means we in one account we can have hundreds of blockage

6275.064 -> and then we can have 20 buckets defined

6277.454 -> for one region as a part of a free account for AWS.

6280.5 -> Right?

6281.3 -> So here we can have 20 different different buckets

6284.2 -> right stored in ourself in a single region, right

6287.9 -> and then each and every bucket Gaston its own type

6290.867 -> of files right suppose

6292.2 -> and here we can keep I was doing multiple files exactly as

6295.552 -> per our requirement as part of the bucket as a part

6298.2 -> of the budget here,

6299.7 -> right and each and every object will also have its own metadata.

6304.2 -> Now when we say metadata it simply includes all the keys all

6308.3 -> the versions all the like all the title description

6312.1 -> and everything and every kind of mediator is also stored along

6315.9 -> with objects as a part of the bucket here.

6318.9 -> Alright, so bucket here is unlimited and again in

6322.6 -> when we are during any kind of files it cannot be

6325.1 -> greater than 5 TB

6326.138 -> as we have seen you

6327.5 -> so we cannot that means we can have multiple buckets

6330.4 -> with unlimited size, right?

6331.862 -> And again this object

6333 -> that we have showing a for example is suppose here.

6335.2 -> We have a media file right here.

6336.825 -> We have a media file or suppose

6338.4 -> if we are storing a backup rewrite then the backup size

6341.6 -> cannot exceed 5 TB in N total, right?

6345.9 -> So single object cannot be greater than 5 TB

6348.7 -> in total as a part of S35 T be here.

6354 -> So NE WS we have $100

6356.3 -> if you can have a total of hundred buckets,

6358.5 -> whereas in one region in one region,

6361.376 -> we can have 20 buckets,

6363.5 -> right so suppose in one region.

6365.09 -> We have 20 buckets in another region.

6367 -> We have we have five buckets

6368.9 -> in another suppose it other region.

6370.9 -> We have inter region.

6372.4 -> We have eight buckets,

6373.771 -> right so you can if you can distribute them,

6376.3 -> but in total

6377 -> which will not be greater than hundred buckets in total.

6379.812 -> All right.

6381.155 -> Alright, so now let's move forward.

6384.2 -> Now next is we have versioning and cross region replication.

6387.9 -> Okay. First of all,

6388.768 -> let's see before we move to the versioning here.

6391.2 -> Let's see how we can get started as a part of our Hands-On

6395.8 -> on created on creation of multiple buckets

6398.3 -> and objects, right?

6399.6 -> So let's go ahead and do that.

6401.9 -> First of all,

6402.707 -> we need to login to our console for AWS.

6405.127 -> So here we can login to our console.

6407.8 -> It's to it Now for logging into console,

6415.784 -> we can simply type in login console

6418.4 -> dot a tablets.com.

6421.3 -> So here we have the here.

6423.4 -> We have to enter the MFA code for our account.

6426.314 -> Let's enter it now once we log into our area

6429.1 -> plus this will be the dashboard that we will be looking at.

6432 -> So now we can search for now.

6433.6 -> If you can use the search bar we can use the search bar here

6436.9 -> or we can use the search bar available on top as well as

6439.6 -> a power of S 3 right as a part of services.

6442.334 -> So here we can search for service name as S3.

6445.5 -> So here we have S3 service available.

6447.9 -> And now this will take us three simple storage service.

6450.9 -> A sport where we can see the list of all the bucket

6453.54 -> that we already have in place here, right?

6455.795 -> So here we can see we have a list of all the buckets

6458.6 -> that we have already created

6460.182 -> or any case we have no bucket created

6462.123 -> or if you want to create a new bucket,

6464.3 -> then we can simply tap on this option

6466.4 -> which says create bucket, right?

6468.477 -> So let's click on it.

6469.7 -> Now.

6469.904 -> Let's see if the concrete bucket here.

6471.8 -> We first of all here we have to define the bucket name right

6475.2 -> suppose we want to call this bucket as Erica and cept.

6480.3 -> Okay, we'd cannot start the neck pocket team

6482.9 -> with any upper cases, right?

6484.9 -> So here we have any regard September

6487.3 -> so you can write the name as Erica September now,

6490.9 -> we have to choose

6491.914 -> a region in which we are deploying the bucket on

6494.686 -> right now region selection is really important.

6497.4 -> Why because let's see suppose we have a user sitting

6502.505 -> in u.s. Right suppose a user is sitting in us

6506 -> and here we have user sitting in suppose users.

6509.4 -> Who are Based in UK and then we have users

6513.153 -> who are based in suppose in India.

6515.7 -> And then we have users who are based

6518.1 -> and supposing Australia in a you right now suppose

6521.9 -> if we now if we deploy any bucket in u.s.

6524.836 -> Right if you have deployed any S3 bucket end up in u.s.

6528.8 -> Then again, it will be much easier

6530.7 -> for the u.s. Audience to access

6532.87 -> the data using this bucket then accessing the data

6536.5 -> in the in the bucket deployed in UK region, right?

6540 -> So again, if you have to price a bucket in UK region suppose

6543.6 -> on it now us orders can be now they will be able to access the

6547.5 -> about the data stored in the bucket deployed

6550.215 -> and UK region,

6551.1 -> but the the rate

6552.8 -> and the latency will be much higher right

6555.33 -> that means the time duration in which they need to the time

6559.4 -> that ended you need to access the data to store the data

6562.635 -> or to fetch the data will be much higher correct

6565.135 -> and that will slow down the performance correct.

6567.9 -> And that's why they would do it would be much better.

6570.4 -> If they access the data stored in their own region itself try

6574.7 -> same for Australia same for India as well.

6577.9 -> Right?

6578.4 -> So although they can be accessed through

6580.49 -> multiple regions we can do

6582 -> that means users can also access the

6584.1 -> off the data the bucket for Australia us can also ask

6587.447 -> the bucket for India,

6588.8 -> but the performance will be much lower as

6590.8 -> compared to accessing data

6592.56 -> in their own region all together, right?

6595.2 -> So we have to make sure

6596.5 -> that we dip we create the bucket in that region,

6599.456 -> which is close.

6600.338 -> This to our users

6601.307 -> so that they can have a better performance.

6603.7 -> Alright, so now let's learn let's assume Monarch

6606.7 -> or a Hands-On creation of a bucket.

6608.6 -> So first of all,

6609.4 -> we have to go to the S3 service

6611.3 -> in a in AWS console then here we can click on create bucket

6615 -> and now we have to define the bucket name and then we

6617.6 -> had to choose a region

6618.649 -> in which we are trying to deploy the pocket end.

6620.999 -> Right for example suppose.

6622.2 -> We are did not here we can decide we have

6624.051 -> we can choose between any of the regions we can choose

6626.8 -> from Mumbai Islands London.

6628.742 -> So in now in terms of Regions,

6630.9 -> then we had credi one regions deployed globally by a WSB

6634.7 -> in which we can choose from right for example suppose.

6637.8 -> We are different now.

6638.887 -> We are deploying we want to deploy this bucket

6641.364 -> in Mumbai region.

6642.3 -> We can choose Mumbai next we can click on next here.

6650.8 -> We if you want we can again keep the all the settings by default

6654.7 -> now here we can decide

6655.994 -> if we want to block all the public access opposed.

6658.5 -> If you want to make this entire bucket private,

6661.473 -> then we can keep it private or if you want to allow or

6664.9 -> if we want to allow the access to the public for this bucket,

6668.7 -> then we can remove the public access

6671.1 -> from this part right.

6672.9 -> Now. First of all,

6673.876 -> we have now here we can block all public access now

6676.4 -> in this option here,

6677.4 -> we can block the public access to buckets and objects Grand.

6680.6 -> True new Access Control list right now here in a diverse.

6684.2 -> We have we have conceived of ACL right?

6686.435 -> So here we can Define multiple Lacs have again

6688.967 -> if you want

6689.656 -> if you don't want this to be accessed

6691.853 -> through new ACS now we already have may have

6694.473 -> Define multiple Lacs

6695.535 -> before but again in terms of new issues.

6697.688 -> We don't want to do to Define to give the access

6700.3 -> to let me get uncheck then we can check this option,

6703.2 -> right if you want to block the access to bucket

6706.6 -> through any access control any

6708.364 -> of the ACL then we can choose this option.

6710.6 -> All right now and third one is

6712.6 -> if you want to block the access to the bulkhead granted

6715.804 -> through new public bucket policies now

6718 -> here we have multiple policies

6719.5 -> that we could have -

6720.4 -> to any user or any group right suppose if if we want

6724 -> that any new user having a new policy attached

6726.999 -> to them right now.

6728.2 -> We don't want this bucket to be allowed the access

6731.082 -> to those new users and new policies,

6733.242 -> then we can attach it.

6734.549 -> Right and again,

6735.5 -> if you don't want this to be a success

6737.4 -> by any user having any kind

6739.38 -> of public Policies

6740.7 -> for bucket then we can uncheck this one as well.

6744.5 -> Now. Once we are done down here,

6746.1 -> we can review all the settings that we have done for the bucket

6749.206 -> and now click on create bucket.

6752.6 -> So as you can see are now we have the bucket created

6755.6 -> that we had deployed as a part of our S3 bucket, right?

6758.554 -> So here we have the bucket name as a rigger September

6761.5 -> in which we can start uploading files, right?

6765.3 -> We can start adding files to a bucket

6767.2 -> that we have created.

6768.5 -> So now we can click on get started.

6770.8 -> And now we can start adding any files here.

6772.836 -> For example, let's click on ADD file.

6774.5 -> So now we can go ahead and choose any files here.

6777.611 -> Let's do that.

6780.8 -> Okay, let's say we do one thing.

6783.15 -> Let's upload our any of the files

6785.5 -> if you want to upload here.

6787.8 -> Let's suppose here.

6789.179 -> We are trying to upload one particular file.

6792.3 -> If you have a small file that we have which contains

6795.6 -> a small application right the suppose we want to approach.

6798.3 -> This is the zip file here right next

6801.1 -> as we can do we can Define the owner sure

6803.722 -> that means the access

6805.1 -> that we want to Grant to this particular user, right?

6809.7 -> Now here, we have multiple storage classes

6811.779 -> that we had discussed.

6813.073 -> Right?

6813.4 -> So if by default we have standard

6815.449 -> and then we have three levels of infrequent access, right?

6819.1 -> So these are so these are three levels of eight frequent access.

6822.3 -> We have intelligent cheering then we have standard

6824.976 -> and standard I and then we have

6826.739 -> one zone is right

6828 -> and then here we have multiple Glacier service.

6831.6 -> All right, and then we have multiple Glacier service.

6834.2 -> So if you want we can choose

6835.6 -> between any of the classes you have suppose

6837.7 -> if you want to start by standard click on next

6840.542 -> and now we can click on upload.

6843.4 -> As you can see it as soon as we have to download now,

6846.3 -> the file is available as a part of bucket object here, right?

6850.025 -> So same way we can we can again here

6852.2 -> if we want to create multiple folders We can click

6854.8 -> on create folder suppose.

6856.433 -> We want to name this folder as images, right?

6859.308 -> We can Kate we can create images

6861.4 -> click on Save now we have folder for images.

6864.6 -> And now if we want to start adding images here we

6867 -> can do that easily.

6868.227 -> So again, we can click on upload actually going

6871.2 -> to begin click on ADD files and now we can choose the images

6874.535 -> that we want to download here.

6876.3 -> Right?

6876.607 -> Also, we images with that.

6878.089 -> We need to upload here.

6881 -> Okay, let's do one thing.

6882.2 -> Let's upload some pictures just a moment the suppose here.

6885.841 -> We asserted selected these three sample images here.

6889.1 -> We can click on next and now we can we can choose a classes here

6893.2 -> correct as standard and now we can click on upload.

6896.1 -> Right?

6896.6 -> So now what we have now,

6897.6 -> we have these three images available that we can all talk

6900.6 -> and if we as we as we had discussed the object

6904.6 -> that is getting stored here.

6906.1 -> They all have their own complete emitted as well.

6908.944 -> Right?

6909.3 -> So if you click on any of these Of did

6911.207 -> that we have selected here?

6912.6 -> We can find the all the metadata Pizza current sighs

6915.317 -> Keys the versions of source code.

6917.238 -> All of these things are already attached

6919.628 -> to the to the object that we have currently uploaded.

6922.823 -> Right?

6924.5 -> And now if we want to share this part here gave me again

6927.2 -> what we can do we can simply make it public right

6929.828 -> and now we have the link available

6931.551 -> so that now we can share this link with anyone

6933.9 -> and they will be having the access to the image

6935.9 -> that we have currently uploaded

6937.308 -> as you can see.

6938 -> Oh, right.

6939.3 -> So now we can shim shim.

6940.6 -> Please share this link with anyone and now they

6942.663 -> can have the access to the file that we have shared with them.

6945.6 -> All right.

6947.7 -> Now let's do one thing.

6948.9 -> Let's say we upload the files for a sample website

6951.903 -> that we are the example dummy website, right?

6954.7 -> So let's do it and For example,

6958.7 -> let's say we go back to our desktop.

6961.9 -> Now.

6962.1 -> Let's say we have a static website here.

6963.83 -> I suppose we have a static website a static page

6966.3 -> for a record or HTML

6968 -> and we have navigation dot PNG as well.

6970.9 -> And then we have multiple CSS folder

6974.7 -> for it as well that we can click on Open click on next

6978.776 -> and now let's add this

6980.6 -> in the same standard class as a part of the bucket.

6983.377 -> Let's click on upload.

6985.9 -> So as you can see here,

6987.252 -> we have the standard HTML file with a dirty car

6989.9 -> with navigation of PNG of also available right now.

6993 -> Let's do one thing.

6994.1 -> Let's make some changes in this HTML file.

6997.311 -> Let's do this.

6998.45 -> Let's go back to a folder.

7001.1 -> Let's make some changes for this Erica file in our HTML

7004.7 -> as you can see here here.

7006.2 -> We have a simple file, right?

7007.7 -> So here we have dummy website

7009.2 -> that we have created as the power of the are as

7011.9 -> a dummy of sight right

7013.4 -> and now let's suppose We do one thing we

7016.3 -> do make some changes in this file as opposed.

7020 -> Let's say we add another Circle Sav add

7023.1 -> one one thing else that suppose.

7025.561 -> We had any particular paragraph example sample paragraph Right

7035.3 -> feel small change.

7036.7 -> Now. Let's do one thing now.

7038.3 -> Let's upload the file back to our AWS

7040.509 -> to our S3 bucket right again.

7042.289 -> We can click on upload.

7043.5 -> Now as you can see here.

7044.7 -> We have the file already available.

7046.4 -> Now, we have made some changes

7047.9 -> and now we are plotting the same file again,

7050.2 -> right add files again.

7052.5 -> We can say the fire as you can see or not.

7054.4 -> This is currently updated right

7056.714 -> so we can upload this file click on next.

7060.2 -> The same class as standard and now upload.

7064.4 -> Okay.

7065.1 -> Bye this will not work

7066.394 -> because first of all we have missed on enabling

7068.809 -> version first, right?

7069.927 -> So first of all

7070.769 -> before we can maintain versions We do have to make sure

7073.8 -> that we unable versioning in our bucket, right?

7076.9 -> So what are how to do that?

7078.488 -> First of all,

7079.2 -> you have to go to properties now,

7081.23 -> I'm properties we have a w

7082.835 -> we have a we have a property enabled

7084.997 -> you're right.

7085.8 -> So here you have a property named as versioning, right?

7089.1 -> So we have to open this up

7090.724 -> and now here we can click on unable versioning.

7093.43 -> Correct.

7093.944 -> So now if we click

7095.095 -> on label versioning then save now remember

7097.7 -> if we have to enable versioning

7099.582 -> for keeping the record of the versions in this bucket,

7102.8 -> right without this versions will not be maintained.

7105.4 -> All right guys,

7106.4 -> so here we can enable versioning in the properties tab.

7109.9 -> Once we have enabled this now we can come back to overview

7113.9 -> and now let's make the same change again now suppose again.

7116.8 -> If you go back

7118.3 -> if we suppose again another paragraph,

7121.7 -> right we Learning is three storage.

7131.2 -> Justice 3 We save it now.

7135.4 -> Let's go ahead and upload.

7138.726 -> The same file it is currently updated.

7142.225 -> And now click on next we choose the same class

7145.686 -> and now upload.

7148.4 -> Now as you can see another this file has been uploaded

7151.2 -> has been updated right and now

7152.7 -> if we want to see the previous file

7154.44 -> the previous version of the same file that has been

7157 -> that we had uploaded but for seeing

7159 -> that what we can do here we on top,

7160.7 -> we have an option called as versions, right?

7163.1 -> So after we unable version you will be seeing

7165.3 -> this option as a part of our history bucket, right?

7168 -> So to see the previous version we can simply click on show by

7171.4 -> and as you can see here now,

7173.047 -> we had two versions of HTML editor Ricardo testable

7175.8 -> and then we can see this as a version so there

7178.252 -> The latest version and this is a previous version

7180.964 -> that we had uploaded.

7182.6 -> All right.

7183.5 -> Now, let's suppose

7184.657 -> if we have to host a static website at

7186.957 -> what we had to do we have to go to bat here in properties.

7190.5 -> We have to enable something called

7192.4 -> as static website hosting right?

7194.5 -> So we had all this will enable us to host

7196.938 -> any static website again,

7198.539 -> not Dynamic but stomach was static upside

7201.1 -> in S3 bucket, right?

7202.5 -> So here we can click on use this bucket to host a website

7206 -> now here we have two in to define the the index document

7209 -> when you say index document.

7210.4 -> We simply mean the root file

7212.255 -> or we can see the homepage right?

7214.486 -> For example n is 3 bucket.

7216.226 -> We had uploaded 10 files.

7217.9 -> We had a product 10 files are right now suppose.

7220.664 -> We have 10 HTML files now,

7222.1 -> which file will be treated like a homepage right?

7224.95 -> That page has to be defined as an index document.

7227.773 -> Right?

7228.135 -> So currently suppose if you want a record

7230.488 -> or HTML to be treated like a homepage, right?

7233 -> Then we can mention is as

7234.4 -> in this document correct error document is just

7237.4 -> like we have Or pages right suppose and

7239.8 -> if any other hack happens

7241.3 -> and which page should be treated like a 404 page

7243.8 -> then we can Define here currently.

7245.5 -> We don't know we don't have that page created

7247.7 -> that if we would have then we

7249.6 -> could have mentioned this right suppose

7252.307 -> if we if we do to have a page called 404 dot HTML,

7255.8 -> then we could have added this as a at a document right

7259.4 -> and now click on save so now what we have done now,

7262.8 -> we have enabled static website hosting as a third

7265.2 -> of our S3 bucket, right?

7268 -> And now we can combine this with us with another service.

7270.944 -> That is cloudfront.

7272.005 -> So now what we can do,

7273.3 -> we now once we have this one created now,

7276.2 -> we can go back to a versions here now suppose here.

7278.494 -> We have the website here right here.

7280.1 -> We have give side.

7281.8 -> So now if you want to see this subsided live preview

7285.2 -> what we can see here here we had our here

7287.697 -> we can click on if I

7288.65 -> and now we have the static website being deployed.

7291.1 -> Right right as a part

7292.6 -> of S3 storage of as a part of S3 storage sure try And

7298.5 -> if you want to see the again,

7300.4 -> if you want to deploy this

7302.04 -> if you want to deploy this subside using

7304.5 -> a temporary URL offered by Arab Louis,

7307.4 -> then we have another service

7309.25 -> then we have another service

7311.4 -> which is called as cloudfront right?

7316.1 -> So here we can now here we can look for the service name

7319.7 -> as cloudfront as Cloud front here, right?

7324.1 -> So cloudfront is basically a Content delivery Network

7327.2 -> offered by AWS,

7328.208 -> so here let us let us open that and again

7330.9 -> if you want we can click on create distribution

7333.9 -> get started now here we can choose

7336.4 -> the default name now here it

7338.1 -> will be the same now here it will be the bucket

7340.307 -> in that we have created right

7341.8 -> so we have the bucket in as a de rigueur,

7343.8 -> September 3 right

7345.7 -> and now we can now we simply have to choose

7348.1 -> the default bucket name.

7349.3 -> Everything else will remain same we don't have

7351.664 -> to worry about changing these things as we as we

7354.165 -> be discussing these things

7355.7 -> when we start our journey on AWS, right?

7358 -> So once we are done,

7359 -> we can simply scroll down and click

7360.8 -> on create distribution, right?

7363.2 -> So as you can see here,

7364.477 -> it may take some like some time to deploy this

7367.2 -> but once we have this one diploid here,

7369.464 -> right then we'll be getting the the URL as you can see it

7372.8 -> then we'll be getting the domain name

7374.8 -> and whichever now

7375.788 -> if we want to share this

7377.245 -> with anyone we can simply share this domain name

7380.1 -> and this will be hosting our static website.

7384.4 -> Correct.

7385.1 -> So currently this is currently being deployed.

7387.35 -> That's why it is not visible.

7388.682 -> But again,

7389.227 -> once we deploy this this will be our static website

7391.9 -> and this will be opening up the same HTML page

7394.7 -> that we are defined as a static page for a website.

7398.3 -> All right.

7404.8 -> Now our agenda for today's session is we are going to talk

7408.7 -> about the Beanstalk elastic Beanstalk of AWS.

7412.7 -> It's a one of the Service of AWS platform

7416.4 -> which is very much in demand

7418.7 -> and apart from that easy to means were firstly

7422.5 -> the easy to and the next is elastic Beanstalk.

7425.811 -> So what is that what it do?

7428.2 -> So I'm not talk about that now while but yes,

7431.2 -> the elastic Beanstalk is our first agenda.

7434.3 -> We're going to talk about the feature

7436.4 -> of the Beanstalk then component

7438.961 -> of the Beanstalk then architecture

7442.1 -> the Beanstalk and hands.

7444.3 -> Jean how to deploy any application on the Beanstalk.

7448.7 -> So this is our agenda for today's session.

7451.746 -> So let's begin.

7452.9 -> What is Beanstalk?

7454.07 -> Okay, even before jumping to the Beanstalk.

7456.6 -> I want to walk you through a few things

7458.5 -> about the cloud why Cloud why we move to the cloud

7462.7 -> and actually Cloud itself is divided

7465.4 -> into multiple categories.

7467.5 -> That is IES paas and saas Okay, IAS,

7479.5 -> that's it infrastructure as a service paas.

7484.01 -> There's a pass platform as a service.

7487.9 -> Then stash that is for threaten the service.

7492.1 -> So we are having three different categories in which all

7496.594 -> our cloud is divided.

7499.1 -> So in short we can say

7500.9 -> that our Cloud have these three categories.

7504.603 -> Let's talk about that.

7506.296 -> So what is cloud?

7507.6 -> Okay.

7507.866 -> Bye we move to the cloud and what happened

7509.8 -> when we don't have a cloud with us.

7511.9 -> The very first thing is

7513.433 -> that we move to the cloud is with the cloud.

7516.71 -> We can focus more on the business.

7519.3 -> We can focus more on our application side.

7523.5 -> Just a sort of book working on the platform.

7527.4 -> How come basically the major use of cloud.

7530.9 -> Okay, then we don't have a cloud.

7532.9 -> No at that.

7533.736 -> That point we have our on-prem solution.

7536.9 -> If you don't have a cloud then we have our on-premise Solution

7540 -> that's 10 for on promises.

7542.4 -> But now we have the cloud with us.

7544.7 -> So but the benefit of that now the benefit is that is

7547.887 -> that guys just take example simple example

7550.7 -> that you have one website.

7552.7 -> Okay.

7553.5 -> This is a number of users versus time graph.

7559.7 -> number of users versus time graph now when we say

7564.415 -> that we have a number of users.

7566.9 -> So if we talk about a simple website,

7569.9 -> okay in a normal website,

7572.9 -> we have a trend in which users connect with us.

7577.9 -> We Are One proper Trend in which user correct with us

7581.2 -> how come means

7582.6 -> if we talked about like say starting from a place

7589.8 -> where timing is in a morning.

7591.839 -> We are talking about suppose 12 a.m.

7594.3 -> In the morning.

7595.085 -> We'll start with 12 a.m.

7596.496 -> In the morning till the 11 p.m.

7598.206 -> In the night with a complete cycle.

7602.6 -> So at this point of time, we know

7604.2 -> that the traffic at 12 a.m.

7606.3 -> Is bit low,

7607.6 -> right then one am again goes low then so

7614.3 -> as the time will keep on increasing the traffic

7617.838 -> is On decreasing

7619.1 -> till morning around say I should draw graph

7624 -> in different manner rather than wrong -

7626.4 -> just one second.

7627.5 -> Let me draw once again.

7629.7 -> So we'll one axis.

7632.5 -> This is the user and is a time graph.

7635.2 -> Okay.

7636.6 -> Now we start at 12 a.m.

7638.346 -> In the morning in the midnight.

7640.7 -> I'll say Okay.

7643.5 -> Now when that 12 a.m.

7645.7 -> In the morning,

7647 -> the users are very less than 1 a.m. 2 a.m. 3 a.m. 4

7652.6 -> a.m. 5 a.m. 6 a.m.

7655.2 -> Or traffic is quite low on the website.

7658.8 -> Suddenly the 7:00 a.m.

7660.082 -> The traffic start increasing and it keep on increasing

7663.2 -> around the day till the 9 or 10 p.m.

7666.2 -> You traffic is on the highest peak

7668.029 -> and again start decreasing after 10:00 p.m.

7670.5 -> And again come down to the lower point, right?

7674.5 -> So the trend is like that in the in the midnight.

7678.3 -> My traffic is low and the suppose SS 7 p.m.

7681.7 -> In the evening.

7682.8 -> My traffic is quite High 7 to 9 p.m.

7685.5 -> In the evening.

7686.2 -> My traffic is quite High.

7688 -> Now suppose at this place.

7689.8 -> We have a 10K users

7691.5 -> and at this place we have only 1 K users

7693.955 -> at the very lowest point register 1K users.

7697 -> So when I have configure

7698.8 -> when I have to configure my application,

7701.3 -> I have to take this in the scenario

7703.6 -> that how much users can come to my website suppose.

7707.021 -> I will say I am going to manage all my design.

7710.1 -> I'm going to manage all my infrastructure.

7712.7 -> So for that particular place,

7714.8 -> I have to take this thing in mind

7717.2 -> that I can get the 10K users right now

7722.7 -> because I have to imagine

7724.315 -> of at least two more cable set 12K users.

7727 -> I'll set up my infrastructure for 12K users.

7730 -> Although still be having a 10K users.

7733.5 -> Now when the traffic is low

7736 -> like in the other say 3 a.m. Or 4 a.m.

7739.5 -> Whether traffic is low still my capacity is 12K

7743.138 -> only right my capacities 12K,

7746.7 -> but I am getting only 1 K users means

7751.1 -> my 11k capacity is getting waste

7753.7 -> but I cannot do anything.

7755.5 -> I have to manage that why

7757.6 -> because if I'm not manage it sometimes such as only

7760.846 -> traffic increase what I do.

7762.812 -> So in short I have to take a margin and this margin is

7766.916 -> that killing why because the price

7770 -> when you set up this margin,

7771.9 -> obviously the price you're paying for that

7774.592 -> and because of that price.

7777.1 -> Your cost of the project will increase

7779.6 -> and when the course

7780.826 -> of the project will increase ultimately your budget will goes

7784.8 -> out of your budget.

7786.283 -> So basically when we set up our own system,

7789.576 -> they are we have to go with this kind of the problem

7793.5 -> where we have this user management issue

7796.3 -> because we have to set up an infrastructure in that gray.

7800.1 -> Now next thing when we say I'm going on the cloud.

7804.1 -> Okay another time

7805.4 -> when I'm going on the cloud at that point of time.

7808.9 -> I don't have to worry

7810.2 -> because they are I am not the one

7812.212 -> who have to manage the things.

7814.343 -> Okay.

7814.728 -> There are a lot be the one who have to manage the things

7817.7 -> why so because how the cloud work cloud is

7821 -> like a virtual okay cloud is like a virtual

7823.92 -> how virtual suppose tomorrow you want to use a Mac machine.

7828 -> Okay.

7828.326 -> I have a Mac machine.

7829.7 -> Well, you will have to test something on a Mac machine.

7833.3 -> You will say Akash.

7834.5 -> I want to use a Mac machine.

7836.227 -> Give me the excess.

7837.7 -> What I will do I will remote access now

7841.2 -> with that remote access you can use that machine now

7844.6 -> when you can use that machine with the remote access,

7847.3 -> it's my responsibility to provide everything

7849.994 -> to that machine

7850.9 -> means suppose you need an internet.

7853.3 -> I have the one

7854 -> who have to provide the internet to that machine.

7856.4 -> I have to one

7857.2 -> who have to manage the hardware of that machine means

7859.8 -> Now is your side you don't have to worry.

7862.8 -> How come because you are just getting the access

7866.1 -> to that particular system.

7867.8 -> You don't have to worry about how other person

7870.5 -> on the other side things are getting manage.

7872.801 -> How much costing is involved nothing you need to worry

7875.8 -> about you just have to look

7877.4 -> into the your Runner application do the things you don't have

7881.747 -> to work on any part of the consideration.

7884.422 -> You just have to work on the your applications are

7887.727 -> it says that when you take a nap It's in the cloud.

7891.1 -> You can focus more 70% more or your business.

7894.8 -> How come because infrastructure side you don't worry because

7897.9 -> that's auto-scaling model.

7899.534 -> Generally the cloud architecture work

7901.8 -> on the auto scaling model auto-scaling means

7904.6 -> you will Tel just say Okay.

7906.6 -> I want to run this application deploy that application

7909.3 -> over that now

7910.103 -> when you deploy that application if the demand

7912.884 -> of the infrastructure increase,

7914.8 -> they will expand that server

7916.9 -> if the demand of infrastructure decrease there.

7919.966 -> Will compress the servers?

7922.9 -> Okay, so in short we can say

7925.053 -> that we don't have to worry about the cloud

7928.2 -> for scaling scale up

7929.562 -> and scale down and it's a very much cost-effective

7933.2 -> because he does have to work on our particular structure.

7938.1 -> We don't have to work on the infrastructure side

7941 -> because once started it started.

7944.4 -> So that's what the cloud is guys.

7946.451 -> That's what the virtual XO cloud is and that is

7949.4 -> why these days everything is moving to the cloud.

7953.1 -> No, guys, we have divided our Cloud into three categories.

7958.3 -> One is iaas.

7960.3 -> Let's talk about that important because that's important

7963.1 -> to understand about the Beanstalk iaas.

7969 -> then paas pass Then saas.

7979.9 -> We don't call it.

7980.9 -> A SAS SAS is SAS.

7983.5 -> I'd leave is SAS.

7985.5 -> Okay iaas paas and SAS.

7990.873 -> What are these?

7992.1 -> So basically I infrastructure as a service.

7997.3 -> I stand what infrastructure-as-a-service s

8001.1 -> stand for software service p stand for platform as a service.

8007 -> Ideally your cloud is divided into these

8009.5 -> three categories infrastructure software or platform.

8014.7 -> What are they and how they are different basically.

8019.2 -> When we say infrastructure as a service here

8024.8 -> you are responsible for doing a lot of things.

8028 -> How come what they do

8030.4 -> where I say infrastructure-as-a-service know

8033.8 -> at that point

8034.8 -> of time you as a user will have given one platform

8041.2 -> like just take an example infrastructure Services example

8045.2 -> that you are the one who bought a new laptop.

8049.496 -> No, as you bought a new laptop

8051.855 -> in that laptop as a user as a provider,

8054.991 -> but I'll do

8055.648 -> I'll give you that laptop.

8057.2 -> Now you are responsible

8058.823 -> for doing everything means you are responsible

8062.7 -> to install a software set up a database with everything

8067.1 -> that you need to run the application you will do.

8071.7 -> Again means you are the one who set up everything as a user.

8076.5 -> We will provide you the infrastructure over which

8079.7 -> according to your requirement Interceptor means you say

8082.7 -> that we want to run our application

8084.976 -> that need 200 GB

8086.089 -> of the hard disk 10gb of garam Core 2 Duo processor and Windows

8091.2 -> operating system now,

8093 -> we will provide you everything in that terms.

8096.9 -> Okay.

8097.7 -> So when I say

8099.3 -> that you got the one platform over which you can run

8103.9 -> your application means you are the one

8106.4 -> who have to configure everything with you.

8109.4 -> So you just get

8110.6 -> an infrastructure that stand for infrastructure as a service

8114.9 -> and from the AWS platform.

8117.5 -> What come under this.

8119.3 -> These are one service called less ec2.

8123.6 -> elastic Cloud compute Ec2 elastic Cloud compute is

8128.805 -> one of the service

8130.3 -> that comes under the iaas infrastructure as a service

8135.3 -> now pass next thing

8138.2 -> when we talk about the pass platform-as-a-service

8141.6 -> why we are talking about a beanstalk here

8144.4 -> because we were talking about the past

8147.246 -> and in this pass it comes up Beanstalk.

8150.9 -> So when we say pass

8154.2 -> what do not pass pass means you as a user

8158.5 -> you will get one platform.

8160.4 -> Now what the Beanstalk do

8162.5 -> for us as a pass means platform as a service.

8168.78 -> So in this category,

8170.4 -> you have to tell suppose

8172.1 -> in this everything you have to set up suppose starting

8175.2 -> from the application in which you gonna work

8177.8 -> on the say infrastructure

8180.2 -> or the software everything your pistol just take one example.

8183.3 -> I have two in one node application.

8185.198 -> Okay, the say angular application now to run

8187.604 -> that angular application

8189.016 -> if I talk about this infrastructure as a service,

8191.8 -> what I have to do is I have to install node.js over that but

8196.6 -> when we talk about this pass

8198.6 -> Or when we talk about particularly elastic Beanstalk,

8201.7 -> what day do what it actually do for us

8204.546 -> that Beanstalk will help

8206.5 -> you to provide the platform how the product platform you tell

8211.1 -> that you want to run the node.js application.

8213.9 -> Okay.

8214.7 -> Now when you want to run the node.js application over

8217.9 -> that as a platform,

8219.6 -> they will give you one structure.

8222.8 -> Although you have option to configure

8225.1 -> that up to a great extent means many people just know be

8228.4 -> in stock in the way

8229.5 -> that just bring the application deployed directly.

8232 -> No other configuration we can do know we

8234.541 -> can change everything of that platform also,

8237.389 -> but the benefit of using the Beanstalk over easy to is

8240.9 -> the first deployment

8243.3 -> how come the first production how come here they say

8247.5 -> that you will directly get one platform over that platform.

8253.3 -> You don't have to worry.

8256.1 -> What was it like

8257.153 -> for you don't have to worry you simply bring the application put

8261.3 -> that over that platform.

8263 -> Okay, you bring the application put

8265.694 -> that over that platform and run it.

8269.2 -> So the here come the Beanstalk into the action

8272.239 -> when we talk about the platform.

8274.4 -> Okay, they did over software.

8276.7 -> They provide a software

8277.916 -> that you can directly use like a sales force

8280.19 -> and you can unde application over that.

8282.5 -> So guys why I'm talking about this thing

8284.66 -> because I have to come to the point.

8286.6 -> Why elastic Beanstalk?

8288.261 -> Why not any other platform?

8290.3 -> So here when we talk about the Beanstalk now,

8294 -> what is Beanstalk AWS Beanstalk

8297.4 -> is a pass service used for deploying

8300.573 -> and scaling web applications

8302.9 -> and services deployed with java.net PHP node python

8309.1 -> Etc on the familiar servers such as

8312.746 -> And the next storm get an IAS.

8315.2 -> What does it mean?

8316.3 -> It's saying that you will get the environment

8319.5 -> over that environment.

8321 -> You can bring the code

8322.4 -> and deploy the application how exactly it look like.

8325.65 -> Okay.

8325.89 -> Let's just have one look we'll talk

8327.5 -> about in detail in both how exactly to look like,

8331.2 -> so we'll go back

8333.8 -> to our These are AWS console over this AWS console.

8341.4 -> If you look for a Services here it come

8344.6 -> under the category of compute.

8348.1 -> You're communicating of compute compute means

8350.7 -> where the processing happen.

8352.865 -> Now, there are one service call elastic Beanstalk.

8357.7 -> So in that Beanstalk,

8360.3 -> let's open that they will ask you

8363.673 -> that which environment you want to set up.

8367.2 -> So if I say create one create one now,

8371.9 -> so I'll walk you through this platform in a while.

8375.271 -> Now the main thing I'm showing you here is see.

8378.5 -> It's saying me

8379.508 -> that which kind of platform you need.

8382.5 -> These are pre-configured

8384.346 -> some for Godot net Java node Ruby python.

8387.5 -> Beat with Tom get these are predefined platform

8391.417 -> pre-configured platform.

8393.8 -> So over that you just have to bring the application

8398.9 -> and deploy it now we have one scenario.

8403.9 -> We just discussed in

8404.9 -> that this scenario Option 1 you can go to the computer

8409 -> where and by the component according to requirement

8412.432 -> and assemble them

8413.6 -> like you will set up everything of your own.

8416.5 -> That's the ec2

8417.8 -> or Deploy an application without elastic Beanstalk.

8422 -> That's what does in the first scenario second.

8425.2 -> You can visit the electronic retail shop and buy a computer

8428.611 -> that fits the requirement the one I just showed you like

8431.9 -> if I have to run this over the ec2.

8434.4 -> I have to configure this platform,

8436.5 -> but here it's a no need to worry about the platform.

8439.5 -> You just say which platform and upload your code.

8442.1 -> That's it means suppose you already have an application

8444.8 -> that is built in the node.js

8446.888 -> OR react or angular or nor Java Ruby

8449.5 -> any language, you don't have to do any pill configuration.

8454 -> You will just pick this up

8456.1 -> and deploy with just upload the code.

8458.8 -> That's it.

8459.3 -> Nothing more than that.

8462.7 -> Okay, no.

8466 -> So that's a beanstalk now.

8469.8 -> I hope you understand this what the Beanstalk is.

8474.6 -> Okay.

8475.2 -> Now as we are talking

8476.7 -> about the see those who are saying

8478.4 -> that I am going to come to that are not just to tell you guys

8481.4 -> that this is something Tas and talk about the past

8484.179 -> is important here.

8485.5 -> Now what all things we do here application and data.

8490 -> That's the only thing

8491.496 -> from Beanstalk you have to manage means your application

8495.417 -> and your database.

8496.7 -> These are the only two things you have to manage as

8501.2 -> a developer as our As end user as a say devops,

8507 -> you just have to manage or as application owner.

8510.5 -> I say you just have to manage your application

8513.565 -> and data why application

8515.2 -> because obviously that's created by you

8518.02 -> and the database and nothing more than that these two things.

8522 -> You have to manage now your runtime environment

8526.238 -> middleware operating this term virtualization servers storage.

8533.1 -> Network everything he does is manage

8536.6 -> benefit quicker deployment

8538.401 -> because I don't have to set up the things simplifies operations

8542.8 -> because obviously

8544.3 -> the infrastructure setup is a major task suppose.

8547.6 -> Then we take application to production know

8549.918 -> as a develops if I have take application to production.

8552.9 -> I'll take around 10 days to set up my infrastructures

8556.6 -> and tested the load bigger say load testing all those things.

8560.382 -> I have to undo an infrastructure.

8562.7 -> Obviously we're infrastructure is already provided to me.

8566.3 -> It's simple simplifies my operation cost effective.

8570.2 -> Why because you don't need a lot of thing to test on you just

8575.5 -> have your infrastructure already over which you can go deployment

8579.6 -> and I lead their provide

8581.1 -> as a very standard infrastructure that required

8583.723 -> for any application.

8584.9 -> But still it doesn't mean

8586.52 -> that when I say node js is the only node.js

8589.243 -> I can do over that know.

8591.5 -> Although they give us a quite good amount

8594.9 -> of the customization option.

8597.4 -> They give us a one standard structure.

8599.7 -> Although they give us one standard structure

8602.3 -> that okay for node.js

8603.6 -> if you don't do anything you can do a standard structure

8606.4 -> But ultimately you have option to configure more.

8610.9 -> Now obviously the cost effective because underlying things

8615.1 -> are ready and multi-tenant architecture multi-tenant means

8620.5 -> when I talk about the tenancy tenancy means

8624.1 -> when we deploy the application know we have option.

8627.775 -> Are we going to take a share tenancy or multiple

8631.276 -> tenancy tenancy means when the application is deployed.

8635.3 -> Okay, so they suppose this one server, okay.

8639.6 -> You say these are suppose a hundred GB server.

8643.5 -> The server off hundred GB.

8646 -> Okay.

8647.4 -> Now you just need a 5gb.

8649.7 -> They will give you the 5 GB portion to you.

8652.372 -> Somebody need 80 gb.

8653.645 -> They give I 80 gb to them.

8655.9 -> So 85 consume somebody

8657.4 -> in the rest 15 they will give 15 to them.

8661.7 -> Correct.

8664 -> So they divided

8665.5 -> that one server into three people.

8668.7 -> This is dividing is basically caused share tenancy.

8673 -> How come how they divide like,

8674.8 -> have you ever done something like your hard disk?

8677.3 -> Is there give one hard disk

8678.935 -> to one user means one person hardest one user directly.

8682.276 -> It's not possible guys.

8683.7 -> They one thing called hypervisor with the help

8686.7 -> of heís a hypervisor.

8688.062 -> We do that part,

8689.1 -> but ultimately they go multi-tenancy means their option

8692.483 -> either to go with us.

8693.8 -> Your tenancy or a prime private agency.

8696.9 -> Now when you say share tenancy in that case your space

8701.3 -> will be allocated with all other people

8703.8 -> when you say you're dedicated tenancy in that case.

8707.1 -> They will make one source server

8709.6 -> and that server is only configured for you

8713.4 -> that's called as say dedicated energy.

8717.7 -> So Beanstalk will give

8719.7 -> both the tenancy you are dedicated

8722.4 -> as less shared.

8724.3 -> And the last one is

8725.8 -> better user experience user experiences better

8729.081 -> because of the multi-tenancy structure seconding

8732.3 -> High availability

8733.3 -> and auto-scaling because of all these things

8736.3 -> that user experience better

8737.888 -> because as I said

8738.8 -> that if tomorrow the load will increase the website is

8742.473 -> a load will increase on the website,

8745.2 -> your infrastructure will become bigger

8748.8 -> automatically it manage the load over that infrastructure.

8752.524 -> So that is how it make the better user experience.

8756.4 -> So quicker development deployment simplifies operation

8760.448 -> cost Effectiveness multiple 10 in architecture

8763.8 -> and better user experience now next so web hosting platforms.

8771.6 -> So although this Beanstalk is not the only one although

8776.442 -> apart from Beanstalk.

8778.6 -> We have openshift.

8780.346 -> We have Google app engine we

8782.5 -> have Go we also have our python anywhere.

8787.9 -> We have elastic Beanstalk as your app service

8791.151 -> and many other what are these platform?

8793.9 -> These all platforms are the one what they do is they

8798.7 -> directly help to deploy the application over them.

8802 -> They all provide as the platform with that platform.

8806.629 -> We can directly over

8808.2 -> that Platinum is a I can directly run my application.

8811.8 -> So ultimately The multiple option available in the market

8816.5 -> apart from AWS but YW s

8818.9 -> because the most cost effective and the most high availability

8823.5 -> that is provided anything is that is being stalked.

8826.5 -> That is why Beanstalk is the most used service

8829.908 -> in the market

8830.892 -> when we talk about the any platform like this.

8834.8 -> Okay.

8836 -> Now feature of Beanstalk

8838.4 -> elastic Beanstalk is a fastest and simplest way to deploy.

8843.9 -> your application AWS

8846.8 -> as already seen that just select

8849.2 -> the platform bring upload your code and you are done.

8854 -> So just select the platform upload your code

8857.465 -> and you are done second

8859.5 -> enabled you to focus

8861.038 -> on writing the code rather spending time on managing

8865.2 -> and configure servers all the things nothing to be done.

8870 -> You just bring your code Focus just on a code

8872.7 -> make the application functionality is better

8875.2 -> because deployment will already happen and when we talk

8878.985 -> about a continuous integration and deployment no CI CD

8882.7 -> c--

8883.9 -> Very well with this Beanstalk.

8887.2 -> So CI CD work best with a beanstalk

8890.4 -> because they give us a platform

8893.372 -> which is already I can correct my drink in jobs,

8896.987 -> or I can correct my code commit of the SS itself with this.

8902.592 -> Structure so it become easy for us to manage it.

8907.426 -> Now next automatically scale your application Up and Down

8911.8 -> based on the specific need.

8913.8 -> I already explained this point that it helped you to scale up

8917.575 -> and scale down the application on the base of requirement

8921.4 -> because here when it come to the scale up

8924.5 -> and scale down automatically do you don't have to worry

8928.653 -> about that part

8929.8 -> because these are some

8931.231 -> of the best thing that Erebus provides us.

8935.1 -> No, give freedom to select the aw sources,

8938.8 -> like ec2 instance their optimal for application.

8942.6 -> As I said that this is not the only thing

8945.457 -> that you can do,

8946.6 -> although you see one platform and those platform

8950.1 -> that you see is something like pre-configured,

8954.8 -> but we have the option where I can configure my platforms

8960.6 -> how let me show you suppose You just select

8965.4 -> that you want to download application.

8967.6 -> Okay, you have a code you can take a sample application

8971.6 -> existing version or upload your code directly,

8974.2 -> but you think

8975.3 -> like the infrastructure that is provided by

8978.3 -> this is not sufficient is not sufficient in that case.

8985 -> They will option call configure more options open

8989 -> that This is the place

8993 -> that very means a lot of people are not aware of this part

8997.2 -> because for them they simply go this select the server moment.

9001.5 -> They give the name then select the platform and upload.

9005.2 -> The code will make some people do like this.

9007.9 -> But point is you have option to configure more

9012.3 -> for many people

9013.7 -> elastic Beanstalk is just pre-configured thing

9016.3 -> and they have just

9017.3 -> one thing they can deploy the application over that

9019.5 -> but when it comes to the configuration,

9021.735 -> A lot of options.

9022.735 -> So let's see.

9027.7 -> now when I go to this configuration options guys

9031.9 -> now every single thing you can configure the bigger point

9035.671 -> of the Beanstalk is although your platform,

9038.9 -> but the best part is platform also can be modified

9042.6 -> means this is the edge of the Beanstalk see here

9046.8 -> when I say it's a platform

9048.564 -> and I have option to configure

9050.6 -> this also now suppose they say the software

9055 -> that you're using is node.js version this

9057.9 -> A double sex a disabled

9059.47 -> rotate logs logs streaming environment properties.

9062.8 -> These are the things but you say

9064.9 -> no no, I don't want to go with something they say, okay,

9068 -> you can modify

9069.049 -> when you modify the server over which they're going to run.

9073.4 -> The application is nginx.

9075.7 -> You can select Apache also the version of the node.js

9079.6 -> so many option to choose the version by default.

9082.106 -> They go with the latest one,

9083.6 -> but you also option to run that and you can give the command.

9087.4 -> Means when the environment will start at that point

9091.2 -> if you want to give some command you can give that also

9095.3 -> so you can provide that command also by this.

9099.5 -> So this is the few things.

9101.5 -> That is we can configure means first of all

9104.635 -> when I talk about my software

9106.8 -> for a platform by default the software's node.js

9109.8 -> but still I have option to change that software.

9114.3 -> Next thing is instance by default again.

9117.9 -> They you have option to choose the instance by default.

9122.3 -> They be the default instance,

9124.3 -> but you can select the disk type means volume SSD.

9127.8 -> There's a solid-state disk.

9129.4 -> If you think

9130.106 -> that the application that you're going to use

9132.7 -> is going to do so many input/output operations.

9135.7 -> Okay, when application is going to do so many input

9139.3 -> out of operation then at that time,

9141.412 -> we'll go with the provision I of this provision

9144 -> I of means input input output structure.

9148 -> so those provision I Ops is used

9152.4 -> when you have a lot of input out operations

9154.931 -> or you can go to the default.

9156.637 -> You can go the magnetic or general purposes T.

9159.688 -> Then you have option to change the size

9163.434 -> how many IHOP's?

9165.5 -> So if I suppose I'll set this magnetic one.

9170.4 -> I have option to the size of that ultimate minimum.

9173.461 -> I have to go with the 8 GB but makes him I can go

9176.5 -> with the Laura like 655 8GB that I can go with but minimum.

9183.2 -> I have to go with the Aging.

9185.6 -> Similarly for general purposes these and I Ops you can choose

9189.812 -> the number of input option also in one second

9192.9 -> how much input out profession you want it to perform,

9196.4 -> but we'll go with the default.

9199.7 -> then you have Security Group

9203 -> either you can have your own security group

9205.99 -> or either you can choose

9207.7 -> from the the one you use for any other purpose.

9211.8 -> So these are some of the security group

9214.3 -> that you can computer.

9217.7 -> get then the next option is capacity.

9223.6 -> Now that was a volume now

9226.4 -> how much instances you are thinking like by default?

9230.3 -> It will just one single instance.

9231.9 -> But you think

9233.1 -> like you sometimes have to scale up and scale down.

9236.2 -> Okay, sometimes you wanted to scale

9238.815 -> and scale down then in that scenario.

9241.735 -> You can select the load balancer.

9245.3 -> The load balancer

9246.373 -> where you choose a load balancer they are

9248.9 -> you can specify

9249.947 -> that maximum minimum start with one instance and maximum go

9254 -> with a hundred installed means

9255.741 -> if the load will increase keep on adding the instance

9258.9 -> if load will decrease keep on reducing that instance.

9264.7 -> so on demand stances I want only one instance

9269.3 -> and I can increase or decrease on the base of the demand

9273.613 -> that completely depend

9275.3 -> upon the your configuration type by default

9278.6 -> It Go with the single instance, okay.

9282.7 -> Then we say see the instances are already do multiplication.

9285.798 -> So I'm not going deep inside that because

9287.9 -> that the easy two configurations availability Jones placements.

9292.5 -> These all are the I'll say

9294.6 -> your Different even things I don't want to go deep

9298.6 -> inside this because

9299.776 -> that's are more related

9301.2 -> to the SP2 now next thing Lord Bellinger.

9305.4 -> If you select load Vector,

9306.533 -> then we option to configure that then you're rolling deployment.

9310.8 -> Now, what do you were rolling deployment deploy all at once

9313.7 -> or immutable means what is deployed is deployed?

9316.987 -> You cannot change that.

9319.3 -> Rolling update or rolling means

9321 -> what the rolling update will do suppose.

9324.3 -> I have an application.

9325.5 -> Okay, I have I took one application

9327.7 -> that is deployed over this application version

9330.8 -> a is deployed now suppose you come up with a version

9335.7 -> be okay when you're trying to deploy this application

9340.4 -> until or unless this is completely tick mug.

9344.1 -> This is completely up

9345.518 -> and running with this water is completely up and running.

9349.3 -> This people will get

9350.791 -> only this version is more like unless or

9353.7 -> until the new deployment is not successful.

9358.2 -> Unless or until the new deployment is

9360.782 -> not successful old will not go is

9362.9 -> doesn't mean that suppose you are deploying that okay.

9367.6 -> Suppose the deploying the application now

9370.2 -> at that time you're deploying the application.

9373.3 -> Okay.

9374 -> Now something got break this application and able

9376.4 -> to deploy some some problem in this application side,

9380.7 -> right if that is a case then

9384 -> what happened your old version will keep on running until or

9388.009 -> unless this will be hundred percent deployed.

9392 -> Get so that's a rolling deployment means always update

9396.2 -> with the latest version,

9397.8 -> but in will wait

9398.958 -> for one version to get completely deployed.

9403.4 -> Next security when it comes

9406.9 -> to security you have option to add the security group to this.

9412.1 -> You can add the multiple Security Group to this

9416.8 -> and then monitoring measures updates

9421.8 -> notifications Network database and tags in short.

9427.3 -> These are all the options that I can configure

9431.079 -> when I'm going the ec2 instance.

9435.3 -> GTA these options are very on this part by default

9439.1 -> of free tire single instance.

9441.3 -> You want to go on spot you want to go a higher available higher

9445.7 -> available spot and on-demand custom configurations.

9449.5 -> So all these options

9450.948 -> are available in the elastic Beanstalk.

9455.9 -> So suppose, let me just show you the thing then we'll talk

9459.4 -> about more Theory now suppose I give a domain name.

9463.088 -> I will say.

9467.2 -> Erica dot U dot this part.

9470 -> Okay.

9471 -> I'll check availability.

9472.2 -> It's this domain name is available.

9473.783 -> You have to give a domain name later on.

9475.6 -> Right?

9476.2 -> Like if you said record dot the URL

9478.6 -> will be either a car dot EU -

9480.953 -> vest but if you later on

9482.8 -> when you take the application to live you will link

9485.3 -> this domain name with your own original domain name.

9488.4 -> That's what DNS so that's how when you say

9491.8 -> Akash hundred dot V.

9493.3 -> It will come to this link

9494.663 -> because that we have to manage by default.

9496.9 -> generate one URL for

9498.438 -> us now you can give the description of a platform.

9504 -> In the description,

9505.1 -> I'll say this is a test node app.

9510.7 -> Now I want to create a platform for the node.js it can be any.

9516.4 -> As of now, I don't have any code.

9518.4 -> I'll just take a sample application.

9520.242 -> The only difference is

9521.4 -> if I upload my code you will see my code

9523.694 -> if I simply take

9524.519 -> the sample application uses a sample application

9527 -> that Dolly different it is up to you.

9528.9 -> If you've already built build code make into zip

9531.8 -> or War file uploaded the simply say create the environment.

9537 -> It is going to take few minutes in that few minute.

9541.1 -> It is going to create one environment for a see this

9544.1 -> will take few minutes.

9546.4 -> So after a few minutes,

9547.8 -> we will return back and this link.

9550.5 -> This is the link that is generated.

9553.2 -> If you go to this link one default,

9556.2 -> your node.js application will be running.

9559.9 -> One default no disappearing learning in a while.

9562.664 -> So I'll ping you this link.

9564.2 -> Also, we'll come back later on after 5-10 minutes.

9567.65 -> This will be ready to use.

9571.8 -> I said that to all of you so we can check in a while.

9576.5 -> Although that's a major about the Beanstalk.

9581.5 -> Now we'll just verify it's ready.

9584.6 -> I think it's not yet ready.

9587.6 -> We'll come back in a later later and we'll just start talking

9591.3 -> about the fundamentals now next passage

9593.764 -> but is composed of elastic Beanstalk.

9596.1 -> Now, what are the component lastik Beanstalk and application

9599.9 -> is a collection of environment including environment version

9605.1 -> and environment configuration

9607.2 -> in moment version environment configurations.

9610.8 -> So Application in elastic Beanstalk is conceptually

9615.1 -> similar to a folder.

9617.9 -> So what they do is you just give them the folder

9621.3 -> they run the application through that folder.

9625.1 -> So it's very similar to running the application

9627.5 -> over local system.

9628.579 -> But instead of that it running over the cloud environment.

9632.9 -> example Tomcat web app so we have Tomcat web app

9640.2 -> so I can have web app that's have a multiple environment

9643.161 -> to configure with that.

9645.8 -> If I go back and refresh this see my environment is ready.

9650.9 -> I click on that just refresh.

9653.3 -> Once again, just click on that.

9656.2 -> You will see Health.

9657.6 -> Okay, the one who's asking if I go port number in that case

9661.4 -> what happened in this case,

9663.615 -> you're healthy check will not appear.

9667.1 -> Okay, so an application version refer to a specific label.

9673.246 -> I traitor of a deploy code for a Application

9677.1 -> and application version point to an Amazon S3 object

9681.1 -> that container Deployable code such as jaar jaar jaar

9684.8 -> or more files

9685.46 -> so we can directly pick those files in up to deploy

9688 -> that so I have a code Pipeline with that code pipeline.

9691.466 -> I have connected my servers

9693.1 -> and when the code will come up it directly deployed

9696 -> over this servers.

9698.596 -> So see it's so he's showing me

9700.903 -> that the Tomcat is running version.

9703.658 -> Is this Tomcat web API every API is deployed

9707.6 -> on version are deployed on the different servers.

9712.3 -> So environment with a beanstalk

9714.5 -> application house different running version of application

9717.852 -> so I can have a different running versions

9720.1 -> of my same application also on that Beanstalk Tomcat web app

9725.4 -> and tommcatt reproduction

9727.1 -> so I can have two different version one is my development

9730.954 -> one is my production.

9733.4 -> Now so there are two type of the tires Z web server Tire

9737.9 -> or worker Tire web server tires.

9741 -> So HTTP request and working Tire background process

9744.9 -> the background task when you consider the environment,

9748.5 -> so elastic Beanstalk report the health of web server.

9752.5 -> So basically you can see here.

9754.7 -> It's showing me the environment is healthy

9757.3 -> in case it generate all the logs

9759.4 -> in case it's an LD it Mark it as unhealthy,

9762.491 -> so According you come

9764.2 -> to know that application is working correctly or not.

9767.6 -> So environment is being updated past recent health check.

9772.2 -> So if the environment color is gray is like being updated

9776.623 -> if it's green.

9777.7 -> It means so what I'm talking about.

9779.8 -> Is this color past recent health check

9782.4 -> if it's yellow failed one or more health check

9786.634 -> and read failed three or more health check.

9790.8 -> So by checking the color of this you can check that.

9794.5 -> What is the state of the environment?

9796.3 -> So great that you just made any change

9799 -> or just a created that green it passed all ready to use.

9805.4 -> Yellow field one or more check

9809.5 -> and read failed three or more check, okay.

9814.6 -> The architecture of these stock is

9816.8 -> web server moment Tire handle.

9818.9 -> The HTTP request is more

9820.7 -> like Beanstalk environment load balancer Auto scaling group ec2,

9826.8 -> instance host manager and Security Group.

9829.515 -> So basically underline underline this elastic Beanstalk

9833.338 -> what they have.

9834.4 -> They any gays have one ec2.

9837.3 -> They have one easy to over that easy to They

9842.9 -> have a security group layer,

9845.765 -> then they have auto-scaling layer over that layer.

9849.8 -> They have the elastic Beanstalk with that.

9853.4 -> Sorry this elastic load balancer this load balancer will divide

9857.8 -> the load into the multiple instances underline.

9861.3 -> It is launching an easy to only suppose.

9863.36 -> I'll show you.

9864.1 -> I launched one elastic Beanstalk.

9866.8 -> If I go to my EC to let me show you

9869.8 -> if I go to my EC.

9870.9 -> to know See by default one instance launch

9876.9 -> right by default one instance get launched

9880.7 -> when I launch one Beanstalk.

9886.5 -> First of all,

9887.5 -> the bigger box is a beanstalk environment.

9890.613 -> Next is a load balancer

9892.515 -> which will give the C name and the route URL.

9896.3 -> Then you have Auto scaling Group,

9897.899 -> which automatically scale up tap is scale up and scale down

9900.8 -> depending upon the requirement.

9902.5 -> Then you have the ec2 instances.

9905.3 -> Then you have the host manager and you have a security group.

9908.8 -> So that is how your complete web server environment work.

9913.1 -> Now, what is worker a worker is a Process

9917.4 -> that handle background tasks

9920.6 -> during resource in intensive or time intensive operation.

9925.3 -> So they launched a worker behind their tasks or application

9930.3 -> which try to handle the load and like

9933.3 -> email notification generate report cleavable database.

9936.7 -> These all are the worker

9938.254 -> that we configure these workers help us to schist

9941.562 -> scale up my application or speed up my application.

9945.3 -> And why do we need worker your web server one request come

9949.5 -> to that is a time taking

9952.4 -> so we'll assign

9953.471 -> that to one worker who will do this task

9956.344 -> and other requests got served.

9958.4 -> If you don't have a web worker between that

9960.8 -> though if next request will come

9962.893 -> that have to wait for one request to get complete.

9966.6 -> Then only it can do that.

9968.3 -> So performance and request except will be decrease a lot.

9973.146 -> But very a worker

9974.5 -> when we request is time intensive.

9977.2 -> It assigned to one worker

9978.9 -> and the worker will process in a meanwhile

9981.6 -> when a second request will come will serve

9984.021 -> that request to the server.

9985.428 -> So that is

9986 -> how your workers work and we have to configure those workers

9989.285 -> if we go back to environment.

9991 -> So we are getting a web app servers

9993 -> that have the workers that help to achieve dysfunctional.

9995.9 -> Ready?

9997.4 -> Know how this environment communicate so we have

10001.1 -> web server and moment dear.

10003.2 -> We have one thing called Route 53 Route 53.

10007.3 -> This Route 53 is given the URL we use the Q services sqs.

10013.6 -> Sqs, that stand for your queue service.

10017.665 -> So what that queue service will do whatever request you assign.

10022.715 -> Okay, just simple queue service

10025.1 -> what it do is whatever request your sign it put in the queue

10029.143 -> if they have a time to resolve

10031.2 -> that they will resolve it else it kept in the queue.

10034.8 -> So it keeping a cube and every time we try

10038.2 -> to that sending the request else it keep in that queue

10042.181 -> until as it reads.

10043.7 -> How it works just like simple example

10046 -> of your WhatsApp what happened WhatsApp

10047.9 -> you send our message suppose other person whom you have sent

10052.8 -> and the message is not right now having the active internet.

10057.2 -> Okay, not having the active internet

10059.641 -> if they don't have the active internet what happened

10063.164 -> that Mr. Gatley

10064.2 -> one tick mark at the time where you get one tick mark,

10067.3 -> where is it?

10067.9 -> Just messages idly at that point

10070.7 -> that message is inside the queue.

10073.1 -> So that message is inside the cube.

10076 -> Once you will able to say other person's active

10080.3 -> that message is received.

10082.5 -> So that is

10083 -> how your queue service also 1 so we have client client talk

10087.7 -> to web server server

10089.3 -> pass the request to the Q Q

10091.5 -> send the message to the HTTP post worker

10094.4 -> and it respond back.

10096.4 -> So always you have deployed our demo for

10098.37 -> how to deploy the application over the elastic Beanstalk.

10101.2 -> So guys, this is how Beanstalk work

10104.5 -> and that's what all about the Beanstalk see you guys.

10108.6 -> My application is active.

10109.999 -> Now.

10110.5 -> If I go to this see

10111.976 -> one node application is running over that Beanstalk.

10115.9 -> You guys can also try by hitting this URL.

10119 -> So this is

10119.938 -> how your Beanstalk work and that's what all about the beans

10124.4 -> of so VPC something guys is very important.

10133.3 -> Topic of AWS indirect VPC particularly,

10136.6 -> I can save if I were planning for any kind of interview

10139.3 -> and so know so 40 percent

10142 -> of your weight age is actually coming from the VC.

10145.811 -> So dpc's a super important topic that we should learn.

10149.9 -> What is VPC see the complete Cloud

10152.4 -> that we have the complete Cloud environment is basically

10155.93 -> called public Cloud right?

10157.6 -> Then what exactly the VPC is BBC stand for work?

10163.2 -> Well private Cloud means over that public Cloud

10166.711 -> when you get a space

10168.107 -> as a private means come some the main say

10171.2 -> that you cannot go for a public Cloud

10173 -> because all data are shall we say no worries.

10175.7 -> You don't want to go to the public Cloud will give

10178.4 -> a separate space of your own

10180.2 -> that's complete space will be of your own

10182.999 -> and over that space.

10184.4 -> You can run that applications or in short.

10186.8 -> We can say that over the public Cloud

10189.183 -> when we get a space is a private space.

10191.7 -> That's refer as your or PPC PPC stand for virtual private cloud

10197.2 -> in which we will get an isolated space

10200.1 -> from the complete Cloud.

10201.663 -> No one else can go to Myspace and configure

10204.4 -> that so it's very important topic all GPC.

10207.6 -> Now we PC the logically isolated

10209.991 -> from the other network in AWS Cloud.

10213 -> We can launch a SS resource.

10214.9 -> I'll tell you how to configure EPC complete heat it give

10218.5 -> all the benefit of traditional Network

10220.6 -> that you can have of a cone Data Center.

10223.1 -> Access the resources

10224.607 -> and application through ipv4 IPv6 on your VPC.

10228 -> Give the better scalability infrastructure

10230.335 -> in the Enterprise environment.

10232.005 -> You will complete control over the night of the best part is

10235.475 -> we have a complete control over the network

10237.9 -> when we go with the deep sea

10240.3 -> as we know it's isolated space for a more secure environment.

10244.1 -> We make our space.

10244.832 -> Okay.

10245.059 -> Let me show you one architect diagram

10246.7 -> for that now VPC something very important to learn

10251.269 -> how to configure that.

10253.2 -> Exactly reconfigure.

10254.7 -> The VCC is PPC contains some components guys,

10258.5 -> if we busy a lot of components

10260.4 -> that the configure what are the component we see

10263.5 -> the very first thing we PC is basically called as

10266.8 -> internet gateway internet gateway is something so

10271.676 -> this green box consider this green box as one VPC.

10275.5 -> Okay to this VPC is isolated space it cannot talk

10280.1 -> to interact guys.

10281.594 -> It's VPC cannot talk.

10283.4 -> Internet to make the VPC to talk to internet.

10288.7 -> We actually have to give one thing

10292 -> called internet gateway internet gateway is the one

10296.41 -> that helped you to make this particular week.

10299.5 -> Is he to talk to internet

10301.235 -> else your GP see the complete isolated space on the AWS Cloud

10305.4 -> that cannot talk to internet now in the VPC.

10309.7 -> There are some important part

10312.1 -> that is one public Cloud one private

10316 -> when we don't give a cloud we call them as subnets.

10319.6 -> This is one space.

10321.3 -> Okay.

10322 -> This is one bigger space in this space.

10325.078 -> We divide that into small small parts why we divide them

10329.1 -> into small small part basic the reason

10331.412 -> for dividing him small part

10333.1 -> so that we can run multiple thing over this area

10336.9 -> so that we can run multiple things

10339.206 -> over this environment decayed of and secure environment over.

10343.4 -> Secured environment will set up this particularly

10346.873 -> your subnet subnets are more

10348.905 -> or less like that a small small areas

10351.517 -> inside the VC over which we launched application.

10355.6 -> How many subnet one VDC can have guys one week is

10359.4 -> he can have multiple subnet

10360.821 -> that depend upon the cider value what is cider video?

10364.456 -> I'll show you basically their day to get the IP address

10367.4 -> to be PC on the base of IP address will get

10370.4 -> that how many subnet I can launch in one VPC.

10374.8 -> So in one week we see I can have multiple subnet subnets

10377.8 -> are the spaces.

10380 -> Now I did Mikey the point is like that

10383.6 -> so we have the Subnet in each subnet guys.

10387.2 -> We can put different different things some subnet are

10390.4 -> the public subnet some subnet are the private something.

10393.9 -> Okay.

10394.8 -> So public subnets are those

10397.1 -> that basically available to the Internet.

10399.7 -> So what we do we divide our application to categories

10402.2 -> will say we have some part will put a public some part.

10405.381 -> We put private all the things that you want to express over.

10408.7 -> The internet as an example suppose in one application.

10411.582 -> We have application

10412.7 -> and database right databases something a secure part.

10415.929 -> You don't want to make it available outside.

10418.608 -> So things that we don't want to make it available

10421.6 -> outside will put them into the private subnet

10424.558 -> and the things

10425.5 -> that we want to make it available outside be

10427.7 -> to the public subnet.

10428.935 -> What compound with is have a player one called

10431.4 -> one complete box called PPC to connect to internet.

10434.4 -> They have an internet gateway.

10436.2 -> We have the divided into the small small.

10439.4 -> Each complete your VPC divided into small small Subnet

10443 -> in that subnet.

10443.9 -> You have some public subnet

10445.488 -> and then private Subnet in the public subnet.

10448.4 -> We have the things application

10450.4 -> that actually run over the my friend

10452.9 -> and application tree.

10454.192 -> It's never happened to you dealt with able to access the database

10457.976 -> of Facebook, right?

10459.1 -> He'd never accept the database of Facebook,

10461.2 -> but they're able to access the application of Facebook.

10463.7 -> So what they do something they

10465.2 -> put in a public something they be put in private.

10467.9 -> So how we decide Of my submitted public or private

10471.988 -> that depend upon one more

10473.911 -> competently physical route tables route tables.

10477.7 -> What is the route table route table is a place

10481.2 -> where we keep the entries of this particularly your subnet

10485.31 -> all the subnets get added into the router table.

10488.8 -> Okay, all the subnet got headed into the route table.

10493.6 -> So point is very simple that The have one default

10498.8 -> but it is Black Box this called default route table

10501.6 -> every sub every VPC have one default route table

10504.99 -> all the subnet

10506 -> that you don't suppose our 50 Subnet in my VP.

10508.794 -> See all the subnet that you launched.

10511.027 -> We were part of this route table by default.

10513.566 -> First of all,

10514.341 -> everything will go in the Black Box.

10516.404 -> Okay your subnets also your internet agait.

10520 -> We also now when everything is a part of Black Box

10523.364 -> what happened now,

10524.6 -> I want to make something which cannot X over it.

10527.7 -> Nick but here if you see as everything apart

10530.642 -> of same place this internet gateways also same place.

10534.2 -> So anyone who's accessing my VPC come to this route table,

10538.2 -> they can know the IP

10539.376 -> of this also and I paid those of this also

10541.788 -> so they can access all the things from my place

10544.3 -> right the no use

10545.7 -> of creating a different different public and private.

10548.4 -> So to overcome this problem.

10550.207 -> We got one solution called

10551.9 -> different route tables will create different route tables

10555.673 -> or something very insert the occurred

10558.1 -> where we insert the IP address of each subnet.

10562.1 -> Now after that

10563.069 -> what happened you have public subnet private subnet,

10566.6 -> we make a public route table

10568.359 -> and the private router table all the things

10571 -> that you want to expose to public will put

10573.1 -> a public route table

10574.1 -> and internet gateway is connected to public route table.

10578.3 -> Whereas the thing

10579.7 -> which I don't want to expose the internet.

10581.86 -> I'll just keep in a private Roundtable all the new subnets

10584.971 -> you launch all the news of Nets will keep entering.

10587.7 -> the default out table and whenever you want,

10590.6 -> you can move from default to public

10592.8 -> or you can move from default to private one in subnet

10596.1 -> can be either a part of public Roundtable private route table

10599.1 -> and by default,

10599.8 -> they are part of default route table,

10601.5 -> but you can move it from this place

10603.2 -> to their own respective

10604.6 -> now cable internet gateway is corrected

10607.1 -> to public Roundtable now what happen

10609.475 -> when somebody accessing the internet they can access

10612.5 -> my public instances

10614.2 -> and how pirate private instances work your Akin starts can talk

10618.7 -> to the private internally.

10620.117 -> They can communicate means you look for some data.

10623.2 -> Your application will actually

10624.858 -> talk to the public subnet Republic subnet will talk

10627.6 -> to a private subnet

10628.6 -> and from private subnet we can access

10630.4 -> the database only database.

10631.9 -> We keep in a private and application became public.

10635.2 -> What is this Nat Nat actually refer to as what happened?

10639.1 -> I have this suppose

10640.417 -> setup created right now the requirement come up

10643.608 -> on the other side that whenever this database is configured.

10647.8 -> Now this database sometimes want to talk to internet

10650.8 -> but in this configuration my database cannot talk

10653.9 -> to internet neither.

10655.134 -> I can talk to the database.

10656.8 -> Neither database can talk with internet

10659.1 -> when both things got stuck

10660.975 -> that neither you neither from the internet.

10663.847 -> I can talk.

10664.6 -> Neither database can talk to internet in both this scenario.

10668.5 -> You have a problem suppose

10669.8 -> you want to download something new suppose.

10672.3 -> I got some new patch for database.

10674.37 -> I will do so guys.

10675.5 -> We introduced one thing called nat.

10677.6 -> At not refer to proxy.

10679.95 -> Okay not actually refer to proxy server.

10683.4 -> So basically what happened now,

10686.4 -> it would be a one-way communication

10688.6 -> how one-way communication your database will talk to the NAT.

10693.93 -> Add not through Roundtable talking to internet.

10698.3 -> Willie Barney communication from private I can access internet

10702.3 -> but no one from outside can access your database

10705.8 -> that is called

10706.767 -> as guys Nat Gateway is color proxy server.

10710 -> Basically when we have to access our content from database

10713.467 -> to the outside Network use an at Gateway,

10715.9 -> but still I cannot accept private to infinite private

10718.9 -> can only access to the public.

10720.8 -> I'll do a quick revision

10722 -> over that once again internet gateway.

10724.466 -> The one that helped to connect to in right subnets.

10727.8 -> In one PPC beginner multiples of that

10729.929 -> how to decide I'll show you in a minute after that.

10732.904 -> Basically.

10733.493 -> What you do is you divide

10734.806 -> that into public and private depend upon your requirement.

10737.8 -> You can have multiple public multiple private.

10740.2 -> After that.

10740.913 -> We have a route tables all

10742.601 -> the entry of your subnet will be a part of a round tables.

10746.4 -> We can have public Roundtable and the private route table

10749.4 -> and the default out able all the new subnet

10752.148 -> that Lodge is always a part of the Court

10754.7 -> how table and later on we can move to public or Language

10758.8 -> internet gateways connected to the public out table

10761.3 -> so that it can access the instances over the internet

10764.3 -> and public subnet can talk the private subnet.

10767.6 -> If a private subnet want

10769.015 -> to access the internet through Nat Gateway,

10771.7 -> they can talk to the in short.

10773.941 -> I can say

10774.7 -> that this complete design is basically reference guys

10778.5 -> VPC also the configuration

10780.9 -> how to how to do all these things Nat.

10785.2 -> Nat is something as private cannot access

10788.076 -> Internet something would happen.

10790.378 -> We have to require the internet at private.

10793.448 -> So private.

10794.2 -> Can you the navigate without a proxy server

10796.889 -> the proxy server private can access the internet

10799.9 -> but no one from outside can access this private now

10804.4 -> route table is something very insert week entry give entry.

10809.1 -> Sorry, sir.

10810 -> We don't take next subnets

10812.9 -> so that we know what our Nate's that connects over internet

10816.7 -> what's up guys should not occur the net that can agree.

10819.8 -> We're in the real time ever.

10821.526 -> We just private environment user navigate now.

10824.431 -> Let me show you

10825.4 -> how many subnet we can launch in one internet.

10829.3 -> So let me open one document.

10839 -> The one thing called Cider what is cider class inter-domain

10843.4 -> routing cider is a one

10845.2 -> that we decide

10846.319 -> how many subnet you can launch in one machine.

10850.4 -> You know how many subnet we can launch into one machine

10853.8 -> in The Cider has some value

10856.9 -> that to range of Ip ipv4 and IPv6

10859.9 -> that even we train up IP of using

10862.1 -> how many subnet I can launch in one VPC with how many sub

10866.5 -> that I can Lon.

10867.6 -> I'm inside the subway.

10868.894 -> How many instances we can launch how many subnet you can launch

10873.4 -> that defined prom total IP range of 32-bit the total IP range

10878.138 -> of this is 32 bit.

10879.7 -> Okay.

10880.7 -> Now out of that 32-bit basically

10883.3 -> what happened you can choose between 16 to 20.

10886.4 -> The value number will be 16 to 22 will choose now

10889.3 -> what they do suppose I choose our cider value is 16

10892.9 -> if a choice either value is 16 then what it will do.

10896.2 -> No 32 -60 Teen

10899.7 -> that is 60 put 2 raised to the power 16 2 raised

10904.3 -> to power 16 and it will become out with 65536.

10908.9 -> What does it mean?

10910.4 -> It means that this many subnet I can launch in one VPC

10915 -> if by cider value is 16 side has our range you have to select I

10920.358 -> say my cider value is 16.

10922.5 -> I can launch one 65536 subnets how 32 -

10928.9 -> 16 is 16 2 raised to power

10930.9 -> 16 is 65536.

10933.7 -> Then suppose my slider values any between 16 17 18 19 20

10938.39 -> anything suppose.

10939.698 -> My cider values 24 either cider value is 24,

10943.299 -> then you will see

10944.3 -> 32 minus sixteen eight tourist over 8 is 256 similarly here.

10949.4 -> Try to -

10949.9 -> 28 is 4 to 2 is to 4 is 16 means minimum 16 subnet

10954.5 -> and maximum 65536 subnet

10956.8 -> we can launch inside the one we see.

10958.7 -> see so that depend upon your requirement either requirements

10961.8 -> of more subnet choose the Lower Side revalue the requirement

10965.3 -> of a higher subnets choose a lower subnets value means

10968.781 -> your subnet value is lower like 16,

10971.096 -> you can launch more subnet 17 more subnet like that

10974.5 -> if your value is 28,

10975.9 -> you can launch only 16 Subnet in one week

10978.6 -> so that completely dependable and generally we try to

10981.3 -> to the lower higher will like 24 26 27 like that

10984.9 -> because if we use a say something no in terms

10988.523 -> of 16 they get so many we in a practical use this only

10992.7 -> but if we use the 16

10995.4 -> what happened we'll get so many subnet IPS.

10998.2 -> So it's a more chance to hack.

11000.1 -> Generally.

11000.8 -> We try to choose a value as 28 27 26 that depends

11004.5 -> upon my cider as architect.

11006.6 -> You are responsible for knowing

11008.388 -> how many basically subnets I should launch

11011 -> so that costs either what happened to other IPS.

11014.9 -> So I choose suppose my side.

11016.9 -> Well as 16 in that I can.

11018.9 -> Launch 65536 subnets and inside the subnet guys.

11023.474 -> We can launch our machines.

11026.2 -> So the one diagram

11027.375 -> that we just understand we do this diagram by practical.

11031.073 -> Now, these are some steps that you have to follow

11034.3 -> how step to create VPC launch subnet

11037.434 -> create route table create internet gateway,

11041.323 -> then set attached internet gateway and subnet

11044.707 -> to the Roundtable step

11046.4 -> to associate internet gateway launch instances

11049.74 -> in the subnet step to connect with the instances step

11053.6 -> to connect the public with private instance.

11055.9 -> First step to integrate the net Gateway.

11058.5 -> So all these steps are very clearly done here.

11061.7 -> There's a number of Ip.

11062.942 -> We had means this this many eyepiece.

11064.887 -> I can launch randomizes how I be selected.

11067.376 -> I'll show you.

11068.6 -> Let's go back.

11069.5 -> Let's just configuration everything down one by one.

11072.9 -> I'll go to AWS so

11083.9 -> yeah, we'll just create database.

11097.565 -> I'll go to the console.

11107.6 -> So, let me just log into one of my account.

11122.588 -> Find log into an account.

11130 -> Okay.

11137.4 -> Now in the services

11138.8 -> that the confronting called Network in networking we

11141.8 -> have EPC will go to this.

11151.8 -> Bastardo qualification we click

11154.184 -> on one of the PC Fix it every step possible bow

11158.376 -> to your BBC Radio busy.

11160.9 -> You're busy.

11165 -> Creativity is here by default every account have one default

11169 -> because you should not delete the default within each region.

11172 -> We have one default

11173.1 -> because you always give some name to that.

11175.9 -> I will say adieu VPC any name I do recovery PC.

11181.1 -> T it asking me the slider value is a 10.0.0.0 Steen.

11186.2 -> I am choosing a cider value

11187.854 -> as 16 you can just any side effects.

11191 -> and create And create so

11194.7 -> what it did it has created one GPC for what it did

11199.9 -> according diagram will open diagram also fairly.

11202.8 -> It has created this green box.

11205 -> And in this green box by default will get this out table.

11208.8 -> Let me show you now.

11210.2 -> There are obstacles out table will go there.

11214.953 -> By default one Roundtable will be tricky for you.

11223.6 -> chief that one for default we busy one for R&B

11232.6 -> see how to know which is where are we busy?

11235.1 -> Are we busy number is zero to eight AFC right?

11239.1 -> It has to this one.

11240.2 -> So this is our Round Table will say it default route the pot art

11245.765 -> so I have read one EPC.

11247.8 -> Why did I BBC?

11248.889 -> We got one default now table?

11252 -> Okay.

11252.6 -> We got one default now table.

11255.5 -> Next Step.

11256 -> So this is created and one default router table.

11258.2 -> Is there with us next launch our subnet inside that VTC now

11262.649 -> inside the VPC.

11263.8 -> We can launch the subnets.

11266.723 -> One single subnet.

11268.1 -> I'm going to grade to submit

11269.7 -> when public and private Reid subnet.

11273.5 -> name also private subnet in which EPC I want

11279.9 -> to create in my VC,

11281.091 -> which I've created any availability Zone.

11284.2 -> I choose any availability Zone and cider value cider value

11288.2 -> for should be between your range the value.

11291.3 -> You have to choose for our main ep0.

11293.8 -> It should be the range.

11295.1 -> So I write 10.0.0.0 / 16.

11298 -> So it should be the range.

11299.2 -> I said 10 dot 0 dot 10.0 /font 4 you can use other IP also,

11303.151 -> but it should be in your ipvanish.

11306 -> this is for my I may get a public first of all,

11308.3 -> this is my public and Will create one for private.

11325.8 -> One for private that is 10 got 0 Dot.

11334.9 -> 2.0 / 24 that's my private subnet.

11339.3 -> So I prayed to subnet

11340.9 -> one public subnet one private sudden all the course

11343.5 -> and I'll take at the end now,

11345.2 -> we just focus on concentration on configuration.

11348.4 -> So I think Nate Lee we created

11350.4 -> to subnet guys one public one private side L

11353.5 -> should be unique all subnet enter in the router table.

11357.2 -> So now we get to subnet by default.

11359.8 -> I told you all subnet will be a part of Route Kevin

11362.3 -> how I can see that see in the route table.

11364.8 -> You go to subnet Association see do you see to subnets by default

11370.1 -> when we create the subnet?

11372.1 -> No, all subnet.

11373.3 -> If Ford get edit to this default out.

11375.7 -> Well, first of all, there's no public subnet.

11377.941 -> No private subnet.

11378.7 -> They are in a one place.

11379.9 -> That's my default route cable will create a separate out table

11383.85 -> one to public Roundtable one word private route table

11386.4 -> create now table.

11388.6 -> I clearly paid one public RT and my VC.

11397.6 -> and one private party in my eyes Public art again

11406.1 -> private are the 2 RT we created right now.

11409.5 -> They are not having any instance so till now

11412.9 -> what we did let's understand.

11414.7 -> We created this big green box.

11416.7 -> We launched two subnets.

11418.9 -> We have by default one round table and we credit

11421.692 -> to Route table public Roundtable and private out table.

11425.005 -> Now, what we'll do is public subnet will put a public out

11428.4 -> table private subnet will put a private out table.

11430.8 -> Can we have duplicate record?

11432.3 -> No one subnet can be in anyone doubting.

11434.876 -> All will do that.

11438.4 -> So let's attach

11439.6 -> that first of all open your private Roundtable

11443.061 -> even legal edit subnet Association click on that.

11447.8 -> It shows you what subnets you have now private route table.

11451.4 -> I add a private subnet.

11454.819 -> Similarly in public route table.

11457.761 -> I'll add the public subnet.

11462.753 -> After that,

11463.6 -> if you check a default route table not default route.

11466.457 -> They will have no subnet

11467.794 -> because when we move to Public Road table

11470.2 -> when we move to private Optical,

11472.2 -> so what we did it allow public into public Roundtable private

11475.7 -> into private property now next step internet gateway.

11480.2 -> Now, you have to launch our internet gateway to connect

11482.9 -> to your PC will go back and talk to him in Trend Gateway.

11490 -> I'll say adieu.

11491.8 -> IG any name I can give I'll create one internet gateway.

11497.3 -> now created after that attach the internet gateway

11503 -> to me see I will do select the internet gateway.

11508.1 -> Click on action attached to V PC select your V PC and attached.

11514.7 -> So ultimately I have attached the internet gateway to visit.

11518.4 -> Oh, so now internet gateway is attached to my PC.

11523.7 -> Add subnet to Route table.

11525.4 -> So we already adjust subject to the purchaser out table.

11529.369 -> Then associate IG in which route table should I attached

11533.6 -> the IG public Roundtable?

11536.2 -> Why because public is something

11538.242 -> that can have 2X over the internet now public route table.

11542.2 -> I'll go we add the subnet now go to route in the route edit.

11548.767 -> A drought say 0 0 means M from anywhere.

11551.767 -> I can access my Subnet we see

11554.3 -> what do you want to attach internet gateway select

11557.9 -> and the name of drinking now save it

11561.1 -> you have attached the internet gateway

11563.364 -> and edit that internet gateway

11565.2 -> to Public Road table till now guys.

11567.777 -> This structure is ready our to subnets are there.

11570.3 -> We have our out tables the our internet gateway all

11573.2 -> of them are attached.

11575.5 -> Now we'll start using that piece is created.

11579 -> Now, we start using that we try to launch

11582.045 -> the instances in the particular subnet one by one

11586 -> how Let's open up one more tab.

11595.8 -> We'll go to ec2.

11604.35 -> Here mr. Running instances in that running instances.

11609.2 -> I will start at to Linux installs launch.

11619.5 -> I launched one Amazon Linux

11622.9 -> with default configuration here in the configuration stance.

11627.573 -> I choose the VTC.

11628.854 -> I launched inside my greasy antique show me a public

11633.525 -> if you have 251 eyepiece

11635.3 -> because we choose the side revelers 24

11637.8 -> 32 minus 24 is 8 2 sot.

11640.8 -> It is 256 so we get total 251 it's--

11645.467 -> I told you totally 256 in short we get to 51 IPS

11649.682 -> for this instance.

11651.7 -> Right.

11652.5 -> I launched a public one public subnet.

11655.2 -> So I give the public IP to Dot and rest is fine rest.

11661.1 -> I'll add the security group.

11663.8 -> That is HTTP and https.

11668.8 -> launch So

11671.9 -> but really I have launched

11673.585 -> what ec2 instance inside the public subnet,

11676.579 -> so we have launched one

11678 -> installed inside the public supplement now similarly,

11680.696 -> we will launch for instance inside the private sometimes.

11690.4 -> select next This time private subnet.

11696.5 -> So choose your new pc Siri.

11699.5 -> So I will go to private.

11702.2 -> And public IP will disable for this storage.

11707.1 -> configuration HTTP and https review and launch.

11713.3 -> So as I will launch

11714.7 -> two instances one in public one in private.

11719.8 -> Let's go back.

11721.8 -> Now they got one public IP.

11723.269 -> But if I check the private IP of this one,

11725.5 -> no see private IP is between our range.

11728.6 -> You see 10.0 dot

11730.1 -> one dot 238 private IP will be in the reign of our side rail

11734.3 -> if she public IP can be anything

11736.5 -> but private IP will be arranged for this also as well as

11740.1 -> for this one also see it show me the private one.

11743.246 -> You have ten dot 0 dot to in the public one

11746 -> you have 10.1 So guys,

11749.292 -> I got a one two instances one public one private

11753.1 -> and kind of accept

11754.7 -> that Gateway these are available now,

11756.967 -> we'll try to first

11758.1 -> of all XS the public subnet miss public easy to through internet

11763.2 -> will see can we access the public to the internet

11766.2 -> and then we'll see can we accept private to internet?

11768.9 -> You have to make it running?

11773 -> Once it ready then we can do that then we'll do an at all.

11775.406 -> So we'll see why we can't do that.

11778.3 -> Now guys are instance are ready.

11780.418 -> Let's try these are public installs, right?

11783.2 -> So we just renamed we name them.

11785.9 -> The public one.

11787.199 -> I'll say public ec2.

11790.2 -> public ec2 and I'll name them as privacy.

11801.1 -> First of all see the public easy

11803.1 -> to the public easy to a public IP

11805.4 -> for we can correct with that.

11807 -> Whereas private easy to don't have IP

11809.7 -> how I can go to connect with a private IP.

11812.5 -> Obviously.

11813 -> I cannot crack on the internet very simple.

11815.1 -> I cannot connect to internet

11816.5 -> because they don't have any public IP.

11819.1 -> Now first of all,

11820.217 -> we'll try to the public somewhere public ec2 instance.

11823.8 -> How click on connect choose this SSH to this Temple.

11828.2 -> You can directly run this command key down.

11836.5 -> So and I have connected

11843.9 -> to my public easy to see 10.0 dot one dot 238 whose IP.

11850.1 -> Is this your public ec2?

11854.242 -> Unable to connect to my public ec2.

11857.7 -> And if a rider ping google.com See,

11867.2 -> let's wait for a minute.

11868.4 -> See it's able to Ping that

11869.9 -> because from my public subnet I can access the internet why

11874 -> because it is connected to internet gateway.

11876.7 -> Now, I'll tell you one thing will go back

11878.7 -> and remove the internet gateway

11880.2 -> from the public route table as try.

11884.4 -> we'll go back to our Public Roundtable

11887.8 -> will edit and we delete

11889.6 -> this internet gateway suppose now once I delete

11892.689 -> the internet gateway.

11895.163 -> Let's try to Ping again.

11901.9 -> Fossil, let's try to connect again.

11904.6 -> Internet gateways not connected now.

11906.7 -> Okay, so we'll go to folder.

11914.4 -> See guys, I'm not even able to connect to the instance.

11917.9 -> Why because it's not closed environment by BBC

11921.407 -> as it's a part of EPC.

11923.1 -> Nobody from outside can access that the reason for that is

11927.407 -> because you have not connected

11929.705 -> with the internet gateway to talk to the VPC.

11933.39 -> You must connect

11934.669 -> to the internet gateway now go back and again connect

11939.3 -> my route public route table to enter a negative way.

11944.8 -> So that were told you that the private Network

11947.05 -> you makeup on private Cloud over your public Cloud.

11949.65 -> I had a internet gateway now.

11952.4 -> Save now go back and again try.

11958.269 -> See able to connect

11960.5 -> so L told you to talk to the VPC.

11963.8 -> You need to have one internet gateway

11966 -> between okay now next step

11970.2 -> as my private installs don't have public IP

11972.7 -> how to connect to private.

11974.9 -> I told you private

11976.343 -> cannot access over internet then through public.

11979.9 -> I can access private how through my public one.

11984.1 -> I will be able to access the private instances.

11987.2 -> So what I have to do is This first of all go

11990.738 -> to the public one now to connect

11993.2 -> to the private ended up m-file bulky here.

11996.4 -> No, I'll make oven temp file to use rubrics as pseudo.

11999.4 -> S you -

12001.8 -> and I write VI my dot m any pem file name.

12006.9 -> You can give just get a one-time file which pem file

12009.9 -> which you choose so the by name

12011.786 -> of Amazon Singapore to go to my folder.

12015.4 -> Open that file copy the code and paste it there.

12018.9 -> So I'll go too.

12020.8 -> I'll search Amazon.

12026.4 -> Singapore I will edit this file.

12035.8 -> Why I'm doing that because public can access private.

12039.9 -> So the public know I'm creating one pem file

12042.6 -> and there I try to exercise of public from private basically

12047.171 -> from of completely

12048.6 -> but private cannot access directly through public.

12051.5 -> I can access private and then what I'm trying to do now,

12055.4 -> I'll take this key.

12058.5 -> This key I'll paste it here.

12063.2 -> I'll save this key now.

12064.952 -> Now what I did guys

12066.407 -> in my public eye cream even temp file.

12071.38 -> Okay now go back to the ec2 again.

12075.2 -> Please click on correct note of public IP the private IP.

12078 -> So we'll try to correct.

12078.9 -> So private IP through public what we are doing here.

12085.2 -> True public are trying to access private.

12088.184 -> Okay, so I'll write this ad I'll get the pem file.

12092.353 -> We just created it is my dot m.

12098.3 -> See you guys.

12099 -> I'm able to access my private through public my private

12105.769 -> to public but if private try to access internet then thing.

12112.4 -> google.com why we're not there is not able to log

12123.1 -> into private private one.

12125.2 -> It's a one only to be

12126.435 -> to basically up with your permission to the file.

12129.83 -> The vampire permission chmod 400 all steps are there as well

12134.8 -> now you are in a private install see?

12140.3 -> Now try to Ping Google

12141.597 -> from here from private and trying to access the internet.

12146.6 -> See you guys.

12147.9 -> I will not get any response from Google

12150.7 -> because from private I told you from private.

12154.084 -> You cannot access the internet from private.

12158.5 -> We cannot access Internet.

12159.8 -> What should we do for that Nat?

12162.4 -> Let's introduce an at how we do that.

12166.3 -> it's a create an ad Gateway how you do that?

12172.6 -> Now subnet you should choose your subject.

12176.4 -> So your NAT Gateway your NAT Gateway will be launched

12182.5 -> inside public subnet.

12186 -> So it is a public subnet

12188.3 -> and I assign an IP to that and create

12191 -> so I can add Gateway guys.

12195.2 -> But not Gateway Aetna private out ever created

12199.6 -> in the public added in the private.

12202.2 -> Let's go back go to private Roundtable route.

12206.3 -> Edit add 0 dot 0 dot 0 dot 0 dot slash zero.

12212.5 -> not Gateway Save it now one does not get rid of God

12219.2 -> created it takes some time to learn and Gateway.

12221.6 -> Once this Nat Gateway

12223.215 -> is created your private can access the internet.

12227.5 -> You cannot access Internet and internet cannot success private,

12231.8 -> but from private I can access center

12234.027 -> that what I told you through this I did not get raped.

12237.4 -> I can access internet but no one can access the private.

12240.761 -> So guys we configure each and everything.

12243.114 -> Once that Nat Gateway is ready.

12244.9 -> We'll see that from Why would I want to explain turn it

12247.9 -> but no one from outside can access the not gate.

12251.8 -> This is the complete setup of EPC that we just did now.

12256.9 -> Let's see.

12257.5 -> My not get is ready.

12259.4 -> It's available go to that you guys already started bringing.

12266.109 -> How come basically

12267.661 -> because now tune at Gateway arm equal to exist.

12272.7 -> How to stop that because you configure

12274.611 -> that to how to stop you

12275.964 -> cannot go in directly delete a VPC directly.

12278.2 -> So you have to step by step

12279.7 -> how to stop first of all go to ec2 and terminate this easy

12283.86 -> to first of all be decision very first step.

12289 -> terminate both the ec2 instances stop Next Step go

12295.8 -> to your instance here.

12299.5 -> Now. First of all,

12300.717 -> you cannot delete this internet gateway

12303.317 -> or navigate away.

12304.429 -> You should go to loud table posts from Route table.

12307.7 -> No, disassociate all the things first of all,

12311.8 -> open load table submit Association edit remove

12315.9 -> that similarly In

12321.2 -> the routes edit remove the internet created.

12326 -> First of all remove the things one by one from route

12329.3 -> for so leader instances then remove from Route table.

12338.7 -> Then subnet edit.

12343.5 -> Disassociate that now all of them are free

12347.2 -> now I can leave public and private both route table.

12350.1 -> I can delete.

12353.3 -> needed now internet gateway first of all detach it.

12359.8 -> detach summarizing attached Gordon at Gateway Delete that.

12374.3 -> Not Gateway leading route table related.

12379 -> subnet subnets, you can select a subnet.

12385.5 -> I need the sunlight.

12387.6 -> Get it.

12399.003 -> Then with this something is usually associated.

12402.5 -> Not simply go to the EPA Tried

12404.4 -> reading with the directly select and eat that.

12410.7 -> Read my route table also get the also default out abilities.

12417.838 -> So guys your VPC is completely remove all the subnet

12422 -> your router table internet gateway and naturally.

12433.3 -> So the main agenda for today's session

12435.477 -> as we are going to discuss on the complete domain offered

12438.8 -> by AWS why we have to use AWS Lambda what exactly it is?

12443.4 -> What are different available

12445.338 -> as you gaze and how we can use Lambda?

12447.9 -> At the Eclipse IDE,

12449.3 -> and we will be looking at a small hands on

12451.795 -> on using Lambda function going further step by step.

12456.1 -> So first of all,

12457.198 -> if you talk about the computation service, then AWS,

12460.7 -> as you know is one of the not just one

12464.2 -> of the but it is

12465.6 -> the leading Global leading cloud computing platform.

12470.5 -> In the entire crew followed by Microsoft Visio

12473.8 -> and then gcp so aw started back in 2006.

12477.1 -> And since then it has been the leading platform

12479.8 -> for cloud computing

12480.917 -> where it offers more than hundred and fifty

12483.388 -> plus Services as of now,

12485 -> which ranges from iot blockchain

12487.8 -> from the competition Services database Services Troy services

12492.4 -> on multiple a rvr

12494.1 -> or gaming or iot.

12495.4 -> So there are multiple components on which it inverse is providing

12498.6 -> the service as a total number is more than Entity class

12502.2 -> and they all are completely structured

12505 -> over the cloud platforms.

12506.1 -> They that means we don't have to worry about provisioning

12508.9 -> any service week.

12510.1 -> If we have an application we can directly choose

12512.555 -> the configuration of servers

12514.018 -> that we need and then we can get application deployed on top

12517.3 -> of a diverse resources same way.

12519.2 -> We can have the entire store services.

12522.9 -> Based on category based on usage that we can get started with.

12529.1 -> And Adam Lewis has

12530.9 -> multiple domains multiple categories of services.

12533.843 -> One of them is the computation services.

12536.244 -> So these are main free service offered by a diverse

12539.322 -> in terms of computation.

12541.246 -> First of all, we have AWS ec2.

12544 -> So basically easy to is like a virtual cloud services

12546.715 -> whether it's like a virtual server.

12548.415 -> Let's say when we are trying to deploy the application.

12551 -> Obviously that application needs a server without a server

12554 -> it cannot run right?

12555.117 -> So same way easy to is a virtual server that we can.

12557.9 -> Probably like a virtual machine

12559.569 -> where we can choose our own Camp number.

12561.764 -> Of course, the amount

12563 -> of ram we can choose the image as a base operating system.

12566.7 -> We can choose a storage type.

12568.771 -> We can choose its capacity.

12570.622 -> We can choose the type and the determine C.

12573.7 -> We can choose every parameter

12575.6 -> and then we can deploy these virtual servers as a part

12579.3 -> of ec2 service model.

12583.1 -> So we were discussing on the computation services

12585.9 -> offered by AWS.

12586.965 -> So easy to is

12587.84 -> like a full-fledged service offered by AWS

12590.6 -> through which we can deploy multiple virtual servers

12593.8 -> like we have virtual machine whenever we

12596 -> are deploying any applications.

12597.715 -> We lead a virtual machine

12599.185 -> where we can Define the number of cores the amount of cram.

12602.341 -> We need the amount of storage.

12604.1 -> We need the type of storage the type

12606.3 -> of operating system any base a vice or we

12608.953 -> can say images the type of keys.

12611 -> We are going to use and the type

12613.036 -> of Of access level in terms of networking and security.

12616.401 -> That means we can Define every kind there is we

12619.4 -> can you find every kind

12620.9 -> of parameter by using the vi using the concept

12623.9 -> of virtual machine

12624.8 -> and then we can start deploying it for Posting Albert obligation

12629.4 -> that is what ec2 is all about easy to refers

12632.2 -> to elastic Cloud compute.

12633.9 -> Then we have been stocks abusing Beanstalk.

12637.8 -> We can we don't have to worry

12639.896 -> about launching the VMS and our own end.

12642.574 -> We only have so

12643.6 -> and that's why this is mostly used by developers.

12646.9 -> So being a developer

12648.3 -> if you are working on any code or node.js on Java on PHP.

12652.7 -> Now, we know that the if you have a dynamic website,

12655.9 -> if you have a PHP based code now,

12657.9 -> we want to deploy it on the servers

12660 -> that means before deployment of that code on the server's

12663.46 -> we do need to set up the environment first.

12666.069 -> That means we do need to configure the ESP servers we

12669.3 -> do need to to provision the entire easy to service

12672.7 -> and then only we can get started correct way as in Beanstalk.

12676.362 -> We simply have to upload an entire code and then we

12679.414 -> can let the code being a security one by one.

12683.2 -> That means we don't have to worry about provisioning

12685.5 -> of servers or solution of entire service.

12687.599 -> We can choose entire environment.

12689.2 -> For example, if we have a node.js application,

12691.4 -> we can choose node.js environment and then we

12693.6 -> can directly upload a code and have a diploid

12696.6 -> and that's an ease that we get

12698.568 -> with with Beanstalk and then we have Lambda.

12701.89 -> So Lambda is basically a server list Computing platform.

12705.5 -> For example, let's say when we are building our website.

12710.3 -> Let's understand a simple use case of girl Let's go back

12715.2 -> to our Notepad.

12718.5 -> And when you talk about serverless Computing platform,

12721.617 -> for example, let's say when we have a website.

12724.286 -> Let's understand the real-time use case.

12726.6 -> We have a vote travel based website.

12729.5 -> We have a travel by sub site.

12731.141 -> And now in that trial basis of side,

12733.2 -> we have developed a chatbot

12735.1 -> which are so users their preferences or

12738.2 -> if there are looking to buy to book a flight ticket.

12741.129 -> Then it automatically gets all the responses

12743.6 -> and then it transfers

12745.3 -> and then it transfers the same detail back to the sales team.

12748.4 -> It generates a decade automatically.

12751.2 -> So what we can do is number if we have a chat board

12753.7 -> where we asking the users for the responses.

12755.871 -> For example, we have asked them.

12757.471 -> Okay where they would like

12758.82 -> to go they have respond with the city name.

12761 -> Then we have asked them how many passengers at what day

12764.1 -> at what time which ill

12765.6 -> and they would like to prefer any food preferences

12768.5 -> NEC preferences and now

12770.3 -> once we have entered each and everything.

12777.5 -> Once they have entered each and everything.

12781.342 -> Then we want them to.

12783.7 -> then he want this entire piece of information to be sent

12786.9 -> either to the sales team to the sales team

12790.3 -> or we want them to be transferred to the CRM

12794.5 -> or we wanted to be processed

12796.5 -> and then we it has to be sent to the To The Escape

12800.2 -> of a ticket management system so that based on whatever responses

12804.2 -> they have recorded.

12805.317 -> We can generate a ticket

12806.723 -> and then we can send it occurred along

12808.9 -> with the payment link as well.

12814.4 -> So here we can choose now for this entire use case.

12817.748 -> We need a processing system.

12819.415 -> We need to process the piece of information and then we

12822.592 -> have delivered correct.

12823.81 -> So there are two ways of doing

12825.4 -> that either we can go ahead and deploy a full-fledged server

12829.299 -> that is easy

12830.1 -> to we can divide fulfil server for ec2.

12833.4 -> And then we can process a request from ec2.

12836.2 -> But when we are deploying easy

12838 -> to we have to deploy it by each and every component

12841.3 -> that means we have to define the image.

12843.9 -> Of the incest side.

12845.2 -> We have to configure the entire options

12847.4 -> for provisioning of servers.

12848.8 -> We have to choose a storage the key.

12851.3 -> We have to do everything correct way as and easy to

12855.153 -> as you know is Bill Doran all your second basis

12859.1 -> for example is

12859.8 -> if we had to pry the ec2 instance,

12861.4 -> then we are built on top

12862.9 -> of every are or every second depending upon the instant side

12866.8 -> that we have deployed.

12868.707 -> Correct and the moment our servers are on the

12872.1 -> for the we had to pay

12873.162 -> for the Entire durations our servers have been up

12875.562 -> and running even

12876.293 -> though they have been idle but as long as they are running

12879.1 -> we have to pay for it and for example suppose

12883.046 -> if processing the incision

12884.788 -> that requires takes days only 10 seconds

12887.9 -> and we are processing only five requests honor

12891.3 -> or we can sit every are now using this ad board

12894.946 -> via processing only five requests every hour

12898.4 -> and a single request.

12899.827 -> Let's say it it takes up to 10 seconds, right?

12902.775 -> That means any VR we are a requirement

12905.2 -> of trepidation of how much of how much time only 50 seconds.

12909.1 -> We need to process incomplete are incomplete are that means

12912.912 -> if we keep our ec2 instance

12914.683 -> Idol then just for processing requests for this 50 seconds.

12918.572 -> We need to pay for a complete one are of idle time

12921.858 -> for easy to correct.

12923.2 -> That means now if we press

12925.5 -> that see another way of handling the entire processing requests

12929.147 -> by using the service name as Lambda.

12931.205 -> So this is a symbol for Lambda.

12933 -> So using Lambda we can have the entire processing done.

12936.3 -> So Lambda is basically a serverless Computing platform.

12939.288 -> When we say server less.

12940.7 -> It does not mean that they are no servers here.

12943 -> Obviously the processing has to be done through servers,

12945.8 -> but here we don't have

12947.102 -> the requirement of deploying the servers at our own it.

12950.279 -> We can have the entire services

12952.1 -> to provide optimal we can see taking K

12954.2 -> by Lambda itself and then we can simply use Lambda

12957.379 -> to process the computation request and suppose

12960.3 -> that if the request was processed only

12962.494 -> four five point four That means we had to pay only

12965.4 -> for five point four second.

12967 -> Nothing less nothing more than that if

12969.2 -> the entire request If we have entire request being processed

12973.624 -> for supposed 3.2 seconds,

12975.5 -> that means we have to pay only for 3.2 second.

12977.749 -> Nothing less nothing more because here the billing

12980.2 -> for Lambda works on every subset K.

12982.5 -> That means the billing threshold

12984.2 -> is only 400 milliseconds for every hurry means.

12986.905 -> I guess we have to pay for it.

12988.67 -> So that's how it becomes

12990 -> a much much better much easier and much more efficient manner

12993.4 -> in which we can have this kind of processing done by

12996.205 -> using the serverless Computing platform.

12998.5 -> That is Lambda.

13003.5 -> Now why AWS Lambda?

13005.4 -> So Lambda is basically an automated version of easy

13008.8 -> to where we don't have to worry about the entire architecture.

13012.513 -> That means we don't have to worry about provisioning

13015.749 -> of the entire ec2 service.

13017.4 -> We have the data services taken care by a doubles itself.

13021.2 -> And then they are no now

13023.5 -> all the background tasks all the deployment security parameters.

13027.2 -> They all are taken care by a doubles itself.

13030.2 -> And that's where Lambda is.

13031.8 -> If we did like a serverless Computing platform meaning

13035.172 -> the developers didn't have to worry about which

13038.1 -> a diverse resource to launch or how will they manage them?

13041.401 -> They being a developer.

13042.754 -> We only have to worry about uploading our code

13045.5 -> to Lambda and then simply running it.

13047.617 -> That's it.

13048.2 -> We don't have to worry about any other component

13050.8 -> when we are working on it.

13055.1 -> And Lambda is also offered as multiple ezekias as well.

13059.3 -> So Lambda is also supported

13061.3 -> write Lambda is also supported by multiple SDK

13064.2 -> is as you case as in software development kits,

13066.7 -> for example, let's say we want to publish

13069.326 -> when we want to use Lambda.

13070.9 -> Then we don't have to even come out

13072.9 -> of our development environment.

13074.5 -> We can directly use

13075.7 -> the tool kits offered by by both by Lambda

13078.7 -> and as well as by being the suppose

13080.9 -> if you're using if you want to use Lambda or Beanstalk,

13083.6 -> and we have a tool kit available.

13085.2 -> That means we can install the tool kit for eclairs

13087.868 -> for visual studio core and then we can get started automatically

13091.7 -> that's the ease with which we get

13093.3 -> by using AWS Lambda services.

13097 -> So you can use both we can use the the SDK is available

13100.7 -> for eclipse and as well as for visual studio code as well.

13106 -> Alright, so first of all,

13107.4 -> let's see how we how the entire Lambda works

13110.4 -> and how we can create a function out of it

13114 -> and how we can launch it.

13117.8 -> Now opposite for let's see

13119.1 -> how weak how the entire Lambda service is structured

13122.8 -> and they have multiple IDs

13124.5 -> that we can use in order to get started.

13126.7 -> We have Eclipse.

13127.8 -> We also have Eclipse.

13129.235 -> We also have Visual Studio code as well.

13131.9 -> So we have SDK is available for both

13134.028 -> if you want to use any of these we can get started for example.

13144.5 -> And then we have Eclipse as one of the most popular ID.

13147.7 -> We have visual studio and when we have Eclipse,

13152 -> so now we have the IDS available.

13155.7 -> Like we have like lives.

13156.9 -> We have IntelliJ.

13158.207 -> We have visual studio.

13160.33 -> So the art the SDK for databases available for both eclipse and

13165.1 -> for Vision Studio as well so we can use any

13168.7 -> of these to get started.

13171.7 -> so first of all

13172.502 -> before we can get started we

13174 -> have to create a Lambda function not as simple use case

13177.214 -> is let's say we have a node.js application

13179.626 -> we have a PHP based application

13181.342 -> then we can choose the entire runtime environment

13184 -> in which you want entire photo be deployed

13186.4 -> for example here we have support

13188.3 -> from dotnet Dalgo Java node.js python

13191.7 -> Ruby we have python 3.7 to Python 3 .8

13195.5 -> as well 2.7 as well

13196.925 -> so we have multiple runtime supported by Nano function

13200.9 -> that we can Enough,

13202.9 -> right.

13203.5 -> So basically here we are going to create a complete now.

13206.1 -> There are three main options

13207.343 -> through which we can create another function.

13209.399 -> We can also from scratch

13210.549 -> that means we can create the entire function

13212.7 -> at our site at our own and we can use a blueprint blueprint as

13216.5 -> in a base code.

13217.6 -> That means these are templates

13219.8 -> for different applications out there like we have

13222.2 -> for kindnesses as a part of data analytical software platforms.

13225.7 -> We have the recommend file based on python.

13228.6 -> We have multiple microservices base position.

13231.4 -> Example if we are trying to develop a simple chat bot

13234.5 -> then we have the blueprint

13236.3 -> for Lex Lex is a is

13237.8 -> a chat board system service offered by aided mystery,

13241.511 -> which we can get started.

13244.7 -> So that's how these are different platforms that we can

13248.9 -> that we can see these are different blueprints

13250.6 -> that we can launch as a part of its entire program set here.

13256.5 -> So these are based on the entire blueprint here.

13259.8 -> We can choose accordingly

13261.2 -> or we can browse the entire server is a proposed three,

13263.9 -> which we can browse through.

13265.1 -> For example,

13265.7 -> if you have the requirement for the entire application,

13268.521 -> there's already built just like we have a GitHub Community

13271.5 -> where we get multiple so

13272.8 -> scored it has been submitted by different developers out there.

13275.926 -> So we have the entire public application repository that

13278.7 -> we can choose from or

13279.863 -> if you want to get started then we can choose

13282.3 -> or the from scratch.

13285.8 -> Now once we are now let's suppose as our use case.

13289.22 -> Now.

13289.5 -> What we are trying to achieve is as a use case,

13291.962 -> we can simply choose.

13293.085 -> OK we want to offer from scratch,

13295 -> then we can start off with them from scratch as well.

13299.6 -> Let's say as a part of a use case.

13301.567 -> Let's do one thing.

13302.7 -> Let's quit simple Lambda function.

13305.2 -> Now S3 as an object's or service offered by AWS, right?

13309.7 -> So now what we want whenever we are adding any object

13313.455 -> in S 3 S 3 is simple

13314.9 -> so it service offered by Arab rulers.

13317.2 -> We want that whenever we are adding any object in S3.

13320.2 -> We should be that particular object addition.

13323.396 -> This event should be processed by Lambda whenever we are adding

13327.9 -> any object this entire And should be processed by Lambda

13331.944 -> and then we should be receiving an email stating

13335.4 -> that something has

13336.6 -> the an object has been added into our bucket

13339.8 -> so that we can take necessary actions.

13342.2 -> So again, this is also an event-based process request

13345.7 -> whenever we are adding any object into our S3 bucket.

13349.105 -> We want the entire event should be processed by Lambda service

13352.965 -> and then it should be sending

13354.8 -> out an email through which we we should be getting notified

13358 -> if anything has to be

13360.1 -> If anything has to be added here, all right.

13364.511 -> So now I can erase this up.

13370.7 -> We have an S3 bucket.

13372.1 -> And now we are now we want to make sure

13374 -> that whenever any object is added to S3.

13376.741 -> We should be

13377.566 -> that particular event should be processed by Lambda

13381.006 -> and then we should be receiving an email by this and whether by

13385.135 -> this entire Lambda function,

13387 -> this is something

13387.7 -> that we are going to achieve as a part of our hands on.

13392.4 -> So before we can achieve this we have to create

13394.7 -> a function first.

13395.549 -> So for creating that function we can come down

13397.8 -> to our Lambda service now here first of all,

13400.7 -> we have to create the functions and all we

13402.8 -> can start from scratch.

13404.1 -> We can choose

13404.9 -> the Lambda function and then we can start from scratch

13407.7 -> if we want to start from scratch itself.

13410.8 -> Just a moment.

13413.3 -> So first of all, we had to search for Lambda.

13415.3 -> We can click on create function we can alter from scratch.

13418.2 -> Let's give it a name as S3 notification.

13422.3 -> Let's name it as SG notification

13424.236 -> because we are going to add the object in S3.

13426.9 -> And that's how we are going to respond.

13430.9 -> And now here we can choose the you here.

13432.9 -> We can give the function a name a zesty notification.

13435.794 -> Then we can choose entire runtime environment.

13438.3 -> For example, we want to we have a program code

13441.2 -> already already written in Python in node.js Java.

13444.4 -> We can choose entire runtime environment.

13446.7 -> Let's say we choose node.js for now

13448.7 -> as we have the application code on top of node.js

13452.169 -> and then we can click on create function here.

13456.9 -> Once we are done we can click on create function.

13463.4 -> So as you can see this in that function is currently

13465.8 -> created now we can scroll

13467.7 -> down we can choose entire runtime even

13471.1 -> after choosing on time beforehand.

13472.75 -> We can also change the run time at any point of time.

13475.2 -> For example, we have a complete function package in Java

13478.246 -> which then we can choose Java 11 and then we can upload

13481.161 -> the function package.

13482.254 -> If you want to write the code in Python,

13484.284 -> we can write the entire Lambda function in Python itself.

13487.2 -> If you want to run the code

13488.82 -> for node.js we can Define the code in node.js as well.

13492.3 -> Right and you'll be have to create the function here.

13495.6 -> So we already have a function pre-configured here

13498.824 -> that we can use.

13501.7 -> Now currently we have an application code

13504.199 -> on top of laptop.

13505.2 -> So here we can choose the region

13507 -> in which you want to start working on.

13509.037 -> For example.

13509.697 -> Currently we had to find a piece out one.

13511.9 -> Currently.

13512.464 -> We are not Virginia, correct.

13514.1 -> So obviously we have

13515.279 -> to change the region in which we are creating the function.

13518.7 -> So first of all, if we I not Virginia,

13520.6 -> we also have to change the app the region code

13523.9 -> North Virginia as us - East one.

13526.9 -> So we have to make sure that the region is correct

13530.7 -> because again You have a different region selected

13533.15 -> and we are green.

13534.047 -> If we are deploying the function some other region then

13536.9 -> that will create issues.

13538.2 -> Correct.

13538.7 -> So you have we had to make sure that these both remain same

13541.9 -> and then here we have to add here.

13544.1 -> We have the end of function created

13546.2 -> so that we can this function

13547.6 -> will be sending out an email just a moment.

13551.7 -> So this function is going to create the salon

13553.8 -> and email having down here way

13555.886 -> where we can Define the entire body as

13558.4 -> in the message body here.

13560 -> We can Define the subject whatever we need

13562.4 -> to Define and for sending the email we have to enter

13565.8 -> the email address

13566.908 -> that we have verified using any other service offered

13570.3 -> by Edibles namely SES.

13574 -> So here let's say we want to send an email we can specify

13577.556 -> the email address.

13578.692 -> Let's say we want to send the email to us we can Source

13582.1 -> we have to refine

13582.801 -> the recipient's email address the code here down here.

13587.751 -> We can Define the to address.

13589 -> Let's say we enter

13589.9 -> our own address to get to receive the same, Maine.

13593.6 -> And now this is a email

13595.173 -> that will be sent as the to address

13597.5 -> and here we have enter the address of the recipient.

13600.7 -> Let's send it to ASL as a part of a Hands-On.

13604.8 -> Now as a good practice,

13606.7 -> we should always be saving the code.

13608.785 -> Once we are done and then we can click on Save function.

13612.113 -> Remember.

13612.643 -> Remember the entire code has to be correct?

13615 -> Because even if there is a slight mistake in India,

13617.8 -> the entire code the function is not going to be saved now

13621.9 -> once we have the function

13623.7 -> created then we can test the function as well.

13626.9 -> If you want to test it we can choose

13629.166 -> event template we can create

13630.979 -> in that event a event Let's see we same way we create the in

13634.8 -> I said in installation script.

13636.3 -> So here we can choose the entire event type

13639.5 -> or we can choose any of the event template.

13641.6 -> For example here.

13642.4 -> We are testing for S 3 S 3 for put request.

13644.953 -> So here we have

13645.864 -> the entire testing template already available.

13650.9 -> If you want to use this one,

13652.3 -> then we can use it or we can customize it exactly as

13655.186 -> per the requirement.

13658.1 -> Now if you want to use it,

13659.4 -> we can click on create we can name this as S3 test.

13671.5 -> If you want it on the test here we can click on run test.

13674.334 -> If everything is correct,

13675.6 -> and we would be able to see the entire education return

13678.6 -> as succeeded and here we can see the map the memory used

13682 -> and the time required

13683 -> for running this entire test code here.

13684.9 -> It was almost nine seconds.

13689.3 -> So now the entire code has been added and tested as well.

13693.9 -> So now we can use the same function

13695.9 -> to send us an email whenever we are going to add any S3 object.

13700.5 -> So let's go back to our SG bucket.

13703.2 -> So first of all,

13704.182 -> we have to create the entire function here

13706.7 -> what we have done and now we are going to use this function

13709.6 -> for Lambda to get an email whenever any event is triggered

13714.4 -> for RSV bucket, right?

13716.335 -> So in Services now we can move back.

13719.1 -> S3 simple storage service and here we can click now here.

13725.5 -> We have to choose the same the bucket

13727.617 -> which has been deployed

13729.1 -> in the same region as in which we have the function deployed.

13732.9 -> So we did create the function North Virginia.

13735.1 -> So we have to choose a pocket available in North Virginia.

13738 -> So let's say here we can choose is bucket.

13741.6 -> We can see the bucket being deployed and now we want to.

13747.4 -> Get notified for any object being added to this bucket.

13750.1 -> So first of all,

13751.1 -> we have to Unable the event-based property

13756.4 -> so you can scroll down

13757.752 -> we can go round 2 we can go to the properties Tab

13760.796 -> and then you can scroll down and events.

13763.3 -> We can find the events the event

13765.307 -> properties So currently we have one event already added.

13768.7 -> So let's delete

13769.537 -> that just to avoid confusion and now have to start from scratch.

13773.3 -> We can click on add notification and here we have to choose

13777 -> the notification that means the event type as a fall.

13780.2 -> They are multiple events supported that from which

13782.823 -> we can get notified.

13784.04 -> For example, we want to get notified on put event.

13787.1 -> So basically these are all actions put refers

13789.9 -> to whenever any object is added.

13792 -> So when we start discussing or multiple policies,

13794.541 -> we are going to discuss her path.

13796.288 -> So for every resource,

13797.585 -> we have multiple actions

13799 -> like we have read actions right actions and put

13801.944 -> is a national billable in the read operations forestry.

13805.469 -> That means whenever any object is being added

13808.341 -> and that is a for us products.

13810.5 -> If we are

13811.2 -> if we are trying to add anything we want to get anything else

13814.2 -> when we have put object get object

13816.8 -> of different options available.

13819.3 -> So if you want to get notified for every time we add any object

13823.4 -> we can use put here we can add prefixes.

13826.099 -> For example, we have a folder by the name of images

13829 -> and now we want to be notified whenever any object is added

13832.7 -> only to that folder not to every other folder

13835.288 -> in the same bucket,

13836.402 -> then we can be specific for that protects itself.

13838.964 -> For example, we have If some documents,

13841.252 -> we have a folder by the name of documents now,

13843.9 -> we want to be notified whenever any particular object is always

13847.6 -> added only two documents not to the other folder.

13850.466 -> Then we can be specific.

13851.9 -> If you want to be specific that we want to be notified

13855.486 -> whenever any spatial extension files are added.

13858.702 -> For example, we want

13860.1 -> to be notified the whenever if we add dot PDF documents,

13864.2 -> we add MP4 videos.

13866.3 -> We add the Json log files.

13868.5 -> We add multiple estimates.

13869.907 -> Trying to whatever extension we want to be notified.

13872.907 -> We can choose a recording grief.

13877.1 -> And then we can click on then we can choose

13879.9 -> the notification type as Lambda function.

13882.5 -> We can choose the function type as S3 and now click on Save.

13887.8 -> As you can see this event has been currently saved

13891.5 -> and now we can start using this event.

13894.3 -> Now whatever whatever Lambda function we

13896.8 -> have associated with it.

13898.259 -> We would be able to get notifications on top of it.

13903 -> Not foreseen this in done down the function implemented.

13906.631 -> We have to go ahead and add some objects.

13909.2 -> So let's scroll up.

13911.1 -> In overview for the bucket.

13912.801 -> Let's add any objects that we can get notified.

13916.6 -> We can click on upload.

13920 -> So let's say we add any file here.

13921.65 -> We can choose any file.

13922.98 -> Let's add a simple key file.

13924.6 -> Click on ADD next we

13927.4 -> can keep the class the same we can click on upload.

13930.698 -> And now one key file is currently being uploaded

13933.8 -> in the bucket.

13936.7 -> Sighs against here of key file has been currently uploaded now

13940.438 -> if you come down to our email we would be receivable to receive.

13945.2 -> An email that has been sent to us from Lambda function.

13950.1 -> And we all serious we have the same function

13952.47 -> that we have created email

13954 -> from Landa and an object has been added to S 3

13963.1 -> so the mean is India for today station is

13965.1 -> we are going to discuss on the need for data pipeline.

13968.8 -> We are going to discuss on what is

13970.7 -> that he dated a pipeline is what are the different components

13974.5 -> available in data Pipeline

13976.5 -> and how we can have the entire pipeline.

13980.1 -> Diploid so now let's get started.

13984.3 -> So first of all,

13985.293 -> let's discuss only need or reader pipeline.

13987.9 -> Now listen sign is by a hypothetical example.

13990.7 -> So for example down the main goal

13992.931 -> of any business currently

13994.7 -> on Pinterest the main goal is to improve the business

13998.455 -> by targeting content

13999.831 -> because Pinterest

14001 -> as you know is a really good content marketing platform

14004.4 -> where we can design

14005.6 -> which is highly useful for Creative professionals

14009.6 -> so that it can upload the designs a paddles

14012.2 -> and they can build a community

14014 -> and then They can get the right target audience

14017.347 -> by who are looking for that particular work.

14020.289 -> They are currently doing.

14022.6 -> Tying all do not we

14023.9 -> can have multiple goals here as well as we have can have gold

14026.9 -> to where we

14027.5 -> can manage application application efficiency,

14030.3 -> and then we can improve the business faster

14032.558 -> but at a cheaper rate,

14033.794 -> so these are main three goals

14035.5 -> that we are trying to achieve as a is as the example right now.

14039.6 -> The problem statement here is again in terms

14041.794 -> of problem statement we have now,

14043.758 -> there's a huge amount

14044.994 -> of data stored in formats in different formats as well.

14048.1 -> So preprocessor processing storing migrating

14050.8 -> and deed by reading the entire.

14052.7 -> That becomes complex,

14054 -> especially when we are talking about unstructured data set.

14057.258 -> So when we talk about data set,

14059 -> then we have 3 times structured unstructured and semi-structured

14062.8 -> and majority of the data coming in

14064.779 -> from the social media platforms.

14066.662 -> They are highly highly structured

14068.9 -> or same wind same scenario semi-structured as well.

14072.7 -> And then here we all do in terms

14075 -> of these social media platforms.

14076.9 -> We have to have a real-time data for registered user.

14080.1 -> We need web servers logs for potential.

14082.633 -> Sirs and demographic data for login credentials

14085.7 -> along with sensory data and third-party data sir.

14089.8 -> So we are different formats of the another now,

14092.2 -> these data are all available in different formats.

14095 -> And again,

14095.648 -> that's why the entire processing taking the storage the migration

14099.8 -> of data from one point

14101.366 -> to the other is also going to be complicated.

14104.7 -> It is not going to be an easy task and

14107.7 -> because again for real-time data

14109.9 -> for registered users we can use the service.

14112.7 -> All as dynamodb so dynamodb is basically used

14116.092 -> for unstructured data set

14118.1 -> where we can have schema-less data set stored

14121.7 -> and then we can do try will begin a fun time to leave

14124.831 -> and live and I give me camera driver files

14127.3 -> at any point of time.

14128.6 -> We can easily do

14129.606 -> that and we have web server logs for mediating laws and

14133.113 -> that too in a cost-efficient service we can use

14136.1 -> something called as

14137.7 -> well as three is a simple sort service

14140.546 -> offered by a dress for store.

14142.7 -> being static data set Then for demographic data

14146.3 -> and login credentials,

14147.819 -> we can use a service

14149.2 -> called as Amazon RDS RDS fos to relational database service

14154.2 -> and then we have

14155.144 -> is three again for storing sensor data and third-party data

14158.574 -> set to maintain the coop balance between the cost and the price.

14163.7 -> So we have different solutions being offered

14165.649 -> for different problem statement

14167.2 -> that we have as a part of services offered by Beta

14170.428 -> plus and again here it is going to be a feasible solution.

14174.26 -> We can analyze the data

14175.843 -> and convert from one structure to structure format

14179.215 -> and the optimal solution would be to use a data pipeline

14183 -> which handles processing visualization and migration

14186.758 -> of data from its own age.

14188.6 -> That's a main solution

14189.897 -> that we can offer for these different problem statements.

14195.8 -> The meaning problem statement from this entire scenario

14198.976 -> is the data migration itself and suppose

14201.27 -> if you want to migrate data,

14202.758 -> we want to Simply store data in multiple locations.

14205.7 -> For example, we want to store the dynamic TV industry here.

14209.4 -> We want to store data from from our EPS columns into S3.

14212.8 -> They're making is he do that?

14216.1 -> And that's why we have to take to a think they help our service

14219.6 -> by the why offered by a diverse

14221.8 -> and in that cluster

14222.807 -> of hundred people a hundred fifty plus services.

14225.3 -> That is data pipeline.

14228 -> So first of all,

14228.965 -> let's understand what exactly a pipeline is

14231.5 -> to read a pipeline is basically a web service

14234.2 -> that allows us to process

14236.4 -> and move data between different a debased computation

14240.1 -> and Sewer Services as well as on-premise data sources

14244.1 -> at specific intervals few.

14246.1 -> So using in a pipeline we can Define

14248.302 -> if he's our suppose

14249.335 -> a the ec2 instance that we have been working on.

14252.1 -> All right.

14252.7 -> So now daily it can copy all the log files

14255.3 -> and store in the S3 bucket.

14257.1 -> And here we can only find the weekly does

14260.2 -> that mean it should launch

14261.873 -> and they are the complete data analysis and that can be mapped

14265.764 -> and that can process back.

14267.5 -> We can see forward with Amazon.

14269.6 -> ER e Mari Marcus elastic mapreduce,

14272.1 -> so Data pipeline.

14275.1 -> Again.

14275.8 -> We are connected.

14276.895 -> They can be used with multiple data stores.

14279.604 -> Like we have RDS dynamodb and then we have S 3

14283.7 -> so here we have our DS generative Ministry.

14286.387 -> It can be used with multiple competition resources

14289.5 -> that you want to deploy and again you can have

14292.758 -> you can have the entire European stored as a part

14295.7 -> of data store itself.

14298.5 -> Now as a first example,

14299.869 -> we can launch our data analysis

14301.641 -> where we can collect data from different data sources

14304.9 -> and we can perform the Emi analysis

14307.1 -> and DJ and we can generate weekly reports.

14310.4 -> If we have two different data coming in from different sources

14313.5 -> from Villanova TV,

14314.6 -> then we can connect them with the daily eay analytics

14317.775 -> that they can perform

14319.1 -> and then here we have bulk data coming in

14321.7 -> from S 3 it can also be prepared can also forces by The EMR

14327.392 -> and then we can simply comply we can combine

14330.643 -> multiple sources coming in and you with complete Mr.

14334.5 -> You can see my and the latest and then you can come

14337.482 -> and then we can use

14338.532 -> on the server so services for storing all the rock price

14341.571 -> for it all the important log files in work one by one.

14345.3 -> Now the main benefit of data pipeline again

14348.8 -> can be used to provide a drag-and-drop console.

14351.23 -> Where do we don't have to manage

14353.112 -> the file here and like all the other platforms.

14355.5 -> It is build on distributed reliable infrastructure

14358.766 -> that needs even in any kind of failures

14361.3 -> or we can say a pillow was the main server has been structured

14364.6 -> in such a way in such a manner in different regions and soon

14367.3 -> that means it will take

14368.7 -> the least amount of a Lover's and in case if we base

14371.9 -> that we can easily come back.

14375.4 -> Because again for large applications the Dante matters

14379.2 -> a lot because again

14380.15 -> if they are large applications and they also was down time

14383.092 -> of your few seconds,

14384.269 -> then that means

14385.1 -> that we are going to support a big loss.

14388.3 -> And it supports scheduling and other handling

14391.4 -> it simply distributes a work to one machine

14394.4 -> or many it is inexpensive to use

14397.176 -> and offers control over computational requirements.

14403 -> Alright, so now next is

14404.441 -> we have a red dress data pipeline components.

14407.2 -> So come so pipeline

14408.6 -> basically has three main core components available.

14411.587 -> Like we have pipeline definition.

14413.5 -> So basically using pipe losing pipeline.

14416.285 -> We can specify the business logic Orbiter management.

14420 -> Then we have pipelines that are beer

14422.5 -> when by proliferation we can Define data nodes

14425.3 -> activity schedules preconditions resources and actions.

14430.4 -> So basically without every component we

14432.82 -> cannot have a complete data management been done.

14435.5 -> So we have to Define

14436.5 -> where exactly data is located as the poverty data nodes

14439.561 -> then the activities which has been scheduled

14442 -> on to on that particular data set along with the time stamp

14445.429 -> then the order access

14446.726 -> that we have to take it for which all the resources is

14450.4 -> entire policy is going to reflect all can say affect

14454.2 -> and then what all the preconditions require defending

14458.7 -> Then we have to define the data pipeline

14461.028 -> where you can schedule it again use pipeline to run the task

14464.6 -> to perform defined activities

14467.4 -> and here we have pipeline components in senses.

14470.247 -> And then we have attempts there is hot.

14472.6 -> Wow, very visual bubbling up once we are going to configure.

14476.9 -> How are you can see

14478.289 -> how many are virtual instance we are going to use

14481.9 -> while surfing again the attack number

14484.502 -> of attempts and then we have to ask - of course.

14487.9 -> So again, it will simply out the Edibles Europe

14490.7 -> or pipeline for task and then perform those tasks

14494.3 -> so it can be pipeline scheduled has an egghead

14497.2 -> can impact a stroller for sauce.

14501.2 -> And then whenever you going to shoes are being fulfilled

14504.1 -> in the then only the entire process going to be deployed.

14508.1 -> And again here when we deploy

14509.571 -> when we are following a tab to see the pipeline for tasks

14512.6 -> and begin to form these given to us as a part

14515.2 -> of the defy primary.

14516.422 -> We can Define the entire schedule tasks for pipeline.

14519.8 -> We can retire the remaining pipelines we can Alligator

14524.3 -> able to specifically going to fold that up.

14527.354 -> We can simply use a strainer to call 240 Poland

14530.665 -> has then again here

14531.972 -> if the entire task has already been sasiegel,

14535 -> then you can simply ask the you don't have to report

14538 -> type any time is done.

14539.7 -> So that's how we know

14540.7 -> that component of data pipeline is structured.

14543.9 -> So now we will be now we are going to look

14546.3 -> at the hand-sewn on top of it.

14548.4 -> So now let's get started on icon the our discussion

14551.7 -> on a service named.

14552.994 -> And as data pipeline that we basically used for see

14556.4 -> how we can migrate our data set from one service to the other.

14560.9 -> And for example,

14561.9 -> let's say we have a be restored in S3.

14564.096 -> Now. We want to migrate a to

14565.823 -> from as a power of unstructured tables in dynamodb.

14569.007 -> We have some data stored in Dynamo DB

14571.3 -> and now we want to migrate it to the we can say to S3

14575.5 -> or for example from S3 to read Shiva shift back to back to S3

14579.8 -> and other services,

14580.947 -> then we can use a service provider.

14583.6 -> I tried so now let's see how we can get started.

14587.515 -> So let's do move back to our console.

14591.4 -> So now any console we have to look for a service name

14595.9 -> as data pipeline.

14599 -> So now just like we have just

14601 -> like we have been looking at multiple Services.

14603.9 -> We have to look for service name as the fight time.

14607.4 -> So as we have been using the same search bar,

14610.1 -> we can search for data pipeline as a service.

14613.492 -> Let's open it up.

14616.6 -> In case you have never you don't have

14619.111 -> any data pipeline deployed yet.

14621.2 -> We are going to see

14622.516 -> this Grand Suite and remember data pipeline is not available

14626.8 -> in every Service as of now.

14628.8 -> So data pipeline is currently available only in five regions

14632.5 -> and to see the reservation we can use the region link

14635.74 -> available on top.

14636.805 -> So you have we have it not Virginia,

14639 -> oreca Sydney Tokyo and Island

14641.9 -> so we have so we Orient

14643.6 -> and again we have only These are the little vision supported

14647.1 -> that you suppose

14647.9 -> if I can as a calm

14649.3 -> and still these Services which are not available currently,

14652.969 -> they are being deployed in multiple Pages

14655.446 -> because first of all for any new service is being tested

14658.806 -> in a selective region and

14660.37 -> if it is successful then only it gets a toy

14662.912 -> with multiple other regions has been said by step, right?

14666.3 -> So you have to get started we can choose any

14668.557 -> of the given region here.

14669.87 -> Let's say we start with God's words not budging item.

14673.3 -> So here we have selected your u.s. Operation has weakened

14676.858 -> state of Virginia to start deployment of our service

14680.1 -> and here we can click on get started out

14682.7 -> and here we can see here.

14683.9 -> We can Define the data pipeline by defined the name.

14686.9 -> That's a we can you find a name as the pipeline

14689.852 -> for for this opposed to how we are going to create

14692.967 -> whether a cup for the month of May 2020.

14695.492 -> So basically we don't mean

14697.255 -> it as a you can say any journal in here.

14699.844 -> We simply keep it restricted to the time.

14702.5 -> Of of job that you're going to create.

14704.421 -> So for example,

14705.2 -> if you're going to create a pipeline for St. From S3

14708.5 -> to dynamically bees now,

14710.1 -> we haven't discussed on these services.

14712.2 -> Like what exactly is demo day be

14713.8 -> what exactly we mean by fresh biomass for tables.

14717.4 -> These are something

14718.6 -> that we are going to discuss in a photo sessions step-by-step.

14722.5 -> So first of all, we have we can build

14724.408 -> using a complete template the first of all here.

14726.9 -> We can define a description as well by be a description

14730.7 -> seen as every other stuff.

14732.516 -> We have if we are using the same if we

14735.1 -> if multiple other people are also going to be using

14738.35 -> the same vibrant

14739.4 -> and they should be aware of K what exactly this pattern

14743.018 -> was created for was the main purpose for it.

14746.6 -> Right?

14747.2 -> And that is actually is what we get.

14748.9 -> A Wi-Fi data pipeline is useful for someone

14751.288 -> who data pipeline is the see the used for migration of data

14754.7 -> from one service to yoga.

14756.01 -> So in case you don't want to migrate them one by one Mary,

14759 -> then we can use data pipeline for migration the suppose.

14762.719 -> If you want to buy page from any table in January p

14766.1 -> and save it to S3 or vice versa.

14768.4 -> We can easily do that using gigabyte card.

14773 -> And again again a reminder that I need.

14775.9 -> This is not a part of the again.

14778.6 -> If you are going for the desertification point of view,

14781.3 -> then this is not a part of certification

14783.594 -> till associate level.

14784.709 -> But again, this comes as a power of discussion

14787.1 -> when we are going for a professional Level Training,

14789.8 -> but not till associate level of certification.

14792.2 -> But in case you want we are going

14793.9 -> for any Enterprise solution we should be well aware

14796.4 -> of how things are being deployed Bellini prices

14799.5 -> by using this nervous.

14801 -> All right.

14801.6 -> So here we can Define the kite.

14803.272 -> So here we can choose a source as a bill time.

14805.7 -> We we can should be we can choose from

14808.196 -> if you want to get done a simple see like a man

14811.3 -> to create a complete template from scratch.

14813.7 -> So in case we are familiar with the entire see guy,

14816.4 -> we as in the Shell scripting

14817.8 -> that they can go ahead and use a sea life

14820.418 -> all quitting attack data set or we can export

14823.7 -> if we have requirement or working with dynamodb.

14826.9 -> So they are able to be now.

14828.464 -> We haven't discussed an anomaly be yet.

14830.7 -> So then We is basically a nosql service offered by area press

14835.5 -> which is useful for transferring

14837.604 -> which is useful for unstructured data set.

14840.3 -> So here we can Define the entire River set in terms of rows

14843.837 -> where we can have a password access to data set

14846.601 -> as compared to a traditional database.

14849.121 -> We can have a complete schema-less structure

14851.7 -> and then we can deploy

14853.2 -> and then we can deploy the entire Dynamic we

14855.932 -> can see unstructured data set as a product table here.

14860 -> So here we can choose from any if we

14862.227 -> if we have any in penny back up now one speak suppose.

14865.635 -> They are today.

14866.6 -> We have a today we did explore our damn rivet able to S3

14870.5 -> and after a while for example suppose

14872.8 -> after 1 week after three weeks.

14874.8 -> Now we want to restore that.

14876.7 -> Please throw that table from the data

14879.1 -> that we have for it.

14880.45 -> Then we can choose

14881.665 -> import parenthetically backup data from S3,

14884.7 -> because the Hereafter is 14

14886.3 -> because various pouring it we have mostly safer you

14888.8 -> have mostly story.

14889.9 -> It has a backup only so therefore any point

14892.375 -> of time we can use it for if you want to share

14895.322 -> that occur with any other counter has we can easily do

14898.3 -> that because then we are going to get a complete

14901.2 -> as a shareable link using S 3 like we discussed

14905 -> so we can either use that thing or we can you

14907.7 -> or we can use the terrible DB backup to restore.

14911.4 -> I fit any new table at any given point of time.

14914.7 -> We can choose any of these different

14916.87 -> and every templates if we have a requirement.

14920.1 -> Out of using EMR cmrs is again,

14922.2 -> not a part of the discussion for the associative certification.

14925.9 -> But Emi is basically lasting mapreduce does

14928.3 -> that we have this

14929.3 -> like we have mapreduce components for big data.

14932.4 -> We have lost a plan to reduce bigger.

14934.736 -> We can use mapreduce cluster

14936.6 -> and we can manage our own battery structure itself.

14940 -> We can easy to that and then we have mainly can also choose

14944.847 -> how we can run the job for RTS ideas as

14947.815 -> in relational database service.

14950.2 -> Again, this is a service

14951.8 -> that we haven't discussed so far.

14953.974 -> But again,

14954.654 -> if you want not RDS is basically a relational database service

14959.2 -> that is offered by a terrorist.

14961.1 -> That is something

14962.1 -> that we are going to discuss in our next model itself.

14965.091 -> And RDS is basically used for Designing the entire databases.

14969.8 -> For example here we can choose from multiple database engines

14973.1 -> of code sap can choose from Maya DV we can choose

14976.7 -> from both gray

14977.827 -> or Aurora or my skeleton in.

14980 -> This is we can choose Oracle database engines.

14982.8 -> We can choose Microsoft SQL servers.

14985.1 -> So depending upon the requirement we can choose any

14988.041 -> of the given database engines

14989.9 -> and then we can copy the full res MySQL table

14993 -> to S3 or same way.

14994.5 -> We can we can do vice versa.

14997.4 -> That is we can import the copy from as you do more deeply

15001.344 -> into bodies as well.

15002.685 -> Or we can copy the incremental copy just

15005.3 -> that we have discuss the concept

15007.2 -> of incremental stamp incremental backups.

15010.162 -> oops So your middle back up just

15012.5 -> as we have incremental backups in S3,

15015 -> right?

15015.356 -> See we have incremental backers available in August as well.

15018.9 -> So for every subsequent changes the same backup

15021.78 -> that will be stay will be stored and updated the site.

15025.108 -> We have discussed earlier and then we have low Des 3des

15029.6 -> into my car and do RDS my extra tables

15032.2 -> if we have a local file, for example,

15034 -> if we have a local SQL him in poor available in S3 bucket,

15038.3 -> then we can use a table in order.

15040.761 -> two Restore the areas

15043 -> that we have launched we can use any of the

15046.2 -> given our recent census.

15048.7 -> And then towards the end.

15050.262 -> We can copy the full RTS as fill into red shift.

15053.2 -> So that ship is basically again a service

15055.7 -> that we are going to discuss further or as a PowerPoint

15058.5 -> a subrogation training.

15060.2 -> So red ship is basically a data warehousing service.

15063.9 -> There is basically used for storing data

15066.5 -> if we have data coming in from multiple sources,

15069.5 -> let's say if we have data coming in from the Imperial coming in

15073.3 -> from multiple three suppose five different sources.

15075.8 -> I say we are trying to perform the analysis

15077.9 -> of say Data for Walmart,

15080.8 -> then we can store data set are coming in

15082.909 -> from multiple sources and that too in a centralized location

15086.1 -> and then we can connect that data warehouse

15088.987 -> to multiple platforms.

15090.5 -> I suppose if you want to connect

15092.2 -> that with machine learning class Falls with with

15094.63 -> with incline multiple bi tools

15096.436 -> that we have Tableau.

15097.7 -> We can connect that with qlik sense.

15100 -> We came with all tracks with Informatica.

15102.4 -> So we have multiple indications available that we

15105.251 -> can connect to as a power of data warehousing service.

15108.5 -> And see if you want to copy the RDS -

15110.94 -> felt able to read shift

15112.518 -> if you want to go

15113.64 -> for incremental copy incremental same as incremental backups.

15117.6 -> If you want to slow incremental copy of our is

15120.135 -> my school table into redshift.

15121.894 -> If you want to load data from S3 into redshift,

15124.6 -> then we can choose any of these Services iconically as

15128.593 -> per the requirement.

15130.3 -> So again, choose any of the given template

15132.35 -> for example suppose

15133.4 -> if you want to explore the anytime re table

15135.762 -> so you can choose export diary in a dynamic table here.

15138.803 -> And then we can juice.

15141.5 -> Not for example suppose if you want to maintain

15143.95 -> if you want to strip any incremental copy here.

15146.9 -> Okay, for example here,

15148.1 -> we want to maintain any criminal copy here for RDS.

15150.9 -> So as you can see are here in RDS,

15152.9 -> we can choose the entire column name.

15155.3 -> You can choose the MySQL credential

15157.3 -> that we have generated for our entire account.

15160.319 -> We can choose Eda output folder

15162.4 -> or would St. Folder as in the bucket name,

15164.654 -> right suppose if we

15165.704 -> have a specific Market we can choose from we can

15168.3 -> for browsing we can choose the entire S3 buckets now,

15171.3 -> We can see the list of all the available packages we have

15174.3 -> right for example sap want to use this one every 26

15178.2 -> and if you have any specific folders,

15180.5 -> we can see we have poulos policy.

15182.6 -> We have folders for financial reports.

15184.4 -> You can choose any of the green folder click on select.

15188.1 -> So here we can see the draft folder has been selected.

15190.846 -> That means if we enter the credentials

15192.823 -> for the RDS instance

15194 -> that we had a ploy we can choose the output as 3 folder

15197.545 -> and then we can apply the solution accordingly

15200.6 -> and then we have defined the RSV MySQL user name.

15204.4 -> That means the database username here.

15207.1 -> We have to choose the instance type

15208.8 -> in which we are going to use the used for the migration.

15212.1 -> Then we are going to do is to specify the

15214.1 -> in society and Society

15215.687 -> hasn't the every service we Obviously is also covered with

15219.9 -> multiple re you can say instance sofa support.

15222.5 -> This guy.

15223.062 -> We deploy ec2 instance.

15224.5 -> We also have to deploy Artisans and then we can choose

15228 -> that instance in order to migrate the data.

15230.1 -> You're in S3.

15232.2 -> All right.

15232.9 -> So basically have you can migrate the entire schema

15235.7 -> the entire database here

15238 -> and then we now must be specified

15239.738 -> that then we can Define the entire schedule as well.

15242.37 -> It means when exactly were

15244.035 -> meantime aggregation to be happening

15246.138 -> so we can Define

15247.1 -> if you want to keep A pit manual

15248.64 -> that means we don't want to automate we don't want

15251 -> to define the complete schedule then we can Define.

15254.1 -> Okay, we want this to be integrated

15256.3 -> on a pipe and activation.

15258.2 -> It means if we go ahead and manually activate

15260.5 -> that they know be this is the migration will take

15263.6 -> place not on a regular basis.

15266.943 -> And then we again

15268.3 -> if you want to keep it on a schedule because generally

15271.472 -> we keep it on skinny with self then we get again

15274.391 -> Define we have to run this entire migration

15277 -> everyone week and that to add a specific time

15280.1 -> as we can keep the entire window open

15282.121 -> so that we can have the data migration

15284.2 -> and the util in that particular time frame itself.

15287.8 -> And then if you want

15288.843 -> to maintain laws for each and every activity here,

15291.4 -> we can enable or disable laws.

15293.194 -> So laws are something that we can also maintained

15296.017 -> by using another service

15297.385 -> that we are going to discuss as a part of ossification training

15301.101 -> that is called as Cloud frame.

15302.9 -> So Cloud layer is basically a full man

15305 -> a fully managed database

15306.8 -> or case a log Management Service

15308.836 -> through which we can maintain the dog activity

15311.64 -> of a Japanese activities

15313.151 -> happening for the entire a deduce account from any user

15316.462 -> from any region and For

15317.873 -> every heated operations happening for every service.

15321.7 -> We can also use the entire application

15323.777 -> for mending the record as well

15325.517 -> that has been generated from this career pipeline.

15328.5 -> For example, if you want to maintain your load,

15330.9 -> of course for the operations team to know

15333.452 -> in case they has been

15334.6 -> some failures then they can use these laws quality references

15338.5 -> or if you want to refer to any other laws.

15342.3 -> Then we can also do that by using the dialogue

15345.1 -> that will be saved in the given folder

15347.2 -> that we can specify your we can easily maintain that.

15351.7 -> And then we have and then we can Define

15353.738 -> the security access that is again,

15355.705 -> if you want to be specific for any particular rules roles

15359 -> as we had discussed it is simply

15360.717 -> gives the access to power one service to the other

15363.6 -> if we are going to add

15364.887 -> if you are going to create a complete schedule report

15367.946 -> let every our earliest private.

15369.77 -> No problem.

15370.4 -> We can save some data

15371.5 -> in history then obviously we have discussed

15373.6 -> that we need to make sure

15375.253 -> that the audience roles are also defined.

15378 -> That means we have to make sure you have a rule defined giving

15381.1 -> the access to the RTS to write data on top of St.

15384.288 -> Because if you don't do that,

15386.051 -> this is not going to generate

15387.788 -> or you can say write anything on history as being discussed.

15391.258 -> So for one service

15392.287 -> to communicate with the other services,

15394.5 -> we have to make sure

15395.5 -> that we are giving the right set of credentials and RD and rolls.

15399.155 -> We simply allow us to do that.

15400.747 -> So if we keep a default again, it can simply read our own.

15405 -> Gold and then have it the poster and then we can use task task

15409.7 -> as we have been discussing

15411.2 -> that is one of the most important component

15413.472 -> for any application

15414.504 -> that we are going to deploy so we can maintain the company

15418.1 -> so we can maintain the source as a part of the application

15423.7 -> that so that we can choose that particular app.

15426.4 -> We can for example

15427.3 -> if we had deployed 50 different resources

15429.9 -> for an application including this entire data pipeline,

15432.811 -> then we can see the entire.

15434.4 -> I have a list of all the resources

15436.141 -> at once we can see

15437.287 -> that that billing as well

15438.879 -> and we can have a complete control over a solution

15442 -> when we are combining them by the come set up touch.

15451.2 -> So we'll be starting off with the first service

15453.8 -> which is a cloud formation.

15455.4 -> So cloud formation is great automation tool

15458.525 -> that helps you provision Resources by using Json

15461.783 -> or a Hamel scripts.

15463.1 -> So essentially you supply Script to the cloud formation service

15467.026 -> and cloud formation service revision all the resources

15470.383 -> that we are specified in the script.

15472.6 -> So it helps you treat infrastructure as a code.

15474.9 -> We're in now

15475.5 -> that you're treating your infrastructure as a code,

15478 -> you can have repeatable architectures on the fly.

15480.9 -> So services like cloud formation are very widely used to build

15486.1 -> your Dr. Environments

15487.521 -> on the Fly subject to our to use and our pews

15490.5 -> what your company has committed

15492.46 -> to your internal and external clients.

15494.8 -> It's then we'll be talking of various options

15498 -> or services available within opsworks services.

15501.2 -> So again, the principal use cases for services

15504.8 -> like Ops for that.

15506.4 -> They help you to manage the configuration state

15509.298 -> of your entire application.

15511.008 -> So imagine you have thousands

15512.847 -> of servers running so managing the configuration state

15516.272 -> of your application can quite be challenging.

15519.039 -> So tools like Chef automate stack and poverty Enterprises.

15522.622 -> These tools actually help you too.

15524.517 -> Manage the configuration State and Nation to that.

15527.4 -> They also help you to manage the entire life cycle

15530.129 -> where in these tools help you to write from the provisioning

15533.6 -> to managing deployment of code managing configuration state.

15537.23 -> So they help you manage the entire play cycle.

15540.1 -> The first service

15541.1 -> that will be talking about is cloud formation

15543.7 -> and cloud formation is kind

15545.512 -> of mother of all Automation Services within AWS

15548.6 -> and that helps you

15549.845 -> essentially to manage various infrastructure components

15553.458 -> that your In uses in the background,

15555.8 -> so it is very good for the river you need reputable environment.

15559.3 -> So I've seen a lot of organizations.

15561.144 -> They actually build scripts to provision

15563.2 -> environments on the fly.

15564.4 -> So for example,

15565.201 -> you ate environments where only the customer has the access

15568.3 -> to food won't needed for full-time basis.

15570.8 -> So you can build these kind of environments repeatedly

15573.994 -> in a similar fashion

15575.249 -> and you can provision them and couple of minutes

15578.2 -> as we see so it's a service

15580 -> that helps you model and set up your resources

15582.9 -> so that we can spend less time.

15584.8 -> Managing those resources

15586.3 -> and rather use more time focusing on your applications

15590.293 -> that run in AWS.

15591.5 -> So essentially we will be creating

15593.429 -> templates that describe all these resources

15595.91 -> that you would want to provision

15597.8 -> like ec2 instances RDS instance has your VPC

15602 -> and cloud formation would take care of provisioning

15605.109 -> and configuring those resources.

15607.1 -> So in that if you're using a service like cloudformation,

15609.9 -> you really need not create resources on individual basis

15613.4 -> and configure them.

15614.6 -> And the service is smart enough to figure out

15616.8 -> the dependencies as well.

15618.27 -> So essentially helps you treat infrastructure as a code

15621.191 -> and can provision all the services that we have spoken

15624.1 -> about on the basis of a cloudformation template,

15626.8 -> which is essentially a Json or XML document.

15629.651 -> So helps you quickly replicate your infrastructure

15632.9 -> easily control and track changes to your infrastructure.

15636.4 -> So essentially we build a stack for you,

15638.978 -> which is the outcome

15640.3 -> of the template that you supply to the cloud formation service.

15644.5 -> So as I said,

15645.187 -> it helps in automating and simplifying the task

15647.721 -> of will be really unpredictable creating group

15650.2 -> of related resources

15651.376 -> that are part of your application.

15653.329 -> So there are three components to it.

15655.4 -> The first one is the template itself,

15657.6 -> which could be a Json or XML formatted file.

15660.393 -> So Jason en gammal,

15661.627 -> they are open standard formats and pretty easy to write.

15665.6 -> So Amazon maintains pretty good number

15667.918 -> of sample architectures on their portal

15670.3 -> so you can always most

15671.499 -> of the time you can always find pre-baked templates.

15674.5 -> Then the output

15675.437 -> as I said a stack

15676.5 -> which is grouping of resources that you have specified

15679.8 -> in the template and you can apply updates to the stack.

15683.2 -> So let's say you opted in

15684.795 -> for a specific instance type and all you want to upgrade it

15688.41 -> using cloud formation.

15689.846 -> You can apply changes to the stack.

15691.983 -> Also the services smart enough can detect errors.

15695 -> We're in let's say the cloudformation service due to a

15697.9 -> here in the script was not able to provision RDS service,

15701.9 -> but already the service has provisions.

15704.7 -> The underlying VPC various other ec2 instances load balancers

15709.2 -> Auto scaling group.

15710.606 -> So Services detects

15711.947 -> that the template is failing at a point.

15714.7 -> So the default action is rollback.

15716.948 -> So what we'll do is it

15718.475 -> would deep Vision all those resources

15720.886 -> that it has provision.

15722.3 -> So we give you an error

15723.766 -> so you can fix that error and them run the template again,

15727.6 -> then the resources

15728.6 -> that will get based on what you have specified.

15731.211 -> They will be in the desired operational State

15733.8 -> and Actively you can manage all those resources as a group.

15738 -> So templates is the key thing.

15739.624 -> We're in based on what you have specified

15742.079 -> in the template and supplied to the cloud formation service.

15745.609 -> You can service

15746.5 -> or provision those resources so major elements

15749.777 -> of your cloudformation template

15751.703 -> would be format version description parameters

15754.9 -> meta data mappings conditions resources transform and output.

15758.9 -> So out of these only resources is the mandatory section

15762.6 -> that you need to specify.

15764.3 -> The template because cloud formation has

15766.972 -> to know what resources you are trying to provision.

15770.4 -> Rest all are optional description again,

15773.414 -> what the script is all about parameters is

15776.568 -> a way wherein you want the user to enter inputs

15780.1 -> during the execution of that particular script.

15782.805 -> So let's say we're giving the user

15784.782 -> who's running this crap a choice

15786.7 -> that during the runtime of the template you want

15790.009 -> to ask the user to specify a specific instance type.

15793.547 -> So we are giving you him an option to specify

15796.64 -> which instance he wants to provision

15798.989 -> so it could be two micro

15800.6 -> or any other instance type for that matter.

15803.1 -> Then you can specify

15804.542 -> what SSH locations that you want to allow.

15807.5 -> So again any input

15808.8 -> that you need from the user you will be specifying it

15811.858 -> in the parameter section.

15813.4 -> Then you have mapping section.

15815.5 -> Where a new map it's kind of a lookup table

15818.185 -> that to can Define within the script itself.

15821.042 -> And then there's the output section So

15823.5 -> within your script You want the cloud formation

15826.8 -> to publish specific outputs

15829.1 -> such as let's say ec2 instance public address

15832.4 -> that is associated with it.

15834.084 -> So you'll have to explicitly publish

15836.182 -> that so resources is the only mandatory elements

15839 -> that you need to specify within the cloudformation template.

15842.5 -> So description again,

15844.8 -> what the script is about the resources

15847.516 -> that are to be provisioning

15849.454 -> and then output is game set of values to be made visible

15853.4 -> after After cloud formation has finished executing the script.

15858 -> So let me show you a sample template.

15861.2 -> So this is a sample template

15863.117 -> where in the first part is the parameters part

15866.2 -> where in looking at the user to supply some information

15870 -> so you can specify what type of information you are expecting

15873.663 -> whether it's a number or a string

15875.617 -> and the default value

15876.7 -> that what we have said is M1 small.

15878.7 -> So if user does not specify

15880.7 -> which instance type to select the default will be selected.

15884.3 -> And we are forcing these allowed values.

15886.6 -> So user has option only to select

15888.8 -> from these instance types.

15891 -> Then is a mapping section.

15892.822 -> So in this case,

15893.892 -> we are specifying for a specific instance type

15897 -> whether we want in terms of virtualization,

15899.717 -> whether you want to use para virtualized or hbm's then again,

15903.616 -> the second mapping

15904.785 -> that what we are doing is depending upon the region.

15908.4 -> So if the region is let's say you are cease to on the a my ID

15912.422 -> that you want to pick up you'll have to specify the am IDs

15916.193 -> depending upon which region you are executing a specific Ami

15920.198 -> has to be picked up easy to is a region specific service.

15924 -> We will have to explicitly specify the am I then

15927.525 -> as I said resources is the mandatory parameter

15930.938 -> that you have to specify.

15933 -> So in this case.

15933.993 -> We are saying

15934.8 -> that the looking out for a ec2 instance

15937.2 -> and within the resources,

15938.752 -> what we are doing is we are configuring it

15941.4 -> and installing PHP onto it and to Cut the image ID.

15945.4 -> I am trying to capture the details based

15947.989 -> on the parameter that was specified.

15950.394 -> I'm using finding map and looking out for the region

15953.9 -> and the a my ID.

15955.3 -> I'm configuring the security groups are where an

15958.542 -> I'm enabling HTTP access for this particular instance.

15962.227 -> And then lastly in the output section.

15964.8 -> I explicitly want what is the DNS name

15967.6 -> that has been assigned to the instance and question.

15971 -> So what do you see on the screen is very similar to

15973.4 -> what we saw in the Template

15975.064 -> so pretty self-explanatory resources is the one

15977.9 -> where and they're not using mappings out here.

15980.3 -> We are simply indicating image IDs whatever the image ID

15983.764 -> is referred to instance type

15985.449 -> and the reference

15986.525 -> to keep are so key player within the parameters.

15989.409 -> We are asking the user which keeper you D like to use

15992.661 -> and then the output section you have just simply

15995.6 -> printing the instance ID

15997.2 -> that is associated with the instance

15999.341 -> that the service creates for you.

16001.5 -> So stack is the resultant output

16003.7 -> that you get Many executor templates

16006.309 -> with the cloud formation.

16007.957 -> So it is a collection of resources.

16010.2 -> So these resources can be created deleted

16012.9 -> or updated in a stack.

16014.3 -> And additionally you could have nested Stacks as well.

16017.486 -> Let's say you are using one template just to provision

16020.769 -> your underlying infrastructure components another template

16024.298 -> or stack to manage your application on top

16026.837 -> of the resultant stack

16028.2 -> that you have created you could have nested as well.

16031.2 -> We're in output of one stack can be passed.

16034.2 -> On to other Stacks as well.

16054 -> To go to the cloud formation dashboard.

16056.8 -> So make sure that you are

16058.288 -> in the right region in which you want to provision your resources

16062.3 -> through a lot of sample

16063.468 -> templates that you can play around with

16065.4 -> as I'll be just simply uploading the template

16068 -> that I have.

16072.7 -> So let's say I'm getting this tag as uat environment

16075.786 -> in the parameter section.

16077.3 -> We had the default value that was supplied was M1 small

16080.6 -> but we still giving the user an option.

16082.707 -> They can actually go ahead and change it.

16084.967 -> So now if I change the value T to my crew,

16087.3 -> so this should be passed on as a parameter

16089.711 -> to the cloud formation service.

16094.6 -> So you can set up a rollback triggers

16096.4 -> where in this would allow the cloud formation service

16099 -> to monitor the state of your application

16100.9 -> during creation and update.

16102.7 -> So by default behavior is to roll back.

16119.7 -> So even stabbed is the one

16121 -> that you would like to refer which indicates the steps

16124.632 -> that the cloud formation Services performing.

16127.429 -> So it is already created a security groups.

16130.1 -> It has started the process

16132.049 -> of initiating the sea to instance any resources

16135.5 -> that it would have completed.

16137.089 -> We'll see them out here in the resources tab,

16139.5 -> then you have output section.

16141.123 -> So this should be published at the end

16143.5 -> when the cloud formation has finished the visioning

16146.808 -> of all the Sources

16148 -> and based on what we had specified to be published.

16151 -> It will be published out.

16154.3 -> So we do see

16155.205 -> that the service has Vision ec2 instance

16158.068 -> along with the security group and in the configuration steps

16162.7 -> when we get the instance to the desired operational state,

16166.201 -> so it's create complete.

16168.1 -> So which indicates

16169.4 -> that the service has been able to provision

16171.5 -> all the resources in this case.

16173.2 -> It was a single ec2 instance.

16175 -> Now if you look at the Outlook stab we

16177.3 -> had explicitly published the DNS name of the instance.

16183.792 -> Also if I want to update the stack.

16188.2 -> So let's say I want to change the instance type.

16191.1 -> So let's say too small.

16196.5 -> So in the background

16197.706 -> what it does is it actually Compares

16199.813 -> with the templates one,

16201 -> which was Run for the first time

16202.6 -> and the one that we are supplying right now.

16205.6 -> So it will look out

16207 -> for the changes and we can very clearly see resource type

16210.7 -> that needs to be modified is ec2 instance.

16216.9 -> Church will actually go ahead and terminate this resource

16220.3 -> and then Louisiana known for us.

16239 -> So now we do see

16239.8 -> that the instance type has changed from T2.

16242.9 -> Micro 2T too small.

16252.7 -> Also note that since now we

16254.5 -> are managing resources as groups under Stacks.

16257.5 -> So all the resources

16258.758 -> that the cloudformation service Provisions,

16261.4 -> they're tied to the life cycle of the stack.

16263.959 -> So if I delete the stack all the resources

16267.4 -> that it would have provision would get the Meanwhile,

16285.4 -> DC cloud formation deletes the entire stack.

16292.2 -> So again, we are allowing the user to select

16294.735 -> the instance type.

16295.794 -> But this time we are going ahead

16297.469 -> where and there are asking the user to make this decision

16300.4 -> with the keys SSH location then mappings.

16302.916 -> We have already seen we're setting up mad instance

16306.1 -> in addition to various other VPC components as well

16309.9 -> in the resources.

16310.9 -> You see that we are specifying VPC

16313.22 -> so it will create a vbz for us.

16315.344 -> It will create subnets for us.

16317.4 -> It will provision internet gateways attached

16319.849 -> internet gateways make changes to the route.

16322.3 -> I will submit associations knackles.

16324.7 -> So essentially we spend about more than two hours

16328.1 -> in understanding we PCN over deployed.

16330.827 -> So now with the help of simple script,

16333.464 -> I can provision the entire underlying Network

16336.6 -> and other application components in couple of minutes.

16340.1 -> So in this case the elastic IP addresses being used.

16343.3 -> So again, it is up to us

16344.678 -> whether we want to use the defaults

16346.697 -> or you want to change them.

16348.3 -> So we'll run the script and we see the what is the output

16351.8 -> that what we get Selecting the instance type it

16362.4 -> will fetch all the keys available in this region

16365.3 -> and SSH location.

16366.7 -> You can explicitly specify which locations you want

16370.1 -> to allow try to keep it open at this point of time.

16386.9 -> So it has already created a vbc for us Define internet gateway

16391.4 -> made the association's of igw to your specific VPC.

16396.6 -> Today is the new

16398 -> between question that it has created for us.

16400.5 -> Then multiple sub Networks.

16405.5 -> You have internet gateway,

16406.902 -> which is attached to it now and still not reach the state

16410.534 -> where it has assigned a plastic iPad restored.

16418.8 -> It has already started the provisioning of the ec2 instance

16421.7 -> once instances available.

16423.3 -> It would be associated with the elastic IP address.

16427 -> So we do see

16427.6 -> that the service has allocated plastic IP address

16431.5 -> and that would be assigned to our instance in question.

16437.9 -> So the create is complete now and the output section.

16443.9 -> We have the desired output.

16445.863 -> So right from creation of the underlying Network,

16449.3 -> which is the VPC and configuring various other components.

16453.3 -> So under couple of minutes,

16454.888 -> we have been able to provision almost every resource

16457.7 -> that we had wanted to provision for our application Stacks.

16460.6 -> So a great tool for having reputable environments wherein

16464.043 -> you want to manage resources in groups,

16466.379 -> and I personally used it for building Dr. Environments.

16469.7 -> We saw that using build the entire environments

16472 -> in depending upon the scale and size.

16474 -> In less than 10 minutes or so so you can use this tool

16478.054 -> for variety of purposes.

16481.6 -> So moving on we'll be talking about various service offerings

16485.6 -> within AWS opsworks.

16487.6 -> So now we had an introduction on cloud formation,

16490.6 -> which is template driven provisioning.

16492.9 -> So if you look at this illustration scale

16495.24 -> of control and convenience again cloud formation is a great tool.

16499.1 -> But again, you need

16500.281 -> to have those scripting skills to build complex scripts.

16503.7 -> So if the environment is large so managing

16506.477 -> at the script level can get complex beyond the point.

16510 -> So on the extreme right wing Is you have the complete control

16513.445 -> where you implement

16514.563 -> the resources on do-it-yourself basis create

16517 -> individual resources managed their configurations.

16520 -> So this is where you have the maximum control.

16522.56 -> But if you want to move on more towards the convenience scale

16525.947 -> you have other services starting off with cloud formation,

16529.3 -> which again is more

16530.576 -> of a do-it-yourself model then moving on further.

16533.8 -> You have another two options available within AWS.

16537.2 -> The first one is AWS opsworks.

16539.8 -> There are three services

16541.27 -> that are supported with in Ops work one

16543.6 -> is Chef second one is puppet and third one is offshore stack,

16548.3 -> which is again implementation of Chef.

16550.6 -> So these tools allow you

16552.1 -> to better visual representation gives you a service layer

16555.6 -> where then provision your resources in much more

16558.939 -> better visual representation.

16561 -> Additionally, they allow you

16562.647 -> to manage the configuration state of your Stacks.

16565.3 -> So as I said earlier,

16566.409 -> let's say you have thousands of hours more to make

16568.998 -> a simple change to a properties file.

16570.7 -> How do you do it?

16571.9 -> So tools like this you can always achieve that

16575 -> and then lastly you have elastic Beanstalk.

16577.7 -> So this is a service from Amazon directly

16580.5 -> whereas it is.

16581.9 -> Well suited for organizations or pretty key man typically

16586.2 -> targeted at developers want to provision resources

16589.402 -> on the side very easy to use with so wherever you want

16592.764 -> to give complete control of resources to developers.

16596 -> So they and spin up environments on the Fly terminate them

16599.166 -> when you don't need them,

16600.555 -> so this is where you We'll be using in stock.

16603.1 -> So now with respect to managing your applications

16606.7 -> your applications reliability and scalability.

16609.611 -> They are very important

16611.1 -> and there are a lot of underlying operational tasks

16614.1 -> that need to be taken care of right from provisioning

16617.5 -> deployment configuration monitoring security scaling up.

16621.625 -> So as your application grows,

16623.8 -> these operational tasks can become more time-consuming

16627.804 -> and error-prone and do not like you trade off controller.

16631.456 -> For ease of him.

16632.5 -> So he needs a source that the service Provisions for you.

16635.384 -> You will still like to access that resource.

16637.6 -> So some tools actually don't allow

16639.384 -> that but Services were available within off so they allow you

16642.913 -> to have complete control over those Services.

16645.5 -> Let's specify what configuration management is.

16648.413 -> It is practice of code

16649.8 -> that is used to define

16651.062 -> and maintain the state of both your new and existing

16653.77 -> resources throughout their entire life cycle

16656.3 -> as we saw right from provisioning managing

16658.421 -> maintaining so venue provision your computer sources again,

16661.511 -> When you have series of activities to perform

16663.86 -> at the operating system or at

16665.563 -> the host level then configuring your application

16668.327 -> with respect to their specific configuration their dependencies

16671.974 -> and then ongoing maintenance would include new version

16675 -> installs wreckage updates

16676.693 -> new configuration new deployments Etc.

16679.4 -> So the need for services like absorb,

16681.65 -> as we have said helps you manage the entire lifecycle

16684.9 -> of your application and the help of offshore tools,

16688.6 -> depending on what we are choosing

16690.2 -> for we can manage It's

16691.666 -> pretty easy to use secure very powerful

16694.342 -> because now you have automated everything so chances

16697.794 -> of manual error are very less.

16699.9 -> So overall it increases your efficiency is

16702.749 -> and that results in enhanced productivity.

16705.6 -> So op zoek essentially is a configuration management service

16709.4 -> that provides managed Services of Chef

16712.1 -> and puppet both chef and puppet our automation platforms

16716.1 -> that allow us to use code to automate the configuration

16719.6 -> of our servers and offshore.

16721.488 -> Let us use chef

16722.5 -> and puppet to automate House services are configured

16725.5 -> deployed and managed across your ec2 instances

16728.517 -> or your on-prem compute environment optional

16731.4 -> gives you three solutions to configure your infrastructure.

16734.652 -> So when they had started off

16736.3 -> that started off with opsworks tax only

16738.8 -> which is implementation

16740.237 -> of open-source automation tool called Chef now you

16743.3 -> have offerings available for offshore thought

16746 -> Chef automate and another very

16748.283 -> widely used tool is puppet Enterprise.

16751.4 -> So as you saw in the console,

16752.935 -> we have three offerings option

16754.7 -> for Chef automate option for pop it into place

16757.7 -> and also stack so Chef automate

16760.5 -> it's again a fully managed configuration Management Service

16764 -> that host Chef automate

16765.9 -> which is a suit of automation tools from Chef

16768.918 -> for configuration management compliance and security

16772.4 -> and continuous deployment.

16774.133 -> So lot of applications

16775.659 -> that you see the build on the basic premise

16778.489 -> that your leases would be done almost based on real-time basis

16782.7 -> and support the concept of continuous integration

16785.764 -> and deployment to officers a service layer

16788.382 -> that they have built on top of Chef server

16791 -> and the service would automatically patch update

16794.6 -> and backup your Chef server.

16796.756 -> So option would eliminate

16798.7 -> the need to operate your own configuration management system

16801.787 -> or worry about it maintaining its infrastructure.

16804.334 -> So it will give you access to all the chef automated features

16807.451 -> such as configuration compliance management,

16809.742 -> which you can manage through chef.

16811.5 -> Ctrl or command line tools like knife

16814.5 -> and it works pretty good with the existing Chef cookbooks.

16818.6 -> So you'll opt for Chef automate

16820.7 -> if you are an existing Chef user.

16823.2 -> So Chef automate is compatible with cookbooks and recipes.

16827.5 -> So Supermarket cookbooks

16829.3 -> are referred to the Community Support

16831.6 -> or the community forums

16832.905 -> where in you can find a lot of cookbooks

16835.267 -> and recipes so recipes

16836.618 -> essentially that is the piece of code

16838.9 -> that you want to execute

16840.454 -> and cookbooks are Repositories for your recipes.

16843.6 -> So with a single to like

16845.2 -> Chef you can manage your servers they could be within the cloud.

16849 -> They could be outside Cloud.

16850.985 -> So with solution like Chef could have you can manage

16854.792 -> an entire distributed workloads using a single tool.

16858.5 -> So if you already are running a tool like Chef

16861.76 -> or puppet in your organization,

16863.8 -> so my recommendation would be to extend

16866.035 -> that to Cloud rather than opting

16867.8 -> in if you don't have then you can definitely look at off.

16871.308 -> Look for that.

16872.1 -> So cookbooks.

16872.822 -> We have already defined

16874.1 -> that they are essentially the containers for Chef recipes.

16877.6 -> So recipes they are synonymous to specific piece of code

16881.388 -> that you want to be executed at a given point

16884.348 -> of time cookbooks should also contain

16886.818 -> in addition to recipes additional files libraries

16890.412 -> or dependencies to configure your environments

16893.5 -> so recipes in Chef they're written in Ruby language,

16897.1 -> and essentially you will have a piece of code written

16900.1 -> in those recipes.

16901.131 -> He's so that piece of code could mean install and configure

16904.759 -> software components deploy our application call.

16907.7 -> In other recipes.

16908.9 -> They're very recently introduced support for puppet Enterprise.

16912.1 -> So again, it's a fully managed configuration Management Service

16915.3 -> that host puppet Enterprise and the shoot includes a set

16918.8 -> of automation tools from Puppet for infrastructure

16921.911 -> and application management.

16923.317 -> Also also maintains

16924.482 -> your puppet master server by automatically patching updating

16928.1 -> and backing up a ferocious servers and off Circle.

16931.2 -> In the case of Chef automated eliminates the need

16934.206 -> to operate your own configuration Management systems

16937.4 -> or worried about underlying infrastructure so off so

16940.4 -> could also give you access

16942 -> to all the underlying property Enterprise features,

16944.9 -> which you can manage through puppet console

16947.729 -> and it works seamlessly with your existing puppet code

16951.3 -> so you can choose officer

16952.862 -> for puppet if you are an existing property user.

16955.8 -> So this is again based on client server architecture

16958.869 -> where you have a designated master all the The nodes there

16962.3 -> are no puppet agent

16963.669 -> and you have specific configurations or rolls defined

16967.326 -> and at the puppet server these nodes pole

16970.139 -> the puppet server on periodic basis.

16972.6 -> So if you want to push some changes make the changes

16975.6 -> on the puppet server

16976.6 -> and these nodes would pull those changes

16978.8 -> and apply those changes.

16980.3 -> So where the abstract Stacks

16981.988 -> it lets you manage your applications

16984.1 -> and servers on AWS

16985.271 -> and on Prim so you can have a distributed kind

16988.2 -> of an environment

16989.2 -> where offshore stack can help you manage.

16991.346 -> Entire workloads.

16993 -> So let's talk about various components of obstacle stack.

16996.7 -> So the first component is the stack itself.

16999.3 -> So it is the top most level entity within offshore

17002.8 -> and essentially like we saw in cloud formation,

17006.2 -> it would represent set

17007.501 -> of resources that you want to manage collectively.

17010.395 -> So a good example

17011.4 -> for stack would be let's say you want to create a stack

17014 -> for Dev environment or uat environment

17016.151 -> where in various underlying components

17018.409 -> would only be applicable to that particular stack.

17021.4 -> And the second component is layers.

17024.1 -> So each stack will have at the bare minimum one layer

17027.405 -> and depending upon your application is the entir

17030.3 -> will have n-tier rather n layers in your application.

17033.586 -> So keep it simple would have a layer for load balancers

17037 -> a layer for web servers layers for app servers

17040.2 -> and player for database.

17042 -> So the idea here is

17043.2 -> that for each and every layer you will have

17045.8 -> different set of configurations that you may want to manage.

17049.4 -> So configurations would be Managed

17051.733 -> at a specific layer to any chain

17053.9 -> that you want to push through Lex a web layer

17056.5 -> or you're a player you can push those changes directly

17060.2 -> and that would be applied to all the resources

17062.875 -> within that particular layer.

17064.7 -> The third component is the instances.

17067.6 -> So compute resources from the Baseline

17070.446 -> for any application.

17072.1 -> So an instance could be of multiple types

17075.5 -> in auto-scaling we had spoken about so this is

17078.22 -> where AWS has performed a custom integration

17080.864 -> with With Chef wherein you can have twenty four

17083.57 -> by seven instances

17084.654 -> and these instances would always be up and running

17087.464 -> and available to you.

17089 -> Then you have time-based instances.

17091 -> So this is specific to shooting plan in order scaling

17094.4 -> where in based on a schedule of Cirque will increase

17097.7 -> and then based on the schedule

17099.447 -> that you have specified at volt decrease.

17101.8 -> Then you have load based instances,

17104.3 -> very similar to Dynamic scaling plan.

17106.6 -> We're in based on the thresholds that you have specified.

17110 -> So let's say CD.

17111.109 -> Glaciation it can spin up additional resources

17114.2 -> to handle additional spikes

17115.9 -> and then it can revert back to normal State.

17118.703 -> Once the threshold

17119.9 -> that you are specified is met then you have apps

17123.7 -> which is the fourth component.

17125.651 -> So it actually represents the code

17127.856 -> that you want to run

17129.192 -> on your specific layer of your application.

17131.864 -> So this would contain

17133.2 -> the information which is required to deploy the code

17136.2 -> so you can set up on automated basis or annual basis.

17141.2 -> So the first part

17142.323 -> of it is to create your stack you can provision a sample stack

17146.9 -> in which AWS would manage the creation

17149.329 -> of the sample stack on its own

17151.3 -> or else we'll start off

17152.657 -> with the chef 11 stack the sub networks

17155.3 -> or the availability zones the forward operating system

17158.486 -> that you want for the operating system.

17161.7 -> So you are just created a stag by the name stage

17164.686 -> that represents the staging environment

17167.1 -> and now we need to add layers to this specific stack.

17172 -> I'll add a layer and I'll use a prebuilt layer

17175.6 -> which means any resources

17177.3 -> that would be added up to this layer.

17179.417 -> Will you come as pre-configured?

17181.5 -> So in this case I am using a PHP a player.

17184.3 -> So there is one limitation of offshore stack here

17187.2 -> that it does not create load balances for you

17189.788 -> at this point of time.

17191.082 -> So if you want to use load balances,

17192.978 -> you will have to manually create them and use

17195.362 -> them within offshore.

17196.5 -> So coming weeks or months.

17198 -> We'll see that we'll be able to create

17199.907 -> the load balancer directly.

17201.3 -> From the service out there.

17202.9 -> So I've added the layer and at each layer we

17206.086 -> can have specific settings applied to resources

17209.387 -> that will become part of this layer.

17211.9 -> So you have ADD instance.

17213.8 -> So you want to add your resources

17216.2 -> or your computer resources to this particular layer.

17219.6 -> So I'll go ahead and add one instance.

17223.9 -> Then you can specify the instances beat

17227.1 -> if they're already running you want to make

17229.2 -> them part of the stack or instances outside AWS.

17232.9 -> I'll start the instance soon before I do a start.

17235.98 -> Let's take a look at the various settings

17238.546 -> that are available at each layer.

17241.2 -> You have instance shutdown in general settings.

17244.1 -> So usually you want to specify a time out here.

17247.096 -> We're in let's say you want to export log files

17250.043 -> from the instance

17251.112 -> when the instance is about to be shut or terminated.

17254.383 -> Then you have Auto healing enable.

17256.5 -> So in case your instance fails options would take care of it.

17260.6 -> So the most important aspect is recipes recipes.

17263.8 -> We know they are the piece

17265.464 -> of code that we want to be executed to a resource

17268.538 -> that is associated with a specific layer.

17271.1 -> Since we picked up rebuilt layer,

17273.292 -> which is PHP we do see

17274.8 -> if Ivy wins out here set up configured Deploy

17277.912 -> on deploying shut down at these events.

17280.8 -> These recipes would be executed.

17283.4 -> So the set of event is it occurs

17285.474 -> after the instance completes the booting process

17288.74 -> the first time and it is used

17290.57 -> for initial installation of software and service.

17293.6 -> If you take a look at the recipes attached

17296.4 -> it is installing

17297.568 -> MySQL any dependencies associating storage gang.

17301 -> Clear client which is the monitoring

17302.8 -> and then PHP an Apache.

17304.29 -> So essentially all the packages

17306.3 -> that you want to get installed during the instance.

17309.1 -> Once the instance has finished up booting process.

17311.9 -> So very similar to bootstrapping that what we saw

17314.616 -> when you provisioning the ec2 instances manually,

17317.217 -> then you have a configured state.

17319.1 -> So this is one sure

17320.327 -> that your configurations on the resources associated

17323.62 -> with your specific layers.

17325.3 -> They are consistent.

17326.3 -> Then you have deployment.

17327.77 -> So this occurs when you execute

17329.634 -> or going to deploy your code Then you have

17332.1 -> a non-deployed event as well.

17333.912 -> So they're in it's completely the reverse of deploy.

17337.1 -> So you want to uninstall the application and lastly

17340.112 -> you have shut down

17341.173 -> which let's say you're stopping

17343 -> or terminating you want to capture some cleanup tasks.

17346.2 -> Most commonly used task is shipping out these logs

17349.503 -> from your instances and you have Network.

17352.7 -> So we're not using elb right now.

17355.1 -> We are using public IP addresses then with respect to storage.

17358.688 -> What is the type of story that we would like to Use

17361.79 -> when security so officer has a service

17363.968 -> can manage security groups

17365.519 -> for you else you will have to create your own security groups

17369.1 -> and apply them.

17370.3 -> So we let off shock manage the service for us.

17373.2 -> If you want to send the logs to cloudwatch logs.

17376.773 -> You'll have to push the logs to the cloud service.

17381.7 -> So we added an instance to the PHP left.

17385.182 -> So we go ahead and start it.

17389.5 -> This in rebooting status at right now

17391.9 -> and it transitions to set up all the recipes associated

17395.213 -> with the set up event would weaken.

17397.9 -> So we've spoken about Stacks we have spoken

17400.3 -> about layers instances will have to specify

17402.99 -> which type of instance

17404.358 -> so by default it is 24 by 7.

17406.1 -> You always set up time based on load based you can do that.

17409.329 -> So rather than interacting is auto-scaling service directly.

17412.8 -> You can set up the rules out here in the service itself.

17419.1 -> See, if you go to the ec2 dashboard

17421.1 -> that we can always see

17422.453 -> that the service has already initiated

17424.73 -> the process of provisioning a instance for us.

17427.6 -> They actually the instance type

17429.2 -> that what we have selected is low on capacity.

17431.524 -> So that's the reason it's taking time.

17433.7 -> So I've selected an instance which is eligible for free tier.

17437 -> But as transition from booting

17438.945 -> to running setup so very shortly will see

17441.6 -> that the status changes to online and then

17444.103 -> once the status is online,

17445.629 -> what we'll do is we'll go ahead and install our application.

17450.7 -> and specify the proposed URL So

17455.3 -> once the instances in the online still State,

17458.5 -> I'll go ahead

17459.399 -> and deploy the application on this particular player.

17464.6 -> Okay, so the instance has transitioned to

17467.3 -> the online State.

17468.574 -> And now what we'll do is go ahead

17470.974 -> and deploy the application.

17475.8 -> So since we have only one instance,

17478.032 -> I am deploying this to our instance only else.

17480.986 -> We do have an option to select the specific instances

17484.6 -> if you like.

17487.7 -> So the application has been deployed

17489.644 -> to the instance in question.

17491.6 -> Now I can go ahead and Access the application.

17498.4 -> So tools like Observer would definitely help you

17501.9 -> in managing your Stacks as a group of components

17506 -> and in the second part of the demo,

17507.752 -> what we'll do is I add a database layer to it

17510.032 -> and the application

17511.149 -> that we'll be building is your thoughts sharing

17513.6 -> or kind of an application

17515.4 -> where all the data would be stored in your data base layer.

17518.6 -> So I'll go to layers again.

17520.4 -> I'll add another layer and select database layer.

17524.442 -> I'll add an instance.

17534.4 -> I will modify the app

17536.058 -> that we had created for a previous demo

17538.982 -> specify the document root.

17541 -> I'll specify the data source

17543.153 -> as offshore and I'm using version 2.

17552.3 -> I'll go ahead and start the database instance.

17557.5 -> The meanwhile, I'll go to the stock properties.

17561.884 -> I'm using a custom Chef book.

17565.7 -> passing the Repose URL so let the instance come online.

17574.3 -> So meanwhile,

17575.129 -> what I will do is for the PHP layer

17577.3 -> that we had created.

17578.9 -> I'll associate a custom recipe on the deployment.

17589 -> Social transition to running set up now and very shortly.

17591.8 -> It should be available the monetary resources directly

17596.1 -> from the Offshore Service plain the resources

17599.198 -> that have been provisioned.

17603.8 -> Okay, so finally a database instance is online.

17606.8 -> And again, I'll add a custom recipe

17609.167 -> to the database layer.

17616.5 -> We had already made those changes to the app.

17619.088 -> So we'll go ahead and deploy it.

17621 -> So this time it did negates

17622.787 -> that it would be executing on both the instances

17626.1 -> and treasure the deployment.

17629.4 -> So it has executed the custom recipe

17631.473 -> for database master.

17632.718 -> And now it's in the process

17634.4 -> of deploying on the PHP a the deployment is complete

17638.7 -> and I'm actually these blank the application.

17660.4 -> I actually backs Lindley specified dub-dub-dub

17663.5 -> instead of web which is the dog default document root

17667.4 -> for your PHP application.

17672.9 -> So post revised deployment it's working now so you can

17681.4 -> So hard our instance election being right we had chosen

17684.933 -> appropriate instance types.

17686.733 -> We would have been able to achieve this in much

17689.8 -> lesser time also like in the case

17692.034 -> of loud formation any resources

17694.2 -> that you create using a service offering they are tied

17697.8 -> to the life cycle of the be stack.

17700.5 -> And once you delete this taxi service

17702.3 -> would go ahead and terminate the resources for you.

17706 -> Okay, I guess then

17707.1 -> we can conclude this session for the day.

17709.3 -> Thank you.

17709.8 -> Bye I hope you have enjoyed listening to this video.

17713.5 -> Please be kind enough to like it

17715.672 -> and you can comment any of your doubts and queries

17719 -> and we will reply them at the earliest

17721.447 -> do look out for more videos in our playlist

17724.226 -> And subscribe to Edureka channel to learn more.

17727.6 -> Happy learning.

Source: https://www.youtube.com/watch?v=CkTEKxK5_gc