AWS Tutorial For Beginners | AWS Full Course - Learn AWS In 10 Hours | AWS Training | Edureka

Aug 16, 2023

AWS Tutorial For Beginners | AWS Full Course - Learn AWS In 10 Hours | AWS Training | Edureka

🔥 Edureka AWS Certification Training (Use Code ”𝐘𝐎𝐔𝐓𝐔𝐁𝐄𝟐𝟎”) - https://www.edureka.co/aws-certificat…
This Edureka video on “AWS Full Course” is a complete AWS Tutorial for beginners who want to learn AWS from scratch with examples and Hands-on. This AWS tutorial will help you learn various AWS services like AWS EC2, AWS S3, AWS Lambda, AWS Elastic Beanstalk, AWS VPC, AWS CloudFormation, AWS CloudFront, AWS CloudWatch and more. After watching this video you have skills of an AWS Solution Architect and you will clear AWS Certified Solutions Architect certification in one go. Below is the timestamp of this AWS Tutorial for Beginners:

00:00 Agenda
02:06 Introduction to Cloud Computing
02:11 Why Cloud?
02:21 Before Cloud Computing
07:11 What is Cloud Computing?
07:51 Cloud Service Models
12:01 Cloud Deployment Model
13:36 Cloud Providers
16:56 Introduction to AWS
18:11 Use-Cases
19:31 Advantages of AWS
22:31 AWS Architecture
25:01 Domains of AWS
34:36 AWS Compute Services
35:13 What is an Instance?
38:46 What is EC2?
46:26 Types of Instances
45:31 Instance Pricing Models
54:16 Use Case
01:10:16 AWS Lambda
01:13:31 AWS Compute Domains
01:15:06 Why AWS Lambda?
01:16:46 AWS SDKs
01:17:41 Using AWS Lambda with Eclipse
01:18:51 Demo
01:41:20 AWS Elastic Beanstalk
1:42:00 What is AWS Elastic Beanstalk?
1:44:25 PaaS
1:47:35 Web Hosting Platforms
1:48:30 Features of Elastic Beanstalk
1:49:50 Fundamentals of Elastic Beanstalk
1:53:50 Architecture of Elastic Beanstalk
2:00:25 Demo: How to Deploy An Application Using Beanstalk
2:12:30 Storage Service
2:13:05 What is Cloud Storage?
2:29:50 Cloud Storage Practices
2:35:25 Cloud Storage Service Providers
3:09:50 S3 Tutorial For Beginners
3:13:40 Buckets \u0026 Objects
3:22:40 Versioning \u0026 Cross Region Replication
3:32:55 S3 Transfer Acceleration
3:40:26 Use Case: IMDB Media
3:43:41 Demo: AWS S3 Complete Walkthrough
3:44:51 Networking Services
3:48:16 AWS CloudFront
3:53:26 How AWS CloudFront Delivers Content?
3:56:11 Applications
3:58:21 Demo: AWS CloudFront Distribution
4:07:06 Monitoring \u0026 Management
4:07:11 AWS CloudWatch
4:07:46 Need For Cloud-Based Monitoring
4:11:21 What is Amazon CloudWatch?
4:13:31 Amazon CloudWatch
4:16:41 Amazon CloudWatch Demo
4:21:01 Amazon CloudWatch Event
4:24:46 Amazon CloudWatch Event Demo
4:32:56 Amazon CloudWatch Logs
4:36:46 AWS CloudFormation
4:40:11 Get started in AWS CloudFormation
4:56:21 Autoscaling \u0026 Load Balancer
4:57:36 Snapshots \u0026 AMIs
5:00:06 Why Auto Scaling?
5:03:46 Why Auto Scaling?
5:17:51 What is the Load Balancer?
5:19:01 Types of Load Balancers
5:22:06 Hands-On
5:34:51 Cloud Security
5:35:41 Why Cloud Security?
5:37:31 Public, Private or Hybrid?
5:40:56 How Secure Should you make your application?
5:42:56 How to Troubleshoot a Threat in the Cloud?
5:43:56 How did they come to know?
5:45:26 Cloud Security in AWS
5:59:29 AWS IAM
6:01:34 What is IAM?
6:26:59 Multi-Factor Authentication
6:33:29 Hands-On
6:46:04 Amazon Redshift
6:58:29 Demo - Setting Up A Warehouse
7:14:04 DevOps on AWS
7:14:14 AWS DevOps Services
7:19:54 What is Continuous Integration \u0026 Delivery?
7:23:44 What Is CodePipeline?
7:25:39 CodePipeline Architecture
7:28:49 Code Deploy, Code Build \u0026 Code Commit
7:30:59 Demo - Deploying An Application Using AWS CodePipeline
7:42:49 AWS Interview Question
7:46:44 EC2 Questions
8:17:29 Amazon Storage
8:27:34 AWS VPC
8:36:44 Amazon Database
9:00:29 Cloud Engineer Jobs, Salary, Skills, Responsibilities \u0026 Resume
9:01:04 Cloud Engineer Job \u0026 Salary Trends
9:11:14 Cloud Engineer Job Skills \u0026 Description
9:22:34 Cloud Engineer Resume
9:26:24 Cloud Master Course At Edureka

🔴 Subscribe to our channel to get latest video updates: https://goo.gl/6ohpTV

📢📢 𝐓𝐨𝐩 𝟏𝟎 𝐓𝐫𝐞𝐧𝐝𝐢𝐧𝐠 𝐓𝐞𝐜𝐡𝐧𝐨𝐥𝐨𝐠𝐢𝐞𝐬 𝐭𝐨 𝐋𝐞𝐚𝐫𝐧 𝐢𝐧 2023 𝐒𝐞𝐫𝐢𝐞𝐬 📢📢
⏩ NEW Top 10 Technologies To Learn In 2023 - • Top 10 Technologies To Learn In 2023 …

🔴 𝐄𝐝𝐮𝐫𝐞𝐤𝐚 𝐑𝐨𝐥𝐞-𝐁𝐚𝐬𝐞𝐝 𝐂𝐨𝐮𝐫𝐬𝐞𝐬

🔵 AWS Cloud Masters Program: https://bit.ly/3BFthbS
🌕 Cloud Architect Masters Program: http://bit.ly/3OvueZy

🔴 𝐄𝐝𝐮𝐫𝐞𝐤𝐚 𝐔𝐧𝐢𝐯𝐞𝐫𝐬𝐢𝐭𝐲 𝐏𝐫𝐨𝐠𝐫𝐚𝐦𝐬

🔵 Post Graduate Program in DevOps with Purdue University: https://bit.ly/3Ov52lT

🔵 Advanced Certificate Program in Data Science with E\u0026ICT Academy, IIT Guwahati: http://bit.ly/3V7ffrh

🔵 Advanced Certificate Program in Cloud Computing with E\u0026ICT Academy, IIT Guwahati: https://bit.ly/3WUbN4S

📌𝐓𝐞𝐥𝐞𝐠𝐫𝐚𝐦: https://t.me/edurekaupdates
📌𝐓𝐰𝐢𝐭𝐭𝐞𝐫: https://twitter.com/edurekain
📌𝐋𝐢𝐧𝐤𝐞𝐝𝐈𝐧: https://www.linkedin.com/company/edureka
📌𝐈𝐧𝐬𝐭𝐚𝐠𝐫𝐚𝐦: https://www.instagram.com/edureka_lea…
📌𝐅𝐚𝐜𝐞𝐛𝐨𝐨𝐤: https://www.facebook.com/edurekaIN/
📌𝐒𝐥𝐢𝐝𝐞𝐒𝐡𝐚𝐫𝐞: https://www.slideshare.net/EdurekaIN
📌𝐂𝐚𝐬𝐭𝐛𝐨𝐱: https://castbox.fm/networks/505?count…
📌𝐌𝐞𝐞𝐭𝐮𝐩: https://www.meetup.com/edureka/
📌𝐂𝐨𝐦𝐦𝐮𝐧𝐢𝐭𝐲: https://www.edureka.co/community/

--------------------------

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

6.9 -> Cloud computing is at the cusp of technological advancement.

10.003 -> And when you talk about cloud computing it cannot shy away

12.881 -> without mentioning Amazon web services (AWS),

14.8 -> which is one of the leading cloud service providers

17.3 -> in the market.

18.5 -> If you are looking for a career in this domain you have landed

21.8 -> at the right place Edureka brings you a complete course

25.24 -> on Amazon web services,

26.606 -> which not only touches upon the fundamental

29.1 -> but also die.

29.891 -> It's deeper at a conceptual level.

32.3 -> So let us take a look at the offerings

34.5 -> of this session first.

36 -> We would start with the fundamentals of cloud computing

38.9 -> and Amazon web services moving on we will talk

41.747 -> about the core services

43.1 -> that Amazon web services has to offer to you.

45.8 -> The first domain is the compute domain

47.952 -> where we would be exploring services like ec2.

50.6 -> Elastic Beanstalk and Lambda moving on.

53.9 -> We'll talk about this storage domain

56.1 -> where we'll be exploring services like S3 EFS and Next

61.4 -> in line is the networking domain

63.7 -> where we'll be talking about services like VPC Route 53 Etc.

68.1 -> Then could be talking about management

70.631 -> and monitoring services like Cloud watch

73.6 -> cloudformation load balances Etc moving on you take a look

78.5 -> at Cloud security

79.7 -> and take a look at services.

81.4 -> Like I am Etc then the database part

84.5 -> where we'll be exploring services like Amazon redshift.

87.9 -> Once we are done with the core Services,

90.1 -> we will be also discussing develops on AWS

92.6 -> where we will be talking about AWS services

95 -> like aw score pipeline,

96.8 -> aw score commit Etc.

99.2 -> Now that the devops part

100.914 -> and the core part of AWS is over.

103.1 -> We can also switch to the career part

104.9 -> where we'd be discussing some numbers

106.7 -> like jobs friends salaries Etc

109.4 -> and would also take a look at the roles

111.332 -> and responsibilities.

112.4 -> And what are the kind of things that you should know

114.95 -> when you talk about making a career in this particular Dome?

117.9 -> So before we get started,

119.2 -> feel free to subscribe to our YouTube channel

121.5 -> to get the latest updates on the trending Technologies.

129.5 -> Firstly let's understand why Cloud to understand

132.396 -> this we need to understand the situation that existed

135.565 -> before Cloud came into existence.

137.472 -> So what happened back then

139.001 -> and firstly in order to host a website you

141.226 -> have to buy a stack of servers and we all know

143.873 -> that servers are very costly.

145.6 -> So that meant we ended up

147.15 -> paying a lot of money next was the issue of traffic now

150.5 -> as we all know

151.2 -> if you are hosting a website we are dealing with traffic

154.038 -> that is not constant throughout the day

156 -> and that meant more pain we would understand

158.41 -> that as we move further.

159.8 -> And the other thing was monitoring

161.556 -> and maintaining your servers.

163.1 -> Yes.

163.7 -> This is a very big problem now all these issues.

167 -> They led to certain disadvantages.

169.311 -> What are those

170.2 -> as I mentioned servers are very costly.

172.6 -> Yes.

173.4 -> The setup was again costly

175.1 -> and thus you ended up being a lot of money

177.511 -> and there were other factors contributing to this point.

180.419 -> Let's discuss those as well.

181.9 -> One troubleshooting was a big issue since you're dealing

185.6 -> with a business your Prime Focus is on taking good decisions

188.8 -> so that you have Business does well,

190.7 -> but if you end up troubleshooting problems

192.952 -> or you focus more on infrastructure related issues,

195.7 -> then you cannot focus more on your business

197.961 -> and that was a problem.

199.2 -> So either you had to do multitasking

201.4 -> or you have to hire more people to focus

203.557 -> on those issues thus again you ended up being more money

206.6 -> as I've discussed the traffic on a website is never constant.

210.5 -> And since it varies you are not certain about its patterns.

214.6 -> Say, for example,

215.6 -> I need to host a website and for that what I

218.155 -> decided is I am reserving.

219.7 -> To petabytes of total memory for my usage based on the traffic

223.5 -> but as the traffic where is there would be times

226.188 -> when the traffic is high

227.6 -> and my whole to petabytes of data is consumed

230.361 -> or space is consumed Roger,

232 -> but what if the traffic

233.3 -> is very low for certain hours of the day.

235.5 -> I'm actually not utilizing these servers.

237.88 -> So I end up paying more money for the servers

240.5 -> than I should be.

241.7 -> So yes upscaling was an issue.

244 -> So all these things were an issue

246.1 -> because we were paying more money.

248 -> We do not have sufficient time to Take our decisions properly.

250.8 -> There was ambiguity.

251.8 -> There was more trouble monitoring and maintaining

254 -> all these resources and apart from that one important point

257.099 -> which we need to consider is the amount of data

259.583 -> that is being generated now

260.992 -> and that was being generated then then it was okay,

263.6 -> but nowadays if you take a look at it the amount of data

266.3 -> that is generated is huge

268.046 -> and this is another reason why Cloud became so important as

272.1 -> of mentioned the data now,

273.758 -> we all know that everything is going online these days

277.2 -> and what that means is we shop online.

279.651 -> And we buy food online.

281.1 -> We do almost everything

282.5 -> that is required as an whatever information we need.

285.125 -> We get everything online bookings and reservations.

287.937 -> Everything can be taken care of that means we have a lot of data

291.4 -> that is being generated these days and this

294 -> is Digital Data back in those times.

296.2 -> We were communicating through verbal discussions

298.639 -> and all those things so

299.856 -> through paperwork and that was a different data to maintain

302.97 -> since everything is moving

304.5 -> on cloud or moving online the amount of data

307.321 -> that we have is used these days.

309.346 -> Days, and then when you have this huge amount of data,

312.7 -> you need a space

313.5 -> where you can actually go ahead and maintain this data.

316.2 -> So yes again,

317.1 -> there was a need of this piece and all these issues

320.407 -> that is your cost.

321.376 -> You're monitoring your maintenance providing

323.699 -> sufficient space.

324.633 -> Everything was taken care by Cloud.

326.5 -> So let us try to understand what this cloud is exactly.

329.4 -> Well think of it as a huge space

331.5 -> that is available online for your usage.

334.13 -> Now.

334.399 -> This is a very generic definition to give you

337.3 -> to be more specific.

338.5 -> I would be seeing that.

339.6 -> Think of it as a collection

341.219 -> of data centers now data centers again at a place

344.1 -> where you store your data or you host applications basically,

347.664 -> so when you talk about these data centers,

350.218 -> they were already existing.

351.9 -> So what did Cloud do differently?

354 -> Well, what cloud did was it made sure

356.537 -> that you are able

357.692 -> to orchestrate your various functionings applications

361.349 -> managing your resources properly

363.6 -> by combining all these data centers together

366.9 -> through a network

367.9 -> and then providing you the the control

370.3 -> to use this resources

372.1 -> and to manage them properly to make it even more simpler.

375.4 -> I would say there was a group of people or organizations.

379 -> Basically that went ahead and what these servers

382.1 -> these compute capacities storage places compute services

385.7 -> and all those things

386.8 -> and they have their own channel or Network.

389.6 -> All you have to do was go ahead

391.531 -> and rent those resources only to the amount you need it

395.013 -> and also for the time that you needed.

397.4 -> So yes, this is what cloud did It let you rent the services

401.5 -> that you need and use only those services

403.891 -> that you need.

404.714 -> So you ended up paying for the services

406.8 -> that you rented and you ended up saving a lot of money.

409.626 -> The other thing is these service providers.

412.033 -> They take care of all the issues

413.717 -> like your security your underlying infrastructures

416.564 -> and all those things.

417.8 -> So you can freely focus on your business

419.9 -> and stop worrying about all these issues.

422.3 -> So this is what cloud is in simple words.

424.4 -> It's a huge space which has all these services available

427.4 -> and you can just go ahead and pick and read.

429.55 -> And those services that you want to use so

431.3 -> what is cloud computing?

432.5 -> Well, I've already discussed

434.173 -> that just to summarize

435.468 -> it I would say it is nothing but an ability

437.914 -> or it is a place where you can actually store your data.

441.1 -> You can process it

442.245 -> and you can access it from anywhere in the world.

445.286 -> Now.

445.522 -> This is an important Point say for example,

448 -> you decide to choose a reason for infrastructure

450.7 -> somewhere in u.s.

452 -> You can certain maybe China or maybe in India

454.5 -> and you can still have access to all your resources

456.8 -> that is there in u.s.

458 -> All you need is a good And a connection

460.201 -> so that is what cloud

461.816 -> does it makes the world accessible it lets

465.1 -> you have your applications wherever you want to

467.8 -> and manage them the way you want to next we would be discussing

472 -> different service models.

474 -> Now you need to understand one thing you are being offered

477.2 -> cloud services the platform to use your services

479.8 -> or your applications basically,

481.4 -> but then different people have different requirements.

484.1 -> There are certain people who just want to consume

486.2 -> a particular resource or there's certain people

488.8 -> who actually want to to go ahead and create

490.7 -> their own applications great the own infrastructure

493.2 -> and all those things.

494.2 -> So based on these needs we have particular service models

497.494 -> that is your Cloud providers provide you

499.6 -> with a particular model which suits your needs.

502.305 -> So let us try to understand

503.831 -> these models one by one we have these three models

506.6 -> that is your iaas your paas and your saas.

511.9 -> I would be discussing them in the reverse order.

514.4 -> That is I would be talking about saas first

516.969 -> and then I would go upwards

518.621 -> so let us start.

519.6 -> Saas, or SAS SAS is nothing but a software-as-a-service.

525.7 -> Now what happens here

526.979 -> is basically you're just consuming a service

529.6 -> which is already being maintained and handled

531.8 -> by someone else to give you a valid example.

534.496 -> We have a Gmail.

535.5 -> All you do is you send mail to people and you receive mails

539.103 -> and whatever functionality you do is you just use the service

542.668 -> that is there.

543.5 -> You do not have to maintain it.

544.927 -> You do not have to worry about up scaling down

547 -> scalings security issues and all those things.

549.327 -> Everything is taken care by Google say for example,

551.913 -> you are Gmail is what

553 -> I'm talking about Google manages everything here.

555.4 -> So all you have to worry about is consuming that service

558.8 -> now this model is known as software as a service

562.4 -> that is saas.

564 -> Next we have passed

565.252 -> that is platform as a service now here you are provided

569 -> with a platform

569.9 -> where you can actually go ahead and build your own applications

572.452 -> to give you an example.

573.4 -> We have our Google app engine.

575.4 -> Now when you talk about Google app engine,

577.8 -> what you can do is you can go ahead.

579.551 -> You can create your own applications

581.309 -> and you can put it on Google app engine so

583.359 -> that others can use it as well.

584.7 -> So in short you're using the app platform to create

587.2 -> your own applications,

588.4 -> and lastly we have iaas

590.007 -> that is infrastructure as a service.

592.7 -> Now.

593 -> What do I mean by this?

594.5 -> Well, the whole infrastructure is provided to you

596.9 -> so that you can go ahead and create your own applications.

599.4 -> That is an underlying structure is given to you based on that.

602.6 -> You can go ahead and choose your operating systems

605.05 -> the kind of Technology

606.147 -> on to use on that platform the applications you want

608.797 -> to build an All those things

610.3 -> so that is what an iaas is infrastructure-as-a-service

614.3 -> basically,

615.2 -> so these were the different models

617.1 -> that I wanted to talk about.

619 -> Now.

619.5 -> This is the architecture

620.762 -> that gives you a clear depiction as in what happens

623.391 -> as far as the service models are concerned.

625.562 -> Now, you have something called as your sass now here

628.272 -> as you see all you're doing is you're consuming your data,

631.25 -> that's it or using it.

632.4 -> Everything else is managed by your vendor.

634.5 -> That is your applications runtime middleware OS

637.3 -> virtualization servers Network.

639.2 -> Everything as far as your past is concerned your data

642.1 -> and applications are taken care by you.

644 -> That is you can go ahead you can build your own applications.

646.1 -> You can use the existing platform

647.7 -> that is provided to you.

648.9 -> And finally you have your iaas.

651.245 -> Now what happens here is only the basic part

654.3 -> that is your networking storage servers

656.2 -> and virtualization is managed by your vendor deciding

659.876 -> what middleware OS runtime applications and data

663.2 -> that resides on your end.

664.5 -> You have to manage all these things

666.2 -> that is you are just given a box of car.

668.7 -> For example people

669.6 -> or maybe parts of car you go ahead and you fix it.

672.369 -> And you use it for your own sake that is what iaas is to give you

676.134 -> another example think of it as eating a pizza.

678.781 -> Now there are various ways of doing that one you order

681.603 -> it online you sit at home

682.934 -> you order the pizza.

684 -> It comes to your place you consume it

685.8 -> that is more of your saas.

687.7 -> That is software as a service.

689.4 -> You just consume the service.

690.955 -> Next is a platform as a service.

692.698 -> Now when I say platform as a service you can think

695.411 -> of it as going to a hotel and eating a pizza.

698 -> Say, for example,

699.006 -> I go They have the infrastructure

700.888 -> as in I have tables chairs.

702.374 -> I have to go sit just order the pizza.

704.55 -> It is given to me.

705.6 -> I consume it and I come back home and iaas.

708.226 -> Now.

708.432 -> This is where you go ahead and make your own pizza.

711 -> You have the infrastructure you buy it from somewhere

713.377 -> or whatever it is.

714.2 -> You use your pizza.

715.049 -> You put it in our new put spices all those things.

717.623 -> Can you eat it now?

718.6 -> This is the difference between these three services.

721.223 -> So let us move further and discuss the next topic.

723.744 -> That is the different deployment models

725.7 -> that are there now

726.6 -> when you talk about deployment models you

728.5 -> can also call All them as different types of clouds

731 -> that are there in the market we have these three types.

733.7 -> That is your public Cloud your private cloud

736.147 -> and your hybrid Cloud.

737.4 -> Let us try to understand these one by one now

739.985 -> as the name suggests the public Cloud it's available

742.985 -> to everyone you have a service provider

745.288 -> who makes these services or these resources available

748.347 -> to people worldwide through the internet.

750.782 -> It is an easy and very

752.1 -> inexpensive way of dealing with the situation

754.6 -> because all you have to do is you have to go ahead

756.8 -> and rent this cloud and you're good to you.

759.5 -> And it is available publicly.

761.288 -> Next we have the private Cloud.

763.329 -> Now.

763.6 -> This is a little different here.

765.667 -> You are provided with this service

767.8 -> and you can actually go ahead and create

770.094 -> your own applications.

771.209 -> And since it's a private Cloud you are protected by a firewall

774.317 -> and you do not have to worry about various other issues

777.1 -> that are there at hand and next.

778.894 -> We have our hybrid Cloud now,

780.6 -> it is a combination of your private cloud

783.3 -> and your public Cloud say,

785.1 -> for example, you can go ahead and build your applications

787.9 -> privately you can use them.

789.249 -> You can consume them you can use them efficiently.

791.7 -> When you sense that peak in your traffic.

793.9 -> You can actually move it to public

795.5 -> that is you can move it to the public cloud

797.4 -> and even others can have access to it and they can use it.

800.485 -> So these are the three basic deployment models

802.853 -> that are there for your exposure

804.474 -> or your usage rather and you can go ahead and use those as well.

807.705 -> I hope this was clear to all of you.

809.5 -> So let us move further and try to understand the next topic

812.151 -> that is different Cloud providers that are there

814.3 -> in the market now

815.344 -> as I've mentioned what happened was

817.4 -> since Cloud came into existence.

819.2 -> Quite a few people went ahead

820.65 -> and they bought their own infrastructure and now they rent

823.4 -> the services to other people

824.801 -> and when you talk

825.65 -> about this infrastructure the quite a few people out there

828.663 -> who are actually providing these cloud services

831.1 -> to different people across the globe.

833.131 -> Now, when you talk about these Cloud providers,

835.6 -> the first thing

836.349 -> that should come to your mind is Amazon web services

838.9 -> because it is highly popular

840.8 -> and it leaves other Cloud providers way behind.

844.1 -> The reason I'm saying this is the numbers

846.592 -> that talk about Amazon web services to You an example

849.828 -> if you talk about its compute capacity.

852.112 -> It is six times larger than all the other service providers

855.6 -> that are there in the market say for example,

857.9 -> if you talk about the other service providers in the market,

860.7 -> if the compute capacity combined

862.7 -> was X Amazon web services alone gives you a capacity of 6 x

867.1 -> which is huge apart from that.

869.3 -> It's flexible pricing and various other reasons.

871.932 -> That is the services it provides and all those things.

875 -> It is rightly a global leader and the fact

877.716 -> that it had a head start.

879.244 -> It started way

880.1 -> before many other services that are there in the market.

882.7 -> It actually gained popularity.

884.2 -> And now we see quite a few organizations going ahead

887.089 -> and using Amazon web services apart from that.

890.17 -> We have Microsoft Azure,

891.582 -> which is a Microsoft product and we all know

894 -> that when Microsoft decides to do something they expect

897 -> that they kill all the competition

898.3 -> that is there in the market.

899.7 -> It is still not in terms with Amazon web services

902.2 -> or few other service providers

903.7 -> that are then the market but not very neck to neck

905.8 -> but it is probably the second best

907.492 -> when you talk about Amazon web.

909.118 -> Services or the cloud service providers in the market?

911.9 -> So yep.

912.7 -> It has a lot of catching up to do

914.2 -> when you compare it with Amazon web services,

916.4 -> but it is still a very good cloud service provider

918.881 -> that is there in the market.

920.3 -> Then we have something called as Google Cloud platform again

923.5 -> a very good cloud provider in the market.

925.852 -> Now, why am I saying this?

927.382 -> We all know the infrastructure

929.147 -> that Google has to offer to you it has one

931.429 -> of the best search engine

932.9 -> that is then the market

934.252 -> and the amount of data they deal with every day is huge.

937.189 -> So they are the Pioneers when you talk about Data

939.658 -> and all those things and they know

941.431 -> how to actually handle this amount of data and

944.078 -> how to have an infrastructure that is very good.

946.7 -> That is why they have a very good facility and that leads

949.711 -> to it being one of the cheapest service providers in the market.

953.099 -> Yes.

953.32 -> There are certain features that DCB offers

955.37 -> which are better.

956.37 -> Even than Amazon web services when you talk about its pricing

959.996 -> and the reason for it is it has various other services

963.2 -> that are there water does is it helps you optimize various costs

967.413 -> how it uses analytics and various other ways

970.289 -> by which it can optimize the amount of power you use

973.656 -> and that leads to less usage of power.

976.1 -> And since you are paying less for power

978 -> that is provided as a paying

979.594 -> less for power you end up paying less for your services as well.

983.3 -> So that is why it is so cost efficient.

985.4 -> Then the other service providers that is we have digital ocean.

988.1 -> We have to remark we have IBM which is again very popular,

991.5 -> but that is a discussion for some other time.

993.7 -> As far as these service providers go.

995.6 -> These are the major ones that

997.1 -> as we have Amazon web services we Microsoft Azure,

1000.127 -> we have DCP which are talked about a lot.

1002.6 -> This was about the basic Cloud providers and the basic intro

1005.149 -> which I wanted you all to have.

1006.73 -> I hope you all are clear

1007.954 -> with whatever Concepts we've discussed in time.

1015.2 -> Let's try to understand a little more about AWS.

1018.1 -> Well, it is a complete

1019.426 -> software suit or a cloud service provider,

1021.9 -> which is highly secure.

1023.402 -> It provides you with various compute storage database

1026.8 -> and a number of other services, which we would be discussing.

1029.2 -> Discussing in further slides as well.

1031 -> And when you talk about the market it is the best

1033.5 -> and it has various reasons to be the best

1035.8 -> in the market one being its flexibility its scalability

1039.731 -> and its pricing other reasons being its compute capacity now,

1044.1 -> why is it so important to compute capacity?

1046.2 -> Well, if you talk about the compute capacity,

1048.225 -> you need to understand one thing

1049.6 -> if you take all the other cloud service providers

1052 -> in the market and you combine the compute capacity

1055.1 -> that is your layout AWS and you take all others

1057.7 -> into consideration

1058.7 -> this Is would be somewhere equal to say x

1061.7 -> and if you compare it with AWS, it is 6X.

1066.2 -> So AWS has more compute capacity,

1068.2 -> which is six times more than all the other service providers

1071.7 -> that are there in the market.

1073.3 -> So that is a huge amount.

1074.9 -> So these are the reasons that make a database one

1077.3 -> of the best in the market and let's try to find out

1080.319 -> what are the other reasons about aw that make it so good.

1083.7 -> What are the services features and its uses basically,

1086.9 -> so I would be discussing some use cases now.

1089.3 -> Now if you are talking about a manufacturing organization now,

1093.053 -> the main focus is to manufacture Goods,

1095.4 -> but most of the businesses they focus so much

1098.052 -> on various other services are

1099.8 -> practices that need to be taken care of that.

1102.249 -> They cannot focus on the manufacturing goal of this is

1105.2 -> where aw steps--and it

1106.3 -> takes care of all the it infrastructure and management.

1109 -> That means businesses are free to focus on manufacturing

1112.1 -> and they can actually go ahead

1113.8 -> and expand a lot architecture Consulting now,

1116.645 -> the main concern is prototyping and During a dove is takes care

1120.771 -> of both the issues it lets you have automated

1123.7 -> or speed up rendering as far as prototyping is concerned

1127.5 -> and that is why architectural business benefit a lot

1130.5 -> when you talk about using AWS or any cloud provider

1133.7 -> but AWS being the best in the market again,

1135.8 -> the services are

1136.796 -> the best media company now as far as a media company

1139.881 -> goes the main concern is generating content

1142.417 -> and the place to dump it out to store it again,

1145.103 -> aw takes care of all these situations

1147.227 -> or both these situations.

1148.9 -> Large Enterprises when you talk

1150.723 -> about large Enterprises their reach is worldwide,

1153.343 -> so they have to reach the customers

1155.2 -> and the employees globally or across different places.

1158.6 -> So AWS gives you that option

1160.644 -> because it has a global architecture

1163.2 -> and your research can be very wide as

1165.5 -> far as these points are concerned the advantages of AWS

1169.3 -> as I mentioned.

1170.212 -> I won't say advantages exactly.

1172.1 -> I would say features as well flexibility.

1174.785 -> Now as far as AWS is concerned

1176.8 -> it is highly flexible now the The reasons to support it

1180.334 -> and one of the major reasons is it's very cost-effective.

1184 -> Let us try to understand these two points together other now

1187.47 -> when you talk about flexibility,

1189.255 -> the first concern you should have is you are dealing

1192.1 -> with big organizations.

1193.407 -> They have a lot of data

1194.635 -> that needs to be managed deployed and taken care

1197.575 -> of now when you talk about a cloud provider

1200.045 -> if it is flexible,

1201 -> all these things are taken care

1202.586 -> of the second thing is it is highly cost-effective now

1205.3 -> when I say cost-effective AWS takes care

1207.622 -> of almost every aspect.

1208.975 -> Aspect if you are a beginner or a learner,

1211.134 -> they have something called as a free tier.

1213.3 -> That means you have sufficient resources to use for free and

1216.581 -> that too for one long year stood have sufficient Hands-On

1219.905 -> without paying anything plus it has something called as

1223.082 -> pay-as-you-go model now

1224.284 -> when I say pay

1225.021 -> as you go model

1225.814 -> what it does is it charges you only for the services

1228.662 -> which are using

1229.5 -> and only for the time being you're using them again

1232.4 -> that lets you scale up nicely

1234.496 -> and hence you end up paying very less

1237.1 -> since you are being very less.

1238.7 -> And since you have so many options

1240.487 -> when you are actually buying it Services

1242.781 -> what that does is

1243.7 -> that gives you a lot of flexibility scalability again,

1247 -> the first two points are related to this point.

1249.4 -> Now, how is that when I say scalability

1252.324 -> what happens is

1253.4 -> as I mentioned it is very affordable.

1255.4 -> So you're paying

1256.2 -> on a daily basis if you're using a particular service

1259.264 -> for one hour you'll be paying it only for one hour.

1262.209 -> That is how flexible it is.

1263.8 -> And what that does is

1265.2 -> that gives you a freedom to scale up and even scale down

1268.277 -> since it Is easy to scale up?

1269.9 -> It is always advisable

1271 -> that you start with less and then scale as

1274.4 -> for your needs plus they're quite a few services

1276.4 -> that are there which can be automatically schedule.

1278.9 -> Now what that means is you would be using them only

1281.9 -> when there is an up time and in down time

1284.3 -> you can miss those get automatically shut down

1286.766 -> so you do not have to worry about that as well.

1289.472 -> So when you talk about scalability scaling up

1291.9 -> and down is very easy as far as AWS course security

1294.91 -> again are now security has been a topic of debate

1297.8 -> when you talk about What cloud services especially

1300.8 -> but AWS puts all those questions to rest.

1303.41 -> It has great security mechanism.

1305.5 -> Plus it provides you with various compliance programs

1308 -> that again help you take care

1309.484 -> of security and when you talk about real-time Security even

1312.482 -> that is taken care of you can take care

1314.506 -> of all the suspicious activities

1316.262 -> that are there and not uaw's takes care of all those things

1319.445 -> and you're let free to focus on your business rather.

1322.3 -> So these are the advantages which I feel that AWS adds value

1325.7 -> to and apart from that the quite a few other points

1328.2 -> like we have automatic scheduling

1329.972 -> which I just mentioned you have various integrated apis.

1333.103 -> Now these apis

1333.9 -> that are available in different programming languages

1336.3 -> and that makes it architecture really very strong to switch

1339.5 -> from one programming language to another so these are some

1342.1 -> of the features I feel

1343.2 -> that make AWS a wonderful wonderful service provider

1346.338 -> in the market.

1347.2 -> So let's move further and try to understand other things

1349.855 -> as far as database is concerned.

1351.4 -> It's Global architecture

1353 -> when you talk about a double usage

1354.7 -> of mentioned it is the best service provider in the market.

1358 -> So what X ews this popular.

1360.6 -> One of the reasons is

1362 -> its architecture now when I talk about its architecture,

1365.3 -> it is very widely spread and it covers almost every area

1368.9 -> that needs to be covered.

1370.306 -> So let's try to understand how it works.

1372.5 -> Exactly.

1373.2 -> Well if you talk about AWS architecture now,

1375.9 -> the architecture is divided into two major parts

1378.5 -> that is Regions and availability zones.

1381.3 -> Now when you talk about the regions

1383.1 -> and availability zones reasons

1384.758 -> are nothing but different locations across the world

1387.51 -> where they have there.

1388.805 -> Various data centers put up now.

1390.7 -> As far as one region

1391.7 -> goes it might have more than one Data Center

1394.342 -> and these data centers are known as availability Zone.

1397.6 -> You being a consumer

1399.153 -> or an individual you can actually access

1402.03 -> or access these Services

1403.8 -> by sitting anywhere in the world to give you an example.

1406.6 -> If I'm sitting in some part of the world say,

1408.7 -> for example, I am in Japan right now.

1410.519 -> I can actually have access to the services or data centers

1413.4 -> that are there in u.s.

1414.5 -> Right now.

1415 -> So that is how it works.

1416.6 -> You can choose your region.

1418.7 -> Accordingly you can pick your availability zones and use those

1421.887 -> so you do not have to worry about anything to throw

1424.5 -> some more light on it.

1425.8 -> You can take a look at this small map

1428.2 -> which is the global map and it shows the different places

1431.8 -> which has its regions and availability zones.

1435.5 -> Now as far as this map goes,

1437.265 -> I believe it's fairly old

1438.9 -> and it has been upgraded in recent times

1441.5 -> because AWS is putting a lot

1443.487 -> of effort to have more data centers

1445.9 -> or more availability zones as far as there.

1448.6 -> Wide reach is concerned

1449.952 -> and we can expect some in China as well.

1452.176 -> So yes, they are actually reaching for and white.

1455 -> So when you talk about these regions

1457.036 -> and availability zones,

1458.5 -> if you take a look at this map

1460 -> what you can see is you have your reason

1462.6 -> which is an orange color.

1464.2 -> And the number that is inside.

1466 -> It is the number of availability zones

1468.271 -> that they has to be now to give you an example.

1471.238 -> We have São Paulo,

1472.4 -> which says that it has three availability zones,

1476 -> so that is how it is

1477.066 -> and the ones that are in the green Are the ones

1479.582 -> which are coming soon are the regions

1481.647 -> that are in progress and some of these have actually gone.

1485 -> I hadn't already started

1486.5 -> or have been made available to people.

1488.7 -> So yes, this is how the architecture works

1491.6 -> and this is how the database architecture looks like.

1496.6 -> Okay, so let's move further

1498.1 -> and take a look at the next concept domains of AWS.

1501.3 -> When you talk about its domains.

1503.3 -> The first domain

1504.1 -> that we are going to discuss is compute.

1506.8 -> And when you talk about compute the first thing

1508.9 -> that should come to your mind is easy to have a nice easy

1511.7 -> to it is elastic Cloud compute

1513.73 -> and what it does is it lets you have

1516.1 -> a resizable compute capacity.

1518.5 -> It's more of a raw server

1519.824 -> where you can host a website and it is a clean slate.

1522.964 -> Now.

1523.21 -> What do I mean by this?

1524.5 -> Say for example, you go ahead and buy a laptop.

1526.8 -> It is a clean device

1528.2 -> where you can have your own OS you can choose

1530.6 -> which OS you want and all those things accordingly.

1533.6 -> Your ec2 is again a clean slate

1536.2 -> and you can do so many things with it.

1538.4 -> Now next you have elastic Beanstalk with lets

1541.282 -> you deploy your various applications on AWS.

1544.1 -> And the only thing you need to know about this thing is

1547 -> you do not have to worry about the underlying architecture now,

1549.6 -> it is very similar to your ec2.

1552 -> And the only difference between the two is as

1554.716 -> far as your elastic Beanstalk is Concern you can think

1557.909 -> of it as something

1559.068 -> that has predefined libraries.

1561 -> Whereas your ec2 is

1562.4 -> a clean slate when I say predefined libraries say,

1565.861 -> for example, you want to use Java as far as easy to goes.

1569.9 -> Now.

1570.142 -> This is just an example.

1571.582 -> Don't take it literally will have to say for example,

1575 -> install everything from the beginning and start fresh.

1578.1 -> But as far as your elastic Beanstalk is concerned

1581.1 -> it has this predefined libraries

1583 -> and you can just go ahead and use those

1584.8 -> because there's an underlying Sighing architecture,

1587.586 -> which is defined.

1588.5 -> Let me say it again.

1589.5 -> I just give you an example don't take these sentences

1592.6 -> literally so next

1593.689 -> we have migration when you talk about migration,

1597 -> you need to understand one thing AWS has a global architecture

1600.577 -> and there would be a requirement for migration.

1603.2 -> And what aw does is it lets you have physical migration as well.

1608.3 -> That means you can physically move your data

1610.7 -> to the data center.

1611.735 -> Which you desire now, why do we need to do that?

1614.603 -> Say, for example, I am sending an email.

1616.9 -> Somebody I can do that through internet,

1619.331 -> but imagine if I have to give somebody a movie.

1622.084 -> So instead of sending it online.

1624 -> I can actually go ahead and give it to someone

1626.1 -> if that person is means reachable for me

1628.394 -> and that way it would be more better for me.

1630.7 -> My data remains secure

1631.916 -> and so many other things so same is with data migration as well.

1635.4 -> And when you talk about AWS,

1636.9 -> it has something called as snowball

1638.9 -> which actually lets you move this data physically now,

1641.8 -> it's a storage service

1643.1 -> and it actually helps you in migration a lot security.

1646.5 -> And compliance now when you talk about security,

1649.264 -> we have various services.

1650.699 -> Like I have I am we have KMS now when I say I am it is nothing

1654.2 -> but your identification and authentication management tool.

1657.2 -> We have KMS which lets you actually go ahead

1659.35 -> and create your own public and private keys

1661.325 -> and that helps you keep

1662.475 -> your system secure the quite a few other services as well,

1665.288 -> but I would be mentioning one or two services from each domain

1668.3 -> because as we move further in future sessions,

1671.181 -> we would be discussing each of these services

1673.772 -> in detail and that is

1675 -> when I would be throwing a lot more Done these topics for now.

1678.2 -> I would be giving you one or two examples and

1680.4 -> because I want you all to understand these

1682.4 -> to some extent getting

1683.8 -> into details of all these things would be

1685.8 -> too heavy for you people

1687 -> because the quite a few domains and quite a few services

1689.6 -> that we need to cover and as we move further definitely

1692.6 -> we would be covering all those services in detail.

1695.3 -> Then we have storage now when I talk about storage

1698 -> again AWS has quite a few services to offer to you.

1701.1 -> We have something called as your S3 now s38 works as

1704.8 -> a bucket object kind of a thing.

1706.682 -> Your storage place is called as a bucket and your object

1709.712 -> which you store in nothing,

1711.217 -> but your files now these objects have to be stored

1714.1 -> in their food files

1715.228 -> which act as the buckets basically and then we

1717.9 -> have something called as your cloudfront

1720.1 -> which is nothing but your content delivery Network.

1722.873 -> We have something called as Glacier.

1724.815 -> Now when you talk about Glacier you can think of it as a place

1728.2 -> where you can store archives

1729.6 -> because it is highly affordable next.

1731.7 -> We have networking when you talk about networking.

1734.7 -> We have services like VPC.

1736.8 -> Direct Connect Route 53,

1738.646 -> which is a DNS a

1739.9 -> when I say VPC it is a virtual Network

1742.4 -> which actually lets you move or launcher resources.

1745.6 -> That is your AWS resources.

1746.95 -> Basically when you talk about Direct Connect,

1749 -> you can think of it as a least internet connection

1751.6 -> which can be used with an AWS next on this list.

1754.453 -> We have something called as messaging.

1756.7 -> Yes AWS Usher's secured messaging

1759.5 -> and the quite a few applications to take care of that as well.

1762.3 -> We have something called as Cloud trial we have opsworks

1765.3 -> all these things there.

1766.659 -> Help you in messaging

1767.894 -> or communicating with other parties basically

1770.482 -> databases now storage and databases are similar,

1773.05 -> but you have to understand one difference when you talk

1776 -> about your storage

1776.942 -> that is where you store your executable files.

1779.3 -> So that is the difference between the two and

1781.519 -> when you talk about databases,

1783.1 -> we have something called as your Aurora,

1785.2 -> which is something

1786.423 -> which is very sql-like and it lets you perform

1789.534 -> various SQL options at a very faster rate

1792.6 -> and what Amazon claims has it is five times faster

1796.5 -> than What aeschylus?

1798.1 -> So yes, when you talk

1799.415 -> about Aurora again a great service to have we also have

1802.798 -> something called as Dynamo DB which is a non relational dbms.

1806.5 -> When you talk about non relational dbms,

1808.8 -> I won't be discussing that but this helps you in dealing

1811.74 -> with various unstructured data sources as well.

1814.3 -> Next on this list.

1815.3 -> We have the last domain that is the management tools.

1819.2 -> Now when you talk about management tools,

1821.1 -> we have something called as cloudwatch,

1823.043 -> which is a monitoring tool and it lets you set alarms

1825.843 -> and all those Those things hopefully today

1827.941 -> when we are done with the demo part you'd be having

1830.5 -> at least one part of your cloudwatch code

1832.6 -> because we would be creating alarms using Cloud was today.

1835.3 -> So stay tuned for that as well.

1837.4 -> So this is about AWS

1838.8 -> and it's Basics as in the points,

1840.9 -> which we just discussed

1842.4 -> that as what it is its use has its advantages its domain

1846.951 -> its Global architecture.

1849.4 -> So you guys what I've done is I've gone ahead

1851.5 -> and I've switched into my AWS account.

1853.9 -> The first thing you need to understand is

1856 -> what AWS does is it offers you a free tier now

1859.418 -> while I was talking

1860.844 -> about these things I just rush through it

1863.7 -> because I know

1864.7 -> that I was going to give you a demo on these things.

1867.4 -> So and I wanted to discuss this thing in detail.

1870.1 -> Now when you talk about AWS,

1871.5 -> if you are a beginner, this is where you start now,

1874.3 -> what aw does is it provides you with its free tier

1877.1 -> which is accessible

1878.116 -> to you for Twelve months and the quite a few Services

1881.098 -> which we just discussed

1882.291 -> which are available to you for free.

1884.192 -> And when I say free the certain limitations on it

1886.9 -> as in these many hours is

1888.4 -> what you can use it for and this is the amount of memory

1891.4 -> or storage you can use in total

1893.223 -> and all those things and its capacity

1895.3 -> and everything based on that you have different instances,

1898.15 -> which you can create an all those things.

1900.1 -> Now.

1900.6 -> What aw is does is it gives you these services for free?

1903.6 -> And as long as you stay in the limits

1905.8 -> that AWS has set you won't be charged anything.

1908.9 -> And trust me when it is for learning purposes

1911.9 -> that is more than enough and let's quickly go ahead and take

1915.015 -> a look at these Services first

1916.6 -> and then there are few other points,

1918.398 -> which I would like to discuss as well.

1920.3 -> But firstly the free tier services and say this is

1923 -> what it has to offer to you 12 months

1924.8 -> of free and always free products

1926.8 -> when you talk about easy to which is one

1928.6 -> of its most popular compute Services 750 ours

1932.3 -> and that is per month.

1933.902 -> Next you have Amazon quick site,

1936.141 -> which gives you 1 GB of spice capacity.

1938.8 -> Now I won't get into the details of these things as an what

1941.6 -> spice capacity is and all those things

1943.58 -> when you have time,

1944.57 -> I would suggest

1945.363 -> that you go ahead and explore these things as in

1947.827 -> what do these things do today?

1949.4 -> We are going to focus more on the easy to part.

1951.7 -> So for now,

1952.272 -> let's quickly take a look at these one

1954.2 -> by one first Amazon RDS,

1955.923 -> which is again,

1957 -> which gives you send 50 hours of your T,

1959.54 -> 2 micro instance Amazon S3,

1961.3 -> which is a storage which again gives you 5 GB

1964.093 -> of standard storage

1965.3 -> and it w is Lambda 1 million free request.

1968.8 -> So there's some of the videos here actually

1971.77 -> which would introduce you to these things

1974.4 -> that would help you get started with how to creating an account

1977.5 -> and all those things and this is the other important point

1980.3 -> which I would like to mention.

1981.7 -> When you do create an AWS account.

1983.8 -> The first thing you need to consider

1985.3 -> as they would be asking you for your credit card details.

1987.9 -> So how does the login process work firstly you go there

1991.08 -> you doing your email ID and your basic details as in

1994 -> why do you want to use it and all those things next?

1996.6 -> What it would do is just to verify your account.

1998.8 -> And it would ask you for your credit card details,

2001.267 -> even the debit card details work.

2002.8 -> I've actually tried those so you can go ahead

2005.156 -> and give you a credit card or debit card details.

2007.4 -> And when you do that what it does is it subtracts

2010.334 -> a very small amount from your account.

2012.515 -> I did this in India,

2013.751 -> and I know that I was charged to rupees

2016.1 -> which is fairly less

2017.4 -> and that was again refunded back to me

2019.305 -> in two to three working days.

2020.8 -> The only reason they cut those two rupees was just

2023.281 -> for the verification purpose

2024.7 -> that my account is up

2026.1 -> and running and I am a legitimate user.

2028.8 -> Now as long as you stay in the limits,

2030.6 -> you won't be charged anything.

2032.1 -> But if you do cross those limits,

2033.4 -> you'll be charged.

2034.3 -> Are you might be worried as an what?

2035.936 -> If I do cross the limit would I be charged?

2037.9 -> Yes, you would be but the fact is you

2039.925 -> actually won't go beyond it.

2041.572 -> And even if you do you'll be notified seeing

2044.1 -> that you are going about the limit

2046.102 -> or about the limit.

2047.123 -> Even when your free subscription ends.

2049.3 -> You are notified saying

2050.499 -> that do you want to enter your billing details?

2052.9 -> And do you want to start billing

2054.5 -> and if you say yes only then would be charged

2057.4 -> for the subsequent.

2058.7 -> Months and that is a very stringent process.

2061.2 -> You don't have to worry about it.

2062.6 -> That is you won't be losing out

2064.1 -> on any money as long as you follow these rules.

2066.523 -> So if you do not have

2067.7 -> an account my suggestion would be you go ahead.

2070.159 -> You would log into AWS and create your free tier account

2073.1 -> which has a very easy and two to three step process.

2080.9 -> So guys, I would start this session by talking about

2083.479 -> what is an instance would understand.

2085.6 -> What is AWS ec2 service which is core for us.

2089.1 -> Standing instances in AWS.

2091.2 -> Then we'll talk about different types of

2093.3 -> ec2 instances would understand

2095.4 -> how instance pricing models work

2097.7 -> and we'll take a look at a use case

2099.612 -> which would be followed by a demo that walks you

2102.306 -> through all the stuff that we have talked about.

2105 -> So it is a fairly good content

2106.857 -> and a lot of stuff to study today.

2108.9 -> So as let us just quickly move further

2110.82 -> and take a look at these things one by one.

2113.3 -> So first and foremost guys,

2114.8 -> we would be talking about an instance.

2117.1 -> So when you talk about an instance,

2118.988 -> we have this definition here.

2120.6 -> Let's try and understand

2121.749 -> what does this definition has to say first

2123.816 -> and then probably I would throw in some light on that.

2126.5 -> So as far as this definition

2128.1 -> goes it says and instance is nothing but a virtual server

2131.5 -> for running applications on Amazon ec2.

2134.1 -> It can also be understood like a tiny part

2136.75 -> of a larger computer a tiny part which has

2139.8 -> its own Hardware network connection operating system.

2143.4 -> Cetera, but it is actually virtual in nature.

2146.9 -> So there are a lot

2148.1 -> of words here and a lot of stuff has been said,

2150.706 -> let me try and simplify this particular definition

2153.589 -> for you people.

2154.4 -> So guys when I say a virtual server running

2157.299 -> on your application not on your application virtual server

2161.1 -> that basically hosts our application is

2163.141 -> what I should say.

2164.2 -> So what do I mean by this?

2165.865 -> What do I mean by a virtual instance a virtual presence

2169.326 -> of a particular device?

2170.8 -> Well guys when you talk about

2172.5 -> software development elopement application development.

2175.3 -> What you do is you are supposed to build an applications and run

2178.8 -> those on servers right?

2180.152 -> But at times there are a lot of constraints like the space

2183.4 -> that you use the resources

2184.922 -> that you want to use say for example,

2187.439 -> certain applications run on Windows certain run

2190.2 -> on Mac OS and certain run on your Ubuntu OS right?

2193.3 -> So in that case,

2194.2 -> I cannot always go ahead and have different systems

2196.7 -> and different operating systems on them and then

2199.05 -> run my applications on top of that right

2201 -> because it is time consuming.

2203.2 -> Stu and also consumes a lot of money

2205.6 -> that you invest into it.

2207.1 -> So what is the solution for that?

2209.2 -> What if I could have a single device

2211.6 -> and on top of which I could create virtual compartments

2214.6 -> in which I could store my data differently

2216.824 -> store my applications run my applications differently.

2219.7 -> Wouldn't that be nice?

2221 -> Well, when you talk about an instance,

2223 -> that is what it exactly does you can think of it

2226.2 -> as a tiny part of a computer.

2228.3 -> Well, that is what it is time to symbolize.

2230.7 -> I mean you have a system on top of which.

2233.4 -> You can run different applications and how it works is

2237.1 -> if you are running an application a in part

2239.57 -> 1 and running an application B

2241.5 -> in Part B of your server these applications have a feeling

2245.4 -> that they are running individually on that system

2248.121 -> and there is no other system running on top of it.

2250.9 -> So this is what virtualization is.

2253.2 -> It creates a virtual environment for your application to run

2257.8 -> and one such instance

2259.6 -> of this virtual environment is called as an instance.

2263.3 -> So when you talk about virtualization,

2265.218 -> it is not something that is very complicated.

2267.5 -> As you can see in the first image.

2269.2 -> You can see a man surrounded

2270.88 -> by various virtual images something that you see

2273.7 -> in an Iron Man movie.

2274.9 -> When you talk about virtualization,

2276.6 -> it is very simple.

2277.9 -> It can be a simple computer

2279.859 -> which is shared by different people and those people

2283.455 -> are working quite independently on that server.

2286.7 -> That is what virtualization is that is

2289.2 -> what an instances in this image the second image each All

2293.1 -> of this individual would be using a different instance.

2296.7 -> So this is what an instance is

2298.5 -> when you talk about virtualization.

2300.7 -> So guys, let us move further

2302.347 -> and take a look at some other pointers.

2304.4 -> Now we understood what an instances

2306.7 -> what virtualization is to some extent at least guys.

2310.3 -> As far as the session goes.

2311.757 -> I believe this information is enough.

2313.7 -> If you wish to know more about virtualization,

2316.409 -> you can visit our YouTube channel and take a look

2319.3 -> at VMware tutorial.

2320.7 -> It talks about this particular Topic in a More detail.

2324.3 -> So let's let us move further and try to understand easy

2327 -> to now now easy to as an Amazon web services compute service.

2332.7 -> It stands for elastic compute Cloud.

2336 -> Now, what do I mean by this?

2337.5 -> When you say an elastic Cloud compute?

2339.931 -> That means basically it is a service with lets you

2343.249 -> actually go ahead and Carry Out computation practice

2346.615 -> and when I say elastic it means

2349 -> that it is fairly resizable and fairly reusable.

2353.1 -> Once we get into the demo part

2354.9 -> probably you'd get a better picture.

2357 -> What do I mean by elasticity?

2358.763 -> Because it is highly flexible highly scalable.

2361.5 -> It is very cost efficient and it serves a lot of purposes.

2365.6 -> Now.

2365.8 -> These are some of the features that I just mentioned right?

2368.725 -> Let me throw in some more light on these pointers as well.

2371.6 -> What do I mean by scalable now

2373.7 -> when you talk about a cloud platform one

2376.185 -> of its best features is it gives you high amount of scalability?

2380.2 -> That means your applications can scale up.

2383.1 -> Down depending upon the data

2384.658 -> that you want to use on top of it.

2386.414 -> So if the traffic increases more you need more performance.

2389.596 -> So your application should be able to scale

2391.9 -> to those needs, right?

2393.297 -> So that is what cloud computing provides you with and

2396.582 -> that is what ec2 also provides you with when I say an instance.

2400.5 -> Basically, what you're doing is you're launching

2402.7 -> a virtual machine.

2403.8 -> It is called as instance in terms of AWS.

2406.6 -> So this virtual machine should be scalable.

2409.143 -> That means it should scale up

2410.985 -> and scale down both in terms of memory.

2413.4 -> A storage and even in terms of the computation

2416.45 -> that it is providing.

2417.817 -> So when you talk about easy to it is highly scalable.

2421.2 -> Once we get into the demo part you would see this now

2424.365 -> it being scalable

2425.4 -> and it being cost-efficient makes it highly flexible.

2428.7 -> So that is the third Point.

2430.1 -> Let us try and understand the second Point as well.

2432.6 -> What makes easy to cost efficient when you talk

2435.7 -> about cost optimization.

2437.3 -> What easy to does is it lets you scale up

2439.776 -> and down I just mention

2441.147 -> that right so instead

2442.4 -> of buying Number of instances or instead of buying a number

2445.811 -> of services you can actually go ahead

2447.9 -> and scale this instance up and down with minimal cost changes.

2451.501 -> So you're saving money

2452.849 -> because apart from that there are burstable instances.

2456.1 -> There are various pricing models that ec2 boasts of using

2460.7 -> which you can actually save a lot of money

2462.7 -> as we move further.

2463.842 -> We'd be talking about those models as well.

2466.313 -> So meanwhile, just bear with me so easy to well it is a service

2470.2 -> which is a computation service and it takes care of

2473 -> Of following pointers.

2474.2 -> I mean it is easily resizable.

2476.2 -> It is cost efficient.

2477.435 -> It is highly scalable

2478.623 -> and all these features make it highly flexible as well.

2482 -> So guys, let us move further and take a look

2484.2 -> at some other pointers as well.

2486.2 -> So what are the types of instances now

2488.4 -> when you talk about easy to it is one

2490.5 -> of the oldest AWS services.

2492.7 -> So if you talk about the type of instances

2494.75 -> that are there in the market.

2496.4 -> Well, there are quite a few types

2498 -> of instances that you can deal

2499.8 -> with and these are some of the popular ones

2503.1 -> Once I move into the demo part,

2504.738 -> I would maybe talk about other instances

2506.8 -> but to keep it simple

2508.4 -> basically these instances they have different families.

2511.576 -> I mean, you have

2512.664 -> the T Series you have the M series The cseries.

2515.67 -> Well, basically these series

2517.5 -> consists of different kind of instances

2519.723 -> that serve different purposes to simplify this process.

2523.3 -> What AWS has done is it has gone ahead

2525.919 -> and categorized these instances into following types.

2529.6 -> The first one is your general purpose instance.

2533.2 -> Now it is basically suited for applications

2535.9 -> that require a balance of performance and cost

2539 -> that means places where you require quick responses,

2542.2 -> but it is still cost-effective.

2544.071 -> I mean say for example

2545.4 -> the example shown here email response systems.

2548.78 -> Now you require a quick response

2550.9 -> and there will be n number of responses

2553.135 -> or n number of emails

2554.214 -> that would pop in but you do not want

2556.631 -> to pay a lot of money for this kind of service.

2559.2 -> So in this case you need cost optimization as well

2562.1 -> and you need Quick response as well.

2564.6 -> So this is where your general purpose instances come

2567.5 -> into picture next on this list.

2569.7 -> You have yard compute instance.

2572 -> Now what a compute instances these are

2574.581 -> for applications that require a lot of processing.

2578 -> Now when you say

2578.894 -> computation they have better computation power.

2581.521 -> That means if there is a lot of data that need

2584.169 -> quicker computation power you can use these kind of instances.

2587.4 -> What is an example.

2588.7 -> You have your analyzing streaming data now

2591.8 -> if you know,

2592.517 -> what stream Data is it is the data

2594.3 -> that continuously flows in and flows out.

2596.653 -> That means you are streaming the data say

2598.774 -> for example this session it is being streamed, right?

2601.593 -> I mean the information

2602.887 -> or whatever is happening here it is going live.

2605.408 -> So in order to process this kind of data,

2607.6 -> you need systems that give you good computation power

2610.75 -> which are very active and very good in nature.

2613.4 -> So when you talk about compute instances,

2615.7 -> they provide you with these kind of services and that is why

2618.755 -> if you are dealing with streaming data

2620.647 -> if you wish to analyze this kind of data,

2623 -> Definitely go for compute instances.

2626.1 -> So next on this list.

2627.4 -> We have memory instances.

2629.1 -> Now, what are these instances for?

2631.1 -> Now?

2631.3 -> These are the instances that are required for applications

2634.1 -> that require more memory or in better terms more RAM,

2637.2 -> right random access memory.

2638.8 -> So these are for applications

2641 -> that require good computation power again,

2643.668 -> like the previous one,

2645.1 -> but when you talk about Ram,

2647.033 -> it is something that resides in your local system, right?

2651 -> So you need instances.

2653 -> Which have good memory capacity

2654.842 -> and what kind of application it serves?

2657.1 -> Well, you can think of applications

2659.1 -> that need multitasking multi processing say for example,

2662.5 -> I need a single system

2663.842 -> that does fetching data for me as well process it for me

2667 -> as well dashboard it for me as well

2669 -> and then gives it to the End customer as well.

2671.3 -> So these kind of applications

2672.8 -> require memory instances moving further guys.

2675.7 -> We have the storage instances as the name suggests.

2678.824 -> These applications are

2680.2 -> or these instances are for applications that require.

2683.258 -> You to store huge amounts of data.

2685.274 -> Say for example,

2686.272 -> you have large size applications like your big data applications

2690.2 -> where the amount of data is used number.

2692.628 -> So you would be requiring more storage more storage flexibility

2696.508 -> in that case.

2697.357 -> You can opt for instances that are specifically

2700.358 -> optimized for storage kind of requirements.

2703.2 -> And then you have your GPU instances.

2705.4 -> If you know what GPU is you would understand

2707.992 -> what it serves that means

2709.5 -> if you are interested in graphical kind of work

2712.087 -> where you have basically A heavy Graphics rendering

2715 -> in that case you can opt for GPU kind of instances

2718.4 -> which basically help you sir purposes like 3D modeling

2721.499 -> and stuff like that.

2722.6 -> So guys, this was about the different kind of instances.

2725.5 -> Now, let us try and understand

2727.8 -> what are the different instance pricing models

2730.472 -> that are out there.

2732 -> So guys when you talk about pricing ec2

2735 -> or a SS in general,

2736.6 -> it ensures that you can save a lot of money,

2739.609 -> but normally what people do is they are under the And that

2743.6 -> if we just go ahead

2744.604 -> and take in Cloud probably you would go ahead

2746.931 -> and save a lot of money.

2748.2 -> Yes Cloud does support applications in such a way

2751.8 -> that you would spend very

2753.288 -> less amount but it involves a lot of planning guys.

2756.229 -> So each time you use a particular service.

2758.708 -> It is very important to understand.

2760.8 -> How does that particular service work?

2763.117 -> And if you actually plan in the services in that manner

2766.5 -> you would actually end up saving a lot of money.

2769.2 -> So let us try and understand

2770.6 -> how the pricing models work when you talk about it.

2773.1 -> See two in particular.

2774.5 -> So Guys.

2774.834 -> These are some of the pricing models

2776.3 -> that easy to has to offer to you.

2778.157 -> You have your on demand dedicated on the spot

2781.665 -> and reserved instances.

2783.6 -> Now, let me try and simplify what these instances are.

2787.1 -> And what do I mean by these now

2789.1 -> when you say an on-demand instance as the name suggests,

2792.2 -> it is an instance that you demand and you get it.

2794.7 -> Now these instances are made available to you

2797 -> for a limited time frame say for example,

2800.1 -> I need a particular instance for an hourly basis.

2803.4 -> So I would be wanting to use that instance

2805.747 -> for only that Eurasian.

2807.1 -> So to use that instance for that particular duration.

2810 -> What I do is I actually go ahead and demand this instance.

2813.3 -> So a tub -

2814.2 -> would give me that instance but it would work for

2817.4 -> an are only

2818.2 -> so my prices for that instance would be fixed on that manner.

2821.7 -> I mean the fact

2822.547 -> that I would be using it for one instance

2824.9 -> or for an one are basically

2826.649 -> so I would be charged only for that one hour.

2829.5 -> And once that are

2830.9 -> is complete that instance it gets Terminated on its own

2834.7 -> it's similar to renting a flat for one month suppose

2838.559 -> if I move to a new city

2840.3 -> and I'm looking something temporary say,

2842.9 -> for example, I'm looking for a hostel

2844.7 -> or a paying guest kind of a living system.

2847.2 -> Right?

2847.9 -> So in that case,

2848.7 -> what I would do is I would upfront go and tell the owner

2851 -> that I would be staying here for a month.

2853 -> You can charge me for a month only

2854.82 -> if it is 1000 more than normal charge.

2856.752 -> It is fine.

2857.4 -> But once the month is over,

2858.938 -> I would like to leave right so that kind of service

2861.88 -> or that kind of instance.

2863.3 -> Demand is called

2864.491 -> as on-demand instances basically dedicated now Guys.

2868.3 -> These instances are kind of given to

2870.81 -> a particular organization

2872.6 -> so that their security is defined better

2875.35 -> than other say for example,

2877.317 -> if I need to protect my data,

2879.364 -> I need my data to be privatized Now understand this thing AWS

2883.9 -> or the other Cloud platforms are highly secure.

2886.6 -> Your data is secure no matter

2888.2 -> whether they are on dedicated instance or not.

2890.776 -> But what happens is you normally share your Space

2893.6 -> with someone else data remains private

2895.842 -> but there are companies

2897.195 -> that deal with highly confidential data.

2899.488 -> And in that case they want that extra Assurance as an okay.

2902.9 -> I am using a space which is not shared by anyone.

2906.13 -> So in that case you have dedicated instances,

2909.3 -> which basically serve your needs like high security

2912.6 -> and basically an isolation from the other vendors as well.

2916.435 -> So that is what dedicated instances do they are costlier.

2920.204 -> But yeah, they give you that isolation on spot.

2923.3 -> Now guys, when I say A non spot instance,

2925.572 -> it is like bidding say for example,

2927.6 -> I am buying a particular share.

2929.5 -> So I have a particular budget right

2931.2 -> so I might have a budget of $300.

2934.2 -> So what I do is I go ahead and buy the chair

2936.7 -> and I sat in a cap as an okay to the max

2939.5 -> I can bid for $300 for the share.

2942.4 -> So if the price goes above 300 dollars,

2944.8 -> I'm not taking that share right?

2946.535 -> So if there is a particular instance you can bid

2949.3 -> for that instance as an okay.

2950.71 -> This is the maximum price that I pay for this.

2952.9 -> Ernst so if that instance is available at that price

2956.004 -> it is given to you

2957.1 -> and if after a particular duration the price

2959.372 -> of this instance can change

2960.8 -> so it is available to you for a limited period of time.

2963.5 -> So if you are dealing with data that is volatile

2966.6 -> and you want to work on the data in real-time,

2969.56 -> so you cannot for this instance

2971.6 -> because after a while the price of this instance might change

2974.6 -> and this instance might be terminated

2976.568 -> and you might not be able to use it for a longer while

2979.449 -> but the thing it does is it is available

2981.743 -> to you at a cheaper price?

2983.3 -> And at the pricing bit that you put on it,

2986 -> so that is why it is more affordable.

2988.318 -> But again, it is good

2989.671 -> for volatile data only finally you have the reserved instance.

2993.6 -> It is like renting an apartment on a lease

2996.8 -> for a longer period right?

2998.513 -> I mean suppose

2999.468 -> if I am getting a flat on an agreement will basis

3002.743 -> where I sign an agreement for a year.

3005.2 -> That means I am reserving this flat

3007.791 -> for one complete year, right?

3010 -> So nobody else in comments say that okay,

3012 -> you have to vacate this.

3013.2 -> A flat right so that is one benefit.

3015.601 -> And the other thing is you have a fixed set of rent.

3019.1 -> So if you're taking something for a longer duration,

3021.724 -> there is a chance

3022.6 -> that you might end up paying lesser money for that as well.

3025.8 -> Now what happens here is

3027.5 -> when you talk about it from the instance perspective suppose,

3030.5 -> you know that you would be needing

3032.1 -> this much configuration for this duration.

3034.2 -> You can rent that particular instance for that duration,

3037.7 -> and probably you end up saving a lot of money now

3040.666 -> when you talk about AWS it gives you Latif

3043.2 -> where you can actually go ahead

3045.1 -> and upscale downscale your instances to your needs.

3047.6 -> You can kinda terminate stuff and move to the next up.

3050.8 -> But if you are certain about certain things as an okay,

3053.3 -> I have to use this no matter

3054.7 -> what happens for a longer duration in that case.

3057.222 -> You can offer reserved kind

3058.813 -> of instances and those are more affordable to you.

3061.7 -> So Guys, these were different types of instances

3064.4 -> based on the pricing that is there.

3066.5 -> Now.

3066.735 -> We have talked about General cluster ization of instances,

3069.885 -> like the general-purpose

3071.257 -> the GPU that was based on They're functioning,

3073.823 -> right then we learned about the pricing models as well.

3077.095 -> Now.

3077.6 -> There is one more type

3079.1 -> that we need to understand or one more classification

3081.798 -> that we need to understand.

3083.2 -> Let us try and take a look at those as well.

3085.5 -> So we are classifying

3086.846 -> instances based on that General functioning.

3089.604 -> Now, what do I mean by this?

3091.6 -> Well, these are the types.

3092.899 -> Let us take a look at those one by one first.

3095.1 -> So when I say burstable instance,

3097.039 -> we've talked about general purpose instances, right?

3100.181 -> So what happens is there is a category of General.

3103.2 -> But was instances with start

3105.607 -> with a base utilization power available to you.

3109.1 -> That means if you want to utilize your CPU

3112.1 -> for a certain amount burstable instances are good here.

3115.4 -> Let me throw in some more light as in what am I talking about?

3118.4 -> Exactly suppose.

3119.8 -> I need a CPU utilization of 20% And I know that

3124 -> so I can go for burstable instances.

3126.6 -> What they do is they start

3128.428 -> with the functioning of 20% but in case

3131.1 -> if I'm dealing with data

3132.7 -> that It is not constant

3134.181 -> that might change with time say for example,

3136.951 -> if my website experiences more traffic,

3139.4 -> so I might need more performance.

3141 -> Right?

3141.5 -> So in that case

3142.508 -> what burstable instances do is they burst

3145.2 -> out of their current performance 200% CPU utilization

3149.2 -> so that you can get more performance.

3151.8 -> Now what happens here is you are charged a particular amount

3155.331 -> for these instances

3156.455 -> and you have certain credits for which you can use

3159.406 -> the burst people performance and if you do not use the bustable.

3163.2 -> Performance those credits can be used later as well.

3166.4 -> So you are getting optimize performance as well.

3169.2 -> And you are saving some money as well in case

3171.788 -> if there is an urgent traffic

3173.4 -> that you experience you have something called

3175.6 -> as EBS optimized now

3177.7 -> when you talk about EBS optimized now,

3180.3 -> these are the applications

3182 -> where basically you are processing data

3185.1 -> at a higher speed.

3186.5 -> Say for example, there is some application

3188.75 -> where the data is flowing in continuously.

3191 -> So I need quick response, right?

3193.2 -> So EBS backed up or EBS optimized instances.

3196.6 -> What they do is they give you high input output processing

3200.5 -> and that is why these are good instances to art

3203.686 -> for these situations cluster networking.

3206.816 -> Basically, they form clusters

3208.736 -> of instances now a particular cluster

3211.206 -> what it does is it serves one kind of purpose say

3214.5 -> for example in my application.

3216.7 -> What I want is I have different sections

3219.5 -> and in different sections my first section requires

3222.895 -> To be processing data at a faster rate.

3225.4 -> The other one.

3226.232 -> I wanted to be storage

3227.581 -> optimized so I can Define different clusters

3230.17 -> of instances that serve different purposes here.

3233 -> And then I have the dedicated one.

3234.808 -> We've already talked about dedicated one.

3237 -> It is more related to the data security part.

3239.52 -> So Guys, these were the different types of instances.

3242.5 -> I know I've talked about a lot of stuff

3244.9 -> once we get into the demo part

3246.4 -> probably this would ease up a little more for you people.

3249.2 -> I believe you people are

3250.4 -> with me and you are following this session.

3252.8 -> So guys now let us move further and take a look at the use case

3255.9 -> so that we can just move further

3257.4 -> and take a look at the demo part as well for this use case.

3260.9 -> I've considered a derecho itself.

3262.882 -> Let us try and understand

3264.359 -> what could be the possible problems

3266.364 -> that can be solved by using these instances.

3268.9 -> Now imagine that

3270.13 -> if it is Erica used AWS as their Cloud partner

3273.7 -> and they used the ec2 service.

3275.9 -> So what kind of problems could be solved by these instances

3279.026 -> that we just talked

3280.064 -> about suppose we have the first problem

3282.3 -> where you have To analyze the data of the customer.

3285.5 -> So what kind of application would you use?

3288.008 -> Can you guess that for me?

3289.6 -> I won't be looking at your answers.

3291.2 -> Let me just quickly go ahead and give you other examples as

3294.1 -> well so that we can discuss these one by one suppose.

3296.8 -> You also have an auto responsible system now compare

3299.9 -> these two and let me know which one

3301.549 -> would you believe would be served better

3303.5 -> by these instances that we've just talked about.

3306.2 -> So when you talk about the performance here guys

3308.807 -> when you talk about analysis of data for the customers data,

3312.08 -> it is never Went right at times

3313.8 -> the data is used at times it is less.

3315.6 -> So in this case, I would need burstable performs.

3318.8 -> So my general purpose burstable performance instances

3322.135 -> would serve me better right auto response email system.

3326 -> I need quick response,

3327.303 -> but I do not want to invest a lot

3329.2 -> of money EBS optimized instances

3331.4 -> with iops would help me better search engine and browsing.

3335.5 -> I believe it is fairly clear.

3337.105 -> I'm talking about browsing and search engine

3339.5 -> to different things I want to do I would be opting

3342.4 -> for Stud Network instances,

3344.412 -> right and confidential data.

3346.5 -> Well, I would be opting for the dedicated instances here.

3350.7 -> So guys, this was a very simple use case.

3353.3 -> So let us move into the demo part and try

3355.3 -> and understand ec2 a little

3356.999 -> more shall we so guys what I've done is I've gone ahead

3360.4 -> and I've signed into my AWS Management console.

3363.4 -> Please forgive me guys.

3364.62 -> I have a lot of gold today

3366 -> and that is why my voice is little Jiggly and echoing.

3369.265 -> So I hope you people are not offended by

3371.559 -> that moving further.

3372.735 -> The guys this is the AWS Management console.

3375.2 -> You can sign in to AWS free tier account

3377.5 -> and probably Avail these Services you can practice

3380.094 -> a lot of stuff by signing into your free tier account.

3382.9 -> How do you do that?

3384.118 -> Just go ahead and look

3385.529 -> for a SS free tier and sign in with your credit card

3388.8 -> or debit card.

3389.5 -> You won't be charged you have these services

3392 -> for free for one complete year

3393.8 -> and you can practice most of the services that are there.

3396.6 -> There is some free tier limit on these services.

3399.401 -> So check the upper cap as in what those limits are so

3402.5 -> that you Get charged.

3404.1 -> So guys this is how the console looks like.

3406.6 -> We are going to go ahead and learn about easy to hear.

3409.3 -> That is the instant service in AWS.

3411.5 -> So let's search for ec2.

3414.6 -> And you would be redirected to this page guys.

3417.247 -> Now when you talk about ec2,

3418.81 -> there are a lot of things that you can do.

3421.1 -> You have Amazon Marketplace

3422.7 -> where you have am eyes, I will tell you.

3425.059 -> What am I is our do not worry you can just go ahead

3428.2 -> and launch our instances.

3429.552 -> You can attach volume to it.

3431.2 -> You can detach volume storage from these instances.

3434.103 -> And when I say am I is those are Amazon machine image has

3437.397 -> that means once you create an instance,

3439.501 -> you can create an image of that instance as well.

3442.023 -> That means a template of that instance

3444.215 -> as Suppose you have certain applications running

3446.98 -> on top of that instance certain specific settings

3449.7 -> that you've done for those instance

3451.4 -> and you do not want to do those settings again.

3453.7 -> And again, you can create images of that instances as well.

3457.5 -> So let us see what all we can do with these instances.

3460.972 -> So let us first launch an instance.

3463.4 -> So guys, once you click on that launch instance button,

3466.64 -> you would be given a number

3468.342 -> of options to choose from you can launch

3470.8 -> Linux instances Ubuntu instances Windows instances.

3474.357 -> And you can choose the EBS backed up non-abs backed up.

3478.2 -> So there are a lot of choices

3479.614 -> when you actually go ahead and launch these instances.

3482.2 -> You can see this Ubuntu Red Hat Microsoft Windows

3485.8 -> and there are specific instances specialized

3489 -> in deep learning some of our service specification.

3492.1 -> You can see that there are quite a few instances,

3494.6 -> but ensure that if you are practicing

3496.844 -> choose the free tier eligible one for now,

3499.4 -> I'm going to go ahead and launch a simple Windows instance.

3502.517 -> Let's not get into the Ubuntu one

3504.4 -> because Request a petition to sign for that.

3507.1 -> So let us not do that.

3509.8 -> So guys once you click on launch an instance,

3512 -> you can see that you are redirected to this page.

3515.6 -> Now if you take a look at the information here,

3518.076 -> it talks a lot.

3519.024 -> Now.

3519.26 -> This instance is general purpose.

3521.1 -> We've discussed the other families, right?

3523.3 -> This is one.

3524.3 -> This one is T 2 micro there are

3526.8 -> t 2 T 3 micro and medium and bigger instances as well.

3531.1 -> The size is very guys the Tito micro one is free tier eligible.

3535.52 -> You have t to Nano you have small right?

3538.3 -> So you have me do Another large instances as well.

3541.6 -> So when you say a microphone,

3543.3 -> it has 1 V CPU and one gigabyte of memory instant storage.

3548.6 -> It is EBS backed up and what kind

3551.2 -> of network performance it gives you low to moderate.

3554.5 -> So I would say configure further.

3557.2 -> These are some configuration details what network it

3559.805 -> is following what subnet ID.

3561.205 -> It is falling

3561.864 -> that means it falls under the cloud Network guys.

3564.3 -> That means your Cloud would have a network

3566.554 -> and under that Network lies are instance

3568.5 -> so that it's accessible.

3569.7 -> SS policies security policies can be managed.

3572.7 -> So let it be basic for now.

3574 -> Let us move further.

3576.9 -> Storage now guys,

3578.3 -> this is the storage it is your route storage

3581.212 -> and 30 GB of space.

3582.578 -> You can change it

3583.8 -> if you want say a hundred but let us take 2 34 now

3587.4 -> and guys you can see these are the types.

3589.131 -> You have a general purpose.

3590.3 -> You have your provisioned magnetic now,

3592.505 -> there is one more type of instance guys.

3594.8 -> That is HDD kind of an instance,

3597.167 -> but guys when you talk about root storage,

3600.2 -> you cannot attach HDD to it,

3602.08 -> right because route storage is something

3604.7 -> that is constantly Constant,

3606.3 -> if you wish to have HDD kind

3608.071 -> of storage it has to be attached secondary.

3610.728 -> So if I add new volume here,

3612.5 -> you can see and if I search for this now,

3615.1 -> it gives me an option of cold HDD, right?

3617.6 -> So that is what guys I mean in order to have this kind

3620.9 -> of HD kind of a volume you need to use secondary storage for it.

3625.4 -> So let us cancel this for now and just go ahead and say next

3629.2 -> you can add in tags guys for the Simplicity

3631.9 -> of namesake say for example sample today and let's just say

3639.9 -> next Security Group guys Security Group.

3643.8 -> What do I mean by this?

3645.2 -> Well, basically you have set

3647.1 -> of policies as in who gets to access.

3649.2 -> What kind of traffic do you want to your instance?

3651.5 -> What kind of traffic do you want to flow out of your instance

3654.5 -> so you can create

3655.5 -> a security group and you can use customized as well

3658.3 -> when you create one this type is RDP.

3660.891 -> That means it can allow traffic from a desktop

3664.1 -> or a remote desktop app and through which I can log.

3667.608 -> To my system I can add other rules as well.

3670.441 -> I can add PCP HTTP kind of rules.

3672.6 -> And these are the port ranges you can specify those for now.

3676.07 -> I'm allowing traffic from everywhere through our DP

3678.9 -> and I can say review

3680.323 -> and launch improve your security it says

3683.1 -> but this is a basic one guys,

3684.7 -> you can add in more rules as I've already mentioned.

3687.3 -> So let's not do that.

3688.6 -> Let's say launch generate a key pair now a key pair is something

3692.8 -> that lets you log into your instance.

3695.1 -> It is a double security for your Instance you

3698.3 -> do not want your instance to be left insecure.

3701.3 -> Right?

3701.6 -> So in that case, you need to generate a key pair.

3704.4 -> You can use an existing one

3705.941 -> or you can create a new one as well.

3708 -> So let's just say

3709.251 -> that I want to create a new key pair.

3712.3 -> So I say create and let us say Vishal 3 4 1 2 1 and let's

3718.7 -> just say download.

3720.8 -> So guys once you download this instance,

3723.5 -> what you do is

3725.1 -> and protects cut it from here and I'm going to go ahead

3730.6 -> and paste this instance

3732.6 -> to the desktop guys and let's just say paste.

3737.7 -> Here it is.

3738.4 -> So the reason I'm doing this is

3739.9 -> because basically we would be needing this thing is

3742.4 -> if you lose this key there is no other way to explain.

3745.4 -> Is your instant so make sure you keep it safe

3748.2 -> and I say lunch.

3752.5 -> So guys now this process it takes a minute

3755.3 -> or two to go ahead and launch our instance.

3758.1 -> So meanwhile you'd have to bear with me.

3760.615 -> So what happens is

3762 -> once you do actually go ahead and launch this instance.

3764.7 -> It involves a couple of steps

3766.783 -> like basically it does some Security checks

3769.739 -> some status checks and while these statistics happen,

3773.4 -> it takes a minute

3774.5 -> or two and once the instances up and ready we can actually go

3777.5 -> ahead and take a look at this instance.

3779.7 -> So meanwhile guys what I'm going to do is I'm going to go ahead

3782.3 -> and take to the ec2 part Now there are three instances

3787.2 -> that are running guys.

3788.3 -> Now, this is somebody else's account.

3790.123 -> So there are quite a few other instances

3792.1 -> that are running you can see

3793.8 -> that there must be some instance here

3796 -> which basically is initializing.

3798.346 -> So this is the one that we are going to use.

3801.6 -> This is the ID.

3802.4 -> Let's not remember

3803.458 -> that we know that this is getting initialized.

3805.9 -> So as these are the other instances this one is start.

3809.4 -> Let us take a look at this instance as

3811.25 -> well to understand as an what happens.

3813.1 -> So Guys, these are the options that I have right?

3815.7 -> You can actually go ahead and get the password.

3818.284 -> You can create a template for your instance.

3820.9 -> What you can also do is you can start stop.

3823.699 -> Now.

3823.935 -> This instance is already stopped.

3825.735 -> So you do not have these options that has stops.

3828.476 -> He Burnett and reboot you can start this instance

3831.3 -> and probably you can go ahead and do that.

3833.151 -> Now when you stop an instance

3834.549 -> if you want to actually

3835.7 -> make a snapshot you want to take snapshots

3837.8 -> you want to create Amazon machine image is out of it.

3840.4 -> What you do is you stop that instance

3842.525 -> so that you prevent any activity from happening.

3845.3 -> In that instance

3846.157 -> so that you can take an exact snap of it.

3848.3 -> So that is why you stopped an instance

3850 -> when you wish to do these kind of operations.

3852.4 -> Once you start it again,

3853.888 -> you can make it function normally at it was functioning.

3857.3 -> If you are done using an instance,

3859.089 -> you can terminate it there

3860.5 -> and there guys, so these are the options instance setting.

3864.4 -> Okay.

3865.1 -> So as these are the options you can add tags to it.

3867.9 -> You can attach replace.

3869.475 -> I am rules that is access management policies guys.

3872.903 -> So you have a user access management.

3875.3 -> Here you can attach roles to it as well.

3877.6 -> You can change the instance type guys you can click on it

3880.654 -> and you can go ahead and do that.

3882.4 -> You can change it to higher versions as well.

3885 -> Now, why do you need to do this suppose?

3887.103 -> I am experiencing a particular traffic

3889.1 -> and my instance supports that need but

3891.3 -> if I move further and future,

3893.166 -> I need to cater more traffic.

3895.001 -> What do I do in that case in that case guys?

3898.001 -> I can actually go ahead and update it

3900.177 -> to a larger version unlike your other applications.

3903.6 -> You are on-premise infrastructure.

3905.4 -> Where you have to actually go ahead

3907.1 -> and have new servers you data on top of it here.

3910.2 -> What you do is you just click on this thing and it happens

3913.552 -> in a couple of seconds.

3915 -> You are instance gets optimized or upscale to a better lever.

3919.2 -> And that is why it is highly scalable

3921.9 -> because what you can also do is you can change

3924.1 -> termination protection of this is for data security suppose.

3927.8 -> If I am using a particular instance,

3930.155 -> and in that case,

3931.3 -> I accidentally deleted my data would be lost.

3934 -> Right?

3934.8 -> So what this Does is it changes

3937.1 -> or turns my termination protection on that means

3939.921 -> if I have to delete this instance?

3941.9 -> I have to get into the instance.

3943.6 -> I have to change the policy and then delete it.

3946.5 -> I mean I cannot delete it unknowingly, right?

3948.7 -> So that is why this service helps now while talking

3951.347 -> about these things guys are instance is up and ready.

3954.1 -> Let us just launch it.

3957.561 -> I say connect.

3959.4 -> And it says download remote desktop file

3961.914 -> the RDP path that I talked about right

3964.3 -> and I need to get in my password as well guys to login.

3967.7 -> How do I do that?

3968.8 -> I click here.

3969.679 -> I choose the file for that.

3971.475 -> I'm gonna go to the desktop.

3973.337 -> I'm going to scroll down.

3975 -> There is a file called as Vishal.

3976.8 -> I open it and I decrypt it and there you go guys.

3980.2 -> My password is here.

3981.4 -> I can just copy it.

3983.1 -> So if this is copied I can launch this.

3987.1 -> Remote desktop file.

3989.3 -> It would ask me for the password.

3991.1 -> I would say take this and okay.

3995.8 -> Do you want to login and securely?

3998.338 -> Yes.

4001.2 -> And guys a Windows instance would be launched.

4006.7 -> It is just like your Windows operating system,

4010.087 -> but it is running on my existing system guys.

4013.6 -> They can see personalized settings.

4015.4 -> It is setting up personalized setting for me

4017.5 -> and in half a minute maybe in 10 seconds.

4020.9 -> My Windows app would be up and running.

4024.1 -> So just like my Windows device.

4026.8 -> I have one more Windows device

4028.4 -> so I can do something in this device

4030.7 -> and something else in my normal Windows device as well guys.

4034.848 -> So this is what you are.

4036.602 -> Instance does it basically creates an instance

4039.757 -> of word Sewell machine

4041.3 -> for you to work on I Believe by Navi one understood.

4044.545 -> What a virtual machine is.

4046.3 -> So guys we are done with this part.

4048 -> So let us just use it for now.

4049.6 -> Let us see

4050.4 -> if there is anything else that we need to talk about now,

4053.715 -> if I come back here I've mentioned

4055.5 -> that you can take snapshots, right?

4058.2 -> So these are am is what am I is

4061.053 -> it is an image basically

4062.9 -> so I can actually go ahead and launch an Emi

4065.429 -> for an instance that I already have.

4067.488 -> I can create an image of it.

4069.1 -> There is a volume here.

4070.515 -> So my instances are EBS backed up right?

4072.867 -> So there is a block storage attached to it.

4075.4 -> Can I add another storage to it?

4077.3 -> Yes, I can remove

4078.3 -> the previous storage and attach a different storage to it.

4081.5 -> Say for example,

4082.314 -> this is the store is that I have with me

4084.3 -> if I click on it and I will go into actions.

4087 -> I can create a A short out of it.

4089.222 -> Once I create a snapshot out of it.

4091.325 -> I can attach it to the existing instance.

4093.825 -> So we just launched an instance, right?

4096.2 -> So if I want to replace the volume

4098.3 -> that is already attached to it.

4100.1 -> What I do is I actually go ahead and detach the volume

4103.316 -> that is already attached.

4104.833 -> So I would be stopping my instance First

4107.2 -> Once I stopped the instance.

4108.847 -> I can come to the volume assume

4110.652 -> that this volume is attached to some instance.

4113.3 -> So I need to detach it from here and the snapshot

4116.403 -> that I've already created.

4118.1 -> Or if I have created one,

4119.8 -> I can select that and I can attach

4122.275 -> that to the existing instance.

4124.533 -> All I have to do is I have to go ahead

4127.458 -> and create an image here.

4129.3 -> Once I create an image it would ask me.

4131.77 -> What can I do with it?

4133 -> I would ask me to actually go ahead

4134.7 -> and given the region in which the instance was created.

4138.221 -> Now my instance

4139.2 -> that I just used was created in a particular region.

4142.3 -> I'm working in Ohio reason for now.

4144.7 -> What do I mean by these regions?

4146.564 -> Well, basically what Says AWS has different data centers

4150.1 -> in different regions of the world.

4151.831 -> So you can choose the reason

4153.264 -> that is convenient to you that suits your business needs right

4156.358 -> so I can create instances in those particular regions.

4159.008 -> So if my instance was in particular region,

4161.3 -> I need to create a snapshot in that region

4163.9 -> and then attach that snapshot or that volume to my instance.

4167.7 -> So guys I Believe by now,

4169.8 -> you've understood a lot

4171 -> of things you've understood what instances are

4173.46 -> how to launch those

4174.427 -> how to create those and how to make those work.

4176.752 -> So as far as this is Ian goes guys.

4178.452 -> I wanted to talk

4179.265 -> about these pointers one more important point

4181.965 -> that I would like to mention here is make sure

4184.3 -> that you terminate your instances so

4186.358 -> that to avoid any charges

4187.829 -> if there are any now this being a free tier account.

4190.7 -> I don't think there would be a lot of charges

4193.018 -> but still I would request you to actually go ahead

4195.6 -> and terminate the instances even

4197.3 -> if they don't charge you a lot because that is a good practice

4199.857 -> because there are certain services that might charge

4202.2 -> you a lot more guys.

4203.8 -> So I'm going to terminate my instances the ones

4206.547 -> that I have created today.

4208.3 -> So let's just wait a minute and in a minute or two guys,

4211.9 -> these instances would be terminated from end to end.

4219.8 -> Today's session is going to be all about AWS Lambda.

4223.1 -> So without making any further Ado,

4224.942 -> let's move on to today's agenda to understand

4227.4 -> what all will be covered today.

4228.95 -> So we'll start off today's session by discussing

4231.5 -> the main services in the AWS compute domain after that.

4234.9 -> We're going to see why AWS Lambda is as

4237.398 -> a separate service.

4238.592 -> We're going to discuss what aw is Lambda actually is

4241.8 -> and then we'll move on to the part where we'll see

4244.2 -> how you can use a double s Lambda using the AWS sdks

4248.3 -> once we're done with that I'll teach You guys

4250.4 -> how you can integrate your SDK with the Eclipse IDE?

4253.9 -> And in the end we'll be doing a demo.

4255.726 -> So let me quickly show you guys

4257.3 -> how we will be using AWS Lambda in today's demonstration.

4262.5 -> So guys, this is a website

4263.875 -> that I created which is hosted on the Local Host.

4266.504 -> Now what this website does is it applauds a file

4269.082 -> onto the H3 file system now once the file is uploaded.

4272.2 -> It sends me a mail regarding that now

4274.4 -> that meal is generated by a SS.

4276.4 -> I'm not now let me quickly show you

4278.4 -> how that mail actually looks

4280.2 -> like so let me upload a file over here.

4282.7 -> So let file be this I click on open and before uploading image.

4287.7 -> I will show you my inbox.

4289.4 -> So as of now,

4290.362 -> I don't have any As you can see, right.

4294 -> So what I'll do is I'll click on upload image now.

4297.776 -> It is S3 upload complete.

4299.699 -> Now.

4299.9 -> What is this website does is it will upload my file?

4302.9 -> It will rename the file according to the system time

4305.7 -> so that there is no conflict in the name of the object.

4308.4 -> Right?

4308.754 -> So whatever file

4309.7 -> that I've uploaded right now will be uploaded

4312.3 -> on in this bucket.

4313.4 -> So if I refresh this you can see

4315.9 -> that there's a file over here, right?

4318.7 -> So this file has now been renamed, right?

4321.761 -> Right, and I also have an email over here,

4325.1 -> which says awacs test, right?

4327.8 -> So if I click on this email,

4329.8 -> I can see that I have got a mail from this address saying

4334.6 -> that an object has been uploaded the name of the object.

4338.181 -> Is this the size of the object?

4340.277 -> Is this the bucket name?

4341.9 -> Is this and it will slash modified on 12/31 UTC right?

4346.9 -> So let me quickly compare

4348.51 -> whether this file name is the same.

4351.226 -> So it's seven four eight

4353.5 -> and it's a sin for it here as well.

4355.9 -> Awesome.

4356.7 -> Now, the next cool thing

4358.139 -> that you can do over here is you can move this file

4361.117 -> to some other folder.

4362.2 -> So all you have to do is you will reply to this mail

4365.2 -> by saying move you click on send now when I send move

4370.694 -> to this email address

4372.4 -> that I have configured in my code what it does

4375.4 -> is it will basically move this file from this bucket

4378.8 -> to some other bucket.

4380 -> So let me quickly.

4380.9 -> Press it and see whether my file has been moved.

4385.323 -> So as you can see my bucket is now empty now.

4388.707 -> Let me go back.

4390.375 -> So basically my file was there in Erica demo now,

4394.067 -> it will be there in quarantine demo bucket.

4397.6 -> So as you can see seven four eight file has now been moved

4400.6 -> to the quarantine demo by simply writing a male over here.

4404.3 -> It says move

4405.6 -> so we'll be creating this demo today.

4408.2 -> Let's move on to the first topic of today's discussion.

4411.7 -> That is the AWS compute domain.

4414.2 -> So the main services are under this domain are easy

4417.5 -> to elastic Beanstalk and AWS Lambda.

4420.5 -> Now among these three the most important service is easy to so

4424.9 -> easy to is basically just like a raw server.

4428 -> It is like a personal computer that you're working

4430.9 -> on remotely, right?

4432.2 -> So it can install any kind of improv operating system

4435.698 -> of your choice,

4436.707 -> which is supported by the AWS infrastructure

4439.7 -> and then you can use it in any manner as you want.

4442.456 -> You can configure it to become.

4444.178 -> A web server.

4444.922 -> You can configure it to become a worker

4447.1 -> to your environment anything.

4448.9 -> Uh, next service is elastic Beanstalk,

4451.3 -> which is an automated version of ec2.

4454 -> So with the elastic Beanstalk,

4455.5 -> you don't get the access to the operating system,

4458.414 -> but you still have a control over the configuration

4461.483 -> of your system

4462.347 -> so you can choose what kind

4464.067 -> of instance you want to launch, right?

4466.342 -> So elastic Beanstalk is used to deploy an application.

4469.6 -> So basically you just upload your code and your application

4473.127 -> is deployed on the AWS infrastructure, right.

4476.002 -> So this is what elastic Beanstalk is all about.

4478.8 -> Then we have the AWS Lambda service.

4481.5 -> So the Lambda service is again an automated version

4484.965 -> of ec2 wherein you don't get the access

4487.6 -> to the operating system with the errors Lambda.

4490.666 -> You don't even have the choice to choose what kind

4493.4 -> of configuration you want with your server, right?

4496.363 -> So with either plus Lambda you just have to upload your code

4500.024 -> and it executes.

4500.998 -> It's that simple but then why do we have?

4503.925 -> Have an AWS Lambda service when we have elastic Beanstalk.

4507.383 -> So let's understand that.

4509 -> So either plus Lambda like a told you guys.

4511.3 -> It is an automated version

4512.925 -> of easy to just like elastic Beanstalk,

4515.3 -> but then with AWS Lambda,

4517.1 -> you can only execute background tasks, right?

4520.6 -> You cannot deploy an application.

4523.061 -> So either plus Lambda is not used to deploy an application.

4527.6 -> It is used to execute background tasks.

4531.1 -> Other than that like I told you guys you don't have

4533.633 -> to choose the Integration

4534.9 -> and a double s Lambda you don't have to choose what kind

4538.2 -> of servers you want on depending on your workload.

4541.4 -> Thus kind of configuration.

4543.153 -> The server configuration is assigned to you, right?

4546.4 -> So this is why we use AWS Lambda,

4549.1 -> but then let's go on

4550.779 -> to the definition part and see what AWS Lambda actually is.

4555.9 -> So according to its definition.

4557.8 -> It's a survivalist compute service

4559.637 -> because you're not choosing the server's right.

4562.2 -> You're not choosing what kind of Aggression you want

4564.9 -> in your server?

4565.6 -> It's a serverless compute service you

4567.4 -> just upload your code.

4568.757 -> And the code is executed.

4570.3 -> It's that simple right

4572 -> and also like it's mentioned in the definition

4574.6 -> and I told you guys again again it is used

4577.1 -> to execute background tasks.

4579.3 -> It is not used to deploy an application guys.

4582.4 -> This is the main difference between

4585.1 -> elastic Beanstalk news12.

4587.1 -> So as an architect,

4588.542 -> you should know what the use case is

4591.2 -> and with service will suit it better.

4593.687 -> So Moving on now,

4595 -> you've understood what AWS Lambda actually is

4598.316 -> and why do we use it?

4599.9 -> Right?

4600.4 -> So let's move ahead to see how you can use this service.

4604.5 -> So you can use the service using the software development kits

4608.6 -> which are provided by AWS.

4610.6 -> So before moving ahead and understanding

4612.8 -> how you can use the skills.

4614.4 -> Let's understand what these kids are all about.

4617.5 -> So the software development kits are basically apis

4621.2 -> which are used by developers

4623.1 -> to connect to the desired service at the wound.

4625.8 -> So it makes the life of the developer easy

4628.5 -> because he can now concentrate on the logical part

4632.1 -> of his application rather than wasting time on understanding

4636 -> how you can connect his code to the service

4638.925 -> which is there on AWS, right?

4641.1 -> The other part is

4642.1 -> that these sdks are used with ID.

4644.8 -> He's right.

4645.5 -> So currently we have only two IDs

4647.695 -> which are supported

4649 -> that is eclipse and visual studio.

4651.5 -> So today in this session.

4652.699 -> I'm going to teach you guys.

4654.2 -> Is how you can connect your SD keys with the Eclipse IDE?

4658.9 -> So let's do that.

4660.2 -> So before that we are going to configure

4662.8 -> or we going to code ra SS and of function in Java,

4666.1 -> right?

4666.486 -> And that is the reason we're using Eclipse.

4669.2 -> Now.

4669.485 -> First of all,

4670.414 -> you have to install eclipse on a system.

4673.4 -> Once you do that.

4674.4 -> This is the eclipse green guys.

4676.414 -> This is how your Eclipse dashboard will look like.

4679.7 -> So for installing ews SDK on your Eclipse,

4682.9 -> you have to click on Help

4684.691 -> and then you'll go to install new software.

4687.7 -> Once you have reached here.

4689.1 -> You will enter the website name.

4690.7 -> That is aws.amazon.com / Eclipse.

4697.4 -> Once you have entered that just hit enter

4700.2 -> and it will list you guys all the SDK is

4702.6 -> which are available all the tools

4704.204 -> which are available select all the tools

4707.028 -> and click on finish

4708.146 -> and then it will take some time to download the SDK,

4711.2 -> but then it will integrate everything into your

4714.1 -> And then you'll have a button like this over here.

4716.982 -> Right?

4717.373 -> So with this button you can actually deploy a new server

4721.001 -> which is configured according to AWS.

4724.1 -> So guys, this is how you install sdks with IDE.

4728.7 -> Alright guys, so it's time for the demo now enough of theory.

4732.5 -> So what we'll be doing is

4734.5 -> where our aim is to create an application

4737.2 -> which will be uploading our files onto the S3 file system.

4741.1 -> And what a Lambda function here Willy We'll be doing is so

4745 -> like I told you guys

4746 -> Lambda function basically executes your background task,

4749.535 -> right so that we don't want to burden server

4752.3 -> on which the website is hosted in this task.

4754.829 -> We want some other server to execute this task.

4757.4 -> What is this task?

4758.354 -> We basically want

4759.307 -> to get an email with all the details of the file,

4762 -> which has just been uploaded on the S3 file system.

4765.3 -> So that email will be sent by the Lambda server now

4769.1 -> once we get that email if you reply to that email

4771.5 -> that the file has to be moved

4773.2 -> Lambda will Pick up that email it will read that email

4776.07 -> and it will perform the necessary operation.

4778.4 -> So if we specify move,

4779.742 -> what will basically do is it will pick that file move it

4783.1 -> to some other bucket and store it over there.

4785.9 -> So this is the project

4787.377 -> that will be doing right now sounds simple right?

4790.6 -> But let me show you the architecture.

4793.2 -> Let me explain you what the architecture tells you.

4796 -> So basically this is our website.

4798.163 -> So what our website we'll be doing is it

4800.734 -> will be uploading a file onto the S3 file system.

4803.9 -> At the same time it will also be making an entry into the sqs,

4807.631 -> which is nothing but a simple queue service

4810.2 -> which use your data, right?

4812.1 -> So as soon as your file is uploaded on to S

4814.9 -> 3 S 3 is bucket is configured

4817.1 -> in a way to invoke the Lambda function.

4819.6 -> Now as soon as the Lambda function is invoked now

4822.3 -> Lambda functions are stateless.

4823.864 -> They don't know anything about what file you have uploaded

4826.714 -> or what you have done.

4827.828 -> You have to feed them information.

4829.5 -> And that is the reason we have updated the entry in s us

4833.148 -> or the file which Recently been uploaded right?

4836.2 -> So what ew is Lambda will do is it will read this queue

4840.2 -> and we'll get the file name

4842 -> and we'll actually retrieve all the properties

4845 -> from that file name from S3.

4846.9 -> Now once it has retrieved

4848.567 -> all the file names all the properties of that file.

4852.035 -> It'll actually mailed me

4853.7 -> with using the SES service in AWS the details of that file now

4858.1 -> once I receive the details of that file,

4860.669 -> I have an option to reply to that email, right?

4863.7 -> Now how will I reply to that email is like this.

4866.6 -> So I will open the email client

4868.956 -> on my computer and I will reply to that email

4872.3 -> that email will actually go to that address

4875.6 -> which is actually pointed to my DNS server and

4879.153 -> that DNS server will actually redirect that email to SES.

4883.314 -> Now SES on receiving

4884.8 -> that email has been configured to invoke the Lambda function

4889 -> that Lambda function will be invoked again.

4891.818 -> The file will be read from the SQL.

4894.5 -> That file will be moved to a new bucket

4898 -> and in the end that message will be deleted by

4900.6 -> ask U s-- now my S us has been configured like this

4903.6 -> that in case I don't reply

4905.7 -> to that email within two or three minutes

4908.7 -> that message will automatically be deleted from the queue.

4912.5 -> And in that case if you try to move that file,

4915.4 -> you will not be allowed to do so

4917 -> because that file is no longer available

4919.321 -> in the cube, hence.

4920.512 -> You cannot move it, right?

4922.2 -> So this is what our project.

4924.1 -> It is going to be all about now.

4926.327 -> I have already showed you how the project works.

4929.6 -> So let me quickly delete the project and again show you

4933.663 -> how it can be configured from scratch right?

4936.902 -> So give me a moment.

4945.1 -> All right.

4945.688 -> So everything is set.

4946.954 -> Now the first thing

4948.1 -> that I'll be doing is I'll be configuring my S3 to interact

4952.205 -> with my Lambda function, right?

4954.4 -> So what I have not done is I'm not deleted the Lambda function

4958.159 -> because there's no point.

4959.7 -> You just have to click next

4961.545 -> and your function will be created.

4963.8 -> What matters is the code,

4965.8 -> so I have uploaded the code in your LMS

4968.221 -> with the proper documentation.

4970.02 -> If you have any doubts,

4971.4 -> you can actually email me regarding the doubt

4974.025 -> and I'll clear it.

4975.109 -> You so as an architect,

4977.5 -> your job will be to act take this architecture.

4979.917 -> Not the coding.

4980.8 -> The coding part has to be done by the AWS developer,

4983.9 -> but it is a good to know knowledge, right?

4986.569 -> So that is the reason I have uploaded the code

4989.5 -> for the website and AWS Lambda to your LMS.

4993.215 -> Okay.

4993.6 -> So like I said,

4994.655 -> I have to configure my is 3 so that it can interact

4998.173 -> with AWS number.

4999.3 -> Now.

4999.5 -> My website's code is like this

5001.195 -> that it will upload the file to a bucket

5003.4 -> in S3 called either a car.

5005.1 -> A demo, right?

5006.1 -> So what we'll be doing is we will be going

5008.8 -> to the Elder a car demo bucket.

5013.7 -> Which is here, I click on the dareka demo bucket.

5016.8 -> I click on properties.

5018.9 -> I'll click on events and let me delete this event right now.

5025.3 -> Right?

5026.082 -> So I will be adding

5027.4 -> a notification now now let me call this notification

5031.2 -> as AWS - Lambda right.

5035.8 -> Now.

5036.3 -> What I want it to do is whenever the event is a put event

5040.517 -> that is and upload event.

5042.5 -> I want it.

5043.623 -> Send a notification to my Lambda function.

5046.8 -> So I have to select the Lambda function.

5048.8 -> So my function should be this one

5051.6 -> and I will click on Save.

5053.9 -> Let me check if everything has been filled.

5056.8 -> Yes.

5057 -> It has let's click on save.

5059.7 -> All right, so I have one active notifications

5062.4 -> now now you might get an error over here saying

5065.6 -> that you don't have sufficient permissions.

5068.3 -> So if you get that error on the right hand side,

5071.1 -> you'll have a button called add permissions.

5073.629 -> Mission just click on that button

5075.3 -> and everything will open up an automatically basically

5078.19 -> those permissions are for your Lambda function.

5080.8 -> Your Lambda function may not have permissions

5083.4 -> to get notifications from S3.

5085.058 -> But once you click on that button,

5087 -> you will get the proper notifications automatic.

5089.8 -> Right?

5090.3 -> So this is how you will configure your S3 bucket.

5094.1 -> Now, let's go back to our slide to see

5096.217 -> what other things we have to do.

5098.333 -> So we have configured RS3 to invoke a Lambda function

5102.333 -> once a file is Loaded to S3.

5105.4 -> Now.

5105.9 -> A Lambda has already been configured to interact

5109.203 -> with ses through the code,

5111.047 -> which is so through the code

5113.031 -> should be calling the SES service

5115.3 -> and we'll be living in a meal now the next function

5119.1 -> or the next thing is to configure SES or

5121.9 -> before that lets configure our sqs, right?

5125.6 -> So our sqs is basically a simple queue service.

5128.961 -> So we have to create a queue in a COS in which our website.

5133.4 -> It will be uploading of files, right so let's do that.

5137.3 -> Let's just go back to our dashboard.

5139.992 -> So this is our dashboard guys and we'll go to the sqs service.

5148.3 -> Well, click on create new Q fifo queue and

5152.8 -> that Q has to be named as hello - Lambda.

5159.8 -> And since it's a fifo queue,

5161.64 -> you have to give the extension as dot fifo.

5165.061 -> All is done.

5165.984 -> Let's click on quick create Cube.

5169.7 -> Okay, so my Q has now

5171.7 -> been created and now I have to configure this Q

5174.754 -> so that whenever the message comes in,

5177.171 -> it gets automatically deleted after 2 minutes.

5180.11 -> All right, so let us configure it

5182.2 -> so Will click on configure q and we set this to two minutes.

5189.1 -> All right.

5190 -> All is done.

5190.694 -> Let's click on Save changes.

5193 -> All right.

5193.69 -> So my Q has also been configured.

5195.7 -> Let me go back to my slide.

5197.8 -> Alright, so my sqs has been configured now,

5201.098 -> so let me configure

5202.5 -> my SES now now this might be a little tricky.

5205.782 -> So hang on with me.

5207.2 -> We'll go back to the dashboard.

5210.2 -> We'll go to the ACs service.

5213.3 -> Now first of all in the SES service,

5215.514 -> you actually have to add the email addresses.

5218.5 -> Now.

5218.7 -> How will you add email addresses?

5220.5 -> You will actually have to verify a new email address.

5223.6 -> Now you have to verify the recipient as well.

5226.9 -> So since I want to receive the email from the SES service,

5230.72 -> I'll have to type in my email address,

5233.4 -> which is he meant at the rate of the rate during car.com.

5238.9 -> And we have to verify this email address.

5242.9 -> Now I'll receive a verification email on him

5246.2 -> and the other a cannot go.

5248.067 -> So, let me quickly go back click on inbox now.

5251.3 -> I have got a verification request right?

5254.9 -> So I'll click on this verification link.

5258.415 -> Okay.

5258.8 -> So my email address

5260.165 -> has now been configured has now been verified.

5263.4 -> So it says congratulations awesome.

5266 -> So let me go back to my ACS says pending verification.

5270.5 -> Let me quickly refresh it.

5272.8 -> All right.

5273.3 -> So it says verified now now let's go back to our slide.

5277.6 -> All right, so guys we have configured the recipient of SES.

5282.3 -> But what about the sender right?

5284.277 -> So we have to configure the sender as well because

5287.412 -> and why do we have to configure the sender?

5290.1 -> And the sender has to be a domain name

5293.1 -> that you own right?

5294.7 -> Can you have to own that domain name

5297.227 -> so that you can send emails via that domain name now

5300.911 -> what I mean by that is

5302.5 -> you may say that okay,

5304.02 -> why not use the recipient address only why not use

5307.406 -> payment Authority diwaker dotco for sending the email

5311.2 -> but our application also receives email

5314.5 -> if you would have noticed right so for receiving the emails

5318.481 -> through a CSU have to actually own the domain name now

5322.169 -> since I'm an employee,

5323.7 -> I don't own any record or go,

5325.9 -> right?

5326.4 -> So what I've done is I have actually created

5329.485 -> a domain name I can get a free domain name.

5333.2 -> This website it is my dot dot dot TK.

5337.45 -> You can go in this website

5339.6 -> and create a domain for yourself for free.

5343.761 -> So basically you will be getting this domain name free

5348.099 -> for three months.

5349.1 -> All right.

5350 -> I am almost from the expiry date.

5352.453 -> So I might have to renew it.

5354.7 -> Okay, but since this is a demo, let me quickly show you.

5357.9 -> All right, so I have actually created this domain name

5361.368 -> and I can use this domain.

5363.07 -> Name to send or receive emails.

5365.6 -> Now what I'll have to do

5367.53 -> or how do I configure this in my CSS is like this.

5371.3 -> So you will go to your SES.

5373.079 -> You see this tab?

5374.2 -> It says email receiving right?

5376.3 -> So we will click on rule sets

5378.6 -> and you'll have to create a new rule said before that.

5381.6 -> You have to actually verify a domain you

5384.1 -> basically have to verify

5385.401 -> that the domain is actually owned by you now how you will do

5388.6 -> that will click on verify a new domain

5391.6 -> and you You will give your domain name here,

5394.902 -> which is any record or TK.

5396.9 -> Click on verify this domain

5399.4 -> and you will get these two records over here.

5401.764 -> Now.

5402 -> Where will you enter these two records is actually

5404.7 -> in the DNS server.

5406.5 -> So the domain name Eddie record or TK has to point

5410 -> to a DNS server, right?

5411.81 -> And in that DNS server,

5413.6 -> you will be putting in these two records.

5416.3 -> Now.

5416.5 -> How will you point any record or TK to a DNS server?

5420.423 -> So DNS server is basically Route 53 8

5423.4 -> so we'll be configuring Route 53 with any record or TJ.

5426.795 -> Let me show you quickly how you can do that.

5429.7 -> Let me open my Route 53 service.

5432.4 -> So this is my Route 53 service.

5434.8 -> I don't have any host of drones as of now.

5437.5 -> So let's click on get started now click on create hosted zone.

5442.5 -> So my domain name is anyway card or DK right?

5446.734 -> Click on create.

5449.1 -> All right, so I have created a hosted zone now

5452.6 -> in my Route 53.

5454 -> Now what I have to do is I'll have to connect this domain

5457.6 -> to my Route 53 now.

5458.93 -> How will you do that?

5460.4 -> You will click on manage domain.

5463.9 -> And you will click on management tools

5466 -> and you'll click on name servers, right?

5469 -> So these name servers have to be updated

5473 -> with the name servers provided you over here, right?

5477.6 -> So let me quickly show you

5479.517 -> so you will copy this paste it here.

5482.1 -> Remember guys don't include the dot in the end.

5484.904 -> Otherwise, it will give you an error.

5488.6 -> So without the dot copy the name server.

5493.1 -> Right, so I first save to and see

5496.5 -> if it's working click on change name server.

5501.1 -> All right says changes saved successfully.

5504 -> All right, so it's saving the server's now.

5507.453 -> So, let me copy the rest to as well.

5515.8 -> All right.

5516.485 -> So I've copied my name servers I click on change name servers

5520.8 -> and fingers crossed.

5522.338 -> Okay, so it says changes saved successfully.

5525.6 -> All right.

5526.4 -> So my domain name is now pointing to Route 53 awesome.

5531.5 -> So now in Route 53,

5533.4 -> I have to include these records now.

5536.5 -> How will I do that?

5537.857 -> Let me quickly show you

5539.7 -> so you go to Route 53 and you will click

5542.9 -> on create record set now you don't have Prototype anything

5546.7 -> here just in the type

5549.5 -> click on MX and in the value.

5553.7 -> So as you can see,

5554.8 -> there's a value for m x over here just copy this value

5559.9 -> and paste it here, right?

5563.092 -> This is it guys nothing has to be done here.

5566.4 -> Click on create.

5568.7 -> Awesome, so I have an MX record

5571.015 -> now now let's we have to create one more record, sir.

5576.2 -> And that name has to be like this right?

5579.1 -> So I'll copy this part paste it here

5583.9 -> as you can see now.

5585.3 -> The name is underscore Amazon SES dot Ed u--

5589.1 -> a card or TK.

5590.7 -> And as you can see the name over here is to seem right.

5594.2 -> So this name has to be the same and the type of value is txt.

5600 -> Select EXT from here and then you have to enter the value.

5604.1 -> So the value is this enter this value over here

5610.6 -> and click on create.

5614.1 -> Awesome.

5614.6 -> So my Route 53 is now configured to actually

5618.6 -> Sue actor receive the emails from the Ed Eureka dot t--

5622.1 -> k domain cool.

5623.7 -> So we'll go back

5624.93 -> to our SES now close it it says pending verification refresh it.

5632.957 -> Alright, so as you can see my domain name is now verified.

5637.5 -> All right, so let's just go to the rule sets now.

5640.8 -> So email receiving we have to configure so I click

5644.4 -> on view active ruleset.

5645.8 -> There is no rule sets while create a rule.

5649.1 -> Now I have to specify a recipient.

5651.8 -> So let me specify hello at the rate

5655.2 -> and Eureka door TK, right?

5657.648 -> I'll click on ADD recipient.

5660.7 -> So my verification status is verified

5663.469 -> because my domain name is verified now will click

5667.2 -> on next step.

5668.3 -> Now.

5668.592 -> What action do you want it to do right.

5671.342 -> So if you receive email on this email-id,

5674.236 -> what do you want to do?

5675.9 -> So what we want to do is we want to invoke a Lambda function.

5681.7 -> Now what Lambda function do you want to invoke?

5684 -> I want to invoke my function to and will click on next step.

5691.3 -> So everything seems fine will click on Next Step again.

5695.4 -> So it is ask me the rule name.

5696.9 -> Let me give the rule name as Lambda - demo.

5701.9 -> click on next step and click on create rule.

5708.2 -> Okay, so my rule set has now been enabled awesome.

5712.7 -> So I have configured my SES as well.

5715.6 -> So let me go back to my slide.

5719.6 -> Alright, so I've configured my CS I

5722.177 -> have configured my Route 53.

5724.5 -> I've configured my ews Lambda.

5727.3 -> I have configured my sqs.

5730 -> I have configured my S3.

5732.8 -> And my website is also configured right so we

5737.2 -> created a rescue SQ.

5739.3 -> So we may have to change the url

5741.9 -> in our code to Let's quickly do that.

5745.6 -> We'll go back here.

5749 -> Go to the dashboard.

5751.8 -> click on SQL s Alright,

5757.7 -> so this is our q and this is a URL.

5763.2 -> So basically I have named the queue seems so

5766.4 -> so if you do that sometimes a URL don't change.

5770.6 -> So let me see

5771.6 -> if I have to upload the code or not.

5775.8 -> So I'll go to my Lambda function Handler go to the part

5780.2 -> where my cue is saved.

5782.7 -> All right, let me anyway space to Q over here.

5786.23 -> I think it is the same.

5788 -> Yes.

5788.6 -> It is the same.

5789.8 -> Anyways, let us save it.

5794.326 -> This is my function one.

5796.173 -> So let me upload the code now.

5800.3 -> So it's my function and click on finish.

5805.6 -> Right, so it is uploading the function right now.

5809.1 -> So meanwhile, let me go

5810.9 -> to my function to and configure in the queue address,

5817.207 -> which is this.

5819.8 -> Paste it here control s save it.

5823.9 -> And once this process is complete.

5826.336 -> I will upload this code as well.

5828.7 -> So while this is uploading,

5830.4 -> let me change the address in my index file as well.

5835.6 -> This is my websites index file.

5839.3 -> So I'll go to the queue URL which is this.

5843.6 -> I will change it save it and close it.

5848.8 -> Alright, so my website's address has also been done.

5854.2 -> Alright, so my code is uploaded for this function.

5859.9 -> Let me upload the code for function to as

5862.8 -> well because we are may change upload function to AWS.

5867.4 -> So it is my function to that is my function

5870.1 -> to in Lambda click on next.

5873.53 -> And click on finish.

5875.6 -> All right, so my code is being uploaded Let's Wait

5878.482 -> Awhile so that my code gets uploaded

5880.548 -> and then we can proceed with our demonstration.

5889.3 -> Alright, so my code has now been uploaded

5891.3 -> to both my Lambda functions.

5893.4 -> Now.

5894.1 -> What I'll do is I will go

5895.9 -> to my local host website click on refresh.

5903.3 -> And I will upload a file.

5905.3 -> So let me go back and see

5907.216 -> what is there in my bucket right now

5909.9 -> so that it becomes easier

5911.9 -> for us to verify that a file has been uploaded.

5915.025 -> So as of now my bucket is empty.

5917.2 -> I there's nothing in my editor

5919.2 -> a car demo bucket and my other bucket is quarantine demo.

5923.265 -> This is the place

5924.5 -> where my other file will go right?

5927.2 -> Let me empty this as well so that we are clear

5931.9 -> that some Checked has been added.

5934.6 -> All right, so this bucket has also been cleared.

5939.6 -> So we'll go to a local host will choose a file.

5943.1 -> So let's upload some image.

5946.6 -> So let it be this image,

5948.7 -> right I click on open and click on upload image.

5953.2 -> All right, so it says S3 upload complete.

5956.3 -> All right.

5957.056 -> So let me check

5958.191 -> if a file has been added in My riruka Demo bucket.

5962.6 -> I'll click on refresh.

5965.3 -> Awesome.

5966 -> So one file has been added and it's called one four.

5969.8 -> Nine two, five four six zero nine seven.

5972.359 -> Let me check in my email to let me check

5976.018 -> if I got an email.

5977.35 -> So yes, I've got an email.

5980.369 -> Let me click on it.

5982.4 -> All right.

5983.1 -> So this is the name of the file that I got,

5985.8 -> which is the same right?

5987.8 -> So, let me see

5989.1 -> if there is something in my Quarantine demo bucket,

5994.3 -> so there's nothing there.

5996.4 -> I'll come back now.

5998.4 -> I'll reply to this email as move.

6003.2 -> So this basically means move my file to some of the bucket

6006.7 -> and I'm replying it

6008 -> to hello either a Teddy Ricardo TK, right?

6011.4 -> So now we'll hit on send.

6014.2 -> So my message has been sent to Route 53,

6016.881 -> which will be sent to ACS

6018.6 -> which will invoke the Lambda function which will move.

6022.5 -> My file to the other bucket.

6024.646 -> So let us check if that is done.

6027.3 -> So first let us check

6028.886 -> if I enter a car demo bucket has been emptied so

6032.437 -> will click on refresh.

6035.3 -> Alright, so my I do take a bucket has now been emptied.

6039.297 -> Let's go back and check

6041 -> if something has an ad in my core and tine Emma bucket.

6044.9 -> Alright guys, so my file has successfully moved

6048.169 -> to this bucket Let Us verify the name.

6050.8 -> So this is one phone nine to five four six zero nine seven.

6055.2 -> Let us check that in the email.

6057.7 -> So the email

6058.595 -> that we replied to had then the object name as one phone

6062.7 -> nine to five four six eight or 7 so this is

6066.23 -> the same file you guys.

6068.5 -> All right guys,

6069.5 -> so we have completed our demonstration successfully.

6078.5 -> Welcome to the session on elastic Beanstalk

6081.225 -> a web application hosting platform offered by Amazon.

6084.513 -> So without any delay,

6085.88 -> let me give you a brief overview

6087.917 -> of what we will be discussing today firstly.

6090.694 -> We will see what elastic Beanstalk exactly is,

6093.6 -> and then we'll discuss certain.

6095.4 -> In Salient features of elastic Beanstalk moving on.

6098.529 -> We'll try to understand elastic Beanstalk a Little Deeper

6102.059 -> by taking a look at its components

6104.113 -> and then at its architecture in finally,

6106.478 -> we'll try to deploy an application on elastic Beanstalk

6109.753 -> for practical understanding of the concept.

6112.442 -> So let's get started.

6118.4 -> What is elastic Beanstalk?

6121 -> If I have going to find elastic Beanstalk

6123.539 -> and Amazon terminology,

6125 -> then it is a platform as a service where you

6127.483 -> can deploy your application,

6129.1 -> which you might have developed

6130.6 -> with programming languages like Java dotnet PHP node.js

6134.747 -> and many others

6135.861 -> on familiar servers such as Apache nginx passenger

6139.5 -> and Tomcat the definition,

6141.2 -> which I just mentioned seems to have a lot

6143.3 -> of technical terms as ended.

6144.836 -> Well, let's try to figure out what elastic Beanstalk is

6147.8 -> and simple terms.

6149.3 -> All right, let's say you Need to build a computer tonight.

6152.789 -> Well, you have two ways to go at it first.

6155.3 -> You can go to a computer Warehouse Computer Warehouse

6158.2 -> is a place

6159 -> where you have different components of computer laid out

6161.9 -> in front of you

6162.9 -> like you have CPU motherboards router disk drive models

6167.1 -> and many other components you can choose

6169.517 -> which have a component you need and assemble them

6172 -> and form a brand new computer.

6173.7 -> This is similar to situation

6175.438 -> when you try to deploy an application

6177.58 -> without using elastic Beanstalk

6179.404 -> when you try to develop Application by yourself you

6182.545 -> will have a list of tasks which you need to do.

6185.035 -> Like you might have to decide

6186.67 -> on how powerful you want your ec2 instance to be

6189.472 -> then you have to choose a suitable storage

6191.917 -> and infrastructure stack for your application.

6194.6 -> You might have to install substrate surface for monitoring

6198.4 -> and security purposes as well moving on to option b,

6202.1 -> you can always visit an electronic retail store

6204.886 -> which has pre-configured computers laid out

6207.356 -> in front of you.

6208.23 -> Let's say you are a graphic designer

6210.289 -> and you want a computer

6211.6 -> which has a modern graphical user interface installed in it.

6215.141 -> All you have to do is specify this requirement

6217.6 -> to a salesperson and walk out with a computer of your choice.

6220.7 -> Well, I personally prefer this option.

6222.7 -> This is similar to the situation where you're trying

6225.2 -> to deploy an application using elastic Beanstalk

6227.7 -> when you use elastic Beanstalk to develop your application.

6231.3 -> All you have to do is concentrate

6233.374 -> on your code list of the tasks

6235.28 -> like installing ec2 instances

6237.207 -> auto-scaling groups maintaining security

6240 -> and monitoring.

6241 -> Etc is done by elastic Beanstalk.

6243.4 -> That is the beauty of elastic Beanstalk.

6245.8 -> So let's go back and take a look at the definition again and see

6249.115 -> if he'll understand it this time.

6250.9 -> Well elastic Beanstalk as a platform as a service

6254.4 -> where developers just have to upload their application load

6258.06 -> balancing auto-scaling an application Health monitoring

6261.469 -> or all and it automatically by elastic Beanstalk.

6264.5 -> Now, let's try to understand

6266.482 -> how elastic Beanstalk as a platform as

6269.101 -> a service is beneficial.

6270.7 -> Vishal to app developer.

6272.3 -> I'm sure most of you know,

6273.623 -> what platform as a service has but let's try to refresh

6276.918 -> what we know platform

6278.2 -> as a service as a cloud computing service

6280.552 -> which provides you a platform

6282.152 -> where you can deploy and host your application

6284.9 -> elastic Beanstalk makes the process

6287.063 -> of app development much more fun

6289.103 -> and less complex and I have five points to prove

6292.1 -> that to you firstly it offers quicker deployment

6295.2 -> suppose you're developing an app by yourself.

6297.571 -> Then you'll have to do a lot of tasks by yourself

6300.395 -> like you might After decide on ec2 instance choose

6303 -> a suitable storage

6304.058 -> and infrastructure stock

6305.316 -> as well as install auto-scaling groups as well.

6307.922 -> And then you might have to install substrate surface

6310.7 -> for monitoring and security purposes.

6312.933 -> Well, this will take quite a lot of time but

6315.6 -> if you have used platform-as-a-service to develop

6318.3 -> your app then all you have to do is develop a proper court

6321.652 -> for your application rest

6323.105 -> will be handled by platform as a service

6325.4 -> or elastic Beanstalk in this case,

6327.3 -> which makes the entire process

6328.961 -> of app development much more faster.

6330.9 -> now secondly elastic

6332.3 -> Beanstalk simplifies entire app development process like the set

6336.5 -> or developers have to do is concentrate

6338.635 -> on developing a code for their application rest,

6341.4 -> like monitoring servers storage networking Etc

6344.411 -> and managing virtualization operating system databases

6347.959 -> is done by elastic Beanstalk,

6349.9 -> which simplifies the entire process

6351.9 -> for a developer using platform as a service

6354.7 -> to deploy our application make Center app development process

6358.5 -> more cost-effective

6359.731 -> if you're trying to dip By yourself,

6362 -> then you might have to install separate surface for monitoring

6365.244 -> and security purposes and I'm sure

6367.2 -> for that you'll have to pay a lot of money extra money.

6369.9 -> But if you're using an elastic Beanstalk

6372.194 -> to deploy your application

6373.656 -> it will provide you all this additional software

6376.299 -> such as a package

6377.3 -> and you can avoid paying unnecessary operating costs

6380.7 -> also elastic Beanstalk

6382.8 -> offers multi-tenant architecture by that.

6385.549 -> I mean, it makes it easy

6387.2 -> for the users to share their application

6389.605 -> on different devices.

6390.9 -> And that too with high security

6392.9 -> when I say high security platform as

6395.2 -> a service will provide you a detailed report

6397.608 -> regarding your application usage different people or users

6400.9 -> who are trying to access your application as well.

6403.35 -> But this information you can be sure

6405.1 -> that your application is not under any cyber threat

6407.9 -> and finally platform

6409.5 -> as a service provides you an option where you can know

6412.5 -> if the user who is using your application is getting

6415.37 -> a better experience out of it or not with platform-as-a-service.

6419.076 -> You can collect feedback

6420.427 -> at Seven stages of your app development

6422.662 -> like during development stage

6424.368 -> like testing Stage production stage design stage

6426.8 -> by doing so you will have a report regarding

6428.9 -> how your application is performing at every level

6431.3 -> and you can make improvements if needed.

6433.6 -> So this is how platform as

6435.3 -> a service like a are an elastic Beanstalk makes it easy

6438.917 -> for developers to develop an all-around perfect up

6442.2 -> guys will be able to relate to this point

6444.6 -> when we try to deploy an application using

6446.687 -> elastic Beanstalk in the later part of this session.

6449.29 -> You'll understand.

6450.349 -> How will a Stick Beanstalk is beneficial

6452.4 -> to app developer in Marquette.

6454.2 -> There are quite a lot of application hosting platforms

6457.166 -> which are providing platform as a service.

6459.45 -> Let's have a look at few of that.

6461.333 -> First.

6461.7 -> We have something called openshift.

6463.4 -> It is a web hosting platform offered by Red Hat.

6466.4 -> Then you have Google app engine

6468.28 -> which we all know ask a lingo at is a platform as a service

6471.9 -> where you can deploy your application and just do minutes

6474.7 -> apparently will provide you a production ready environment

6477.827 -> where all you have to do is deploy your application code.

6480.9 -> Then you have python anywhere.

6482.782 -> It doesn't online integrated development platform

6485.828 -> and web hosting service as well.

6487.806 -> But based on Python language,

6489.6 -> then you have elastic Beanstalk offered by Amazon moving on.

6493.242 -> We have a sure app Services by Microsoft and many others.

6496.7 -> But today our main focus will be on elastic Beanstalk,

6500 -> which is a web hosting platform offered by Amazon now

6508 -> that you have basic understanding of elastic.

6510.602 -> Stop, let's go ahead

6511.779 -> and take a look at few of its features.

6514.2 -> Mostly all the features are similar to the ones

6516.905 -> which we discussed earlier,

6518.5 -> like elastic Beanstalk makes an app development process

6522.334 -> more faster and simpler for developer moreover.

6525.6 -> All developer has to do is concentrate

6527.7 -> on developing code list of the configuration details

6530.7 -> and managing and monitoring

6532.069 -> details will be handled by elastic Beanstalk.

6534.3 -> Also elastic Beanstalk automatically scales up

6537.675 -> your abs resources,

6539.1 -> which have been assigned to your uh,

6540.9 -> Occasion by elastic Beanstalk based on your application

6544 -> specific needs but there is one feature

6546.261 -> which is specific to elastic Beanstalk suppose.

6549 -> You have deployed an application using elastic Beanstalk,

6552.058 -> but now you want to make changes to the configurations

6555.117 -> which have been already assigned

6557 -> to your application by elastic Beanstalk though.

6560.036 -> Bienstock is a platform as a service.

6562.3 -> It provides you with an option

6564.138 -> where you can change the pre-assigned configurations

6567.159 -> like you do and infrastructure as a service.

6569.7 -> Well if you remember Member when if you're trying to use

6572.4 -> infrastructure-as-a-service to deploy an application,

6575.2 -> you will have full control over AWS resources.

6577.7 -> Similarly Beanstalk also provides you with full control

6581.206 -> over your AWS resources

6582.7 -> and you can have access to the underlying resources

6585 -> at any time.

6590.1 -> Now, let's try to understand

6592.189 -> elastic Beanstalk a little deeper first.

6595.1 -> We'll be discussing few components of elastic Beanstalk,

6598.105 -> then we'll have a look at its architecture.

6600.5 -> What we have your first we have something called

6603.372 -> application suppose you have decided to do a project.

6606.434 -> So what you do you go ahead

6608.015 -> and create a separate folder on your personal computer,

6611.196 -> which is dedicated to your project.

6613.2 -> Let's say your project needs Apache server SQL database

6616.683 -> and a platforming software like Eclipse.

6619.2 -> So you install all the software's

6621.5 -> and stole them in the folder

6622.945 -> which is dedicated to your project.

6624.7 -> So that will be easy

6625.7 -> for you to access whenever you need all

6627.8 -> the software's similarly

6629.6 -> when you try to do deploy an application

6631.8 -> on elastic Beanstalk Beanstalk will create a separate folder

6635.303 -> which is dedicated to your application

6637.5 -> and an aw storms.

6638.9 -> This folder is what we call an application

6641.9 -> if I have to Define folder or application in technical terms,

6645.7 -> then it is a collection of different components

6648.4 -> like environments your application versions

6650.635 -> and environment configuration.

6652.4 -> Let's try to understand each of these components one by one.

6655.6 -> We have something called application version suppose you

6659 -> have written a code stored.

6660.599 -> In the file and deployed this coat on elastic Beanstalk

6663.8 -> and your application has been successfully launched

6666.3 -> but now you want to make certain changes to the code.

6668.9 -> So what you do you go ahead

6670.488 -> and open the file make changes to it save it

6673.017 -> and then again deployed

6674.311 -> on elastic Beanstalk elastic Beanstalk again,

6677 -> successfully launches your application.

6678.9 -> So you have two versions of your application now,

6681.737 -> it's just a copy of your application code,

6684.148 -> but with different changes

6685.641 -> and elastic Beanstalk will provide you with an option

6688.7 -> where you can upload different versions.

6690.6 -> As of your application

6691.7 -> without even deleting the previous ones then we have

6694.7 -> something called environment environment is a place

6697.2 -> where you actually run your application

6699.4 -> when you try to launch

6700.8 -> and elastic Beanstalk environment Beanstalk starts

6704.229 -> as ining various AWS resources,

6706.4 -> like ec2 instances auto-scaling groups load

6709.706 -> balancer security groups to your application the point

6713.5 -> which you have to remember is at a single point

6716.2 -> of time environment can run only a single version

6719.2 -> of your application.

6720.6 -> Elastic Beanstalk will provide you with an option

6723.564 -> where you can create

6724.8 -> multiple environments for your single application suppose.

6727.868 -> I want and different environment for different stages of my app.

6731.135 -> Like I want an environment for development stage

6733.734 -> one for production stage and one for testing stage.

6736.5 -> I can go ahead and do

6737.439 -> that create a different environment for different stages

6740.1 -> of my application

6740.956 -> and suppose you have same version or different version

6743.654 -> of your application installed on all these environments.

6746.6 -> It's possible to run all this application versions

6749.6 -> at same time.

6750.417 -> I hope that was clear.

6751.8 -> Well, you'll understand them practically when we

6754.059 -> try to deploy an application in the later part of the session.

6756.95 -> Then we have something called environment Tire

6759.3 -> when you try to launch an elastic Beanstalk environment

6762.3 -> elastic Beanstalk asks you to choose amount

6764.9 -> to environment tires,

6766.2 -> which are web server environment.

6767.921 -> And then you have worker environment.

6769.857 -> If you want your application to handle HTTP request,

6772.616 -> then you choose web server environment.

6774.642 -> And if you want your application to handle background task

6777.681 -> that is where a work environment comes into picture.

6780.8 -> Sure, which to choose either web server

6783.1 -> or work environment and how to work with them

6785.301 -> when we'll try to deploy an application in later part.

6788 -> And lastly we have something called environment

6790.4 -> Health based on

6791.282 -> how your application is running Beanstalk reports the health

6794.892 -> of your web server environment

6796.7 -> and it uses different colors to do.

6798.8 -> So first gay indicates

6800.6 -> that your environment is currently being updated.

6803 -> Let's say you have installed one version

6804.721 -> and now you're trying to upload different version.

6806.9 -> Well, it's taking a lot

6808.1 -> of time so that time it shows gray color.

6810.4 -> It means your environment is still under updating process.

6813.467 -> Then you have green which means

6815.291 -> that your environment has passed the recent health check.

6818.114 -> Then you have a low which means

6819.746 -> that your environment has failed one or more checks and red

6822.8 -> failed three or more checks moving on.

6829.7 -> Let's try to understand

6831.08 -> the architecture of elastic Beanstalk.

6833.4 -> Like I said early on when you try to launch

6836.228 -> an elastic Beanstalk environment Beanstalk ask you to choose Was

6840.719 -> among two different environment tires firstly we have

6844.121 -> web server environment web server environment

6847.4 -> usually handles HTTP requests from clients

6850.2 -> and it has different components firstly we have something

6853.4 -> called environment.

6854.6 -> You know, what environment is it's a place where we

6857.1 -> actually run your application

6858.7 -> and Beanstalk provide you with an option

6860.887 -> where you can create multiple environments and

6863.534 -> the main point is at a point of time

6865.5 -> this particular environment can run only one version

6868.5 -> of your application moving on we have Something called

6871.3 -> elastic load balancer.

6872.594 -> Let's say your application is receiving a lot of requests.

6875.9 -> So what elastic load balancer does is it distributes

6879.1 -> all this request among different ec2 instances

6881.952 -> so that all the requests are handled and no request

6885.196 -> is being delayed.

6886.298 -> What actually happens is

6887.846 -> when you launch an environment or URL is created

6890.789 -> and this URL in the form of C name is made to point

6894.034 -> elastic load balancer senior is nothing

6896.7 -> but alternate name for your url.

6899.2 -> So when your application receives requests all

6901.849 -> these requests are forwarded to elastic load balancer

6904.907 -> and this load balancer distributes.

6907.1 -> These requests among ec2 instances of Auto scaling group.

6911.2 -> Then we have Auto scaling Group Well,

6913 -> if your web server is trying to handle a lot of traffic

6915.7 -> and it's having a scarcity of ec2 instances,

6918.358 -> then Auto scaling group

6919.78 -> automatically installs few easy to instances.

6922.477 -> Similarly.

6923.12 -> If traffic is very low,

6924.6 -> then it automatically terminates under use ec2 instances then

6928.7 -> we Have ec2 instance.

6930.1 -> So whenever you try to launch an elastic

6932.5 -> Beanstalk environment Beanstalk will assign your application

6935.7 -> with a suitable ec2 instance,

6937.5 -> but the software stack like the operating system the servers

6941.3 -> and different software's

6942.5 -> which are supposed to be installed

6944 -> on your instance are decided by a device called container type.

6947.7 -> For example,

6948.606 -> let's say my environment as Apache Tomcat container.

6952.388 -> So what it does it installs

6954.365 -> Amazon Linux operating system Apache web server

6957.6 -> and Tomcat software.

6959 -> Do you see two instance similarly depending

6961.67 -> on your application requirements it installs different software

6965.2 -> stack on your ec2 instances.

6967.2 -> Then we have a software component called host manager

6970.258 -> which runs on every easy to instance

6972.3 -> that has been assigned to your application.

6974.5 -> There is host managers responsible for various tasks

6977.5 -> firstly it will provide your detailed report

6979.752 -> regarding performance of your application.

6981.976 -> Then it provides instant level events.

6985.1 -> It monitors your application log files as well

6987.922 -> and it monitors your Datian server,

6990.054 -> you can view all these metrics log files

6992.5 -> and create various alarms on cloudwatch monitoring dashboard.

6995.8 -> Then you have security groups Security Group is

6998.54 -> like a firewall to your instance.

7000.447 -> Not anybody can access your instance.

7002.6 -> It's just for security purposes.

7004.6 -> So elastic Beanstalk has a default Security Group,

7007.701 -> which allows client to access your application using Port 80.

7011.7 -> You can Define more security groups

7013.7 -> if you need and then

7014.743 -> elastic Beanstalk also provides you with an option

7017.3 -> where you can define a security group.

7019.4 -> All your database for security purposes moving on.

7022.4 -> We have something called Walker environment.

7024.884 -> First question that comes to our mind is what is worker.

7027.794 -> Well suppose your web server has received a request from client.

7031.5 -> But on the way

7032.3 -> while it's trying to process the request it has come across tasks

7035.3 -> which are consuming a lot of resources.

7037.2 -> I'm taking a lot

7038.199 -> of time because of which it's quite possible

7040.8 -> that your web server might deny other request.

7043.5 -> So what it does it forwards these requests to something

7046.459 -> called Welcome these worker handles all this stuff.

7049.2 -> Us on behalf of web server.

7050.8 -> So basically worker is a process that handles background tasks

7054.835 -> which are time intensive and resource intensive.

7057.899 -> And in addition.

7058.917 -> If you want you can use walker

7060.826 -> to send email notifications to generate metric reports

7064.334 -> and clean up databases

7065.749 -> when needed let's try

7067.1 -> to understand why we need Walker with the help of you skis,

7070.5 -> so I have a client he has made a request to a web server

7074 -> and the web server has accepted the request

7076.47 -> and it starts processing the request

7078.5 -> but While it's processing the request it comes

7081.344 -> across the switch are taking a lot of time.

7084 -> Meanwhile, this client

7085.4 -> has requested or send another request to a web server

7088.7 -> since web server is still processing the first request

7091.838 -> it denies second request.

7093.319 -> So what is the result of this as the performance

7095.9 -> and the number

7096.6 -> of requests accepted by a web server will drastically

7099.316 -> decrease alternatively let's say a client has made a request

7102.4 -> and your web servers accepted it

7103.854 -> and it starts processing the request and again,

7105.954 -> it comes across Stars

7107.052 -> which are doing a lot of time this time.

7109.129 -> What it does it transfers

7110.6 -> or it passes all this task to walk our environment

7113.5 -> and this work environment will handle all these stars

7116.4 -> and request one is successfully completed.

7118.982 -> Meanwhile, if it receives a second request

7121.5 -> since it has completed processing request one,

7124.217 -> it will accept requests to I hope the scenario was clear.

7127.8 -> We'll all we are doing by installing work environment

7130.4 -> is we are avoiding spending lot of time on single request here.

7133.7 -> Now, you know what web server environment is

7136.067 -> and work environment is and why do we need work environment?

7139.2 -> But there has to be some way so that this web server environment

7142.7 -> can pass on this task to work environment.

7145.5 -> Let's see how so you have your web server environment.

7148.172 -> It has received a request

7149.422 -> and while processing it as encounter tasks

7151.402 -> which are taking a lot of time.

7152.9 -> So what it does it creates and sqs message sqs is a simple

7157.8 -> to service offered by Amazon

7159.6 -> and this message is then put into es que es que

7162.5 -> and the different requests are arranged

7164.635 -> based on priority in this qsq.

7166.4 -> Meanwhile when you're trying to install Walker.

7169.1 -> Environment elastic Beanstalk has installed

7171.57 -> something called demon.

7172.9 -> What is demon does it pulls sqs message from Askew

7176.7 -> and then it sends the Stars to web application,

7179.767 -> which is running

7180.8 -> on vodka environment as a result or as a response

7184.2 -> to spin start application handles all the stars

7186.905 -> and responds with an HTTP response option.

7189.3 -> So this is how the entire process

7190.6 -> of handling tasks transferring and then handling does goes on

7194 -> so you have a client he has made a request to a web server,

7196.9 -> but the web servers encounter with tasks

7198.7 -> which are I'm consuming and resource consuming.

7200.9 -> So it passes this request rescue is Cube.

7204 -> And when you try to install walking environment,

7207.133 -> there's a demon which pulls out all this messages art us

7210.8 -> from your rescue.

7212.2 -> And then this demon sends all the stars to

7215.4 -> our application application results all the stars

7218.4 -> and then it responds with a HTTP response option.

7221.6 -> So this is how your to application communicate I

7229.33 -> can read was lot of 30.

7231.1 -> Don't worry.

7231.724 -> We have arrived at the fun part of session

7233.953 -> where we'll be trying to deploy an application

7236.4 -> using elastic Beanstalk hear you

7238.436 -> by doing or by creating

7239.9 -> an application on elastic Beanstalk practically,

7242.4 -> you'll understand different concepts its architecture

7245.162 -> and different environment tires and all this.

7247.507 -> So let's go ahead.

7249.784 -> So this is my area plus Management console.

7253.1 -> And if you want to take a look at all the services, then you

7255.775 -> have all the services here,

7257 -> but were mainly concerned with elastic.

7258.9 -> Up, which have recently used.

7260.7 -> So it shows that all recently used resources or Services here.

7264.4 -> So I'm going to choose that elastic Beanstalk and this

7267.979 -> is my Beanstalk console.

7269.6 -> If you're trying to deploy an application for first time,

7272.1 -> this is the page where you land when we scroll down it says

7275.1 -> that I can deploy an application and three easy steps.

7278 -> All you have to do is select a platform of my choice then

7281.294 -> upload our application code

7283 -> if I have one or use a sample application code

7286.319 -> and then run it.

7287.493 -> Let's see if it's as Easy as it says here,

7290.5 -> so go ahead and click on create new application option here.

7293.9 -> It will ask you for application name and description.

7297.2 -> I'm going to name my application as Tomcat app then description

7301.7 -> as my new web app.

7304.4 -> And then I'm going to click on this create option C.

7307.4 -> When I try to create an application.

7309.2 -> It has created a separate folder

7310.941 -> which is dedicated to my application.

7312.9 -> And in that folder,

7314 -> we have different components as you can see here.

7316.4 -> I have my environment then I have application versions and

7320.3 -> if I've saved any configuration,

7321.9 -> it will show all the saved configurations here.

7324.2 -> Now.

7324.4 -> Let's go ahead

7325.094 -> and create an environment on the right side.

7327.444 -> You see an actions option and you click on

7329.4 -> that you get different choices.

7331.069 -> You can just select the create environment here.

7333.7 -> So again, it's asking you

7334.961 -> to choose among two different web environment tires.

7337.526 -> You have web server environment

7339.166 -> and work environment in web server environment.

7341.8 -> Your application handles HTTP requests from clients.

7345.3 -> Then you have work environment

7346.8 -> where your application will process background tasks

7349.4 -> like time intensive

7350.299 -> and resource consuming task in this demo.

7352.299 -> I'm going to work only with Observer environment.

7354.7 -> You can go ahead explore and create work environment.

7356.897 -> Once you understand

7357.7 -> how to deploy an application on elastic Beanstalk.

7360.2 -> So I'm going to click on the select option here.

7362.685 -> It will take me to a It's bad enough to give a domain name

7365.7 -> or in technical terms are URL to my application.

7369.1 -> You can give any URL of your choice and see

7371.646 -> if it's available.

7372.587 -> So let's say my Tom app and it see if it's available.

7376.1 -> It says the domain name is available then description.

7378.9 -> I'm going to give it a same as before.

7380.6 -> So my new web app then

7382.6 -> when I scroll down it asked me for a platform of my choice.

7386.1 -> There are different options.

7387.4 -> You have go then you have

7389.2 -> dotnet Java Ruby PHP node.js python Tomcat.

7393.6 -> At and if you're trying to deploy an application

7395.6 -> on the platform,

7396.4 -> which is not here,

7397.5 -> you can configure your own platform

7399.5 -> and deploy turn elastic Beanstalk.

7401.7 -> It provides an option here.

7402.95 -> You can see there's in custom platform here.

7405.2 -> So I'm going to choose Tomcat platform for my application.

7408.2 -> And since I'm not any kind of developer,

7410 -> I'm just going to go ahead and use the sample application

7412.8 -> provided by Amazon.

7413.9 -> But if you have any application code

7415.866 -> if you have created or develop some code you can store

7419 -> that in a file and upload your it says you can upload

7422.17 -> your code then you have a zip.

7423.8 -> You need to convert your file to zip our war file

7426.2 -> and then upload it here.

7427.4 -> So I'm going to just select sample application

7429.5 -> and then click on create an environment here.

7431.5 -> So it's going to take awhile for elastic Beanstalk to launch

7434.2 -> my environment though.

7435.523 -> It's not as much time

7436.741 -> as it would have taken me to develop

7438.8 -> entire application by myself

7440.9 -> while elastic Beanstalk is trying to launch environment.

7443.852 -> Let's discuss some points or in the earlier part of the session

7447.5 -> with discuss some benefits of elastic Beanstalk firstly I said

7451.69 -> that it fast ins your process.

7453.751 -> Of developing an entire.

7455.6 -> So it's true.

7456.7 -> Doesn't it?

7457.347 -> All I did was select the platform

7459.187 -> of my choice dress is done by elastic Beanstalk itself.

7462.363 -> So thereby saving a lot of time similarly it

7464.791 -> simplifies the process of app development again.

7467.556 -> All I did was select a platform of my choice

7469.9 -> like installing easy to instances security groups

7473.15 -> Auto scaling groups

7474.437 -> and assigning IP addresses rest is done by elastic Beanstalk.

7478.6 -> I even mentioned a point where I said

7481 -> that it will provide

7482 -> elastic Beanstalk provides you with an opportunity.

7484 -> And now you can change the present configuration.

7486.4 -> We'll explore that.

7487.3 -> Once the environment is created.

7488.8 -> Let's go ahead and see what elastic Beanstalk is doing.

7491.5 -> It says that it has created a storage for my environment.

7495.3 -> Well S3 bucket solar all my files

7497.5 -> where I have my application code are stored there then test

7501.319 -> created a security group

7502.9 -> as well and elastic

7504.239 -> IP address then it says it's launching an ec2 instance.

7508.2 -> So you see it's as easy as that.

7510.3 -> All you have to do is select a platform of your choice rest

7513.57 -> is Founded by elastic Beanstalk and later on

7516.1 -> if you're not satisfied.

7517.3 -> If you want to change some configuration,

7519.346 -> you can go ahead and do that here.

7521.146 -> Look at this.

7521.897 -> This is the IP address which are domain name

7524.382 -> which are assigned to my up.

7526 -> It says new instance

7527.274 -> has been added and in addition it showing each task

7530.46 -> while it's doing Isn't that cool?

7532.5 -> You'll know what your environment is currently doing.

7535.1 -> So it's still taking a while.

7537 -> So it says it has installed

7539.025 -> and added instance to my application

7541.541 -> and my environment has been We

7543.7 -> launched it is finished almost all the tasks.

7546.5 -> It should have taken to environment page now.

7549.5 -> So this is my environment page

7551.562 -> or you can see our dashboard first.

7553.9 -> You have environment healthier.

7555.3 -> It says green.

7556 -> It means that my environment has successfully passed

7558.679 -> the health check then it shows the sample version

7561.149 -> of your application

7562.099 -> since I've used the sample application and saying

7564.5 -> sample application here

7565.7 -> since I've chosen Tomcat as my platform.

7568.2 -> It has installed suitable infrastructure stacked

7571.2 -> like Amazon Linux

7572.311 -> and you have Java 8 aiming language.

7574.6 -> Let's go ahead and explore this page first.

7577 -> We have something called configuration here.

7578.988 -> Like I said, though, it is a platform as a service.

7581.488 -> It provides you with an option value can change configuration.

7584.3 -> So you will have full control of your resources first.

7587.122 -> We have something called instances here.

7589.2 -> When I click on modify option,

7590.9 -> you can see

7591.6 -> that elastic Beanstalk has assigned micro instance

7594.8 -> to our application

7595.7 -> if I want I can go ahead and change it

7597.769 -> to different instance based

7599.378 -> on my application requirement scrolling down.

7601.966 -> I have cloudwatch monitoring.

7603.6 -> If I want detailed monitoring, then I can go for one minute

7606.659 -> if I want basic monitoring or not.

7608.4 -> So detailed monitoring then I can choose five minutes here.

7611.4 -> Then I have an option of resigning storage

7614.302 -> to my application as well at says we have

7617.1 -> magnetic storage general purpose

7619.465 -> and provision.

7620.5 -> Iops as well.

7621.6 -> When we scroll down again.

7622.9 -> We see different security groups.

7624.782 -> I can just click on that

7626 -> and the security group will be added to my application.

7628.7 -> So once you've made the changes you can click

7630.554 -> on apply option or do I haven't made any changes.

7632.577 -> I'm just going to click here.

7633.8 -> So now elastic Beanstalk is trying to update my environment.

7637.017 -> So it's showing gray color here.

7639 -> If you recollect a mentioned during the earlier part

7642 -> that grey indicates.

7643.1 -> My environment is being updated.

7644.7 -> Okay, let's go back to configurations.

7646.7 -> We did have a look at instances.

7648.4 -> Then you have something called capacity apparently

7651.1 -> elastic Beanstalk is

7652.1 -> design a single instance to my application.

7654.1 -> If I want I can go ahead and change to auto-scaling groups.

7656.9 -> You have an option called load balance

7658.531 -> so you can click on that here and you can set the minimum

7661.1 -> and maximum number of instances that your auto scaling.

7663.8 -> Group can install as well then

7665.7 -> if you have chosen a load balancer option earlier

7668.1 -> than a load balance would have been enabled here.

7670.4 -> Then we have monitoring details

7672.4 -> which provides you with two options enhanced monitoring

7675.1 -> and basic monitoring

7676.224 -> and when we scroll down you can see a streaming

7678.93 -> to cloudwatch logs option here.

7680.693 -> So if you want your log files,

7682.4 -> you can view them on cloudwatch dashboard as well.

7685.3 -> You can set the retention period according to your choice

7688.3 -> and suppose you want

7689.3 -> your application for some private purpose.

7691.1 -> Then you can create a generate a private VPC for you.

7693.876 -> Your application similarly,

7695.464 -> you can add or decrease the amount of storage as well.

7698.422 -> So by explaining all this

7699.783 -> what I want to say is your hands are not tied you can make

7703.136 -> changes to configurations.

7704.5 -> If you want.

7705.3 -> Then we have logs option.

7706.8 -> If you want to have a look at the last 10 lines

7709 -> of your log files, then you have an option.

7711.1 -> It says last hundred line.

7712.629 -> Sorry lost a hundred lines then if you want full log files,

7715.598 -> then you click on that do provide you a file

7717.8 -> and download format.

7718.822 -> You can just download it.

7720.3 -> Then we have health option here where it provides health.

7723.894 -> You are a cc sources basically shows ec2 instance here.

7727.082 -> It says it's been 7 minutes or six minutes

7729.3 -> since my ec2 instance has been installed.

7731.3 -> Then you have monitoring

7732.7 -> where it shows different monitoring details

7734.9 -> like CPU utilization Network in network out.

7737.9 -> If you want you can go ahead and create an alarm

7740.3 -> with alarm option here suppose

7741.805 -> you want notifications to be sent to you

7743.968 -> when the CPU utilization or when the number

7746.223 -> of ec2 instances are scarce in your auto scaling group.

7749.486 -> Then you have events here

7750.973 -> events basically are nothing but it's a list of things

7754.09 -> which has happened

7755.149 -> since you started launching an environment when I go down

7758.3 -> it says we have seen earlier

7759.65 -> on the black screen the same things are applied your

7762.2 -> so it says create an environment starting

7764.9 -> then we saw that AC to instance

7767.1 -> has been installed security groups elastic IP address.

7770 -> So basically it shows all the events

7771.9 -> that has happened from the time elastic Beanstalk has started

7774.9 -> to launch our environment

7776.295 -> and till the time you terminated the environment.

7779 -> So that's it.

7779.796 -> Then you have tag files.

7781.266 -> You can assign different key values as well.

7783.911 -> Let's go back.

7785.1 -> This is a sample application,

7786.688 -> which I've tried to use not let me try to upload and deploy

7790.1 -> a new application version here.

7792.8 -> Okay, I'm gonna go to documentation here.

7795 -> I'm interested with elastic Beanstalk.

7796.99 -> I'm going to select on that

7798.499 -> and then develop a guide click on getting started on

7801.5 -> when you scroll down on deploy

7803.1 -> a new application Virginia based on your sample application.

7806.209 -> You have different versions of your application

7808.736 -> since I've selected a tomcat is my platform.

7811.1 -> I have a tomcat zip file.

7812.812 -> You're a boy.

7813.5 -> Already downloaded

7814.4 -> that so I'm gonna just going to upload the file then

7817.1 -> so let's go back and it says upload

7819.1 -> and deploy but let's go back to our folder.

7821.8 -> Then there's an application versions option here.

7824.3 -> So it gives you deploy and upload option separately here.

7827.4 -> I'm just going to upload first then we'll deployed

7830 -> version label new version and upload the file.

7833.9 -> I have it here zip file.

7835.4 -> I'm just going to attach the file and then click

7837.75 -> on upload optional.

7838.8 -> The new version of my application has been uploaded

7841.1 -> but it's not been deployed yet.

7842.886 -> So when I go Can you can see

7844.5 -> that I can still see the same version

7846.5 -> which was there before now?

7848 -> Let's go back and deploy it.

7849.6 -> Okay.

7849.8 -> I'm going to select this and then I'm going to click

7851.8 -> on deploy option and select employer.

7854.1 -> Let's go back to environment and check

7856.3 -> so my environment is being updated.

7858.363 -> So again the gray color here

7860.062 -> once it's updated as and show the new version name here.

7863.823 -> It is uploaded.

7865.1 -> So as you can see it showing

7866.5 -> the version name of my new version application version.

7869.6 -> Like I said all your both my application versions.

7871.723 -> Are there have been deleted any you don't.

7873.503 -> Have to delete your application versions

7875.15 -> when you create a new one similarly,

7876.919 -> you can upload multiple versions of your application going

7879.8 -> back actions option.

7880.9 -> Then you have load configuration,

7882.6 -> which will definitely load your configuration.

7884.85 -> Then you have saved we can save this configuration suppose.

7887.444 -> You want to create an application with

7889.039 -> the same configurations again,

7890.362 -> you don't have to start from the beginning

7892.122 -> from creating application environment all that.

7894.067 -> You can just save the configuration and use

7895.849 -> for the other application

7897.1 -> or other environment of your application.

7899.208 -> Then you can clone your environment as well rebuild

7901.844 -> and I environment and terminate as well.

7903.9 -> So here I have saved configuration.

7905.8 -> If you have saved this configuration the configuration

7908.2 -> of been listed here and like that conversation.

7910.5 -> I can use when I'm creating a new environment.

7912.9 -> Okay, just let's see

7914.106 -> if have explored all the options environment

7916.7 -> how well I forgot to show you one most important thing

7919.35 -> when I click on this URL.

7920.5 -> It takes me to a page where it shows

7922.5 -> but my application has been successfully installed.

7925.7 -> Well, that's it.

7927.1 -> So now you know

7927.982 -> how to deploy an application using elastic Beanstalk.

7931.1 -> Do I have used the sample application?

7933.1 -> Are you can go ahead and upload a code of yours

7935.805 -> if you have any and try it out.

7937.6 -> Well, all the options here seems to be user-friendly

7940.1 -> so you will know what to do.

7941.8 -> It seems to be easier process.

7943.4 -> You'll understand it better when you try to reply

7945.5 -> an application by yourself.

7951.4 -> So first and foremost,

7952.5 -> I would start by talking about what cloud storage exactly is.

7956.8 -> Then we would move further and understand some of the myths

7959.9 -> that surround cloud storage

7961.8 -> but also discuss certain cloud storage practices

7965.4 -> and would understand

7966.8 -> how different cloud storage service providers work.

7970.7 -> Finally, I would finish things off with the demo part

7973.2 -> where I would be talking about how cloud storage Services work

7976.647 -> on Amazon web services.

7978 -> So I hope this agenda is clear to you guys.

7980.1 -> So let's not waste any time and quickly get started then.

7984.1 -> So what exactly is cloud storage now first and foremost,

7987.635 -> let me tell you what prompted me to actually go ahead

7990.594 -> and take this session.

7991.8 -> Well recently.

7992.5 -> I had been interviewing and where I asked people

7995.178 -> what do what did the know about cloud computing

7997.8 -> and they told me

7998.991 -> that cloud computing is a place

8001.3 -> or it is a place online where you actually store data.

8005.3 -> I went to some extent I agree.

8007.206 -> Yes cloud computing helps you store data,

8010.049 -> but that is not the definition on the longer run.

8013.6 -> So that is why I thought that we should actually go ahead

8016.05 -> and have this session

8017.1 -> so that we can discuss some of the myths

8019.111 -> that surround cloud computing and tout store is in particular.

8023.1 -> So guys, let's start with a basic definition first.

8029.1 -> Storage.

8030.3 -> Well, it is something

8031.8 -> that is made available in the form of service.

8035.78 -> Which is connected over a network.

8039.2 -> So guys this is a very basic definition

8042.3 -> and the throw some more light.

8044.4 -> I would like to actually go ahead and given certain examples

8047 -> as well to specify what does this definition mean?

8049.65 -> But to some point this definition is correct.

8051.8 -> It says that it is nothing but a storage

8054.14 -> which is available as a service

8056 -> which is connected over a network now again,

8058.9 -> you might wonder as in this is what people told me

8061.488 -> in the interview, right?

8062.9 -> I mean it is a place where you store data.

8065.4 -> So yes cloud storage to some extent.

8067.8 -> Yes.

8068.5 -> This is what it is.

8069.773 -> But when you talk about cloud storage it is lot more

8073.125 -> than this basic definition.

8074.9 -> Let's try to understand what all this cloud storage

8077.578 -> exactly has to offer to you people.

8081.3 -> Well first and foremost

8082.45 -> as I've already mentioned it is storage it can let

8084.8 -> you store emails media.

8087.1 -> Now when I say media you can store

8089.209 -> in a different kind of media

8091 -> whether it's your images

8092.807 -> whether it's your videos or maybe other kind of files.

8097.7 -> It also lets you hold Services as well.

8100.595 -> Yes.

8100.9 -> We are living in the world of internet right now and there

8104.677 -> are various Services websites

8106.6 -> that are online

8107.645 -> and this data can be stored by using Cloud platform.

8112.2 -> and finally I'm sorry guys

8117.4 -> finally it is nothing but the backup now

8120.052 -> when I say back up guys,

8121.7 -> we are talking about large Enterprises

8124.222 -> that let you back up the data

8126.2 -> and the using Cloud platform to do that.

8128.6 -> But again, it's to still holds the same point right?

8131.3 -> I mean when I say emails Media Services backup

8135.7 -> for large organizations,

8137.5 -> I mean it is still a simple storage know now,

8140.6 -> let me tell you what it does

8142.423 -> when I say backup for large organizations.

8145.6 -> We are referring to a lot of pointers here data coming in

8149.4 -> from different sources.

8151 -> The weight is processed.

8152.497 -> The weight is integrated and stored into a particular storage

8156.132 -> how it is handled and what all can you do with it.

8159.1 -> Now when you talk about a cloud storage,

8161.3 -> it actually takes care of all these things.

8163.9 -> That means it's not redundant or a dead storage

8167.2 -> where you just take your data and put in

8169.6 -> your data you can think of it as smart data storage.

8173.6 -> So to understand

8174.625 -> that let's talk about cloud computing a little so

8177.672 -> what cloud computing does is it lets you have this data

8181.12 -> on the platform and it is a platform

8183.5 -> where it has a number of services

8185.611 -> that lets you compute

8186.945 -> or process this data to suit your business needs now,

8190.16 -> it can be using machine learning Big Data finding

8193.236 -> out certain patterns using power bi tools

8195.8 -> or not power bi tools bi tools.

8198.5 -> And also do a lot of other things

8200.633 -> like maybe use a cloud platform

8202.599 -> where the data can be used for marketing purposes, Maybe.

8205.601 -> I think I owe to Bots and stuff like that.

8207.8 -> So this is what a cloud computing platform.

8210.441 -> Does it basically lets you use different sources and use

8213.9 -> this particular data to do multiple or different

8217.2 -> kinds of things.

8218.348 -> So when I say a cloud storage

8220.345 -> it basically ensures there is a mechanism

8223.1 -> that in first place it stores data and lets you perform some

8227.061 -> of the actions

8228 -> that you can actually perform on this data.

8230.2 -> So as we move further,

8231.387 -> I would be discussing quite a few pointers

8233.6 -> that support this claim or this.

8235.482 -> Definition of mine.

8236.487 -> So let's just move further and try to understand

8239.073 -> a little more pointers or some other pointers

8241.494 -> that talk about cloud storage but to keep it simple.

8244.6 -> It is a storage

8245.7 -> that lets you do a lot of things with the data primary reason

8248.7 -> being storing the data

8250 -> and the other reasons being processing it

8252.5 -> or managing it also so let's move further and take a look

8256.257 -> at the next pointer.

8258 -> So what are the myths that surround a cloud storage?

8261.8 -> Well when you talk about the myths,

8264.3 -> this is what some people The same that cloud computing

8267.7 -> is suitable only

8269.1 -> for large scale organizations know this is not true.

8272.9 -> Let me give you an example recently.

8275.25 -> What happened was one of my friends.

8277.6 -> He actually happen to format his mobile phone

8280.9 -> and he lost all the images and other data

8283.252 -> that was there on that phone.

8284.9 -> So the problem was he never backed that data

8287.74 -> on any Drive neither on Google Drive

8289.945 -> or anywhere so he lost the data

8291.9 -> so he came to us and he told us that this is what happened.

8294.573 -> So we told him that You should have backed it up.

8296.785 -> Maybe on Google Drive.

8297.9 -> So next time he did that and again,

8299.9 -> he being used to losing his data.

8301.5 -> He lost his data again.

8302.65 -> So he again comes up and he's

8304.037 -> like I've lost the data so we reminded him

8306.4 -> that he had his data stored on Google Drive.

8308.7 -> So when you talk about Google drive,

8310.8 -> it is nothing but an online storage where you actually

8314.333 -> make a copy of a data,

8315.8 -> so he made a copy of his data

8317.4 -> and he could actually get that data back.

8319.6 -> So when I say cloud storage it gives you a simple application

8324.215 -> or a simple.

8325.5 -> That you can actually go ahead and just put in your data just

8328.5 -> like Google River you can put in your data as well.

8331 -> So it is not limited to large-scale organizations only

8334.167 -> if even you are a single individual

8336.2 -> where you just need to store your data,

8338.2 -> you can use cloud storage.

8339.8 -> Now, there are there are various cloud service providers

8342.5 -> that actually meet

8343.595 -> or cater different cloud computing needs So based on

8346.7 -> that the cloud storage is might get complicated

8349.3 -> and might give you more functionality.

8351.258 -> But even if you need is as basic as storing data,

8353.853 -> don't worry cloud computing or cloud.

8355.8 -> Storage is for you as well.

8357.388 -> Now if you talk about small scale businesses,

8359.8 -> yes these days the amount of data

8361.7 -> that is generated is huge.

8363.5 -> And that is why

8364.382 -> what happens is even for small scale organizations.

8367.2 -> You need a place

8368 -> where you can store your data and somebody can manage the data

8371.05 -> for you so you can focus on your business goals.

8373.4 -> So this is where cloud storage comes

8375.241 -> into picture for even small scale businesses as well.

8378.3 -> So if you ask me,

8379.3 -> yes last scale organizations are suitable

8382.4 -> for cloud computing or only large-scale organizations.

8385.517 -> A suitable for cloud storage.

8387.351 -> This is a myth.

8390.8 -> Complexity with cloud guys.

8392.615 -> Now.

8393.7 -> What does this term symbolize people normally assume

8396.5 -> that having that private infrastructure makes it easier

8400.8 -> for them to actually go ahead and put in your data

8403.271 -> that is not true.

8404.18 -> The fact that people are used to certain methods

8406.699 -> or methodologies.

8407.699 -> They feel comfortable with it.

8409.4 -> Whether cloud is complex or not.

8411.028 -> I would say it is not why

8412.3 -> because if you get used to certain Services,

8414.635 -> you would realize that storing

8416.4 -> or moving a data to cloud is actually lot more easier

8419.7 -> than Normal infrastructures are

8422.1 -> your previous or traditional infrastructures is

8425.1 -> what I would say,

8426.166 -> so whether cloud is complex,

8427.813 -> I would say no

8428.6 -> as we move into the demo part probably we would be talking

8431.665 -> about this pointer

8432.606 -> or once I give the demo

8433.806 -> probably you would have a clearer picture

8435.992 -> how easy it is to actually move your data to Cloud.

8440.8 -> Not eco-friendly.

8442.2 -> Now this might sound out of the blue.

8444.3 -> I mean you might wonder this is not a sociology session.

8447.355 -> So where did this point coming from?

8449.3 -> I mean not eco-friendly.

8450.827 -> Yes what people assume is the fact

8452.924 -> that a large amount of data is being stored

8455.516 -> on these platforms.

8456.711 -> So we have use amounts or use numbers of data centers

8459.873 -> which are big in size

8461.186 -> and they consume a lot of electricity.

8463.5 -> So there is power wastage electricity wastage.

8467.3 -> Well, that is a myth again first and foremost the fact

8470.1 -> that Getting a centralized storage somewhere.

8472.7 -> That means most of the data would be stored there.

8475.205 -> So yes, you are automatically saving out

8477.517 -> on your power consumption

8479 -> when you talk about it from a global or an Eco perspective.

8482.7 -> The other thing is I would not want to point

8485.007 -> out a particular cloud service provider.

8487.1 -> But when you talk about GCB that is Google Cloud platform,

8490.7 -> then Amelie provide

8491.8 -> their cloud services at a very affordable price now,

8494.8 -> why is that?

8495.8 -> The reason for that is they've actually put

8498.27 -> in a lot of effort into the research part.

8500.689 -> Where the researched a lot on

8502.4 -> how they can actually minimize the cost

8504.704 -> and how did they do it?

8506.119 -> They basically ensure that the amount of power

8508.9 -> that is consumed by the resources.

8511.9 -> They tried and optimize that amount to a minimum amount

8515.738 -> so that they are charged less

8517.8 -> and in a way you are charged less.

8519.5 -> So if they're optimizing that particular process,

8521.971 -> obviously you're consuming less amount of electricity.

8524.7 -> So whether it's eco-friendly

8526.566 -> definitely it is eco friendly friendly.

8531.3 -> Zero down time again.

8533.1 -> There's no such thing as zero downtime.

8535 -> Now the fact

8535.57 -> that I'm talking about cloud storage does not mean

8538.02 -> that I tell you

8538.751 -> that it has zero downtime

8540.062 -> and you're completely secured know there is a possibility

8543.3 -> that there might be a downtime the fact

8545.736 -> that cloud ensures that this downtime is very less.

8549.128 -> Now.

8549.391 -> That is a plus Point

8550.779 -> what loud also does is it ensures

8553 -> that there is disaster recovery

8555.5 -> and there is always a backup of your data or your resources.

8559.4 -> So even if something goes down for a very little time

8562.403 -> and we normally it happens for a very less time

8564.911 -> if it does happen and it happens very rarely,

8567.9 -> but even if it happens care is taken

8570.406 -> that nothing harms your resources or your data.

8573.661 -> So zero downtime.

8574.736 -> No that is not true.

8576 -> But definitely downtime is taken care of when you talk

8578.7 -> about Cloud storages.

8582.5 -> There is no need of cloud storage.

8584.5 -> Okay, this is one of the biggest myths

8587.1 -> whether people agree or not.

8588.85 -> If you go back like 10 years from now probably people

8592.1 -> did not know a lot about cloud computing.

8594.1 -> But with time people are actually moving to cloud

8597 -> and if you take a look at recent statistics,

8599.4 -> they would agree as well.

8600.8 -> I mean people would be wanting to switch to cloud

8603.5 -> in near future.

8604.449 -> And the reason for that is the quite a few service

8607.489 -> is quite a few facilities that cloud gives you

8610.28 -> and that is why people are moving to And

8612.7 -> if you do move to Cloud,

8613.9 -> you'll be using cloud storage inevitably.

8616.6 -> So yes that is going to happen.

8618.775 -> And if you think

8619.7 -> that there is no need for cloud storage

8621.6 -> definitely near future.

8623.5 -> I would assure you

8624.432 -> that even you would be moving to Cloud.

8626.5 -> So Guys, these are some of the major myths there are

8629.05 -> some other myths as well as we move further not worried.

8631.6 -> We would be discussing that as well in some other pointers.

8635.6 -> So let's just go ahead and talk about some of the benefits

8638.6 -> of using a cloud storage for data storage

8642.1 -> or basically using Cloud for data storage.

8644.255 -> So what are the benefits of the signal I purposely kept

8647.175 -> this pointer for the later half and I first discussed the myth

8650.5 -> because these pointers would definitely help

8652.905 -> you understand some of those myths better.

8657.5 -> Not a cloud platform is customer-friendly.

8660.8 -> What do I mean by this?

8662.463 -> Well, first and foremost

8664.2 -> when you talk about cloud storage,

8666.4 -> what you're able to do is you're able to scale

8669.314 -> up your storage scale down your storage keep

8672.1 -> it secure monitor it

8674.2 -> and you can ensure

8675.1 -> that there is constant backup taken of your data.

8677.9 -> So when you talk about it from a security perspective,

8681.1 -> it is secure as well plus what cloud service providers do

8684.947 -> is they've had so many services

8686.8 -> that In the market you talk

8688.161 -> about any popular cloud service provider they

8690.38 -> have lot of services that are made available.

8692.6 -> What do these services do is they ensure

8695.16 -> that you're functioning on cloud platform is

8697.983 -> very smooth and same is for cloud storage as well.

8701.2 -> You can utilize various Services which ensure

8704.4 -> that you're functioning

8706.057 -> or you're working on cloud becomes easy again,

8709.3 -> which I have been reiterating for a while.

8711.555 -> Now that I would be talking about these in future slides.

8714.5 -> Don't worry as we get into the demo part you would

8717.1 -> and how user-friendly these Cloud platforms

8720 -> are Security now again,

8724.4 -> this is an important point

8726.6 -> when you talk about Cloud platforms Cloud storages

8729.662 -> are they secure or not?

8731.1 -> Definitely they are very secure

8733.5 -> and there was a time when people believed

8736.1 -> that these platforms

8737.4 -> when not secure to a greater extent

8739.9 -> and that out was understandable.

8741.5 -> I mean if there is something

8742.9 -> that is new in the market you tend to doubt

8744.7 -> that but if you talk about Cloud platforms

8747.2 -> these platforms are actually more secure than your on-premise

8751.5 -> or your traditional.

8752.8 -> Says which people are used to using the reason for this is

8756.4 -> if you talk about cloud service providers,

8758.53 -> let's talk about AWS.

8759.621 -> That is Amazon web services in this case.

8761.7 -> What it does is it gives you a shared security model now,

8764.9 -> what do I mean by this you have service level agreements

8768 -> where you and your customer

8769.928 -> or maybe the customer and the AWS providers.

8773.2 -> They basically come to a term

8774.8 -> where the decide as in what kind of security

8777.6 -> or what kind of principles are to be implemented

8780.185 -> on the architecture and you can take control as a new.

8783.1 -> You can decide what accesses do you want to give to the vendor?

8786.6 -> And what are the axis is you want to keep to yourself?

8789.4 -> So when you do combine this approach?

8791.7 -> It ensures that security is is at the optimum and you get to be

8796.4 -> or you get to take control of your security as well.

8799.5 -> So yes,

8800 -> if you talk about cloud storage being secure or not.

8802.7 -> Yes.

8803 -> It is very secure to name some we have S3 and AWS.

8806.7 -> It is highly durable and it is highly reliable.

8810.3 -> So when you talk about disaster recovery

8812.5 -> and T it is almost up to there

8815.6 -> and as I've already mentioned not everything

8817.7 -> is hundred percent

8818.9 -> when I talked about the downtime or yeah

8822 -> the downtime part so yes,

8823.6 -> not everything is hundred percent.

8825.3 -> But when you talk about security and durability

8827.805 -> when you talk about S3

8829.1 -> in particular it is 99 point something

8832.127 -> six or seven times nine that is 99.999999 times durable.

8836.9 -> So that does make a system very secure.

8842.2 -> Another benefit guys.

8843.435 -> It is pocket-friendly.

8844.588 -> Now, if you talk about cloud service providers,

8847.004 -> whether it's storage,

8848.262 -> whether it's compute service database Services all

8851.2 -> these Services you can actually go ahead and use these services

8855.3 -> for rental basis.

8857.6 -> It's just like paying for electricity.

8859.525 -> I mean, if you're using

8860.878 -> a particular service you would be paying for that service

8863.752 -> for the duration you use that service

8865.6 -> and you would be paying only for the resources

8867.699 -> that you've used.

8868.7 -> So it is pay-as-you-go kind of a model

8871.3 -> where The only for the resources

8873.2 -> you use and only for the time duration you use

8875.639 -> so whether it's pocket friendly or not.

8877.694 -> Yes.

8877.894 -> It is pocket friendly.

8879.044 -> And as you move further,

8880.3 -> I mean if you are using more storage the cost again,

8884.1 -> it comes down to a greater extent.

8886.262 -> So it is already cheaper and if you decide to scale up,

8889.8 -> it would be more cheaper or it would be cheaper is

8892.441 -> what I should say.

8893.7 -> So yeah, these are some of the benefits now

8895.749 -> if you talk about cloud computing and storage again,

8898.353 -> there are other benefits like as I've already

8900.6 -> mentioned durability.

8901.9 -> Scalability and various other benefits but these

8905.246 -> are some core ones.

8906.6 -> I would not want to get into the details

8908.322 -> because I wish to keep everyone on the same page for people

8910.949 -> who have been attending

8912.1 -> this session for the first time and for people

8915.3 -> who probably know a bit about cloud computing again guys,

8919.5 -> if some of the terms that I'm talking

8921.3 -> about in this session you feel

8922.7 -> that these terms are fairly new for you

8925.3 -> and I'm probably going at a faster Pace,

8928.1 -> I would suggest that you actually do go ahead

8930.7 -> and check into the The sessions

8933.1 -> that we have on our YouTube channel

8935.6 -> because we've talked about a lot of stuff there.

8938.077 -> I mean other cloud services

8939.5 -> what cloud computing is what cloud service providers are

8943.05 -> what are different service models and

8945 -> quite a few other videos and sessions to be honest.

8947.9 -> So I would suggest

8948.8 -> that you go through those sessions as well.

8950.9 -> And I'm sure

8951.7 -> that by now many of you might have been wondering as

8954.345 -> in whether this session would be recorded

8956.475 -> and a copy of it would be available to you.

8958.753 -> People are not not very most of us sessions.

8961.654 -> They go on you.

8962.536 -> Boop so probably a copy of it would be there on YouTube.

8965.596 -> And if not,

8966.396 -> you can actually share your email IDs as well.

8968.77 -> If it does not go on YouTube.

8970.3 -> Somebody would share a copy of the session with you people.

8973.2 -> So guys if I'm

8974.9 -> if I'm happening to go a little faster than

8977.136 -> what you're expecting

8978.204 -> do not worry you'd be having a copy of this as well.

8980.8 -> But for now just try to keep up with the pace that I am going

8983.8 -> with and I'm sure

8984.7 -> that by the end of the session we all would be good.

8988.3 -> So guys what are some of the cloud storage practices

8992.048 -> that you should take care of now?

8994.4 -> These are the practices that should concern somebody

8997.2 -> who is planning to move to Cloud again.

8999.666 -> If you are a newbie

9000.9 -> and you're just here to practice we are not talking about you

9004.7 -> in particular but these pointers

9006.699 -> are important for you as an individual as well.

9009.008 -> But I'm talking

9009.891 -> about it from more business business perspective

9012.387 -> or more industrial perspective.

9014.303 -> So if your organization is planning to move

9016.9 -> to Cloud Definitely.

9018.3 -> These are some of the practices or pointers

9020.488 -> that you should take care of.

9025.3 -> So first and foremost scrutinize SLA,

9028.5 -> so as I've already mentioned you have SLS

9030.794 -> where your service providers or vendors basically come to a term

9034.662 -> where you actually go ahead and decide

9036.881 -> on particular rules as a nugget.

9038.8 -> These are the terms and these are the services as a vendor.

9041.937 -> I would be providing you people and you as

9044.177 -> a customer you agree to certain terms as an okay.

9046.8 -> This is what you would be giving us.

9048.502 -> And this is what we would be paying you.

9050.4 -> So there are certain pointers that you should consider

9052.699 -> while you are actually signing your essays.

9054.9 -> That you need to understand is when they say

9058.2 -> that you would be this is the base charge try to understand

9061.5 -> how the charges would be

9062.726 -> when you decide to scale up and stuff like that other thing

9065.689 -> that you need to consider as I've talked about downtime.

9068.5 -> Right?

9069 -> So normally you have SLS

9070.2 -> where people talk about the stuff

9071.8 -> that there won't be an outage which is more than 10 minutes.

9075.606 -> So yes, I mean this sounds fairly good right?

9078.445 -> So in an hour's time,

9080 -> this is a hypothetical example do not consider

9083.1 -> that there would be a downtime of 10.

9084.9 -> Minutes, this is for your understanding.

9087.4 -> Let's assume that there's a downtime of maybe 10 minutes

9091.1 -> in an hour's time,

9092.1 -> which is too high for now, but let's assume

9094.1 -> that so what service provider would claim is

9098.4 -> if there is a downtime

9099.92 -> once probably this is what the charge would be.

9103.1 -> But if it goes down after that probably you get

9106.4 -> some more consistent discount and those kind of things.

9109.7 -> So if there is an SLA where you say

9113.4 -> that it is 10 minutes,

9114.9 -> What if they were to down times of nine minutes in an hour

9118.7 -> and that is fairly close, right?

9120.3 -> So you've been robbed of your right?

9121.95 -> So that is what I'm trying to say.

9123.6 -> I mean if you do actually

9125.07 -> go ahead and have particular SLS make sure

9127.357 -> that you consider in right points that suit

9129.7 -> in your business as well.

9133.1 -> Follow your business needs again guys storage

9136.6 -> as we move further,

9137.438 -> we will be discussing what are the different kinds

9139.6 -> of storage is so when you talk about cloud service providers,

9142.705 -> they provide UN number

9144 -> of storages or In types of storage is what I should say.

9146.969 -> So depending upon the business you're dealing with the kind

9150.1 -> of data that is generated.

9151.71 -> You should be able

9152.773 -> to choose a proper storage for your requirements.

9155.6 -> I mean, whether you're dealing with a real time data,

9158 -> whether it's stationary data archival data based on

9160.967 -> that you should be able

9162.391 -> to actually go ahead and set up your cloud storage.

9165.373 -> Also, you need to understand as an okay.

9167.7 -> Um, this is the date I would be putting in

9169.6 -> and these are the Integrations I would be needing

9172 -> because I'm using these kinds of tools.

9173.9 -> So are those With my cloud platform,

9176.2 -> so probably you need to consider these pointers as well.

9179.4 -> And if you follow these rules

9181.3 -> probably a business would end up saving a lot of money.

9184 -> Now there have been used cases

9185.6 -> where businesses have actually gone ahead

9188.216 -> and saved lakhs of dollars thousands of dollars.

9191.343 -> So yes considering these pointers understanding

9194.404 -> your business also becomes important.

9197.8 -> You need to ensure

9199.063 -> that the security which you are actually

9202.8 -> managing or monitoring is defined properly.

9205.8 -> I've already mentioned

9206.9 -> that if you talk about cloud service providers,

9209.5 -> they let you have an SLA

9211.3 -> where you both come to a similar agreement.

9214.1 -> So understand the security what are the accesses

9216.7 -> that you have?

9217.3 -> What are the accesses?

9218.4 -> You want to give?

9219.262 -> What kind of data are you dealing with and based on that?

9222.062 -> Probably you can come to terms

9223.562 -> when you're actually moving to Cloud.

9228.4 -> Plan your storage future

9230.1 -> what we are trying trying to say here is plan the future

9233.1 -> of your storage again.

9234.5 -> Do you need to scale up in your future?

9236.688 -> What are the peak times that we can expect

9239.138 -> and stuff like that.

9240.315 -> So when you initially actually set your storage up probably

9243.6 -> you would be in a much better position to scale up.

9246.2 -> I'm not refraining from the fact

9248.1 -> that cloud providers are already scalable,

9250.9 -> but just to be secure you can do

9252.608 -> that when you talk about Cloud providers

9254.736 -> mostly the give you an option of scaling, right?

9257.3 -> V or instantly but still having an understanding of

9260.7 -> how much storage you need

9262.2 -> where you going to move in like two years

9264.018 -> three years time probably having an understanding

9266.2 -> of all those things would definitely hold you

9268.9 -> in a much better position.

9272.8 -> Be aware of hidden costs again guys have talked

9275.711 -> about the first SLA, right?

9277.347 -> So it is similar

9278.288 -> to that understand what you're paying for.

9280.612 -> How much are you paying for?

9282.133 -> It is a pay-as-you-go model

9283.6 -> but having an understanding of which Services would cost you

9286.6 -> how much would help you in performing proper essays

9289.6 -> or having proper policies for your storage.

9292.4 -> So these are some of the do's and don'ts

9294.6 -> of cloud storage guys.

9295.9 -> Again, if you need more insights on different Services as well.

9299.7 -> We have a video or a session on YouTube which is called

9302.4 -> as Interviews best practices you can take a look at that as well

9305.738 -> where we talk about different services

9307.7 -> and how can you actually perform certain tasks which would ensure

9311.503 -> that you are in the best possible position.

9316.3 -> So guys we've talked about quite a few things.

9318.568 -> We wonder stood what cloud storage is.

9320.43 -> We were understood what are the benefits

9322.38 -> what are some of the myths

9323.471 -> and what are some of the practices

9324.838 -> that you should take care of now,

9326.241 -> let's take a look at some

9327.4 -> of the different cloud service providers

9329.369 -> that provide you with the services

9331.019 -> and once we are done with it,

9332.365 -> then probably we would move into the demo part.

9336 -> So guys the quite a few cloud service providers,

9338.764 -> which also provide you with storage Services.

9341.135 -> We have Google cloud platform,

9342.9 -> which is one

9344.192 -> of the leading ones digitalocean probably it's everywhere

9348.5 -> whether you search for Internet ads companies.

9352.043 -> It's there.

9353.8 -> Tara Mark again,

9355.03 -> this is a popular cloud service provider IBM.

9358.415 -> Is there in storage or in Cloud for a very long time guys now

9363.5 -> if you go way back I happen to did

9365.3 -> like I happened to attend a session

9367.1 -> where I believe it was AWS and some reinvent session

9370.5 -> where I do not remember the name of the speaker,

9373.505 -> but that wasn't made a very valid point.

9376 -> He's at that in 1980s.

9378.6 -> He remembered or he happen to visit a facility.

9383.1 -> I believe it.

9384 -> As IBM's I'm not sure who's I think it was IBM's

9387.629 -> so he said

9388.307 -> that they had this huge machine which was for storage.

9392.1 -> I mean, it looked very cool in 1980s use machine

9395.4 -> and it was very costly

9398.6 -> it was like somewhere around thousands of dollars

9401.1 -> and the storage space was 4mb.

9403.98 -> Yes for 4mb, the cost was thousands of dollars.

9407.838 -> So you can understand how far storage has come

9411.3 -> how far cloud has come and And yes, IBM,

9415 -> it has been there.

9416.1 -> I mean it has been there since then.

9417.8 -> So if you talk

9418.623 -> about IBM you talk about Google's Cloud platform.

9421.1 -> These are principal cloud service providers.

9424.7 -> Then you have Microsoft Azure knife you talk

9427.164 -> about current market.

9428.4 -> I mean if you go by the stats alone Microsoft Azure and AWS.

9433.2 -> These are the leading cloud service providers AWS

9436.5 -> is way ahead of all the other cloud service providers.

9440.6 -> I'm so sorry,

9441.8 -> but if you talk about Mike Soft

9444 -> as your it is actually catching up

9446.309 -> that Amazon web services and greeson starts show

9449.6 -> that Microsoft Azure is doing fairly fairly.

9453.1 -> Well, so yes,

9454.5 -> these are some of the popular cloud service providers and more

9457.8 -> or less all of them have good storage Services as well.

9461.5 -> But as I've already mentioned Amazon web services is one

9464.25 -> of the best in the market and in today's session,

9466.95 -> we would be understanding

9468.2 -> some of the popular cloud service services

9470.611 -> that Amazon web services has to offer to you

9473.141 -> and when I say popular Services,

9474.9 -> I would be focusing on storage Services specifically.

9479 -> So guys, let me switch into the console and we can discuss some

9482.1 -> of these Services there

9483.269 -> and directly move into the demo part.

9486.5 -> So yes guys,

9487.35 -> I hope this screen is visible to you people.

9490.9 -> This is how the AWS Management console looks like.

9494.3 -> So again for people

9495.459 -> who are completely new to Cloud platform.

9497.961 -> Let me tell you

9498.9 -> that what Amazon web services

9501 -> are most of the other cloud service providers

9503.1 -> do is they give you a free tier account?

9505.3 -> What they're trying to say here is you come you use our services

9508.5 -> for free for a short duration of period

9510.7 -> And if you like then go ahead and buy our services

9513.5 -> so These services are actually made available to you

9517.1 -> for free for one complete Year.

9519 -> Yes.

9519.207 -> There are certain limits or bounds on these services.

9522.2 -> So if you exceed those limits you would be charged.

9525.085 -> But if you stay in the bounds or limits,

9527.123 -> you won't be charged

9528.294 -> and if you talk about exploring these Services,

9531 -> these limits are free tier services are more than enough.

9534.9 -> So again guys,

9535.6 -> if you are completely new you should come here.

9538.3 -> That is Amazon web services Management console create

9541.9 -> a free tier account.

9543.4 -> It is a very simple process.

9544.864 -> Put in certain details where you work.

9546.8 -> Why do you want to use these services are basic details

9549.9 -> and then probably you would have to enter your debit card

9552.5 -> or credit card details.

9553.6 -> Don't worry.

9554.2 -> They won't charge you but this is for the verification purpose.

9557.6 -> And again,

9558.042 -> if you're worried about whether you would be charged

9560.3 -> or an amount would be -

9561.652 -> from your credit amount that or your credit card

9564.417 -> that does not happen guys,

9566.5 -> aw is gives you a notification saying that okay,

9568.94 -> you've been using these services and probably you might be

9572.393 -> over using some of your services also you An setting alarms

9575.8 -> where if you reach a particular limit after that,

9578.9 -> you can actually go ahead and ensure

9581 -> that there is an alarm

9582.247 -> so that you do not exceed the free tier limit.

9584.8 -> So yes, once you do have

9586.6 -> an account you can Avail all the services that are here guys.

9589.7 -> So let's just go ahead and take a look at the console a little

9593.1 -> and just jump into the storage Services right away.

9598.1 -> So when you click on this icon here storage guys

9600.8 -> or Services rather you get access to all these Services

9604.3 -> as I've already mentioned AWS provides you

9607.1 -> quite a few Services the same room hundred Services guys,

9609.9 -> and they cover different domains.

9611.5 -> You can see the domain names at the top computer

9614.6 -> Vortex analytics business applications storage.

9617.9 -> You have management

9618.924 -> and governance security identity management

9621.189 -> and all those Services guys.

9622.7 -> So the in number of services whether it's migration

9625.9 -> whether its Media Services you Services

9628.257 -> for almost everything so

9629.746 -> as we would be focusing on the storage Services

9632.6 -> before we go there.

9634.065 -> This is one thing probably you can select a region

9638.1 -> where you want to operate from that is you want

9640.7 -> to create your resources in this particular region.

9643 -> You can always have this option of using it.

9646.2 -> So what is the reason guys your data is based

9648.788 -> in a data center, right?

9650.383 -> I mean your data is copied somewhere.

9652.7 -> So if you are using those resources,

9654.9 -> probably your data

9655.713 -> would be fetched from that particular location.

9657.728 -> Asian so you can choose a region probably

9659.406 -> which is close to you

9660.35 -> if you like if your business is located somewhere else

9663 -> probably you can choose that region as well.

9665.1 -> So you need to go through the list of regions

9666.9 -> that are available and accordingly make a decision.

9669.5 -> Now this being a simple demo guys,

9671.2 -> I'm would be sticking up or sticking to Ohio basically.

9675.2 -> So let's just go ahead

9676.8 -> and jump into the cloud services part and let's talk

9681 -> about storage in particular.

9682.6 -> So guys,

9683 -> if you take a look at the storage services

9685.665 -> that are here you can see

9687.35 -> that These are the storage services

9689.644 -> that AWS has to offer to you.

9691.6 -> We have S3.

9692.6 -> We have EFS you have FSX you have S3 Glacier storage

9698.094 -> Gateway an AWS back up.

9700.1 -> Let me just try

9700.85 -> and throw some light on some of these services

9703.151 -> and probably we would just go ahead and get

9705.3 -> into the demo of one or two of these services at least.

9708.8 -> So guys, I'm when you talk about S3,

9710.9 -> it is simple storage service.

9713 -> So that is s now

9715.7 -> this storage is basically Object bucket kind of a storage.

9719.878 -> I mean your container where you put in your data

9722.5 -> where you store your data is called as bucket

9725.3 -> and your data or your files are basically stored

9728.555 -> in the form of objects.

9730.1 -> Let's just go ahead and quickly create a small bucket.

9732.6 -> This would be a very small introduction to the service.

9735.3 -> Let's just go ahead and do that.

9737.3 -> So when you keep on click on this icon guys,

9739.5 -> that is S3.

9740.8 -> It redirects you to the S3 console guys

9743.1 -> where you can actually go ahead and create a bucket.

9745.5 -> I've mentioned the pointer

9746.8 -> that there are Don't services

9748.301 -> that make your job very easy with cloud service providers

9751.2 -> and when you talk about storage Services,

9753.38 -> it is no different.

9754.423 -> I mean there are Services which ensure

9756.66 -> that your job is fairly easy.

9758.412 -> So let's just go ahead and see how easy it is to work with S3.

9763.2 -> If you wish to create a bucket guys,

9764.7 -> if you wish to create a container,

9766.249 -> it is very easy.

9767 -> Just go ahead and click on create bucket

9769 -> and give it some name say Sample for today, maybe guys.

9773.1 -> I'm very bad at naming conventions.

9775.1 -> But please forgive me for that.

9777.4 -> Again.

9778.4 -> The names here should be unique.

9779.9 -> I mean if the name is taken somewhere else probably

9782.581 -> you cannot renamed.

9783.605 -> I mean you cannot use that name again.

9785.6 -> So yes, and so that your name is unique

9788 -> and probably guys you should try

9790 -> and name your buckets in such a way

9791.8 -> that those are more relatable say for example,

9794.4 -> if you have a bucket

9795.7 -> for maybe creating a particular application,

9798.9 -> so maybe bucket for that application.

9801.5 -> And or something like that

9802.7 -> so that you have a hierarchy

9804.558 -> and in that way you can assign IM users

9807.08 -> or access to those buckets in a particular order

9810 -> because you would not want

9811.3 -> all your users to have access to that bucket.

9813.3 -> Right?

9813.667 -> So naming convention becomes very important.

9816.5 -> So just go ahead and say next.

9820 -> Keep all the virgin's guys versioning becomes

9822.588 -> very important again.

9823.8 -> Let's not get into the details.

9825.35 -> But let me give you a small idea what happens here versions.

9828.2 -> That means each time of buckets get updated.

9830.8 -> Probably I would want to version or a copy of it

9833.15 -> and I would want the latest one.

9834.7 -> So when I was on it,

9835.754 -> it maintains those copies

9837.073 -> and if I need to go back I can actually go back

9839.5 -> to a particular level or a benchmark,

9842.3 -> which I set the previous time in this case.

9845.2 -> Let's stick to basic one

9846.4 -> and I'd not want any logging details either.

9848.6 -> So just next.

9850 -> Again, guys, there are certain Public Access has

9853 -> which have been given so

9854.7 -> permissions and access we would talk about

9856.805 -> that not worry for now

9858.1 -> just say next and I would say create a bucket.

9862.9 -> And guys the bucket is already ready.

9864.776 -> I'm in my container is already ready

9866.6 -> so I can just go ahead and probably open

9869.008 -> this bucket and put in a file

9870.8 -> if I want and that was very easy guys.

9873.02 -> I say upload and if I'm connected to my local system,

9876.282 -> I just say add files.

9877.6 -> Let's pick this random file,

9879.7 -> which uses this name and I see upload.

9888.4 -> And there you go guys the file is already there.

9890.526 -> I mean, we've created a bucket a container will put in a files.

9893.2 -> It's as simple

9893.9 -> as that permissions as I've already mentioned now,

9896.664 -> let me talk about this point.

9898.3 -> I skip this point, right?

9899.6 -> So let's discuss this a little so guys security something

9903.1 -> that you can handle.

9904.2 -> So you would decide or you need to decide

9906.4 -> what are the users

9907.3 -> that need to access a particular bucket suppose.

9909.8 -> Your organization has different people working

9912.646 -> on different different teams.

9914.158 -> I mean you have somebody who is a developer.

9916.4 -> There's somebody who's working on maybe The administrative part

9920.133 -> on maybe on the designing part.

9921.997 -> So for particular bucket,

9923.5 -> you have particular data

9924.72 -> so you can decide who gets to access

9926.5 -> what so setting in policies becomes important.

9929 -> You can create your own policies as well initially.

9932.072 -> We saw that certain Public Access is restricted

9934.983 -> to this bucket.

9935.932 -> I said, let's skip it skip that for now.

9938.4 -> So when I say that Public Access is restricted,

9941.5 -> that means not any public policy can come in

9944.3 -> and dictate terms are saying that use this policy why

9947.076 -> because There is a restriction.

9948.9 -> This is a private bucket and not anyone can use it.

9951.7 -> So guys when you talk about S3 in particular,

9953.925 -> you can create buckets you can have backups.

9956.1 -> You can have your EBS backups also moved here.

9959.2 -> You can have your you can move your data from here to Glacier.

9961.911 -> We would be talking about they should not worry.

9964.5 -> You can have your elastic Beanstalk applications

9967.564 -> your past applications

9969 -> and the data can be stored in your S3 buckets.

9971.1 -> You can have your CI CD pipelines

9972.7 -> and the data can be moved again to the S3 bucket.

9975.1 -> Now, this is highly durable and highly reliable.

9978.5 -> It's of storing data

9979.9 -> and it gives you fast retrieval of data as well.

9983.6 -> Let's go ahead and try

9984.723 -> to understand some other services as well guys.

9987.088 -> So when I come back here

9988.5 -> and I cefs elastic file storage or system browser.

9992.041 -> So here basically

9993.212 -> in this storage you can store files.

9995.6 -> Yes.

9995.806 -> We are talking about data that is in the form of files.

9998.6 -> And if you wish to connect it better

10000.15 -> with the network you can go

10001.5 -> for EFS as well because then

10003.171 -> you have something called as S3 Glacier.

10005.5 -> Yes.

10005.8 -> We talked about S3 right where data is.

10008.419 -> Is durable and it can be accessed very quickly S3

10011.626 -> on the other hand lets you store archival data.

10014.7 -> Let me tell you what archival data is first.

10017.7 -> So guys when you talk about archival data,

10020.111 -> basically what happens

10021.6 -> with archival data is you're dealing with data

10025.8 -> that you do not need to use every day.

10028.4 -> Let me give you an analogy.

10029.76 -> I'm not sure

10030.249 -> whether you'd be able to relate to that.

10032.2 -> So guys, I'm your birth certificate now,

10035 -> I belong to India

10036.1 -> and we've been taking A lot but we still have a lot of data

10040.3 -> that is in the form of papers.

10042 -> Even if you go to hospitals attempt to request

10044.068 -> for a birth certificate.

10045.141 -> It might take days

10045.926 -> for you to get that birth certificate.

10047.6 -> Why because there is some person

10049.2 -> who will be going through all those documents

10051 -> and giving you that document.

10052.4 -> This is just an example.

10053.6 -> Do not relate it like very seriously.

10055.3 -> But yeah, so it might take a couple of days,

10058.304 -> right so and the birth certificate thing.

10060.9 -> I mean, I might not need birth certificate every day.

10063.5 -> It might be once-in-a-decade that I might go to a hospital

10066.15 -> and probably request that particular birth.

10068.437 -> Ticket, right?

10069.2 -> So this is a kind of data probably

10071 -> which had not need regularly or in real time.

10075.4 -> So I can compromise a little on the fact

10077.1 -> that if the person is giving me that data in two days time.

10080 -> It's okay because that does not cost me anything.

10082.544 -> I can wait for two days maybe but that's not the case

10085.8 -> at times you need the data to be retrieved very quickly.

10089.483 -> So if that is the case you should store it where in S3,

10093.1 -> but if you're fine with this delay,

10095.4 -> probably you would want to store it in Glacier.

10097.7 -> Why?

10098.2 -> These are normally takes a longer while

10100.2 -> to retrieve your data,

10101.857 -> but the advantage of Glacier is it is profitable

10105.4 -> because it is very affordable

10107.264 -> compared to S 3 S 3 is already affordable.

10109.9 -> You can check in for the prices.

10111.5 -> But if you have archival data,

10113.058 -> which you won't be using everyday, you can store

10115.5 -> it here and the fact that it takes a longer

10118 -> while it won't cost you.

10119.7 -> I mean, it won't cost

10120.98 -> in that perspective of accessing your data in real time.

10124.43 -> Right?

10124.813 -> So if the data is something

10126.599 -> that is not needed regularly you can Move to S3 Glacier, right?

10130.632 -> So what happens is S 3 you can actually move in all your data.

10134.6 -> And then if you realize that there is certain data,

10136.698 -> which would not need every day.

10138 -> Just move it from S 3 to S 3 Glacier

10140.552 -> where the data is stored in archival form and it is

10144.2 -> or it does not cost you a lot.

10145.909 -> So again guys,

10146.733 -> I won't be getting into the demo of S3 Glacier.

10149.4 -> We have a session on S3 Glacier

10151.668 -> or Amazon web services Glacier other and to do that.

10155.4 -> What you need is you need probably a third party tool.

10158.146 -> That makes it easier for you to retrieve the data.

10160.703 -> So I won't be getting into the stuff

10162.607 -> where I download that to land and show you how it works.

10165.6 -> It's very simple.

10166.9 -> We'll just like we created buckets.

10168.411 -> Are you create volts there and you probably move

10170.7 -> in your data and you can retrieve that data.

10172.872 -> But again, it takes a long while to retrieve that data.

10175.6 -> So it is similar to S3, but little different so

10178.969 -> yeah, that is S3 Glacier.

10180.8 -> We understood what EFS is and what S3 is then again guys,

10185.2 -> you have some other services as well here

10187.8 -> if I Scroll down you have your storage Gateway.

10190.9 -> You have your AWS backup as well.

10193.1 -> So what are these things?

10194.801 -> And what do these things do well storage Gateway

10198 -> an AWS back up basically back up

10199.9 -> as it says you can have backup of your data

10202.3 -> and you can like save it from going down and stuff like

10205.6 -> that when you talk about storage get with these are services

10208.6 -> that let you move your data from on-premise atmosphere

10212.6 -> or your infrastructure rather to Cloud.

10215.8 -> So if you already have data that is on your existing on-premise

10220.5 -> or infrastructure rather,

10222 -> you can actually move that data to Cloud as well.

10224.3 -> So there are services to help you do that.

10226.3 -> And those services are your storage Gateway services?

10229.9 -> So guys we've discussed some

10231.6 -> of these Services there is something else

10233.9 -> which is called as elastic block storage.

10236.8 -> Elastic Block store is

10238.2 -> what it does is it lets you create volumes snapshots

10241.668 -> and copies of the volume

10243.3 -> that is attached to your instances.

10245.8 -> Let's go ahead and take a look at how this works.

10248.2 -> I mean there are a lot of pointers to talk about it.

10250.7 -> So as I move further,

10251.969 -> I would be discussing those pointers while I

10254.568 -> also show you how to do it.

10257.9 -> So guys when I say EBS or elastic block storage

10262 -> what that does is it lets me attach some kind of volume

10266.033 -> to my instance now instances.

10268.2 -> Let me tell you what instances are first.

10270.6 -> Now when you talk about cloud services,

10272.7 -> they give you compute Services where you can spawn instances

10276.7 -> or spawn temporary servers or servers

10280.2 -> where you want to host a data now each time.

10282.8 -> I won't be going out and buying a new machine right instead.

10286.2 -> What cloud does is it?

10288.4 -> What happens?

10296.8 -> Yes, guys.

10299.4 -> Okay, guys, I'm not sure whether there was a lag

10301.499 -> while you were going to this session.

10303.3 -> What happened is let me tell you what happened my connection

10307.2 -> the streaming connection to my software,

10309.299 -> which I'm using to stream.

10310.7 -> This session did go down a minute back and it shows now

10314.7 -> that it is connected.

10316.4 -> So I would like to know

10317.8 -> whether I'm audible to you people are not if yes,

10320.2 -> then we can continue with this session guys.

10328.7 -> Okay, I'm guessing we're fine.

10329.999 -> So I'm just gonna go ahead and continue with the session.

10332.8 -> I was talking about instances.

10334.3 -> Let me talk a little more about it.

10336 -> So when I talk about these servers

10338.22 -> that are ready to use basically these servers are something

10341.966 -> that you can use

10343 -> and you can have some memory attached to it.

10345.4 -> So what we're going to do is we're going

10347.2 -> to go ahead and launch one instance and understand

10349.6 -> how memory or hose storage works with it.

10352.5 -> So to do that we were going to go ahead

10354.857 -> and just launched that particular service.

10357.4 -> It is called as To which is a compute service guys.

10360.341 -> So here I can actually go ahead and create servers

10363 -> or launch instances in simple words.

10364.866 -> So let's just go ahead and launch a particular instance.

10367.8 -> Now, I have the freedom of launching both

10371.57 -> linux-based windows-based one to based kind of instances.

10374.8 -> So you have the freedom of choosing what kind

10377 -> of instance do you want this being a simple demo guys.

10379.693 -> I'm going to stick with the windows instance.

10382.096 -> I'm not going to show you how to deal with that instance

10385.1 -> because I've done that in previous sessions.

10387.27 -> You can take a look

10388.228 -> at some of those switch sessions as well guys.

10390.8 -> Let's just go ahead and launch this particular session

10394.112 -> or this particular instance rather now guys,

10397.6 -> this is a Windows instance and okay,

10400.669 -> not this let me launch on basic one.

10403.7 -> This is also free tier guys.

10405.4 -> But yeah, I would want this make sure

10407.7 -> that your instance is EBS backed.

10409.8 -> So guys, you're backing up Works in two ways.

10412.4 -> You can back it up on S3.

10413.723 -> You can back it up on eBay

10415.1 -> as that is elastic block storage now elastic block.

10418.503 -> Storage is important why it lets you create images and volumes.

10422.6 -> What are those we'll talk about that

10424.45 -> once we create this instance.

10426 -> So ensure that for now it is EBS.

10428.4 -> So if I click on this is the thing

10431.3 -> if I click on this icon,

10434.2 -> It would give me details what kind

10435.85 -> of instance I'm launching when I say T2 micro.

10437.9 -> It is a small instance which has one CPU

10440.8 -> and one gigabytes of memory

10442.876 -> for now and I can just go ahead and say next.

10450.3 -> Okay, some of the other details

10452.5 -> whether you want to be PC or not.

10454.384 -> Let's not discuss that and then you get

10456.619 -> into the storage part guys.

10458.4 -> This is the device with two

10460.7 -> which I am attaching my root volume.

10462.619 -> So this is the path rather.

10464.1 -> So I need to focus on this.

10465.6 -> It is SDA one guys.

10467.4 -> That is slash Dev slash sd1.

10469.7 -> You need to remember this when you create new volumes

10472.4 -> and the types of volumes

10473.8 -> that you can attach to your instance are these

10476.2 -> you have general-purpose SSD provision tie offs and magnetic.

10480.2 -> It is take a something

10481.315 -> that is getting outdated probably might be replaced.

10484.2 -> So these are the few ones you also have some other kind

10487.17 -> of volumes that you can attach but the point

10489.7 -> that you need to remember is

10492.1 -> when you talk about having a primary volume in that case

10496.2 -> you have only these options

10497.968 -> because these are bootable guys

10500 -> so there are certain other volumes that you can attach

10503 -> if I attach a secondary volume,

10505.7 -> you see the options are more.

10507.3 -> I have SSD for traffic optimization and then I

10510.348 -> have cold SSD as well.

10511.746 -> But this is a basic thing.

10513.4 -> We not going to get into the details of that.

10515.675 -> You would skip

10516.4 -> that so guys all I'm trying to say is this is the device

10519.5 -> this is the size

10521.4 -> and probably this is the type of instance or volume.

10525.133 -> Sorry is that would be attached to my instance.

10528.5 -> So let's just go ahead and say next a tax for now.

10532.105 -> Let's not add anything

10533.6 -> and then let me say configure the settings.

10536.2 -> So guys when I launched an instance it says

10538.4 -> that security is not Optimum.

10540.3 -> It's okay.

10540.8 -> I mean you can assign the port you want to when you use it

10544.404 -> for a higher security purpose.

10547.4 -> And then this is important guys for your each instance.

10550.5 -> You need a key pair

10551.617 -> which is a secret way of logging in

10553.54 -> or a secure way of logging in not secret a secure way.

10556.423 -> So this is a second place authentication.

10558.6 -> Once you're logged into your account.

10560.534 -> You would be needing a key pair

10562.2 -> if you wish to use this instance,

10564.4 -> so make sure you create one

10566.7 -> and you store that one as well if you have one

10568.95 -> which you can use probably.

10570.4 -> can do that as you can just create one say Nuki I

10577.1 -> said download guys.

10578.7 -> Once you download it.

10579.847 -> Keep it safe somewhere.

10581.2 -> It is stored in the form of that p.m. File.

10583.8 -> So do that and then I say launch an instance.

10588.5 -> So guys once this happens

10590.784 -> if I just go back to the ec2 dashboard

10594.1 -> probably I can see

10595.1 -> that there is an instance which is running for now.

10597.8 -> It is 0 why

10599.3 -> because guys my instances still getting launched.

10602.223 -> It takes a couple of minutes

10603.935 -> or 1 and 1/2 or 1 minute probably to launch an instance.

10607.3 -> The reason for this is probably a lot of things happen

10610.123 -> in the background.

10611.061 -> I mean certain network is associated.

10612.88 -> If you talk about an instance,

10614.35 -> it needs to communicate with other instances, right?

10617.1 -> So in that case Probably you need to have a network

10620.203 -> that lets all these instances connect.

10622.5 -> So a network is set here basically and probably all

10626.4 -> the storage volume is attached in a lot of things happen.

10629.454 -> That is why there are certain statistics

10631.592 -> that your instance needs to go through and hence.

10634.23 -> It takes a minute or so to launch this instance.

10636.878 -> So if you take a look at this the status text it says

10639.972 -> that it is initializing.

10641.7 -> So if you refresh it probably it happens at times.

10645.1 -> So let's just try our luck see whether it's No,

10648.4 -> it's still initializing but guys

10650 -> we can see the volume that would be attached to it.

10652.8 -> So, let me just come here and rather go here

10657.453 -> if I click on volumes,

10660.4 -> there is there is a volume that is attached to it.

10662.9 -> So there is a 30 GB volume.

10664.8 -> So there's a volume

10666.3 -> that probably has a size of 30 GB.

10668.896 -> So it is here already and it is in use

10671.8 -> so it would be attached to my instance

10673.9 -> once it is up and running.

10675.3 -> So the point I'm trying to make here is what elastic block.

10678.2 -> Storage does is it lets you manage all these things now?

10680.974 -> There are two ways to manage these things either you create

10683.9 -> a copy of this volume disable this volume

10686.5 -> and then attach the next one

10688.1 -> or probably you can directly scale your existing volume

10692.376 -> or make changes to it right away.

10694.2 -> So what elastic Block store

10696.234 -> is does is it lets you manage the storages?

10699.4 -> So again, let me tell you how it works.

10702.7 -> So when I create an instance probably discredited

10705.1 -> in a particle particular region,

10706.796 -> right so in that A particular region say for example

10709.547 -> now I'm based in India.

10710.9 -> So I have a data center in Mumbai.

10713.166 -> So my instance would be created at that data center

10716.6 -> and probably the storage for it would also be there.

10719.823 -> So there is no latency when I try to use that storage.

10723.9 -> So this is

10724.6 -> what EBS does it lets you manage that particular storage.

10728.2 -> So how it works is I can create a copy of it.

10731.3 -> So what this copy does is it serves two purposes so next time

10736.4 -> if I wish to make In just to that storage I can do

10740.2 -> that if this particular storage or volume goes down.

10743.3 -> I have a backup copy again.

10745 -> I can create snapshots as well.

10746.694 -> Now what snapshots do is basically they let me replicate

10749.8 -> my instance and the volume that is attached with it.

10752.8 -> So instead of creating an instance again,

10755.1 -> and again with

10756 -> if I've defined certain properties for my instance

10759 -> and not have to worry about defining those properties again,

10761.2 -> and again, I can just create a snapshot or I can rather

10764.4 -> create an Emi out of it,

10765.854 -> which I can store and use it next time.

10768.157 -> If I want to spawn a similar instance,

10770.4 -> so this is very BS helps in it lets you have backups

10773.4 -> of all these storages

10774.8 -> it lets you create copies of it.

10776.5 -> So even if something goes down you can work on the copy

10779.7 -> that you have so guys by now.

10782 -> Our instance would be created.

10783.5 -> Let's just go ahead and take a look at it.

10786.4 -> It says it is running guys,

10788.187 -> and we've already taken a look at the volume.

10791.6 -> Let us create a copy of this volume to do that.

10794.1 -> I'm going to go to the actions my instances selected already.

10797.347 -> I can just go to modify

10798.7 -> and make changes to this volume right away,

10800.9 -> which is an easier way,

10802.059 -> but I'm going to show you

10803.325 -> how it can be done the other way as well

10805.6 -> how it used to work previously so I can just say

10808.6 -> that create a snapshot.

10811.2 -> details Sample, and I say create.

10818.3 -> So guys are snapshot is created.

10820.6 -> If I come here I can take a look at the snapshot again.

10823.936 -> It is spending might take half a minute

10826.284 -> for the snapshot to get created

10828.9 -> so I can just come here and replace or refresh other.

10843.3 -> These things at times take a little while.

10845.5 -> So guys we would be creating a copy of it probably viewed

10848.3 -> by detaching the volume

10849.6 -> that we have created and it is attached to our instance

10852.507 -> and we would replace that with the copy

10854.569 -> that we are creating now.

10855.925 -> So once this thing is done and created we can do that.

10862.9 -> For some reason it's taking longer while today.

10865.9 -> Let's hope that it gets done quicker.

10870.2 -> Look, it's still processing.

10871.6 -> Let's bear with me or just bear with me.

10873.7 -> Meanwhile this happens.

10890.6 -> Again guys if I was too fast and if I missed out

10893 -> on certain things I would like to tell you

10894.7 -> that you can go through our other sessions on YouTube

10896.9 -> and probably you would be in a much better state to understand

10899.3 -> what has happened here again,

10900.89 -> there was an outage we're not out.

10902.7 -> It's my software did not work properly the streaming software

10906.4 -> and probably there was a lack of a minute or two.

10908.747 -> So I'm hoping

10909.4 -> that you are did not miss out on anything that was happening.

10912.5 -> Meanwhile.

10913.3 -> Just hope that this Snapshot gets created quickly.

10917.9 -> It is still pending and this is irritating at times

10920.4 -> when it takes a long while It's completed guys.

10927.853 -> A snapshot is ready.

10929.6 -> I can just go ahead and say create a volume out of it,

10933.3 -> which I wish to attach.

10935 -> So guys there are certain details

10937.4 -> that we need to do.

10938.7 -> So for that laces go back first.

10941.9 -> Let's go back to the instance that we have and let's see

10946.2 -> where the instance is created guys.

10948.7 -> So as you can see if you come here,

10951 -> it would give you the details of the place

10953.598 -> where the instance is created.

10955.5 -> So it is u.s.

10956.327 -> East to see so when you create an volume a volume,

10959.501 -> it is necessary

10960.417 -> that you created in the same region guys

10962.8 -> because as I've already mentioned the benefits

10965.3 -> of having it in same reason is region is

10967.6 -> that you can attach it to your existing instance

10970.5 -> and it saves you from various Layton sees so,

10973.764 -> yep, let's go back

10975.1 -> to the snapshot spot and say create a volume of it.

10980.1 -> I say create and then

10981.7 -> I probably let's say I want more storage guys

10985 -> that's in 90.

10991.2 -> Okay, this is general purpose it is to way.

10993.352 -> So let's go to to see if I'm not wrong.

10995.3 -> It was to see let's

10996.8 -> just go ahead and create it in to see and say create volume.

11004.5 -> Clothes so guys are instances

11007 -> where our volume is created successfully again guys.

11010 -> Now you can take a look at it.

11012.5 -> From this perspective.

11013.662 -> I have my Snapshot here, right?

11015.3 -> So this snapshot says 30gb that does not mean

11017.886 -> that the snapshot which I took its size is 30 GB.

11020.71 -> It says that it was created

11022.2 -> from an instance or size is 30 GB.

11024.1 -> So there's a difference between these two things guys understand

11027 -> that as well.

11028.807 -> So I have a volume

11030.3 -> which is based in availability Zone to see I have an instance

11036.1 -> which is here and it again is it availability Zone to see

11041.8 -> so we can attach to it.

11044 -> Let's just again go back to the volume spot.

11047.6 -> So guys, I have two volumes.

11049 -> I created this one and this is attached to my instance.

11052.3 -> Let me just try and remove this first.

11055.9 -> detach volume Okay,

11058.7 -> it's giving me an error try to understand why

11061.044 -> this error is there guys.

11062.408 -> My instance is already running.

11064.1 -> So I cannot directly remove this volume from here for that.

11068.572 -> I would have to select this instance go

11071.5 -> to instant State and say stop so it stops working for now.

11075.9 -> And once it does I can attach the volume.

11080.1 -> So for now what you can see is there are these volumes here

11083.5 -> it is in use right?

11084.7 -> So once the instant stops it would be available

11087.6 -> and won't been used

11088.633 -> so I can replace it with this instance.

11098.3 -> So it has stopping it hasn't stopped yet.

11107.2 -> So as do not worry,

11108.317 -> we would be done with the session very soon.

11110.6 -> And once we are done probably you all would be free to leave.

11114.701 -> I believe that this session has taken longer

11117.139 -> than my normal sessions.

11118.5 -> But yeah, there was a lot of stuff to talk

11120.4 -> about we talked about the complete story services

11122.799 -> that you have reached has to offer to you people hence.

11125.5 -> This session was so long.

11126.8 -> So let's just quickly go ahead and finish the stuff.

11136.2 -> It has stopped.

11137.6 -> So guys I can now go ahead and remove the volume

11141.5 -> or detach this volume and go ahead and attach the other ones

11145.9 -> if I say detach it would detach.

11158.6 -> Yeah, see both are available.

11160.2 -> Now.

11160.507 -> Let's try to attach this volume and say

11165.8 -> attach volume search this is the instance guys,

11170.4 -> which I have created

11172.4 -> and you need to give in the device details,

11174.5 -> which was / what with the details.

11180.6 -> Let's just go back and take a look at the details

11183.5 -> that we're supposed to enter in here.

11185.5 -> So as a you need to give in the path that we talked

11188 -> about which is the drive that we've discussed, right?

11192.1 -> So that is the part that you need to enter.

11196 -> And then you actually go ahead and say SD a one.

11200.9 -> Slash and probably you would be more than four to go.

11205.1 -> So this is the other thing I do not remember the other part.

11207.575 -> So you need to go ahead and put in these details here.

11209.8 -> If you put in these part details guys,

11212.5 -> you can just go ahead

11214.115 -> and attach your volume right away and this volume

11218 -> would get attached to your instance.

11220.2 -> So this is how it works

11221.7 -> and you can actually go back and do other things as well.

11224.9 -> So if I just come here I have this instance.

11230.2 -> So what you have to do is you have to actually go ahead

11233.5 -> and click on this thing for now.

11235.785 -> It's not working.

11237 -> But if you just come back here or to the volume part.

11252.5 -> So if you just go to the volumes part

11254.3 -> with we were at in the previous.

11258.1 -> Slide you can actually go ahead

11260.1 -> and attach the volumes now here you go by just go to instances.

11266.9 -> Probably go back and I say ec2 again.

11274.7 -> Yeah, if I come back two volumes guys.

11278.1 -> You can attach the volumes

11279.4 -> that are there you can delete those

11280.906 -> and you can do a number of changes that you wish to do.

11283.3 -> So just go ahead and attach these volumes

11285.676 -> and you would be more than good to actually go ahead

11288.7 -> and launch our instances or manage the storages

11291.64 -> that are there.

11292.6 -> Again.

11292.9 -> The only thing that I missed out on is the path I told

11295.715 -> you to note the path the device name, right?

11298 -> You just have to go ahead and enter in the device name here.

11301.1 -> And if you enter in the device name

11303.2 -> while creating your volume

11305.6 -> or attaching your volume your instance.

11308.1 -> Get attached to that

11309.5 -> or your volume would get attached

11311.526 -> to that instance right away.

11313.9 -> So yes guys thus pretty much sums up today's session.

11317.9 -> We've talked about quite a few things here guys.

11322.1 -> We've talked about S3 Services we've talked about we've talked

11326.4 -> about EBS in particular.

11327.725 -> We've understood like how to detach a volume

11330.1 -> how to attach on I just did not show you

11331.928 -> how to attach the volume,

11333.1 -> but you can do that.

11334.1 -> The reason I'm not showing you

11335.7 -> that is probably lost out on On the device name here,

11339.6 -> which normally comes in here.

11341.384 -> So before you deactivate your device,

11344.1 -> make sure that you have this name and when you do launch

11347.7 -> or attach your volume to that particular thing,

11350.3 -> all you have to do is you just go to the volume spot.

11354.691 -> And probably when you

11356.4 -> say attached to a particular instance put in that device name

11359.7 -> there and you are instance would be attached

11362.2 -> or your volume would be attached to your instance

11364.5 -> and you can just go ahead and say launch

11367.8 -> or just start this so-called instance again,

11371.7 -> and you'll be good to go guys.

11373.286 -> So as far as this particular session goes Guys,

11375.719 -> these are the pointers I wanted to talk about.

11378.1 -> I hope that I've talked about most of these pointers

11381.047 -> and I've cleared all your mints or doubts that were there.

11389.5 -> So that's when you talk about S3.

11391.601 -> Now.

11391.879 -> It has a simple storage service

11393.961 -> which is simple or easy to use in real sense.

11396.9 -> It lets you store and retrieve data

11399 -> which can be in any amount

11400.47 -> which can be of any type and you can move it

11403.1 -> from anywhere using the web or Internet.

11405.685 -> So it is called as storage service of the internet.

11409.1 -> What are the features of this particular service?

11411.8 -> It is highly durable guys now.

11414 -> Now, why do I call it durable,

11416.2 -> it provides you durability of 99.999999 some 11:9 now

11421.8 -> when you talk about that amount of durability,

11424.499 -> it is understandable

11425.7 -> how durable this Services what makes it this durable.

11429.4 -> It uses a method of checksum wear.

11431.77 -> It constantly uses checksums to analyze

11434.5 -> whether your data was corrupted at a particular point and if yes

11438.814 -> that is rectified right away,

11440.8 -> and that is why this service is so durable, then it is.

11444.3 -> Be flexible as well as I've already mentioned S3 is a very

11448.032 -> simple service and the fact

11449.8 -> that you can store any kind of data.

11451.888 -> You can store it in any reason or any available reason is

11455.2 -> what I would mean by the sentence.

11457.1 -> It makes it highly flexible to store the data

11459.32 -> in this particular service and the fact

11461.246 -> that you can use so many pi

11462.686 -> as you can and of secure this data in so many ways

11465.3 -> and it is so affordable.

11466.8 -> It meets different kinds

11468.3 -> of needs thus making it so flexible available.

11471.761 -> Is it available?

11472.67 -> Yes, definitely it is Is very much available

11475.3 -> as we move into the demo part,

11477.064 -> I would be showing you which regions

11478.898 -> basically let you create these kind of storages

11481.323 -> and how can you move

11482.5 -> and store data in different regions as well.

11484.9 -> So if you talk about availability, yes,

11487 -> it is available in different regions and the fact

11489.4 -> that it is so affordable

11491.085 -> making it available becomes all the more easy cost-efficient.

11495.3 -> Yes now to start

11496.5 -> with we normally do not get anything for free in life.

11499.4 -> But if you talk about S3 storage AWS has a free tier

11503.07 -> which lets you use.

11504.4 -> Public services for free for one complete year

11507.6 -> but this happens in certain limits.

11509.3 -> Now when you talk about S3,

11511.047 -> you can store 5 GB of data for free at least to get started

11514.8 -> or get used to the service.

11516.278 -> I believe that is more than enough and

11518.455 -> what it also does is

11519.6 -> it lets you have somewhere around 20,000 get requests

11523.1 -> and somewhere around 2,000 put requests as well.

11526.1 -> So these are something that let you store

11528.291 -> and retrieve data apart from that.

11530.4 -> You can move in 15 GB of data every month outside.

11534.2 -> Side of your S3 Service as well.

11536.9 -> So if you are getting this much for free,

11538.8 -> it is definitely very much affordable.

11541.09 -> Also, it charges you on pay as you go model.

11543.737 -> Now.

11543.973 -> What do I mean by this?

11545.331 -> Well, when I say pay as you go model

11547.4 -> what we do here is we pay only for the time duration

11550.9 -> that we use the service for and only for the capacity

11554.007 -> that we use this service form.

11555.8 -> So that is why as you move along

11557.406 -> if you need more services, you would be charged more.

11560.1 -> If you do not need more amount

11561.866 -> of the service you won't be charged to that.

11564.4 -> Extent, so is it cost efficient?

11566.5 -> Definitely it is scalable.

11568.5 -> Yes.

11569.3 -> That is the best thing about AWS Services.

11571.456 -> Most of them are scalable.

11572.812 -> I mean you can store huge amount of data,

11575.092 -> you can process huge amount of data.

11577 -> You can acquire use amount of data

11578.993 -> if it is scalability

11580.2 -> that is your concern you do not have to worry about it here

11582.8 -> because even this service readily scales

11584.82 -> to the increasing data that you need to store and the fact

11587.686 -> that it is pay

11588.417 -> as you go model did not have to worry

11590.4 -> about the cost Factor as well.

11592.5 -> Is it secure definitely?

11594 -> It is now you can encrypt your data you have

11596.612 -> various bucket policies as well

11598.309 -> that let you decide who gets to access your data

11601.073 -> who gets to write data or gets to read data.

11603.3 -> And when I said you

11604.206 -> can encrypt your data you can actually go ahead

11606.4 -> and encrypted data both on client side

11608.8 -> and on your server side as well.

11611.1 -> So is it secure I believe

11612.452 -> that answers the question on its own.

11614.4 -> So Guys these were some of the features of Amazon S3.

11617.9 -> So guys now let us try to understand

11620.2 -> how does S3 storage actually work now it works

11623.61 -> with the Concept of objects and buckets now bucket,

11627.4 -> you can think of it as a container

11629.1 -> where as an object is a file

11630.826 -> that you store in your container.

11633.1 -> These can be thought of as AWS S3 resources.

11636.6 -> Now when I say an object

11638.5 -> basically object is your data file.

11640.8 -> I've already mentioned

11641.9 -> that you can store any kind of data whether it's your image,

11644.2 -> whether it's your files blocks, whatever it is,

11646.5 -> these are nothing but your data

11648.123 -> and this data comes with metadata

11649.899 -> when I say an object.

11651.076 -> It is combination of your data plus some metadata

11653.9 -> or Or information about the data what kind

11656.3 -> of information basically you have the key

11658.3 -> that is the name of the file

11660.043 -> that you use inversion ID is something

11662.347 -> that tells you which version are you using

11664.9 -> as we discuss versioning?

11666.4 -> Probably I would talk about Virgin ID a little more.

11669.4 -> But meanwhile,

11670.1 -> I believe this is more than enough your objects

11672.4 -> are nothing but your files with the required metadata

11675.8 -> and the buckets

11676.8 -> as I've already mentioned.

11678.3 -> These are nothing but containers that hold your data.

11681.358 -> So how does it work guys?

11682.9 -> Well, what happens is Sickly you go ahead

11685.5 -> and create pockets in regions

11687.799 -> and you store your data in those regions.

11690.1 -> How do you decide what buckets to you is what reasons to use

11692.771 -> where to create the bucket and all those things.

11694.899 -> Well, it depends on quite a few factors

11696.8 -> when I say I have to create a bucket.

11698.7 -> I need to decide what reason would be more accessible

11701.3 -> to my customers or to my users

11703.4 -> and how much cost does that region charge me

11705.929 -> because depending upon the region your cost might vary.

11709 -> So that is one factor

11710.05 -> that you need to consider and let and see as well.

11712.539 -> I mean if you put your data In an S3 bucket,

11714.932 -> that is far away

11715.8 -> from you fetching it might cause high amount of latency as well.

11719.3 -> So once you consider these factors,

11721.3 -> you can create a bucket and you just tore your objects

11724.5 -> when I said version ID key,

11726.6 -> actually a system

11727.7 -> automatically generates these features for you.

11730 -> So for you it is very simple create a bucket pick

11733.1 -> up your object put it in it

11734.732 -> or just go ahead

11735.7 -> and retrieve the data from the bucket whenever you want.

11739 -> So I believe this gives you some picture about

11742 -> what S 3 is now let me Weekly switch

11744.662 -> into the demo part and let me give you a quick idea

11748.343 -> or quick demo as to how S3 works

11750.7 -> so that it is not too much theory for you people.

11753.9 -> So guys what I've done is I've actually gone ahead

11756.4 -> and I've switched into my Amazon Management console.

11759.3 -> Now as I've already mentioned AWS gives

11761.417 -> you a free tier for which you can use AWS services

11764.469 -> for free for one complete year.

11766.4 -> Mine is not a free tier account.

11768.104 -> But yeah,

11768.562 -> if you are a starter you can create a fresh account.

11771.156 -> You just have to go ahead and given certain details

11773.678 -> all You do is

11774.385 -> you just go to your web browser search

11776.4 -> for AWS free tier and sign in with the required details.

11779.8 -> They would ask you for a credit card

11781.817 -> or your debit card details enter

11783.7 -> any one of those for the verification purpose

11785.9 -> and you can actually go

11786.862 -> ahead and set up alarms as well which would tell you as in.

11789.4 -> Okay.

11789.68 -> This is the limit to which you have used the services

11792.6 -> and that way you won't be charged for Access of data usage

11796.2 -> or service usage having said that guys this is

11799.1 -> about creating an account.

11800.4 -> I believe it is fairly simple.

11801.5 -> You can create an account once you create an account.

11804.3 -> Is this is the console that would be available to you?

11807 -> What you have to do is you have to go ahead

11808.9 -> and search for Amazon S3.

11811.16 -> If you search s3r,

11812.564 -> it would kind of redirect you to that service page.

11818.5 -> So guys as you can see,

11819.669 -> this is the company's account probably somebody

11822.098 -> uses it in the company and they have the buckets

11824.587 -> that are already created.

11826.058 -> Let's not get

11826.8 -> the that is just go ahead and create our own bucket

11829.9 -> and just go ahead and put in some data into it.

11832.2 -> It is fairly simple guys.

11833.2 -> I've already mentioned.

11834.2 -> It is very simple to use kind of service.

11836.4 -> All I have to do is click on create bucket and enter

11839.4 -> in name for some bucket guys.

11841.9 -> Now this name is unique.

11843.9 -> It is globally unique

11845.5 -> once you enter a name for the bucket you

11848.3 -> Not use the same name for some other bucket.

11850.829 -> So make sure you put in valid name and the fact

11853.6 -> that I use the term Global something reminded me

11856.6 -> to be explained of so guys

11858.323 -> as you can see if I go back here.

11860.444 -> I want you to notice this part.

11863.8 -> So guys when you are into the Management console

11866.6 -> or you open any service

11868.2 -> by default the region is North Virginia?

11870.9 -> Okay.

11871.222 -> So if I create a resource, it would go to this region.

11874.7 -> But when I select the service that is S 3 you can see

11878.086 -> that this region automatically goes to Global

11881 -> that means it is a global Service.

11883 -> It does not mean that you cannot create bucket

11885.1 -> in particular regions you can do that.

11887.1 -> But the service is global is

11888.511 -> what they're trying to see so let us go ahead

11891.1 -> and create the bucket Let Us call it today.

11893.8 -> Demo, you cannot use caps guys.

11896.4 -> You cannot use some symbols.

11898.8 -> So you have to follow the naming Convention as well.

11901.7 -> Today is demo.

11903.8 -> Sorry.

11904.152 -> I'm very bad at naming conventions guys.

11906.4 -> I hope it is.

11907.2 -> Okay, let it be in u.s.

11908.9 -> East you can choose other regions as well guys,

11911.5 -> but for now, let it be whatever it is.

11913.7 -> So I'm going to stick to North Virginia.

11916.2 -> There are 76 buckets that are being used.

11918.572 -> Let us just say next bucket name already exists.

11921.749 -> So this was already taken guys see So you cannot use it.

11925 -> Let's call it say.

11928.1 -> vamos bucket 1 3 1 1 3 Okay.

11933.9 -> Do you want to keep all the versions of the object?

11936.4 -> We will talk about what versions are.

11938.1 -> Okay guys.

11938.6 -> Meanwhile, you just bear with me.

11940.1 -> I'm just going to go ahead and create a bucket create

11943.6 -> a bucket and there you go guys.

11946.3 -> I'm sure removes bucket should be here somewhere.

11948.8 -> Here it is.

11949.9 -> If I open it I can just go ahead and create folders inside it

11953.3 -> or I can directly upload data.

11955.1 -> So I say upload select a file.

11957.1 -> Let's just randomly select this file.

11959.395 -> It is Van Dusen founder of python.

11961.5 -> Basically, let's just say next.

11963.6 -> Next next and the data is uploaded guys.

11967.6 -> You can see the data

11969.3 -> being uploaded and my file is here for usage.

11971.974 -> So guys, this is how object and bucket kind of stuff works.

11975.5 -> You can see that this is the data that I have

11977.8 -> if I click on it, I would get all the information.

11980.3 -> What is the key?

11981.6 -> What is the version value for now?

11983.5 -> Let's not discuss version.

11984.828 -> But this is the key

11985.8 -> or the name of the file that I've uploaded.

11987.7 -> So it is fairly clear right guys.

11989.5 -> So let us just quickly switch back

11991.057 -> to the presentation and discuss some other stuff as well.

11993.7 -> Well now guys another important topic

11996.2 -> that is to be discussed here is S3 storage classes.

11999.8 -> Now, we've discussed

12001.115 -> how the data is stored or how buckets and objects work

12004.6 -> but apart from that we need to discuss

12006.7 -> some other pointers as well as in how does AWS charge me

12010.05 -> or what kind of options do I have

12012 -> when it comes to storing this data.

12013.813 -> So it provides you with three options guys

12016 -> standard infrequent and Glacier.

12018.7 -> Let me quickly give you an explanation to

12020.7 -> what do these storage classes mean and what all this?

12023.7 -> Offer to us when I say standard it is the standard storage

12027.48 -> which gives you low latency.

12029.189 -> So in case

12029.8 -> if there is some data that needs to be refreshed right away,

12033.2 -> you can actually go ahead and use standard storage

12036.082 -> say for example,

12037.001 -> I wish to go to a hospital for certain kind of checkup.

12040.1 -> So in that case my details would be entered in and the fact

12043.647 -> that I am getting myself checked in a hospital

12046.353 -> or diagnosed in the hospital.

12048.101 -> What happens is

12049.007 -> this data is important and if it is needed right away,

12052.21 -> it should be available.

12053.4 -> So this kind of data can be stored in your standard storage

12056.3 -> where the latency is very less the next we have

12059.6 -> in frequent access.

12060.856 -> Now, what do I mean by that now in this case

12063.7 -> my latency period has to be low

12065.657 -> because I'm talking about data that I

12067.967 -> would actually need any time

12069.745 -> if I want to but when I store this data

12072.213 -> for a little longer duration,

12073.995 -> all I want is this data to be retrieved quickly say,

12077.243 -> for example, I get a particular report

12079.6 -> or a particular test done.

12081.506 -> So in that case I Actually go ahead

12084.2 -> and submit my details or say for example,

12086.591 -> my blood samples,

12087.607 -> but I need this information maybe after three days.

12090.548 -> So what happens is in this scenario,

12092.582 -> I would want to store this data for a longer term,

12095.464 -> but the retrieval should be faster here in the first case

12098.527 -> that was not the case if I needed that data right away,

12101.465 -> and if I wanted it to be stored for a very short duration,

12104.486 -> I would use standard.

12105.602 -> But if I want to store it for a longer duration,

12108.1 -> and I want a quick retrieval in that case,

12110.5 -> I would be using in frequent access

12112.5 -> and finally I Glacier we have already discussed this here.

12116.078 -> Your retrieval speed is low

12117.744 -> and the data needs to be put in for a longer duration.

12121.016 -> And that is why it is more affordable.

12123.3 -> If you take a look at the stats

12125.1 -> that are there in the image above you can see

12127.6 -> that minimum storage duration is nothing

12130.2 -> for standard for infrequent.

12132.132 -> It is 30 days and for Glacier it is 90 days.

12135.1 -> If you take a look at latency,

12136.864 -> it is milliseconds milliseconds and four hours.

12139.5 -> So that itself explains a lot of stuff here.

12142.3 -> So what art This classes and what do they do?

12145.068 -> I believe some ideas clear to you people again

12147.9 -> as we move into the demo part,

12149.485 -> we would be discussing this part as well.

12151.6 -> And we would also discuss expiration and transition

12154.877 -> that supports these terms but let us move

12157.5 -> further and try to understand

12159 -> something else first versioning and cross

12162.2 -> region replication now guys

12164.095 -> when I say virginie,

12165.5 -> I'm actually talking

12166.5 -> about keeping multiple copies of my data now,

12169.7 -> why do I need versioning?

12171.4 -> And why do I need multiple copies?

12173.42 -> He's of my data.

12174.4 -> I've already mentioned

12175.6 -> that AWS S3 is highly durable and secure.

12179 -> How is that because you can fix the errors that are there

12181.8 -> and you can also have multiple copies of your data.

12184.043 -> You can replicate your data.

12185.3 -> So in case

12186.1 -> if your data center goes down a copy of it is mentioned

12189.6 -> or maintained somewhere else as well.

12192.087 -> How is this done

12193.235 -> by creating multiple versions of your data say for example,

12197.286 -> an image, I store it in my S3 bucket.

12199.8 -> What happens here is there is key the name is same image.

12203.6 -> And virgin is some 3 3 3 3 3 right now take a look

12207.3 -> at the other image.

12208.504 -> If I actually go ahead

12209.9 -> and create a copy of the first image its name would remain same

12213.937 -> but it's version would be different.

12216.181 -> So suppose both of these images.

12218.122 -> They reside in one bucket.

12219.7 -> What these images are doing is they are having

12222.347 -> multiple copies are giving me multiple copies now

12225.2 -> in case of image not a lot would change

12227.567 -> but if I have doc files or data files

12229.7 -> in that case versioning becomes very important

12232.2 -> because if I make changes Changes to particular data

12234.9 -> if I delete a particular file a backup should always be there

12238.1 -> with me and this is

12239.246 -> where versioning becomes very very important.

12242 -> What are the features of versioning by default poisoning

12244.95 -> is disabled when you say or when you talk about S3,

12247.6 -> you have to go ahead and enable this versioning

12249.942 -> it prevents over writing or accidental deletion.

12252.292 -> We've already discussed

12253.5 -> that you get non-concurrent version by specifying

12256.4 -> version ID as well.

12257.555 -> What do I mean by this?

12258.944 -> That means if I actually go ahead

12260.717 -> and create one more copy of the data and store it.

12263.6 -> So the latest copy would be available on top

12266.283 -> but I can go to the virgin's option put in the ID

12269.377 -> that belong to the previous version and I can fetch

12272.6 -> that version as well.

12274.1 -> So what is cross reason replication now guys,

12277.1 -> we've discussed versioning.

12278.8 -> Let us talk about another important topic that is

12281.3 -> cross region replication.

12282.8 -> Now when you talk about S3,

12284.5 -> basically what happens is you create a bucket in a region

12287.2 -> and you store data in that region,

12288.9 -> but what if I want to move my data from one region

12291.848 -> or from one bucket in The region to other bucket in other region,

12295.7 -> can we do that?

12296.8 -> Yes cross reason replications let you do that.

12300.1 -> So what you do is you basically go ahead

12302.186 -> and create a bucket in one region you create

12304.487 -> another bucket in another region

12306.2 -> and probably you give access

12307.904 -> to the first bucket to move data from itself to the other bucket.

12311.8 -> So this was about versioning.

12313.5 -> This was about cross region replication

12315.936 -> and I believe you've also talked about storage classes.

12319.4 -> Let me quickly switch into the demo part

12321.5 -> and discuss these topics too little He did so

12324.5 -> guys moving back.

12325.6 -> What we have done is we've actually gone

12327.599 -> ahead and created a bucket already right

12329.6 -> when you talk about what was the name of the pocket.

12332.2 -> It was removes if I'm not wrong.

12334.1 -> Yep.

12334.9 -> So if you click on the bucket name removes

12337.745 -> what it does is it basically shows you these details guys.

12342.046 -> Now you can see

12343.1 -> that your versioning is disabled, right?

12345.942 -> So if I click on it,

12347.4 -> I can actually come to this page and I can say enable virginie.

12351.1 -> That means a copy of the data.

12353.303 -> That I create is always maintained.

12355.9 -> So if I go to the most bucket,

12358.5 -> or I just move back get this interface

12361.6 -> can be a little irritating at times you have to move back

12364.895 -> and forth every now and then so guys there is a file

12367.864 -> which we have stored.

12369.1 -> You can just take a look at this date first.

12371.3 -> It says that it is 235 that was the time

12374.6 -> when the object was moved.

12376.8 -> Let me just say that upload the same file.

12381 -> This was the file will be uploaded as

12383.5 -> in next next next upload.

12387.4 -> So where is this file is getting uploaded.

12389.8 -> You can see the name of the file is still same.

12392.9 -> We have only one file here.

12394.896 -> Why because it was recently modified at 2:45

12398.5 -> from to 25 to 35.

12400.3 -> It got changed to 245.

12402.1 -> So it is fairly clear guys.

12403.45 -> What is happening here?

12404.7 -> Your data is getting modified.

12406.8 -> And if you wonder as in

12408 -> what happened to the previous version, don't worry.

12410.5 -> If you click on this show option,

12412.3 -> you can see that both

12413.682 -> of your virgins are still here guys.

12415.986 -> This was created to 30.

12417.5 -> And at 2:45.

12419.046 -> So this way data replication

12421.2 -> and data security works much better.

12423.9 -> So you can secure your data.

12425.3 -> You can replicate your data.

12426.7 -> So in case if you lose your data,

12428.2 -> you always have the previous versions to deal

12430.5 -> with how does the previous version thing works so

12433.6 -> as what happens is if I delete this file

12436.4 -> what Amazon S3 would do is it would set a marker

12439.4 -> on top of this file.

12440.7 -> And once I delete it

12442.7 -> if I search for that ID that ID won't be available.

12445.938 -> Why because the our car has switched to the next ID now.

12449.5 -> So whatever I want to do I can do with the next ID as well.

12453.3 -> So there is one more thing

12454.6 -> that you also need to understand here is

12456.514 -> what happens to the file.

12457.75 -> I mean, I've actually deleted a file but a virgin is there

12460.8 -> with me can I delete all the versions?

12463.112 -> Yes, you can specify the ID

12464.8 -> and you can delete all the versions that you want.

12467.7 -> You can also do one thing

12469.316 -> that is you can set a particular life cycle for your files

12473 -> when I say life cycle you can decide as an okay now.

12476.1 -> I have a file instead.

12477.367 -> That storage we've discussed.

12479.073 -> This storage is Right standard storage infrequent and Glacier

12482.3 -> what you can do with your life cycle management

12484.734 -> is you can decide as an okay for a particular time duration.

12487.905 -> I want this file to stay in standard maybe after a while.

12491.2 -> I want to move it to infrequent and after a while.

12493.881 -> I want to move to Glacier say for example,

12496.005 -> there is certain data,

12497.15 -> which was very important for me but having used that data,

12500.315 -> I don't want to use it for next few months.

12502.591 -> So in that case I can move

12504 -> to the substitutes or to the other storage classes.

12507.232 -> We're probably I won't be needing to use that data

12510.297 -> for a long while and doing that.

12512.3 -> I won't be paying for this data

12513.9 -> as I used to pay for the standard

12515.541 -> because standard is the costliest of the three.

12517.9 -> So let us quickly.

12519.089 -> See can we do that or how does it work?

12521.6 -> At least if I just go back?

12524.634 -> This is my file.

12526 -> I can actually just go ahead and switch to management in that.

12529.3 -> I have the option of life cycle if I click here.

12533 -> There is no life cycle add a life cycle.

12535.5 -> You can add a lifecycle rule as well.

12537.5 -> This new let me call it new and let me say next it asks me.

12541.7 -> What do I want to do?

12543 -> You can add rules in life cycle configuration

12545.2 -> to tell Amazon S3 to transition objects

12547.3 -> to another storage class.

12548.9 -> There are three requests fees

12550.7 -> when using lifecycle to transition data

12553.3 -> to any other S3 or sa Glacier storage.

12556.8 -> So which version do I wish to use current?

12559.953 -> I can say yes a transition

12562.55 -> and I can select transition to this tear

12565.9 -> when after 30 days.

12567.297 -> Days, and if I say next it would agree expiration.

12570.9 -> You can select other policies as well.

12573 -> So guys when I say transition first thing

12575.4 -> what it does is it tells me what time to transition

12578.8 -> to which storage class and expiration.

12581.498 -> It tells me when does this expire so I can decide

12585 -> when to clean up the objects and when not to let's not do

12587.8 -> that for now.

12588.3 -> Let's just say next next so guys

12591.1 -> what will happen here is after 30 days my data would move

12594.3 -> to a standard one a storage

12596.1 -> so you can actually go Then decide

12597.75 -> whether you want to move to Glacier in that drop-down

12600.35 -> you had more options as well.

12601.682 -> I did not do that, but it is pretty understandable.

12604.282 -> You can move to Glacier as well.

12605.8 -> So this is about life cycle guys.

12607.7 -> One more thing.

12608.6 -> You have something called as

12610 -> replication you can add replication as well.

12613 -> If you wish to replicate your data cross reason replication.

12616.9 -> I believe guys,

12617.7 -> I do not have access to do

12619.056 -> that because I'm using someone else's account for now,

12621.706 -> but let me just give you some idea as

12623.5 -> to what you can do to replicate your data.

12625.385 -> You can just go ahead and click on get started.

12627.5 -> Dated so replication to remind you people it is

12629.964 -> nothing but a process

12631.199 -> of moving data from bucket

12632.646 -> in one region to add the bucket in some other region.

12635.5 -> So for that I need to select the source bucket.

12638.087 -> So let us just say

12639.1 -> that this is the bucket that I have next now guys in my case.

12643.4 -> I haven't created the second bucket.

12645.7 -> What you can do is you can just go ahead

12647.6 -> and create one more bucket.

12649.4 -> Once you create the bucket you can select

12651.568 -> the destination bucket for now.

12653.391 -> Let us just say that this is a bucket

12655.249 -> that has been created by someone else.

12657.2 -> I'm not gonna transfer data are but let's just select this

12660.3 -> for the demo sick.

12661.5 -> This is the bucket that I have see it says

12663.711 -> that bucket does not have versioning enabled.

12666.333 -> This is very important Point guys.

12668.3 -> I showed you how to enable versioning right?

12670.8 -> If you select the bucket there

12672.099 -> is an option on the right side saying virginie,

12674.4 -> you can actually go ahead and enable versioning there.

12677.5 -> So once you enable versioning you would be able

12680.967 -> to use this bucket.

12682.4 -> Do you want to change the storage class

12684.6 -> for the replicated objects

12686.026 -> if you say yes it Would give you the option of selecting.

12688.9 -> What storage class do you want to select right?

12691.2 -> If you don't you don't have to you can say next you have

12694.866 -> to enter an IM role.

12696.2 -> If you do not have any you just say create a roll

12699.4 -> and then the rule name in this case.

12702.1 -> I do not have any details

12703.3 -> about this and I don't want to create a role

12705.2 -> because this account does not belong to me.

12707.3 -> Sorry for that inconvenience,

12709.2 -> but you can actually go ahead and select create a role

12712.3 -> in just say next and I'm sure

12714.3 -> that you can actually go ahead and your bucket starts.

12717.5 -> Audio our cross reason replication starts working.

12720.5 -> What happens after that is

12722.076 -> once you store your object in a particular file,

12724.841 -> you can actually move

12726.024 -> that object not in a particular file in a particular bucket.

12729.109 -> You can move the data from that bucket

12731.305 -> to the other bucket and a copy of your data is maintained

12734.6 -> in both the buckets

12735.787 -> that you use.

12736.557 -> So this is what cross region replication is guys.

12739.4 -> I believe that we have discussed

12740.9 -> what our storage classes we have discussed.

12743.04 -> What is cross region replication and we've discussed versioning

12746.2 -> in general let Let's quickly move back

12748.293 -> to the presentation

12749.411 -> and discuss the remaining topics as well.

12751.7 -> So guys have switched into the presentation part

12754.4 -> till time we've discussed

12755.8 -> how cross region replication Works we've discussed

12758.682 -> how versioning works and we have seen

12761 -> how to carry out that process.

12762.9 -> The other important topic

12764.385 -> that we need to focus on is we've know like

12766.703 -> how to create versions

12767.97 -> how to move data from one place to the other but the thing is

12771.524 -> what if I have to move data from a particular location

12774.857 -> to a location that is very far away from me.

12777.4 -> And still ensure

12778.6 -> that there is not too much latency in it.

12780.956 -> Because if you're moving data from one location to location

12784.368 -> that is far away from you.

12785.8 -> It is understandable

12786.9 -> that it would take a longer while why

12788.967 -> because we are moving data from internet.

12791.137 -> So the amount of data

12792.277 -> that you move and the further you move it should take

12795.1 -> a longer while for that.

12796.4 -> So how do you solve that problem?

12798.1 -> You have S3 transfer acceleration.

12800.3 -> You can do that by using other services as well.

12803 -> We discussed snowball and snowmobile as well,

12805.755 -> but they physically move.

12807.282 -> The data and at times it takes a number

12809.521 -> of days to move your data with S3 transfer acceleration

12813.118 -> that is not the issue

12814.4 -> because it moves at data at a very fast pace.

12817.7 -> So that is a good thing.

12819.5 -> So, how can you move your data at a faster Pace by using

12822.6 -> S3 transfer acceleration?

12824.4 -> Okay, let us first understand what it is exactly.

12827.446 -> So what it does is it enables fast easy

12829.745 -> and secure transfers of files

12831.554 -> or long distances between your client

12833.8 -> and S3 bucket and to do that.

12835.807 -> It uses a service call.

12837.4 -> Cloudfront and the S locations it provides you

12841.3 -> as I move further

12842.3 -> I would be talking about what cloudfront

12844.1 -> is do not worry about it first.

12845.707 -> Let us take a look at this diagram.

12847.431 -> So normally if you are moving your data

12849.437 -> or directly uploading your data to a bucket that is located

12852.5 -> at a far away distance.

12853.903 -> I mean suppose I'm a customer and I wish to put my data

12857.3 -> into an S3 bucket,

12858.434 -> which is located maybe a continent away from me.

12861.4 -> So using internet it might take a longer while instead.

12865.064 -> What I can do is I can use transfer.

12867.222 -> Generation.

12867.912 -> So how is it different now guys,

12869.993 -> there is a service called as AWS Cloud front what it does.

12873.597 -> Is it basically lets you cash your data

12876 -> when I say cash or data

12877.445 -> that means you can store your data at a location

12880.275 -> that is in the interim

12881.6 -> or that is close to your destination.

12883.9 -> Now this service is basically used to ensure

12886.4 -> that data retrieval is faster suppose.

12888.665 -> I'm searching for a particular URL.

12890.721 -> What happens is when I type

12892.34 -> that URL request is sent to the server it fetches the data

12895.835 -> and sends it to me.

12897 -> So If it is located at a very far location,

12899.6 -> it might take long while for me to fetch the data.

12902.2 -> So what people do is they analyzed as in

12904.594 -> how much requests are coming from a particular location

12907.567 -> and if there are frequent and a lot of requests

12910.273 -> what they do is they set up an age location

12912.6 -> close to that particular region.

12914.574 -> So you can put your data you can cash a data

12917.296 -> on that is location

12918.5 -> and the data can be fetched

12920.42 -> from that is location at a faster rate.

12923.069 -> So this is how is locations work

12925.3 -> what transfer acceleration does is it basically puts

12928.4 -> in your data at the edge location

12930.5 -> so that it can be moved

12932.244 -> to your S3 bucket at a quicker pace.

12934.816 -> And that is why it is fast.

12936.8 -> So guys this was about S3 data acceleration.

12939.6 -> Let us quickly move

12940.629 -> into the console part and try to understand

12943.1 -> how S3 acceleration works.

12945.2 -> So guys have switched into the console S3 acceleration

12948.419 -> or data transfer acceleration is very easy thing to do.

12951.7 -> I do not remember the bucket name.

12953.273 -> I think it was Ram or something.

12954.8 -> Okay, if I select this and open it I actually go

12958 -> to the Properties part less.

12960.9 -> There are other things that you might want to consider.

12963.102 -> You can come here and take a look at those as well for now.

12965.586 -> I'm just going to say go ahead and enable

12967.3 -> transfer acceleration.

12969.934 -> It is suspended.

12971.2 -> I can enable it it gives me the endpoint as well

12973.9 -> and I say save So guys what this means is

12977.5 -> if I'm putting my data into this bucket,

12980.1 -> it would be transferred very quickly

12982.106 -> or I can use this bucket to transfer my bit data

12984.8 -> at a quicker Pace by using data transfer acceleration

12988.6 -> by S3 again guys.

12989.9 -> I missed out on one important point the fact

12992.3 -> that we have been talking about buckets and stuff like that.

12995.25 -> There is something important

12996.6 -> that I would like to show to you people first.

12999.1 -> Let us just go back and disable this part.

13002.073 -> I do not want it to have the transfer acceleration.

13005.8 -> Going and I just wanted to show it to you people how it is done.

13009.3 -> I just say go back to suspended and one more thing guys,

13012.935 -> if you once you actually unable the transfer part and

13015.994 -> if you upload a file,

13017.091 -> you can see the difference in the speed.

13019.076 -> The problem is you need a third party tool to do that.

13021.774 -> So you can actually go ahead

13023.2 -> and download a third-party tool as well and using

13025.6 -> that you can actually go ahead and see how it works.

13028.2 -> Having said that I was talking about buckets in general.

13031.3 -> So let us just go back and go to removes again.

13034.3 -> There you go.

13035.6 -> And I'm going to copy the a RN.

13037.533 -> I'll tell you why I've copied the iron now

13040.591 -> when I open this bucket guys,

13042.7 -> we have quite a few things permissions.

13044.6 -> I talked about security,

13045.8 -> right so you can decide Public Access as in

13048.375 -> who gets to access your bucket.

13050.2 -> So guys, you can actually go ahead and decide

13052.188 -> who gets to access what kind of buckets say,

13054.249 -> for example here in your blog Public Access.

13056.439 -> You can decide

13057.284 -> who gets to access what data publicly for

13059.7 -> that you have access control lists using these ACLS.

13063.6 -> You can actually decide who gets to How other thing you can do is

13067.1 -> you can just go ahead and create a bucket policy and decide

13070.054 -> who gets to access your bucket or who gets to put your data

13073.009 -> or delete your data and do all these things.

13075.159 -> Let us just go ahead and create a policy.

13077.179 -> Now, you can write your own policy or you

13079.179 -> can just use a policy generator

13080.8 -> which again is a third party tool.

13082.7 -> So I want to create a bucket policy forum is 3 so,

13085.745 -> let's just say S3 bucket policy and what kind of effect I want.

13089.897 -> I mean do I want someone to access my system

13092.5 -> or do I want to deny someone from accessing my system I can.

13095.9 -> Decide that so let's for now just say

13098.1 -> that I want to deny someone from doing something

13100.7 -> and what I wanted someone to do is to deny a particular thing

13104.1 -> for that person for all the objects.

13105.9 -> I mean, I do not want that person to access any

13108.23 -> of the objects that is there.

13109.7 -> So what I say is star

13111.3 -> that means nobody should able to do anything

13114.4 -> to any of the objects that are there in this bucket.

13117.2 -> So it says star service Amazon S3 what action I want.

13121.4 -> I want to prevent someone from deleting an object they go

13124.9 -> and This is the AR n that is why I copied it.

13128.2 -> It should be followed by a forward slash

13130.8 -> and a star add a statement and Ice Age ended policy.

13135.6 -> So guys the policy has been generated.

13137.776 -> I just have to copy it

13139.072 -> if I copy this thing and I go back to the console

13142.007 -> if I paste it here

13143.8 -> I can say save It saved I'll save it

13148.207 -> again just to be safe.

13149.9 -> So guys we have actually gone ahead and let me just go ahead

13154 -> and again go to ramose.

13156.4 -> So there's not there is an object here.

13158.2 -> Let me just try and delete this object.

13160.8 -> If I just go to the actions part here

13163.6 -> and I say delete see the file is still here.

13168.4 -> Is it the other version?

13169.8 -> No, it's not deleted.

13170.961 -> See there's an error here.

13172.4 -> If I click on it.

13173.452 -> It says hundred percent field why access denied

13176.3 -> because I do not have the access to delete the object right now.

13180 -> Why because I've created a bucket policy guys.

13182.737 -> So that is what bucket policies an AC else do the Let

13185.834 -> you make your objects or your data more secure.

13188.573 -> And as you saw in the option,

13190.3 -> there are quite a few options that you have at your disposal,

13193.3 -> which you can choose from which you can mix

13195.2 -> and match and decide as an look at this is

13197.4 -> what I want to do.

13198.3 -> I want to probably give someone an access to delete a bucket.

13201.3 -> I want to give someone an access to do this or do that.

13204.1 -> So, where's this was about S3 data transfer acceleration,

13207.683 -> and we've also seen

13208.9 -> how you create a bucket policy how you attach it to your bucket

13212.329 -> and stuff like that now,

13213.8 -> let me just go back and kind of Shove this session

13216.8 -> or finish this session up with a use case

13219.4 -> so that you can probably understand the topics

13221.875 -> that we've discussed a little more first.

13224.075 -> Let us go back to the use case guys.

13226.2 -> So guys have switched into my presentation console again,

13229.1 -> and we would be discussing IMDb media now for people

13233.1 -> who watch movies.

13234.9 -> They might know what IMDb is it is a website

13237.987 -> that gives you details about movies.

13240.5 -> They tell you what are the movies that are nice

13243.5 -> if you probably select or type a particular He

13245.8 -> named they would give you details about it as a whole

13248.3 -> where the actors how was the movie

13250.326 -> how was the review a short snippet explaining you what

13253.1 -> the movie is about its genre and stuff like that.

13255.5 -> Plus they have their own ratings to kind of gauge

13257.9 -> in the customers even better as an IMDb being a popular site

13261 -> and when they say

13261.922 -> that this movie is this person good or like

13264.189 -> by these many people people normally believe it

13266.672 -> so they have that score as well.

13268.4 -> So if you talk about a website that basically deals

13271.464 -> with movies you understand the number of movies

13274.274 -> that are released worldwide.

13275.943 -> And if most of them are present here on IMDb,

13278.534 -> that means that database is huge but we are talking about data

13282.2 -> that is being processed in great numbers great amounts.

13285.2 -> I mean when you talk about the data that is here.

13287.793 -> What is happening here is you have n number of movies

13290.658 -> that are being released.

13292.07 -> So if someone searches for a particular movie,

13294.549 -> it has to go through the database and the data has

13297.247 -> to be fresh to him right away.

13298.9 -> So how do you deal with the latency issue?

13301.4 -> Well, this would answer a lot of questions

13303.349 -> or it would sum up lot of topics that we've discussed.

13306 -> Here let us go through this use case probably.

13308.6 -> So what happens here is in order to get

13310.8 -> the lowest possible latency all the possible results

13314.1 -> for a search our pre-calculated

13315.923 -> with a document

13316.8 -> for every combination of letters in the search

13319.5 -> what this means is probably based on the letters.

13322.8 -> You have a document

13324.019 -> that is created and it is traversed in such order

13327.1 -> that all the data is scanned letter wise

13329.8 -> when you actually go ahead and put forth a query

13332.588 -> what happens is suppose

13333.941 -> if there is a 20 character Or a word that you put

13337.1 -> in so there are somewhere around twenty three two,

13339.673 -> one zero three zero combinations that are possible.

13342.3 -> So your computer has to go through these many combinations.

13345.5 -> What S3 does is it

13346.816 -> basically lets you store the data that I am DB has

13350.4 -> and once IMDb has told that data they use cloudfront again,

13354.1 -> we have discussed.

13355.072 -> What cloudfront is they use cloudfront to store this data

13358.1 -> to the nearest possible location so that

13360.586 -> when a user fetches this data,

13362.5 -> it is Fest from that location.

13364.432 -> So what happens is Basically,

13366.3 -> when these many possibilities are combinations are to be dealt

13369.2 -> with it becomes complicated but in practice

13372 -> what IMDb does is it basically uses analytics in such a way

13376.212 -> that these combinations become lesser?

13378.883 -> So in order to search

13380.4 -> for a 20 character letter they basically have to go

13383.2 -> through one five zero zero zero zero documents

13386.4 -> and because of S3

13387.7 -> and cloudfront you basically

13389.581 -> can distribute all the data to different Edge locations

13393.231 -> and two buckets with in as And since we're talking

13396.914 -> about huge amount of data,

13398.557 -> it is more than terabytes.

13400.2 -> It is like hundreds thousands of terabytes of data

13403 -> so we can understand

13404.282 -> how much data are we talking about and S3 actually features

13408 -> or serves a number of such use cases or requirements.

13412 -> So as I Believe by now,

13413.684 -> you've understood what S3 is let me give you a quick sum

13417.606 -> up or a quick walkthrough as to what we've studied

13421.1 -> because we've talked about a lot

13423 -> of topics guys first we started with the basic.

13425.838 -> Six of different storage Services we

13428 -> were understood sorceresses like EFS EBS storage Gateway.

13432 -> We've talked about Glacier.

13433.687 -> We've talked about snowmobile snowball

13436 -> and then we move to S 3 S 3 we talked about buckets.

13439.08 -> We talked about objects.

13440.5 -> We talked about versioning

13441.9 -> we understood why versioning is needed

13443.873 -> so that we can basically replicate our data prevent it

13446.7 -> from deletion prevent it from corruption.

13449.1 -> We also talked about across region replication

13451.702 -> where you can move data from one region

13453.9 -> to the other we talked about

13455.6 -> how we can Move data Faster by using

13457.97 -> S3 data transfer acceleration.

13460 -> And then we also took a look

13461.767 -> at the basics like what are the storage classes?

13464.855 -> What are the bucket policies

13466.634 -> how to create bucket policies

13468.539 -> and we also discussed an important topic called

13471.6 -> as transition and expiration

13473.438 -> where if your data expires it is deleted

13476 -> if your data needs to be transferred

13478.154 -> to different stages you can do that as well.

13480.8 -> So all these topics are discussed and we also discussed

13483.8 -> some important features

13485.2 -> and finally We finish this session up with a use case.

13493.3 -> So networking domain basically offers three kind

13496.365 -> of services the VPC Direct Connect and out 53.

13499.3 -> Let's discuss each.

13500.394 -> One of them.

13501.1 -> So vbc is a virtual private Cloud.

13504 -> So it's a virtual network.

13505.694 -> If you include your all your air pollution sources

13508.774 -> that have launched inside one VPC then

13511.1 -> all these resources become visible to each other

13513.896 -> or can interact with each other.

13515.9 -> Mine said inside the VPC now the other use for PPC is

13520.3 -> that when you have a private Data Center

13522.7 -> and you are using AWS infrastructure as well

13525.231 -> and you want your AWS resources to be to be used

13528 -> as if they were on your own network in that case,

13530.823 -> you will establish a virtual private Network

13533.197 -> that is a VPN connection to your virtual private cloud

13536.5 -> in which have included all the services

13538.4 -> that you want in on your private Network.

13541.085 -> You will connect a private Network

13543.24 -> through the V PC using the VPN

13545.124 -> and then you You can access all your AWS resources

13548.2 -> as if they were on your own network.

13550.324 -> And that is what we see is all about.

13552.596 -> It provides you security it makes communication

13555.8 -> between the AWS Services easy

13558.2 -> and it also helps you connect your private data center

13561.3 -> to the AWS infrastructure.

13563.085 -> So guys, this is what VPC is all about.

13566.108 -> Let's go ahead on to our next service,

13569 -> which is Direct Connect so Direct Connect is a replacement

13573.2 -> to an internet connection.

13574.5 -> It is a leased line.

13575.889 -> A direct line to the AWS infrastructure.

13578.6 -> So if you feel

13579.7 -> that the bandwidth of internet is not enough

13582.359 -> for your data requirements or your networking requirements.

13585.839 -> You can take at least line to the AWS infrastructure

13588.9 -> in the form of the direct connect service.

13591.086 -> So instead of using

13592.1 -> the internet you would now use the direct connect service

13594.8 -> for your data stream to flow

13596.46 -> between your own data center to the illness infrastructure.

13599.9 -> And that is what Direct Connect is all about.

13602.1 -> Nothing much further to explain.

13603.7 -> Let's move on to a next service which is is Route 53 be

13607.34 -> so Route 53 is a domain name system.

13609.7 -> So what is the domain name system, basically,

13612 -> whatever URL you enter has to be directed

13614.4 -> to a domain name system

13615.759 -> which converts the URL to up IP address.

13617.9 -> The IP address is

13618.807 -> of the server on which your website is being hosted.

13621.523 -> The weight functions is like this you buy a domain name

13624.5 -> and the only setting

13625.6 -> that you can do in that domain name

13627.1 -> or the setting which is required

13628.7 -> in that domain name are the name servers right.

13631.184 -> Now.

13631.4 -> These name servers are provided to you by Route

13633.909 -> 53 these name servers that are To provide you are to be entered

13637.856 -> in the settings of that domain name.

13639.7 -> So whenever user points to that URL,

13641.758 -> he will be pointed

13642.715 -> to Route 53 the work in the domain name settings is done.

13645.696 -> You have to configure the Route 53.

13647.696 -> Now another your request has reached out 53.

13650.1 -> It has to be pointed

13651.1 -> to the server on which your website is hosted.

13653.5 -> So on a Route 53 now you have to enter the IP address

13657.074 -> or the Alias of the instance

13659 -> on of to which you want your traffic to be directed to

13662.1 -> so you peed in the IP address or you feel in the Alias

13665.3 -> and It's done.

13666.189 -> You're the loop is now complete your url will now get pointed

13670 -> to Route 53 and Route 53 in turn will point to the instance

13673.8 -> on which your application

13675.211 -> or website is being hosted.

13676.8 -> So this is the role which Route 53 plays.

13679.1 -> It's a domain name system.

13680.5 -> So it basically redirects your traffic from your url

13683.9 -> to the IP address of the server on which an application

13687.428 -> or website is hosted.

13688.8 -> Alright guys, so we're done with the networking domain.

13696.5 -> In today's session we would be understanding

13698.8 -> what AWS Cloud front is

13700.6 -> but before we do go ahead and understand

13702.674 -> what cloudfront exactly is.

13704.262 -> Let's start by taking a look

13705.797 -> at today's agenda first first and foremost.

13708.7 -> I would be talking about what AWS exactly is good.

13712 -> Also understand.

13712.984 -> Why do we need it abuse cloudfront

13714.911 -> and what it is exactly the never talked about

13718.002 -> how content gets delivered using Amazon cloudfront

13721 -> and what are its applications?

13722.9 -> Finally, I would finish things off with the demo part

13725.4 -> where I would be talking about AWS Cloud turn

13727.8 -> distributions having said

13733.7 -> that let's not waste any time

13735.2 -> and jump into the first topic of discussion

13737.3 -> that has what is AWS.

13739.1 -> Will AWS stands for Amazon web services,

13742.4 -> which is a leading cloud service provider

13744.8 -> in the market and it has the highest market share

13747.3 -> when you talk about any cloud service provider.

13749.7 -> Now what Amazon web services does is it provides you

13752.5 -> with 70-plus services

13753.943 -> and these services are Growing the name some

13756.9 -> of these Services we have something called

13758.8 -> as your computation Services your storage

13760.8 -> Services your database services

13762.5 -> and all these services are made available to you through Cloud.

13765.9 -> That means you can rent all

13767.47 -> these services and pay only for the services

13770.116 -> that you use and only for the time duration

13772.638 -> you use these services for

13774.2 -> if you want to know more about how a database works exactly.

13777.242 -> I would suggest

13778.037 -> that you go through the videos that we have on YouTube.

13780.9 -> We have quite a few videos on YouTube with talk about AWS

13784.1 -> in particular all you have To do is you have to go

13786.584 -> to our YouTube channel

13787.7 -> and type a direct iaws and you'd be having all the videos

13790.8 -> that are related to AWS.

13792.2 -> But that is not the discussion for today.

13794.217 -> We are here to discuss what cloudfront is

13796.435 -> and I would like to stick to that.

13798.1 -> So coming back to cloudfront

13800.057 -> when you talk about AWS you have some Services now,

13803.4 -> what aw does is

13804.4 -> it offers you various infrastructure as services

13807.264 -> and even platform as Services now these services are made

13810.649 -> available to you in the form of infrastructures or platforms

13813.9 -> where you can actually go ahead and host.

13815.8 -> Applications or websites.

13817.7 -> So when you do go ahead and host these applications online

13821.2 -> what your cloud provider has to worry about is

13823.9 -> the way data is fetched

13825.346 -> because if you have a website online now

13827.8 -> that website would be visited by quite a few people

13830.7 -> and they would be requesting particular content

13833 -> or data, right?

13834.246 -> So in that case

13835.4 -> that data has to be made available to your customers.

13838.458 -> So how does it happen?

13839.767 -> Exactly and how does AWS make it happen to understand

13842.826 -> that consider the scenario suppose you You are

13846 -> a particular user

13847 -> in your trying to visit a particular website and imagine

13850.5 -> that that website is based somewhere

13852.8 -> at a very far location suppose.

13854.95 -> You are based somewhere in USA.

13857.1 -> And that website its server actually hosts

13860.992 -> or is based in Australia.

13863.1 -> Now in that case

13864.096 -> when you make a request for a particular object

13867.035 -> or particular image or maybe content now your request

13870.378 -> is sent to the server

13871.728 -> that is in Australia and then it gets delivered to you.

13875.5 -> In this process

13876.384 -> to there are quite a few interrelated networks

13878.9 -> that deal which you are not aware about the content

13881.7 -> directly gets delivered to you and you have a feeling

13884.3 -> where you feel

13885.152 -> that you type in a particular URL

13887.1 -> and the content is directly made available to you,

13889.55 -> but that is not how it works quite a few other things happen

13892.8 -> in the interim and due to that.

13894.411 -> What happens is the data that gets delivered to you.

13897.054 -> It does not get delivered to you very quickly.

13899.4 -> Why is that because you'd be sending

13901.204 -> in a request it would go to the original server.

13903.554 -> And from there.

13904.396 -> The content is delivered.

13905.8 -> To you now, if you are based in USA,

13908.4 -> the situation would be convenient if the data

13911.1 -> is delivered to you from somewhere close by now

13913.7 -> when you talk about a traditional system

13915.568 -> where you are sending a request to somewhere in Australia,

13918.3 -> this is what happens your data

13920.241 -> or your request is sent to the server based in Australia

13924 -> and then it processes that request and that data

13926.35 -> is made available to you which gets delivered to you.

13928.8 -> But if you have something like cloudfront

13931.2 -> what it does is it sets in an intermediate point where?

13935.507 -> Data actually gets cached first

13937.9 -> and this cache data is made available

13940.379 -> to you on your request.

13941.9 -> That means the delivery happens faster and you

13945.064 -> save a lot of time.

13946.342 -> So how does AWS Cloud front exactly do it?

13949.1 -> Let's try to understand that but when you talk about aw,

13952.675 -> cloudfront what it does is first and foremost,

13955.521 -> it speeds up the distribution process

13957.8 -> and you can have a any kind of content

13959.976 -> whether it's static

13961.094 -> or dynamic and it is made available to you quickly.

13963.9 -> What cloudfront does is it?

13965.62 -> It focuses on these three points one is your outing to is

13969.19 -> your Edge locations

13970.348 -> and three is the way the content is made available to you.

13973.822 -> Let's try to understand these one by one

13976.2 -> when you talk about routing.

13977.671 -> I just mentioned

13978.576 -> that the data gets delivered to you

13980.5 -> through a series of networks.

13982.5 -> So what cloudfront does is it ensures

13985.5 -> that there are quite a few Edge locations

13988.34 -> that are located close to you

13990.4 -> and the data that you want to access it gets cached

13993.4 -> so that it can be delivered to you quickly.

13995.9 -> And that is why the data

13997.218 -> that is being delivered to you is more available

13999.8 -> than in any other possible case.

14006.5 -> So what happens exactly

14007.715 -> and how does this content gets delivered to you?

14010.3 -> Let's try to understand this with the help

14012.2 -> of this diagram suppose.

14013.7 -> You are a user.

14014.9 -> So basically what you would do is you would send in a request

14018.1 -> that needs to reach a particular server.

14020.9 -> Now in this case

14022.078 -> what happens is first your request it goes

14025.2 -> to an edge location

14026.234 -> and from there to your server to understand this

14029.399 -> to you have to understand two scenarios first

14031.933 -> and foremost suppose you're based in USA

14034.3 -> and you want to fetch a particular day.

14036.638 -> That is based in Australia.

14038.375 -> You would be sending in a request.

14040.39 -> But what AWS does is instead

14042.1 -> of sending the request directly to your server,

14044.7 -> which is based in Australia.

14046.651 -> Maybe it has these interim as locations

14049.3 -> which are closer to you.

14050.768 -> So the request it goes

14052.114 -> to the edge location first and it checks

14054.5 -> whether the data

14055.3 -> that you are requesting is already cashed their or not.

14058.4 -> If it is not cached then

14059.921 -> the request is sent to your original server.

14062.6 -> And from there the data is delivered to the edge location

14066.022 -> and From there it comes to you.

14068 -> Now, you might wonder

14069.4 -> as an this is a very complex process and

14072.6 -> if it is taking these many steps.

14074.5 -> How is it getting delivered

14075.927 -> to me quicker than in normal situation.

14077.937 -> We'll think of it from this perspective.

14080 -> If you do send in this request directly

14082.235 -> to the main server again,

14083.6 -> the data would flow through some Network

14085.596 -> and then it would be delivered to you instead.

14087.9 -> What happens here is

14089.2 -> at your age location the data gets cached.

14091.77 -> So if you requested again,

14093.4 -> it would be delivered to you quicker

14095.15 -> if it is requested by anyone.

14096.6 -> It would be delivered to them quicker plus how

14099.4 -> as locations work is

14100.7 -> when you do send in this request

14102.7 -> and when there's

14103.5 -> location Fitch's this data from your so-called original server

14107.3 -> in that case 2 when the first bite it arrives

14109.8 -> at your age location,

14110.941 -> it directly gets delivered to you and how does this content

14113.953 -> exactly get stored here?

14115.228 -> Well, first and foremost what happens is

14117.3 -> what your age location has is it has some Regional cash as well.

14121.6 -> Now this cash would basically hold all the content

14124.836 -> that is requested more.

14126.41 -> More frequently in your region suppose

14128.859 -> a website has summon number of content and out of it.

14132.3 -> Some content is kind

14133.483 -> of requested a lot in a particular region.

14136.025 -> So surrounding that region.

14137.65 -> The closest is location would have a regional cash

14140.602 -> which would hold all the content

14142.529 -> that is more relevant for those users

14144.647 -> so that it can be frequently delivered to these users

14147.795 -> and can be made available to them quickly in case

14150.681 -> if this data gets outdated and it is no longer

14153.428 -> being requested then this data can be replaced with Guys

14156.785 -> that is requested more frequently.

14158.8 -> So this is how cloudfront work.

14160.9 -> What it does is it creates a distribution

14163.566 -> and you have some Edge locations

14165.7 -> through which you can actually request the data faster.

14173.3 -> So what are the applications

14174.805 -> that cloudfront has to offer to you now,

14177.113 -> I won't say applications instead.

14179 -> I would say some of the benefits of using cloudfront.

14182.1 -> Let's try to understand those one by one first and foremost

14185.4 -> what it does is it accelerates

14187.236 -> your static website content delivery.

14189.354 -> We just discussed that that means

14191.2 -> if you are requesting a particular image

14193.05 -> or something like that,

14194.2 -> it gets delivered to you quicker.

14196 -> Why because it is cashed at your age location

14198.482 -> and you do not have to worry about any latency issues.

14201.6 -> Next.

14202.4 -> What it does is it provides you various static

14205.3 -> and even Dynamic content suppose you need some video

14208.6 -> or a live session or something like that even

14211.1 -> that gets delivered to you quickly.

14213.033 -> I just mentioned

14213.974 -> that when you request a particular thing When

14216.459 -> the first bite it arrives at your age location

14219.111 -> your cloudfront starts streaming

14220.805 -> that to you our start delivering that to you same happens

14224.1 -> with the live streaming videos as well.

14226.3 -> You would be getting that streams instantly

14228.995 -> without any Latin see what server encryption now

14232.079 -> when you do access this content

14234.195 -> what AWS Cloud Trend does is it lets you have

14237.2 -> this so-called domain where you put in HTTP

14240.146 -> and you get secured data.

14241.9 -> So you already have one layer of security,

14244.316 -> but it also lets you add another.

14246.2 -> Layer of security by giving you something called as encryption

14249.3 -> by encrypting your data or by using your key value pairs,

14252.856 -> which is the same.

14253.8 -> You're actually ensuring that your data is more secured

14256.5 -> and it can be accessed privately as well customization

14259.4 -> at the age.

14260.1 -> Now.

14260.3 -> What do I mean by this now?

14261.701 -> There is some content

14262.792 -> that needs to be delivered to the user or to the end user

14265.7 -> if the customization it happens at the server again,

14269 -> it might be time consuming

14270.3 -> and there are quite a few drawbacks of it.

14272.423 -> Say for example,

14273.364 -> I need a particular content and it needs to be processed

14276.3 -> or Customized at the very last moment.

14278.5 -> So these things can be done at the age location as well.

14281.468 -> Thus helping you save time money

14283.158 -> and various other factors as well.

14285.1 -> And finally what it does is it uses something

14287.3 -> called as Lambda H

14288.405 -> which again lets you deal with various customizations

14291.589 -> and lets you serve your content privately.

14294.1 -> So these are some of the applications

14295.9 -> or uses of cloudfront.

14302.3 -> What I'm going to do now is I'm going to switch

14304.4 -> into my AWS console

14305.8 -> and I'm going to talk about AWS Cloud Trend distributions.

14308.7 -> And how can you go ahead and create one?

14310.618 -> So stay tuned and let me quickly switch

14312.662 -> into the console first.

14313.9 -> So yes guys,

14315.2 -> what I've done is I've gone ahead and I've logged

14317.6 -> into my AWS console.

14318.8 -> Now for people who are completely new to AWS.

14322 -> What you can do is you can actually go ahead

14324.3 -> and create a free tier account.

14326.2 -> You have to visit AWS website

14328 -> and search for free tier you would get this option.

14330.5 -> Just create an account.

14331.773 -> They would ask you for your credit

14333.6 -> or debit card details probably

14335.499 -> but And charge you a minimal amount is charged

14338.5 -> and that is reverted back to your account

14340.5 -> that is for verification purposes.

14342.3 -> And after that what aw is does is it offers

14344.485 -> you certain Services

14345.526 -> which are made available to you for free for one complete year

14348.7 -> that is as long as you stay in the limits

14351.4 -> or the specified limit switch AWS has set

14353.975 -> so those limits are more than enough to practice

14357 -> or to learn AWS.

14358.3 -> So if you want to do go ahead and get a proper hands on

14361.1 -> on various database Services,

14362.7 -> I would suggest

14363.45 -> that you do visit their website and create this free Terror.

14366.424 -> Count once you do have

14367.528 -> that account you have all these services

14369.478 -> that are made available to you as I just mentioned.

14371.9 -> There are 70 plus services and these are the services

14374.5 -> that are there

14375.2 -> which are can actually go ahead and use

14376.8 -> for different purposes our Focus today.

14378.9 -> However is creating a cloudfront distribution

14381.7 -> which we just discussed in the so-called theory part.

14385 -> I would be repeating few topics here to

14386.9 -> while we do go ahead and create our cloudfront distribution.

14390.3 -> Now as I've already mentioned we want to fetch data

14393.34 -> or fetch a particular object

14394.987 -> and if that is placed A particular Edge location

14398.18 -> that would be made available to me.

14400.2 -> So what we are doing here is imagine

14402.6 -> that our data is placed

14404.249 -> at a particular original server in our case.

14407.286 -> Let's consider it as an S3 bucket.

14409.523 -> Now S3 is nothing but a storage service

14412.136 -> with AWS that is simple storage service rather.

14415.3 -> That is SS and that is why we call it S 3

14418.5 -> so what we are going to do is we're going to go ahead

14420.8 -> and create an S3 bucket in

14422.533 -> that we would be putting in certain objects,

14425.4 -> and we'd Be accessing

14426.8 -> that by using our Cloud Trend distribution.

14429.4 -> So let's just go ahead and create a bucket

14431.8 -> first you can see we have S3 in my recently Used Services.

14435.3 -> You can just type S three-year

14436.7 -> and that would made available to you.

14438.5 -> You can click on it

14439.551 -> and your simple storage service opens.

14441.6 -> You would be required to go ahead and create a bucket.

14443.992 -> This is how you do it.

14445.092 -> You click on Create and you give it some name say

14447.7 -> maybe bucket use small letters bucket for AWS demo,

14452.1 -> maybe and I would given some number 0 0 0

14456.4 -> I see next next next I need a basic bucket.

14460.2 -> So I won't be putting in any details.

14462.9 -> Do we have a bucket here?

14464.7 -> There you go.

14466.2 -> We have a bucket here.

14467.7 -> And in this bucket,

14468.9 -> what I'm going to do is I'm going to put in some content

14471.4 -> that we can actually request for so let's just go ahead

14474.501 -> and create an HTML file and put in maybe an image or something.

14478.2 -> So I have a folder here in that folder.

14480.7 -> I have a logo of ADA Rekha, I would be using that logo

14484.6 -> and I would want to go ahead and create.

14486.5 -> Create an HTML file which I can refer.

14488.7 -> So I would open my Notepad

14490.629 -> and I would write a simple HTML code.

14493.7 -> I won't get into the details of how to write an HTML code.

14497.106 -> I assume that you all know it.

14498.9 -> If not, you can use this code.

14500.7 -> So let's create a head file basically or a head tag rather.

14506.2 -> Let's see a demo tag,

14508.4 -> maybe and I close this head tag.

14512.4 -> I need somebody in here, right?

14514.4 -> So let's say Did the body we say?

14523.196 -> Welcome to Eureka

14525.4 -> and I and the body here and I save this file and save as

14531.4 -> where do I want to save it?

14534.6 -> and see if it here and I would save it as

14536.8 -> a maybe index dot HTML.

14543.9 -> I save it probably got saved somewhere else.

14547.4 -> Let me just copy it and paste it here.

14551.1 -> I've done that.

14552.144 -> This is the file now.

14553.709 -> We have these files.

14555.2 -> Let's upload it to our S3 bucket.

14557.9 -> Come here.

14558.7 -> I say upload I want to add files.

14561.4 -> So add files.

14563.1 -> Where do I go?

14564.111 -> I go to the folder I go to demo and I select these two files

14568.472 -> and I say upload.

14569.7 -> There you go.

14570.5 -> My files are here

14571.6 -> and I say upload small files so should not take a long time

14576 -> fifty percent successful hundred percent successful.

14578.7 -> There you go.

14579.394 -> You have these Two files now,

14581.1 -> we have our S3 bucket and we have two files.

14583.868 -> This is our origin server.

14585.715 -> Now.

14586 -> I need to create a distribution and use it to do that.

14589.9 -> I would click on services

14591.4 -> and come here and I would search for cloudfront.

14594.455 -> There you go.

14596.1 -> And I say create a distribution.

14598.7 -> So I click on this icon.

14600.7 -> Now you have two options.

14602.7 -> First one is something

14604.134 -> that lets you have your static data moved in

14607.016 -> or moved out or if you want

14608.7 -> to live stream your data you should go for this option.

14611.7 -> But that is not the case.

14612.97 -> We would be sticking with this thing.

14615.057 -> I say get started.

14616.5 -> I need to enter in a domain name.

14618.5 -> So it gives me suggestions and this is the first one

14621.181 -> which I just created original path is something

14624 -> that you can give in father.

14625.4 -> A folders from where you want to access the data,

14627.8 -> but mind directly resides in the bucket.

14629.78 -> There are no extra folder.

14631.1 -> So I don't need to enter anything original ID.

14633.529 -> This is what I have here.

14635 -> Basically I can use this

14636.8 -> or I can just go ahead and change the name

14639.211 -> if I want to but I would let

14640.862 -> it stay the waiters restrict bucket access.

14643.832 -> Yes.

14644.57 -> I want to keep it private.

14646.1 -> So I say restrict and I create a new identity

14648.9 -> and the you I have a new user created here apart from

14652.58 -> that Grant read permissions on bucket.

14655.3 -> Update my bucket policy according this

14657.5 -> what I would say then I would scroll down customer headers

14661 -> and on I don't need to put in these details.

14663.8 -> How do I want my data to be accessed the protocol policy?

14667.764 -> I would say redirect is TTP to https,

14670.186 -> so that it is secured

14671.6 -> if I scroll down I have some other options as

14674.4 -> well cast STP methods and all those things.

14677.144 -> Do I need to change these object caching?

14679.7 -> Can I customize it?

14680.817 -> Yes, I can.

14681.464 -> But again, I would be using the by default one

14684 -> if you want to you can Is it smooth streaming?

14686.8 -> No, these are some of the things

14688.4 -> that you need to focus on if you have some streaming data,

14691.3 -> you can put in details accordingly,

14693.3 -> but we are not doing that.

14694.8 -> What is the price class that you want to choose?

14697.049 -> You have some options here which you can pick from I

14699.6 -> would be going for the default one and then I just scroll down

14703 -> and I say create a distribution.

14705.8 -> So your distribution is getting created now

14709.2 -> and this process might take a long while

14711.768 -> if you click on this thing you realize that.

14715.1 -> It is in progress

14716.1 -> and it takes somewhere around 10 to 12 minutes

14718.411 -> for this distribution to get created.

14720.511 -> So meanwhile, I'm going to pause this session

14723.1 -> and I would come back with the remaining part.

14725.912 -> Once this distribution is completed.

14728.1 -> So bear with me for that while so there you go.

14732.6 -> The distribution has been deployed.

14734.7 -> The status is deployed here

14736.3 -> so we can actually go ahead and use this thing.

14738.917 -> Now, we have a domain name here,

14740.8 -> which I can use and I can just enter it here

14743.666 -> and we would be redirected to the page.

14746.214 -> And what happens here is you would be actually given

14749.6 -> access to this page through the age location.

14752.1 -> That means you're not going to the server instead.

14754.4 -> The data has been cast away from your distribution

14756.7 -> or your eyes location other so

14758.218 -> you enter this website and you hit the enter button.

14760.9 -> As an error it shouldn't have been.

14763.7 -> Oh, I know what just happened.

14765.5 -> When you do go ahead and create your so-called distribution in

14769.3 -> that you actually have an option of selecting a by default file,

14773.6 -> which I did not so

14774.985 -> I will have to give an extension here saying slash index dot HTML

14781 -> and if I hit the enter button now,

14782.98 -> it should redirect you

14784.3 -> to the demo tag with says welcome to edu Rica, right?

14787.957 -> So this was the HTML file

14789.708 -> that we created and we also had a PNG file

14792.651 -> which we wanted.

14793.8 -> Access the name was logo dot PNG.

14797.4 -> Okay, this is funny.

14798.4 -> This should not happen.

14800.1 -> Why is this happening?

14801.394 -> Let's take a look at it.

14802.716 -> Whether we have that file there

14804.424 -> because if it was there we should be able to access it.

14807.7 -> And what was my bucket this was the one

14810.7 -> oh, this has happened

14812 -> when I uploaded that file it got saved

14814.312 -> with this extension dot PNG dot PNG.

14816.6 -> So if I come here and I type dot PNG here,

14820.6 -> there you go.

14821.4 -> You have that object delivered

14823 -> to you through your Or so-called distribution in this session.

14830.9 -> We will be discussing about Amazon cloudwatch.

14833.831 -> So without any delay,

14835.2 -> I'll walk you through the topics

14837 -> which we will be discussing today firstly.

14839.623 -> We will see

14840.333 -> what Amazon cloudwatch has and why do we need it?

14843.4 -> Then?

14843.749 -> We'll discuss certain Amazon cloudwatch Concepts moving on.

14847.8 -> We'll take a look at two most important segments

14850.5 -> of Amazon cloudwatch.

14851.885 -> What chart Amazon cloudwatch?

14853.8 -> Events and Amazon

14855.1 -> cloudwatch locks and finally to make the soil more fun

14859 -> and interesting for you of included Adam as well.

14862.9 -> So let's get started first.

14865.1 -> Let us try to understand why we need cloud based monitoring

14868.5 -> with couple of scenarios in our first scenario consider

14872.176 -> that you have hosted a messenger app on cloud

14874.764 -> and your app has gained a lot of Fame

14876.733 -> but clearly the number

14878.027 -> of people using an application has gone down tremendously

14881.1 -> and you have no idea what the issue is.

14883.6 -> Well, it could be due to two reasons firstly

14886.5 -> since your application has complex multi-tier architecture

14889.9 -> monitoring the functionality

14891.3 -> of every layer by yourself will be a difficult task.

14894.469 -> Don't you think and secondly,

14896.7 -> since you're not using any kind of monitoring tool here,

14899.809 -> you wouldn't know

14900.809 -> how your application is performing on cloud.

14903.2 -> Well one solution for that is

14905 -> to employ a monitoring tool this monitoring tool

14908.2 -> will provide you insights regarding have your application

14911.494 -> is performing on cloud

14912.639 -> and with the state.

14913.664 -> You can make necessary improvements

14915.503 -> and you can also make sure

14916.971 -> that your application is in part with today's customer needs

14920.233 -> and definitely after a while you'll notice

14922.511 -> that the number of people using your application has increased

14925.9 -> moving on to our next scenario.

14927.641 -> Let's say your manager as assigned you with a project

14930.7 -> and he wants you to make this project

14932.881 -> as cost effective as possible.

14934.7 -> So as you can see

14936 -> in this project you using five virtual servers

14939.2 -> which perform highly complex computations

14942 -> and all these Servers are highly active during data.

14945.824 -> That is the and most traffic during data.

14948.8 -> But during nighttime,

14950.284 -> the servers are idle by that I mean the CPU utilization

14954.1 -> of these servers

14954.9 -> during night time is less than 15% and yet

14958.1 -> as you notice here

14959.2 -> in both the cases you are paying same amount of money.

14962.4 -> You have to notice two points here firstly

14965.005 -> all your virtual servers are underused during night time

14968.6 -> and secondly you're paying for the resources

14971.3 -> which are not using

14972.5 -> and this definitely Is not cost-effective.

14975.2 -> So one solution is to employ a monitoring tool

14978.5 -> this monitoring tool will send you a notification

14981.323 -> when they serve as our Idol

14982.946 -> and you could schedule to stop the servers on time.

14986 -> So guys, this is one way to make your project most cost-effective

14989.792 -> and avoid paying unnecessary operating costs.

14992.4 -> Let's consider another scenario for better understanding.

14995.6 -> So let's say I have o stood an e-commerce website on cloud

14999.3 -> and during sale season many customers are trying

15002.064 -> to access my website

15003.2 -> which Which is definitely a good thing,

15005.3 -> but for some unfortunate reason application downtime

15008.2 -> has occurred and you guys have to remember

15010.517 -> that I'm not using any kind of monitoring tool here.

15013.4 -> So little bit difficult

15014.752 -> for me to identify the error and troubleshoot

15017.341 -> that in reasonable amount of time and it's quite possible

15020.6 -> that in this period my customer might have moved on

15023.673 -> to different website.

15024.939 -> So you see that I've lost a potential customer here.

15028.019 -> So if I have had a monitoring tool

15029.912 -> in this situation,

15030.935 -> it would have identified the error in all yours.

15033.7 -> Just itself and rectify the problem.

15035.952 -> Well at could have easily avoided losing my customer.

15039.3 -> So I hope guys with help of these use cases you were able

15042.66 -> to understand as to why we need cloud-based monitoring.

15046 -> So let me just summarize what we have learnt till now.

15048.9 -> We need monitoring firstly

15050.55 -> because it provides a detailed report regarding performance

15054.19 -> of your applications on cloud and secondly,

15056.825 -> it helps us to reduce unnecessary operating costs,

15059.9 -> which we are paying to the cloud provider

15062.067 -> moreover it did.

15063.3 -> Ex problems at all your stage

15065.259 -> itself so that you can prevent disasters later

15068.3 -> and finally it monitors the users experience

15071.226 -> and provides us inside

15072.722 -> so that we can make improvements.

15075 -> So while guys in this session,

15077.1 -> we will be discussing

15078.385 -> about one such versatile monitoring tool called

15081.2 -> Amazon cloudwatch

15082.7 -> Amazon cloudwatch basically is a powerful monitoring tool

15086.256 -> which offers your most

15087.599 -> reliable scalable and flexible way to monitor your resources

15091.2 -> or applications which are currently active.

15093.687 -> One Cloud it's usually offers you

15095.6 -> with two levels of monitoring

15097.365 -> which are basic monitoring and detailed monitoring

15100.3 -> if you want to resources to be eligible for basic monitoring.

15104.017 -> All you have to do is to sign up

15105.982 -> for 80-plus feet here in basic monitoring.

15108.951 -> Your resources are monitored less frequently,

15111.584 -> like say every five minutes

15113.2 -> and you're provided with a limited choice

15115.323 -> of metrics to choose

15116.5 -> from whereas in detail monitoring all your resources

15120 -> are monitor more frequently like say every five minutes.

15123.3 -> And you're provided with a wide range

15125.212 -> of metrics to choose from but

15126.705 -> if you want your resources to be eligible for detail monitoring,

15130.079 -> you'll have to pay a certain amount

15131.9 -> of money according to a SS pricing details.

15134.8 -> Now, let's have a look

15136.22 -> at few monitoring services

15137.9 -> offered by Amazon cloudwatch Amazon cloudwatch firstly

15142 -> it provides a catalog of standard reports,

15144.811 -> which you can use to analyze Trends

15147.142 -> and monitor system performance

15149.2 -> and then it monitors stores and provide access to system.

15153.4 -> And application log files moreover.

15155.8 -> It enables you to set up high-resolution alarms

15158.979 -> and send notifications

15160.5 -> if needed and Amazon cloudwatch also send system events

15164.9 -> from AWS resources to AWS Lambda functions SNS topics Etc.

15169.9 -> So if you have not understood any terms,

15171.904 -> which I've used here, don't worry,

15173.6 -> we'll get to know more about this terms

15175.5 -> as we progress

15176.2 -> through the course of this session earlier.

15178.5 -> I mentioned that Amazon cloudwatch allows administrators

15182.042 -> to monitor multiple.

15183.394 -> Sources and applications from single console

15186.3 -> these resources include virtual instances hosted in Amazon ec2.

15190.6 -> Database is located on Amazon RDS data

15193.6 -> stored in Amazon S3 elastic load balancers

15197.1 -> and many other resources

15198.3 -> like auto-scaling groups Amazon Cloud 12 Etc.

15202 -> So guys now let's try to understand Amazon cloudwatch

15205.335 -> a little deeper firstly we'll have a look

15207.871 -> at few Amazon cloudwatch Concepts

15209.964 -> and then I'll explain you

15211.56 -> how Amazon cloudwatch actually operate So

15214.1 -> it's metric or metric represents at time audit set of data points

15218 -> that are published a cloud.

15219.588 -> So what I mean by that is suppose let's say you have

15222.4 -> three variables XY and z and you have created a table

15226.224 -> which has values of X with respect to Y

15228.9 -> over a period of time in this scenario the variable X,

15232.6 -> which have been monitoring till now

15234.3 -> is a metric so you can think of metric as a variable

15237.656 -> which needs monitoring next.

15239.5 -> We have Dimensions.

15240.8 -> Let's consider same variables XY & Z Basically,

15244.249 -> you had created a table

15245.905 -> which has values of X with respect to Y now,

15249 -> let's create another table

15250.76 -> which has values of X with respect to Z.

15253.4 -> So basically we have two tables which describes same variable X,

15257.6 -> but from two different perspectives.

15259.737 -> These are nothing but Dimensions.

15261.7 -> So basically our Dimension is a name value pair

15264.617 -> that uniquely identifies

15266.144 -> a metric and Amazon cloudwatch allows you to assign up

15269.612 -> to ten Dimensions

15270.751 -> to a metric then you have statistics previously.

15273.891 -> We had created two tables

15275.559 -> which are values of X with respect to Y

15278.17 -> and as well as that you can combine data from these tables

15282 -> like to create a chart

15283.445 -> or maybe plot a graph for analytical purposes.

15286.4 -> This combination of data is nothing

15288.686 -> but statistics statistics are metric data aggregations

15292.226 -> over specific period of time,

15294.045 -> then you have alarm.

15295.3 -> Let's say you have been monitoring this variable X

15298.052 -> for some time now and you want a notification to be sent to you

15301.7 -> when the value of x reaches certain.

15303.758 -> Short all you have to do

15305.13 -> is set an alarm to send you a notification.

15307.7 -> So basically alarm can be used

15309.738 -> to automatically initiate actions on your behalf.

15313.1 -> Now that you have clear understanding of concepts

15315.5 -> of Amazon cloudwatch.

15317.062 -> Let's see how Amazon cloudwatch operates Amazon cloudwatch has

15321.6 -> complete visibility into your AWS resources and applications

15325.6 -> which are currently running on cloud.

15328 -> So firstly it collects metrics

15330.104 -> and locks from all these AWS resources

15332.899 -> and applications.

15334 -> And then by using this metrics it helps you visualize

15337.668 -> your applications on cloudwatch dashboard moreover.

15341.1 -> If there is some sort of operational change

15343.976 -> in a SS environment Amazon cloudwatch becomes aware

15347.461 -> of these changes

15348.456 -> and response to them

15349.7 -> by taking some sort of corrective action,

15352.245 -> like maybe it sends you a notification

15354.6 -> or it might activate a Lambda function Etc.

15357.5 -> And finally it provides your real-time analysis

15360.606 -> by using cloudwatch metric map.

15362.7 -> So if you're wondering What cloudwatch metric Mathis

15366 -> it is a service

15367.137 -> which integrates multiple cloudwatch metrics

15370.28 -> and creates a new time series

15372.4 -> and you can view this time series

15374.399 -> on cloudwatch dashboard as well.

15376.4 -> So working this way Amazon cloudwatch provides you

15379.842 -> with system by disability

15381.6 -> it even provides you actionable Insight

15383.965 -> so that you

15384.628 -> can monitor your application performance moreover.

15387.689 -> It allows you to optimize resource utilization

15390.5 -> if needed and finally it provides a unified.

15393.6 -> I'd view of operational health of your AWS environment.

15396.864 -> So I hope that by now

15398.138 -> if you know

15398.809 -> what Amazon cloudwatch has so now let's try to understand

15402.338 -> how Amazon cloudwatch works with help of a demo.

15405.3 -> So guys, this is my AWS console.

15407.6 -> Let's say AWS Management console

15409.815 -> and the services which you can see

15412.1 -> on the screen are the services offered by Amazon AWS.

15415.169 -> But in this demo we are going to use only few Services.

15418.4 -> Let's say cloudwatch, and then you have easy to

15421.234 -> and a service called Simple notification.

15423.8 -> Service and when I click on ec2 it takes me to ec2 dashboard

15429 -> where you can see

15430 -> that I have four instances which are currently active,

15433.1 -> you know that here in this demo.

15434.833 -> I'm supposed to get a notification saying that

15437.373 -> CPU utilization of my instances less than or

15439.8 -> if a person for me to receive a notification first,

15443 -> I'll have to create a topic

15444.705 -> And subscribe to it with my email ID.

15447.152 -> So let's explore a service called

15449.239 -> Simple notification service

15451 -> where you can create a topic And subscribe.

15453.845 -> To it.

15454.285 -> Once you reach

15455.27 -> SNS dashboard click on topics optional navigation Pane

15459 -> and click 'create new topic give you a topic a name.

15462.4 -> Let's say CW topic and if the display name as well,

15466.4 -> let's give the same name

15468.4 -> and click on create topic option here.

15470.8 -> You can see

15471.472 -> that I've successfully created a topic now click on the topic,

15475.2 -> which you have created and select actions

15477.942 -> and subscribe to topic option.

15480 -> Well, I want notifications to be sent to me

15482.379 -> in form of email you Of different options as well

15485.3 -> and form of Lambda function or Jason Etc.

15488.6 -> But I'm going to choose it as email and give my email ID

15492.135 -> which is her and then click on create subscription option.

15495.8 -> So now whenever AWS console wants to send me a message.

15499.6 -> It will send to the email ID

15501.385 -> which are used to subscribe the topic now,

15504 -> let's go back to cloudwatch dashboard.

15508.3 -> So guys this is

15509.2 -> my cloudwatch dashboard and you can see different options

15512 -> or navigation pane firstly.

15513.687 -> I have dashboard

15514.687 -> where I can view all my metrics at same place.

15517.5 -> Then you have alarms which shows the list of alarms

15520 -> which you have configured

15521.475 -> and then you have events and locks

15523.416 -> which will be exploring later.

15525.1 -> Our topic of interest is the last one

15527.051 -> which has metrics select the metrics option here

15529.838 -> and then choose ec2 and then / instant metrics

15533.6 -> when you do that or list of metrics will be shown to you

15536.7 -> like Network out.

15537.746 -> Soup utilization Network packet in network packets out

15541.122 -> and various other metrics for various resources,

15544.119 -> which are currently active on your Cloud.

15546.5 -> So but we are interested only with CPU utilization.

15549.176 -> So I'm going to type that here.

15553.5 -> Well, it shows the list of instances

15556.1 -> which are active on my cloud

15558.5 -> and I'm going to choose Windows to instance and then click

15561.946 -> on graph metrics option here.

15564 -> Okay, let's select Windows to only and then on the right side,

15567.361 -> you can see you have a alarm button when you click on

15570.235 -> that a dialog box will be open

15572.053 -> where you can configure your alarm firstly.

15574.6 -> Let's give alarm a name.

15576.155 -> Let's say low CPU utilization.

15579.6 -> And a brief description as well.

15582.1 -> Let's say lower than 25 percent lower

15584.869 -> than 25 percent CPU utilization.

15589.8 -> Now I'm going to set the threshold Which is

15592.4 -> less than 25% in this case and on the light side,

15596.218 -> you can see of period option

15597.917 -> if you resources are eligible for basic monitoring

15600.837 -> the speed option by default as five minutes.

15603.4 -> And if your resources

15604.578 -> are eligible for detailed monitoring,

15606.6 -> it's usually one minute

15607.9 -> and when you scroll down you can see a send notification

15610.9 -> to option here so select the topic

15612.77 -> which you have previously created that will be C Topic

15615.788 -> in my case and then click on create Allah.

15620.8 -> But there is some error.

15622.6 -> Okay.

15622.9 -> It says there's an alarm already with this name.

15625.5 -> So let's give it another name of my instance.

15630.1 -> Now, let's try again and when you click

15633.1 -> on this alarm button And click on refresh option here.

15637.4 -> It says that I've successfully created a alarm here.

15640.5 -> You can see that low CPU utilization of my instance.

15643.4 -> And when you click on that it shows you all the details

15646.6 -> like description threshold

15648.2 -> and what action it is supposed to take

15650.382 -> when alarm is configured and all the details.

15652.97 -> So guys try it out.

15654.088 -> It'll be easy

15654.853 -> for you to understand cloudwatch console much better.

15658 -> Okay guys.

15658.8 -> Now, you know what Amazon cloudwatch has

15661.3 -> what it does and wait operates,

15663.3 -> but to understand the capabilities.

15665.3 -> You have Amazon cloudwatch completely we should be aware

15668.4 -> of two important segments of Amazon cloudwatch,

15671.2 -> which are cloudwatch events and cloudwatch locks.

15674.231 -> So let's discuss them one by one firstly we have

15677.2 -> Amazon cloudwatch events consider the scenario.

15680.33 -> Let's say you've created an auto scaling group

15683.1 -> and this Auto scaling group currently

15684.9 -> has terminated an instance

15686.55 -> so you can see this as some sort

15688.58 -> of operational change in area Bliss environment

15691.5 -> when this happens

15692.5 -> Amazon cloudwatch becomes aware of these changes.

15695.2 -> Changes and response

15696.317 -> to them by taking some sort of corrective actions,

15699.2 -> like in this case.

15700.3 -> It might send you a notification saying

15702.2 -> that your auto scaling group has terminated an instance

15705.393 -> or it might activate and Lambda function

15707.7 -> which updates the recording Amazon Route 53 zone.

15711 -> So basically what Amazon cloudwatch Evans does is

15714.6 -> it delivers a real-time stream of system events

15717.893 -> that describe change in your AWS resources.

15720.9 -> Now, let's have a look at few concepts related

15723.5 -> to Cloud watch events.

15725 -> First TV happy Venter and even indicates change

15728.738 -> in a SS environment and AWS resources generate events,

15732.9 -> whenever the state changes.

15734.543 -> Let's say you have terminated an active ec2 instance.

15737.764 -> So that state

15738.584 -> of this ec2 instance has changed from active to terminated

15742.188 -> and hence an event is generated.

15744.212 -> Then you have rules rules are nothing but constraints

15747.5 -> every incoming event is evaluated to see

15750.055 -> if it has met the constraint.

15751.89 -> If so, the event is routed to Target Target is is

15754.968 -> where the events are handled

15756.848 -> Target can include Amazon ec2 instances

15759.4 -> or a Lambda function or an Amazon SNS topic Etc.

15763 -> Now let's try to understand Amazon cloudwatch events better

15766.411 -> with help of use case in this use case.

15769.101 -> We are going to create a system

15770.968 -> that closely mimics the behavior of Dynamic DNS.

15773.8 -> And for those who don't know

15775.3 -> what Dynamic DNS has Let me Give an example.

15778.2 -> Let's say you want to access internet at home then

15781.203 -> internet service provider assigned to an IP address,

15784.525 -> but Since internet service provider users different kind

15788 -> of online systems.

15789.237 -> This IP address keeps changing

15791.3 -> because of which it might be difficult

15793.623 -> for you to use this IP address with other services

15796.7 -> like webcam security camera thermostatic cetera.

15800.2 -> So this is where Dynamic DNS comes into picture

15803.3 -> what Dynamic DNS does is it assigns a custom domain name

15807.106 -> to your home IP address

15808.683 -> and this domain name is automatically updated

15811.7 -> when IP address changes so basically

15814.369 -> dynamic ANS is a service

15816.2 -> that automatically updates a name server

15818.995 -> in domain name system

15820.499 -> and Amazon office you

15822 -> with a similar kind of service called Amazon Route 53.

15825.6 -> So in this use case,

15826.942 -> we are going to update Amazon dropped 50 3 whenever

15830.3 -> a Amazon ec2 instance changes its state.

15833.2 -> Now.

15833.4 -> Let's see how the use case actually works this use case

15836.817 -> precisely works this way.

15838.4 -> So whenever an ec2 instance changes,

15840.92 -> it states Amazon cloudwatch event becomes aware of these.

15844.85 -> Operational changes and it triggers a Lambda function

15848.5 -> this Lambda function uses different kind

15850.831 -> of information regarding the instance like that's

15853.7 -> public and private IP address

15855.7 -> and it updates a record

15857.247 -> in appropriate Route 53 hosted zone.

15859.6 -> So let's say you have an ec2 instance and you

15862.191 -> have terminated the instance.

15863.9 -> So Amazon cloudwatch events become aware of this

15866.517 -> and it triggers a Lambda function

15868.455 -> and this Lambda function deletes the record

15871.1 -> from Amazon Route 53 similarly

15873.1 -> if you have created a new instance,

15874.8 -> Once again Amazon cloudwatch events become aware of this

15878 -> and it triggers a Lambda function

15879.6 -> in this Lambda functions creates a new record in Amazon Route 53.

15884.1 -> I hope you have understood what Amazon cloudwatch even sees

15887 -> and what it does.

15888.1 -> Now, let's discuss

15889.2 -> how Amazon cloudwatch events works with help of a demo.

15892.5 -> So in this demo,

15893.5 -> we will schedule to stop and start ec2 instances

15896.407 -> with help of Lambda function and cloudwatch events.

15899.5 -> So let's go ahead with demo.

15901.6 -> So guys, you can see that I have four instances

15904.2 -> which are currently Deaf first,

15906.4 -> I'm going to create a Lambda function

15908.2 -> which is going to stop my windows to instance

15911 -> and you guys need to know that for Lambda function to do that.

15914.1 -> We need to assign permission.

15915.6 -> So Amazon provides you with the service called I am

15918.895 -> which is identity and access management

15921.4 -> where you can assign permissions when you search

15924.164 -> for I am in the tab,

15925.3 -> it shows you the service select

15927.124 -> that and on IM dashboard on the navigation pane.

15930.089 -> You can see a policies option here select that and click

15933.299 -> on create policy option.

15934.9 -> First it's asking you for a service here.

15937.529 -> We should be easy to in our case click

15939.853 -> on easy to function and actions

15941.8 -> which will be to start and stop may see two instances.

15944.6 -> So let's search for start instance.

15946.4 -> Well, a predefined function is already there.

15948.636 -> So you can choose

15949.5 -> that then you have stopped instance again select

15952.9 -> that And then I wanted to be eligible for all the resources.

15957.7 -> So I'm going to choose all resources here and click

15960.2 -> on review policy option.

15961.9 -> Let's give our policy a name

15964 -> that is to start and stop ec2 instances

15968.3 -> and description as well a brief description.

15971.041 -> Let's say to start and stop instances.

15974.469 -> And now click on create policies.

15977 -> It's taking a while.

15978.5 -> So I've successfully created a policy here.

15981.064 -> Next we have to assign this policy to Lambda function.

15984.3 -> So click on rolls here then

15985.977 -> click on create role choose Lambda function here

15988.898 -> and click on next permission.

15991.2 -> Search for the policy which we have created earlier

15993.7 -> that is to start and stop the found the policy select

15996.881 -> that and click on next view option

15998.9 -> that's asking for a name.

16000.4 -> Let's give a name start-stop instances

16005.4 -> and click on create role.

16007.4 -> I've successfully created a role.

16009.7 -> So what we have done here is we have assigned permission

16012.7 -> for Lambda function to control ec2 instances.

16015.4 -> Now, let's create a Lambda function.

16017.459 -> You can search for Lambda in the search

16019.7 -> that and there R click

16020.971 -> on create function give you a Lambda function a name.

16024.17 -> Let's say to stop instance and select the role,

16027.7 -> which you have previously created and click

16030.454 -> on create function.

16031.8 -> You can see that I've successfully created

16034.191 -> and Lambda function

16035.3 -> and now I'm just going to copy the code to stop

16038.484 -> ec2 instances here.

16042.4 -> I'm going to select this and paste it over here

16045.126 -> and make sure to save it

16047.2 -> as you can see here in this function a task

16050.077 -> for instance region and instance ID.

16052.476 -> So let's configure the details.

16054.734 -> Let's give it a stop instance

16057.534 -> and here you will have to insert instance region and ID.

16063.4 -> and Stan's region an instance ID Novel have to copy

16074.1 -> the instance region and ID of the instance,

16076.9 -> which I ever need.

16078.3 -> So let's go to ec2 dashboard here.

16083.4 -> Now let's say I want my windows to instance to be stopped.

16086.4 -> But this is the instance ID,

16087.8 -> which I'm going to paste it over there.

16090.7 -> similarly instance region now Well,

16094.1 -> in this case, I'm choosing Windows to instance.

16096.495 -> You can choose whichever instance you want to stop.

16099.6 -> Once you're done that you click

16101.4 -> on create option here test the configuration details.

16106.2 -> When you scroll down you can see the execution results here.

16109 -> It says that my instance has been successfully stopped.

16111.7 -> Let's go and check

16112.7 -> and easy to dashboard here on the ec2 dashboard.

16115.685 -> I'm going to refresh it and you can see

16118.036 -> that my windows to instance has successfully stopped now,

16121.5 -> we'll create another Lambda function

16123.369 -> which will restart this function again the same search

16126.6 -> for Lambda function in the search tab

16129.1 -> and click on create function option it ask for a name.

16133.1 -> So let's say start instance.

16136.2 -> And choose the role

16137.387 -> with your previously created and click

16139.7 -> on create function again.

16141.4 -> You'll have to paste the code to start the instances over here.

16146.738 -> And click on Save option.

16149.3 -> Let's try to configure this.

16152.369 -> Let's name it as start instance.

16156.6 -> and again a task

16159 -> for to our tributes which are instance region and ID.

16169.1 -> Now what we have to do is copy the instance region and ID here

16172.88 -> like we did earlier.

16175.7 -> Let's go to easy to dashboard and copy

16178.7 -> the instance ID and region.

16182.3 -> Well, you guys can see that here.

16184 -> My windows to instant has been successfully stock now.

16187.203 -> I'll copy this and paste it over there.

16190.3 -> similarly instance region as well and click on create option

16197.7 -> not test the configuration and when you scroll down you can see

16201.469 -> that my instance has successfully restarted

16204.079 -> in the ec2 dashboard.

16205.384 -> I'm going to refresh this.

16207 -> Well, my windows

16208.05 -> to instance is on its way to get restarted till now.

16211.4 -> I've used Lambda function to start and stop my instances.

16214.906 -> But now I'm going to automate this process with help

16218.1 -> of Amazon cloudwatch.

16219.6 -> So let's go to cloudwatch dashboard here.

16222.819 -> Well, it's taking a while to load then choose events option

16227.3 -> and click on create true.

16229.089 -> So here we are going to share Jewel to stop my instances

16232.917 -> every day at 6:30 p.m.

16234.449 -> And to restart this instances every day at 6:30 a.m.

16238 -> So click on schedule.

16239.7 -> If you want to know more about Grand Expressions,

16242 -> you can visit Amazon documentation.

16244 -> So let me show you it has six Fields firstly it's minused.

16247.7 -> Then you have hours then day of month day of the week

16250.505 -> and your your concern.

16251.8 -> Only with minutes and house

16253.4 -> because we want our instances to be start

16255.9 -> and stop every day every month.

16257.9 -> So let's give the details.

16260.1 -> So if you're going to create a rule to stop the instance,

16263.5 -> let's say 6:30 in the evening 30 minutes and 18,

16268 -> which is nothing but 6 p.m.

16270.1 -> And then rest all you don't have to mention anything.

16274.5 -> When you give a proper cron expression sample timings

16277.268 -> would be provided to you.

16278.6 -> You can see her the rest of the sample timings

16281.247 -> and now let's add the target function

16283.3 -> which is Lambda function in our case and select

16286.604 -> on stop instance function

16288.4 -> and click on configure details give you a rule a name.

16293.1 -> Let's say stop my ec2 instance

16296.8 -> and description to stop my ec2 instance.

16302.8 -> At 6:30 p.m.

16304.2 -> Every day.

16306.3 -> And click on create video you can see

16309 -> that I've successfully created a rule to stop my instance

16312.294 -> every day at 6:30 p.m.

16313.645 -> Now.

16313.892 -> Let's create another rule to restart this instance

16316.967 -> every day at 6 a.m.

16318.159 -> In the morning.

16319.1 -> Again.

16319.5 -> The scene shows the schedule here and cron expression

16322.966 -> which will be 6 a.m.

16324.299 -> In the morning.

16327.9 -> Again, the sample time is shown here.

16330.2 -> Then that's that Target function again Lambda function

16333.452 -> and select the function

16334.863 -> that is to start instance and click on configure details.

16338.8 -> Let's name it

16339.8 -> as start my ec2 instance and the scripture has

16344.6 -> to start my ec2 instance every day at 6 a.m.

16351.48 -> And click on create.

16353.1 -> So now we have successfully created two rules to start

16356.854 -> and stop the easy two instances at 6:30 p.m.

16359.9 -> And 6:30 a.m. Respectively.

16362 -> So what we have done is we have saved our time here.

16364.764 -> We've automated the process of stopping

16367 -> and starting ec2 instances.

16368.7 -> So try it on yourself.

16370.3 -> It will be easier for you to understand.

16373.3 -> So guys now let's discuss our next topic which is

16376.966 -> Amazon cloudwatch locks.

16378.8 -> Have you guys heard of log files?

16381.9 -> Well log files are nothing

16383.599 -> but detailed record of events that occur

16386.049 -> when you are using your AWS environment,

16388.5 -> you can view a log files on your on-premise server as

16391.7 -> well search for an app called Event Viewer select the app

16397.007 -> and click on Windows locks and select systems

16400.9 -> or list of log files will be shown to you

16403.3 -> when you choose a particular log file all the details

16406.263 -> regarding the clock files

16407.665 -> will be shown like the number of keywords the login time number.

16411.231 -> Of hours, the file has been logged

16413.1 -> onto and various other details.

16415.4 -> Similarly.

16416.1 -> You have log files created

16417.777 -> when you use AWS environment as well.

16420.3 -> So you can consider this log files is a data repository.

16423.9 -> Most of the metrics are generated from these log data.

16427.1 -> So whenever a metric is generated a part

16429.549 -> of data is extracted from this log data.

16432 -> So you're designing metrics according to your like

16434.919 -> by choosing a part of data from this log data.

16437.6 -> So basically this log files are

16439.489 -> what we call a primary data store.

16441.6 -> Please and Amazon cloudwatch locks is used to monitor store

16445.7 -> and access log files from AWS resources,

16448.6 -> like ec2 instances cloud trail Route 53 Etc.

16452.3 -> Let's try to understand cloudwatch locks

16455 -> better with help

16455.8 -> of some features firstly you

16457.525 -> can use Amazon cloudwatch locks to monitor your application

16461.03 -> and system log files.

16462.3 -> Let's say you have made a lot of errors,

16464.1 -> but trying to deploy your application on cloud

16466.5 -> in this scenario.

16467.5 -> You can use cloudwatch locks to keep track of your errors.

16471.4 -> And send a notification to you

16472.9 -> when the error rate increases certain threshold

16475.605 -> so that you can make avoiding errors again,

16478 -> then you have log retention

16479.8 -> by defaults logs are kept indefinitely

16482.4 -> but cloudwatch provides you with an option

16484.645 -> where you can set the period between 10 years to one day.

16487.718 -> Then you have locked storage.

16489.34 -> You can use cloudwatch logs to store your log data

16492.2 -> and highly durable storage and in case of system errors,

16495.8 -> you can access raw log data from this storage space

16498.9 -> and then you have DNS queries you can use Watch lugs

16502.3 -> to log information about the DNS queries

16504.8 -> that Route 53 DC's

16506.7 -> now let's have a look at few Concepts

16508.5 -> regarding cloudwatch locks

16510.2 -> firstly we have something called log even so log even

16513.9 -> is just to record a fact DVD that has occurred

16516.7 -> in AWS environment.

16518.2 -> It's straightforward.

16519.5 -> Then you have locked stream a log stream

16521.6 -> as a sequence of log events that have same Source.

16525 -> Then you have something called Law Group Law Group defines

16528.3 -> group of lock streams.

16529.9 -> That has same.

16531.2 -> And access control settings by default.

16533.3 -> You have to make sure

16534.417 -> that each log stream belongs to one

16536.3 -> or the other Law Group guys not let's try to understand

16539.3 -> cloudwatch logs better with help of this use case

16542.1 -> in this use case.

16543.1 -> We are going to use Amazon cloudwatch

16545.234 -> looks to troubleshoot the system errors,

16547.5 -> you can see that I have three instances here

16550.029 -> and a cloudwatch agent

16551.333 -> which is monitoring all these three instances.

16554 -> So what cloudwatch agent does is it collects custom level metrics

16558.1 -> from all these easy to instances and then This metrics

16562.146 -> and locks collected by the agent are processed and stored

16566.1 -> in this Amazon cloudwatch Lots Amazon cloudwatch locks,

16569.816 -> then continuously monitors these metrics

16572.6 -> as you can see here by then.

16574.451 -> You can set an alarm which will send you notification

16577.781 -> when some sort of error occurs in the system.

16580.6 -> So whenever you receive a notification saying

16583.253 -> that some sort of error is there

16585.129 -> in the system you can access the original log data,

16588.084 -> which is stored in Cloud watch locks to find the error.

16591.2 -> So this is how you can use

16592.5 -> Amazon cloudwatch locks to troubleshoot the system errors.

16595.569 -> So basically you are having a look at original data

16598.261 -> so you can solve your problems faster and quicker.

16601.1 -> So this is it guys today in this session.

16608.3 -> We are going to discuss about the service AWS cloudformation.

16612.2 -> So without wasting any more time,

16613.9 -> let's move on to today's agenda.

16616 -> So we'll start today's session by discussing

16618.345 -> why cloud formation is actually needed

16620.361 -> in the first place.

16621.6 -> Once we're done with that, we'll move on to the what of

16624.3 -> what is cloud formation.

16625.99 -> Actually after that.

16627.4 -> We'll be discussing what things are needed to get started

16630.2 -> in the cloud formation service.

16631.8 -> Now among those things.

16633.1 -> You have a Json document.

16634.9 -> So we will be learning how to create a Json document.

16637.77 -> So before that we'll be seeing the structure

16640.3 -> of a Json document.

16641.9 -> Once we learn the structure will see

16643.8 -> how a Json document actually looks like so we'll see

16646.9 -> how a sample Json document looks

16649 -> and in the end we'll be doing a demonstration.

16651.25 -> Ocean so in the demonstration will be doing two demos.

16654 -> The first one will be a really simple one

16656.313 -> and the other one will be a little Advanced.

16659.2 -> Let's move on to the first topic.

16661.4 -> That is why AWS cloudformation?

16664.3 -> So why do we need cloud formation?

16666.342 -> So for example,

16667.229 -> you have an application now most of you guys know that for

16670.6 -> and we have done this in the previous sessions as

16672.9 -> well that we created an application right.

16675.2 -> Now.

16675.405 -> The application is actually dependent on a lot

16677.9 -> of AWS resources.

16679.6 -> Now if we were to deploy

16681.5 -> and manage all these resources separately it will take up a lot

16685.909 -> of time of yours, right?

16687.5 -> So to reduce that time or to manage all these resources.

16691.8 -> What if I told you you have a service?

16693.785 -> Yes.

16694 -> Yes, you got that, right.

16695.3 -> So you have a service called AWS cloudformation.

16698.577 -> So using AWS cloudformation,

16700.432 -> you can manage and create and provision

16702.949 -> all these resources at a single place.

16705.4 -> Now, this is what cloud formation does.

16708.1 -> But now what is cloud formation exactly.

16710.7 -> So a cloud formation is basically a service

16713.2 -> which helps you model and set up your AWS resources

16717 -> so that you can spend more time on your application rather than

16720.3 -> setting up and provisioning these resources, right?

16723.3 -> So basically It's a tool using

16725.194 -> which you can create your applications quickly.

16728.3 -> Also, you can create templates in AWS cloudformation.

16732.4 -> Now, how do you create templates?

16734 -> Basically, you would be using the cloud formation designer

16736.424 -> you'd be putting in all the resources

16738.276 -> that are needed.

16739.081 -> You would be defining the dependencies of these resources

16741.9 -> and then you'll be saving this design as a template right now.

16746 -> What will you do with this template?

16748.1 -> This template can be used to create as many copies

16751.537 -> as you want right?

16752.8 -> Say for example Example you have a use case wherein

16755.778 -> you want your application in multiple regions

16758.383 -> for backup purposes.

16759.56 -> Right?

16760.36 -> So if you want

16761.2 -> that you won't be implementing or you won't be creating each

16764.813 -> and every resource one by one in each of the regions.

16768 -> What you can do is you will create it at one place

16771.2 -> in cloud formation have the template in your hand

16774.4 -> and deploy that template in the other regions as well.

16777.7 -> Right?

16778.2 -> So what will this do?

16779.7 -> So first of all,

16780.5 -> your replication will be very precise,

16782.535 -> right so they won't be Any changes in the copies

16785.6 -> that you have made second of all you will be doing that quickly

16789.247 -> because you don't have to do the process all over again.

16792.301 -> You just have to click a button

16793.966 -> and that template will be provisioned

16795.9 -> or will be launched in that region.

16798.1 -> So this is what AWS cloudformation is all about.

16801.126 -> It makes your life simpler

16802.8 -> by handling all the creation and the provisioning part, right?

16806.6 -> So this is what is AWS cloudformation.

16809.2 -> Now, how do we get started

16811.1 -> in cloud formation says it's a very useful.

16813.799 -> Is how can you

16814.689 -> as a user use the service so let's move on.

16817.7 -> So for using the cloud formation service.

16820.122 -> First of all, you need a Json script now.

16822.474 -> Why do you need a Json script

16824.1 -> because you would be creating a template right

16826.379 -> in the cloud formation designer.

16828 -> You would be using the drag-and-drop option

16830.1 -> and filling in the AWS resources right now

16833.4 -> when you will be doing that in the back end

16835.6 -> it will actually be creating a Json script.

16837.8 -> Now what you can do as a user is if you're good in Json,

16840.611 -> you can create your own Json script.

16842.487 -> Otherwise you can use Cloud formation designer

16845 -> to create a template now for creating a template.

16847.948 -> Like I said, you need a Json script.

16850.033 -> Now.

16850.272 -> What is the Json script then?

16852.1 -> So a Json script is basically a JavaScript object notation file,

16856.5 -> which is an open standard form.

16858.2 -> And that means it is human readable

16860.4 -> so you can read it as well as well as the computer.

16862.9 -> So if you don't need the programming knowledge for this,

16866 -> what you as a user would be doing is you

16868.3 -> would be designing your template in the cloud formation designer

16871.742 -> and that will automatically create.

16873.598 -> Eight a Json script you can do it.

16875.8 -> The other side is well.

16876.9 -> Like I said,

16877.5 -> you can create your own Json script and feed it

16880.017 -> in the cloud formation designer.

16882.3 -> So this is how cloud formation works.

16884.841 -> This is how you would be using AWS cloudformation.

16888.698 -> But then how can you learn the Json script?

16892 -> So it's very easy.

16893.2 -> So basically you have to follow a structure

16895.886 -> in the Json document.

16897.2 -> What is this structure?

16898.5 -> So that structure is

16899.4 -> like this you would be creating the following Fields.

16902 -> So the first field will be the This template format version.

16905.7 -> So this will basically contain version of your template.

16909.181 -> Next up is the description.

16910.827 -> So description is a text-only file or is a text-only field

16914.3 -> wherein you will be describing your template in words, right?

16917.9 -> So if I'm a user and I want to know

16920.516 -> what your Json does

16921.7 -> without reading your Json script from beginning to end.

16924.7 -> I can read the description in simple English and understand

16928.2 -> what ages from triple to right then you have the metadata.

16932 -> So metadata will basically When the properties

16934.9 -> of your template then you have the parameters.

16937.8 -> So any values

16938.6 -> that you have to pass through the template will be included

16941.5 -> in the parameters next comes mappings.

16944.6 -> So mappings would basically include the dependencies

16947.3 -> between your AWS resources.

16948.902 -> Then comes conditions.

16950.196 -> The conditions are basically the conditions

16952.688 -> that you would be giving to your template

16955.041 -> when the Kristof will be created or while the stack is upgraded.

16958.747 -> So if we are stack is being created

16960.526 -> or their stack is being updated.

16962.2 -> These conditions will be looked.

16963.8 -> One two, then comes output.

16965.8 -> So whatever outputs your template will provide

16968.685 -> or your creation of Stack will provide will come

16971.7 -> in the output header.

16973.4 -> Then you have the resources field.

16975.7 -> So resources will basically include all the AWS resources

16979.8 -> that you want to include in your infrastructure right now.

16983.7 -> If you look carefully you actually will be only dealing

16987.1 -> with the resources part,

16988.6 -> right because you will just be populating in the resources

16991.809 -> and creating the dependencies.

16993.447 -> Right.

16993.8 -> So basically you'd be populating the resources part

16996.583 -> and that is what it was all about the resources,

16999.2 -> but right now, this is Theory now,

17002 -> how does a Json document actually look like right

17005.6 -> a Json document looks something like this.

17007.809 -> So like I said,

17008.691 -> you would be working on the resources field, right?

17011.3 -> So you'd be including the resources field

17014 -> and in that say you

17015.5 -> so this Json document is all about

17017.974 -> if you had noticed it's about S3, right?

17020.9 -> So you are basically including an S3 bucket.

17023.5 -> It and the type you'd be specifying the type

17026 -> of service that will be including this bucket.

17028.459 -> Right?

17028.761 -> Like in this example a Json document

17030.511 -> doesn't know what service you're talking about.

17032.8 -> So you specify the name of the bucket

17034.9 -> and inside the brace is you'll be specifying

17037.268 -> which service over here.

17038.68 -> You'll be specifying the S3 service.

17040.6 -> Don't worry.

17041.333 -> I'll be showing you guys this Json document in a moment.

17044.5 -> But before that you should understand

17046.3 -> how a Json document is structured and this is

17048.592 -> what we're doing right now.

17050.6 -> Now guys, this is the cloud formation dashboard.

17053.426 -> Now, you have to create a stack over here, right?

17056.2 -> And for the creation of a stack you require a template so

17059.267 -> first we'll design a template and then we'll create a stack.

17064.7 -> So this is my cloud formation designer.

17066.734 -> Let's go back to our slide and see

17068.501 -> what we actually have to do.

17070.4 -> So, this is our first demonstration here

17073.057 -> in will be creating a S3 Bucket from cloud formation.

17076.6 -> So we'll be designing a template

17078.429 -> around that for first and then we'll be deploying this code.

17081.899 -> Right?

17082.5 -> So let's do that.

17084.2 -> So let's go to our cloud formation window now

17086.916 -> so we have to create an S3 bucket.

17088.954 -> So we'll scroll down to the S3 service.

17091.3 -> So here is AC Service.

17092.664 -> We click on this we service.

17094.5 -> Click on bucket and drag it over here.

17097.6 -> Right.

17098 -> So this is the recipe bucket guys.

17100 -> Now you can edit the name of the template over here.

17103 -> You can name it as either a car CF

17106.1 -> that means and Eureka cloud formation, right?

17109.1 -> So you specify that now,

17111.2 -> this is your Json code now you can compare the Json code guys.

17115.4 -> Let me make it a little bigger for you guys.

17118.479 -> Yeah.

17118.833 -> So this is the Json code guys now,

17121.099 -> I didn't code this Json script, right?

17123.6 -> I just dragged

17124.4 -> and dropped this Bucket over here in cloud formation

17127.3 -> and Automatically generated this script comparing it

17130.3 -> with the code

17131.1 -> that we have in our presentation.

17132.9 -> Let's see so we have resources.

17135 -> Yes.

17135.7 -> We have resources.

17136.8 -> We have the name of your bucket part.

17139.3 -> So basically this is the name of your bucket

17141.829 -> and then it's a type.

17143 -> We're in you'll be specifying this you service.

17145.5 -> So you have type and specifying the SC service over here, right?

17150.4 -> So if you want to change the name of the bucket,

17152.75 -> we can do that over here.

17154.2 -> Let's specify it as and Eureka CF.

17158.253 -> Alright, so we are done.

17160.1 -> This is it guys this is all you have to do.

17162.7 -> So now for running this in cloud formation,

17165.662 -> all you have to do is click on this icon create stuck.

17170 -> Now this will lead me to this page

17172.474 -> which is the create stack page.

17174.8 -> Now, it has automatically uploaded this template

17177.9 -> to the S3 bucket

17179 -> and it has specified the URL here, right?

17181.8 -> We click on next you specify the stack names.

17185.1 -> Let's specify it as a lyric RCF,

17187.9 -> right so you don't have to specify anything are let's click

17190.9 -> on next click on create.

17193.7 -> So you'll be seeing the events on this page.

17197.4 -> Let's refresh this.

17199.2 -> So it says create in progress, right?

17201.7 -> So my template is now being created into a stack

17205.3 -> and that stack will have the AWS resource in it,

17208.592 -> which is the S3 bucket.

17210 -> Right?

17211.143 -> So I think the time is enough.

17213.5 -> Let's refresh it and check if our stack has been created.

17217.13 -> So it's still in the creation phase.

17219.576 -> Let's wait.

17220.7 -> All right, so now it shows me that the Creator is complete.

17224.465 -> All right guys,

17225.448 -> so let's go to our S3 service and check whether we have Bucket

17230.047 -> that are AWS cloudformation created for us.

17232.9 -> So we go to the AC Service.

17241.8 -> And here it is guys.

17243.1 -> So this is the bucket that we created right?

17246.7 -> I see you can see the time.

17248.2 -> It's March 28th.

17249.6 -> 2017.

17250.8 -> Today is March 28th, 2017.

17253.1 -> And the time is 7 5 and the time is 7 7 here.

17256.3 -> Alright, so this bucket has just been created

17259.233 -> by cloud formation.

17261.4 -> So guys, like I said, it is very easy.

17263.628 -> It is easy to understand and to deploy as well.

17266.4 -> You basically just have to create a template and

17269.408 -> that is it AWS cloudformation will do the rest for you

17272.8 -> and the cool part is

17273.799 -> that you can replicate the template as many times

17276.2 -> as you want.

17276.8 -> Right?

17277.2 -> So it will save you the time.

17279.2 -> Okay this demonstration is done.

17281.6 -> So we have created an S3 bucket using cloud formation.

17285.1 -> Let's see what our second demonstration is all about.

17288.5 -> So now we'll be creating an easy domain students

17291.58 -> in which we will be deploying the lamp stack

17294.4 -> which means in that easy to instance.

17296.227 -> You'll installing Linux you installing a patch

17299.135 -> a you'll be installing MySQL and we'll be installing PHP as well.

17303.1 -> Right?

17303.678 -> So, let's see.

17304.593 -> How will we do that?

17306.1 -> So for our second demonstration,

17307.928 -> we will again go back to the cloud formation console.

17311.6 -> We will click on create stack

17313.264 -> and now we have to launch a lamp stack.

17315.7 -> So a lamp stack is basically a sample template in AWS,

17319.1 -> right so we can select the sample template

17321.9 -> and we'll click on view or edit template in designer.

17325.5 -> So a lamp stack is basically an easy to instance

17328.5 -> with Linux Apache MySQL and PHP installed onto it,

17331.7 -> right you can see the designer that you have only specified

17334.6 -> and easy to instance anyway to ask the security group to it.

17337.55 -> So you need the security group obviously

17339.5 -> because you have to connect to this.

17341.606 -> You do instance right now.

17343.171 -> A lamp stack is basically a web server remember?

17346.784 -> Now, let's see the template for this lamp stack.

17350.4 -> So we discuss the structure of a Json document

17353.225 -> if you guys remember so the first part was

17355.8 -> the AWS template format version.

17357.951 -> Then you have description.

17359.663 -> Then you have parameters so parameters

17362.1 -> if you guys remember it is basically the values

17364.499 -> that will be passing to the template right now.

17366.976 -> If you are creating a lamp stack

17368.7 -> you'd be needing the database name

17370.8 -> you'd be needing the database password.

17373.563 -> You'd be needing a lot of things, right?

17376.4 -> If you're installing MySQL you be needing the username

17378.923 -> you'll be needing the password.

17380.4 -> So all of that you can feed in here in the parameters

17383.5 -> so you can specify the key name.

17385.1 -> So if you are connecting

17386.4 -> to the slough instance through SSH connection,

17388.802 -> you'd be needing a keeper right?

17390.511 -> She would be specifying the keep are here.

17393 -> Then you will be specifying the DB name

17395.4 -> and the other detail now

17397.2 -> how will that look when you'll be creating a stack?

17400.2 -> So let's do that.

17401.7 -> We will click on this icon which will now create

17404.3 -> a stack automatically so will be prompted.

17406.688 -> It on this cage click on next then you will reach this page

17410.8 -> where in you are feeling the entry right?

17413.152 -> So you would specify the stack name.

17415.2 -> So this is by default so stack name,

17418.2 -> so we'll be specifying the stack name first.

17420.3 -> So I'll let us tag name be lamb demo,

17423.1 -> and then we move on to the parameters part.

17425.57 -> So whatever you specified

17427.1 -> in the Json parameters field will be reflected over here.

17430.9 -> So we specified DB name over here.

17432.744 -> So it was asking me for the DB name.

17434.7 -> So let's give it as a rake.

17437.2 -> And let's give the DB password as something candy.

17441.5 -> Be root password DB user as a Eureka instance type

17445.6 -> as Steven dot micro wide even got micro because

17448.4 -> if you guys noticed in the template,

17450.447 -> we didn't specify a virtual private Cloud

17452.854 -> that is a VPC now all the instances

17454.9 -> which are launched these days of with all the new instances

17457.5 -> which are there in easy to have to be by default launch the VPC.

17461.3 -> But since we are creating a Json file and we

17463.9 -> didn't specify a VPC you have to select T' an older version

17467.791 -> of your ec2 instance.

17469.2 -> So let it be T 1 so T 1 is an older version.

17471.729 -> It runs without a V PC as well.

17473.8 -> And then you have to specify a key name the key name

17476.7 -> would basically be used to create SSH connection

17480.078 -> to your instance.

17481.3 -> Right?

17482.1 -> So our key pair was array calendar score a will select

17485.9 -> that and will click

17487.4 -> on next now SSH location is basically your IP address

17490.5 -> if you want to specify I don't want to specify it.

17493.3 -> So we'll click on next you don't have to enter anything over.

17496.7 -> Click on next confirm and click on create.

17501.8 -> Now is happening

17503.03 -> in the background as it is picking up that Json file

17506.2 -> and is creating a stack first launch an ec2 instance.

17510.5 -> It will then install the next onto that it will then install

17513.6 -> Apache MySQL and then the end a PHP installation.

17517.5 -> So what we will do the once it says

17520.3 -> that the creation is completed we will go and check

17523.541 -> if everything has been installed

17525.6 -> on our server by creating an SSH connection, right?

17529.6 -> So let's wait until the stack.

17531.9 -> complete Alright guys,

17535.9 -> so as you can see in the events

17538.1 -> that the creation is now complete.

17540.5 -> So let's check

17541.335 -> that if our installation has been correct will go

17544.3 -> to the ec2 instance.

17548.1 -> Now this is our instance which has just been created.

17552 -> We can check that.

17553.7 -> It's been created on March 28, right?

17556.469 -> So today is 28.

17557.9 -> Alright, so now let's connect to this instance.

17561.263 -> So for that we will have to copy the IP address.

17566.3 -> This is the police officer.

17567.8 -> For those of you who don't know how to connect to easy

17570.8 -> to you'll be pasting an IP address here.

17573.8 -> Right?

17574.9 -> And then you have this private file, right?

17579.1 -> So this is of the pemex tension,

17581.2 -> but the party software needs a PPK extension.

17584.3 -> So you have to convert this pem file to PPK

17586.79 -> that can be done using the puttygen software.

17589.9 -> So this is the footage and software so I

17592.591 -> will be dragging this file here.

17595.2 -> Okay, it doesn't work.

17596.6 -> So well click on load go to downloads click

17599.4 -> on all files select my pem file click on Open click on OK

17606.1 -> and then click on save Private key.

17608.834 -> So let's name it as a Eureka.

17612.18 -> Underscore a click

17613.565 -> on save so a file has been saved will close it.

17617.5 -> Go back to our party software here enter the IP address here.

17622.2 -> You will click on SSH click on authentication.

17626 -> Click on browse go to your PPK file click

17629.215 -> on open and click on open here.

17631.8 -> So now you'll be connected to your SSH through your SS has

17636.184 -> to your ec2 instance.

17638.6 -> So any Linux installation on Your AWS infrastructure.

17643 -> The login will be easy to - user.

17646.8 -> I see you're in let's see

17648.7 -> if you can connect to a MySQL installation.

17651.4 -> So MySQL - Edge so it is on localhost.

17656.9 -> - P port number

17659.6 -> which is your 6 and then the user

17663.2 -> that we gave was a Eureka and the password was this.

17671.3 -> Okay guys, so we are in so

17673.1 -> that means we successfully created the Eddie Rekha username

17677.6 -> which is specified in the Json script.

17679.5 -> That works.

17680 -> Well and then you specified.

17682.6 -> Okay.

17682.94 -> We also specify that we need a database right?

17685.914 -> So, let's see if it is showing a databases

17688.624 -> or our databases have been created as well.

17691.5 -> Okay, so it has a data-based called Ed, Eureka?

17696.6 -> Right.

17697.333 -> So the Json script worked.

17699.333 -> Well now the thing here to notice.

17702.399 -> Is that how granularity you can configure your Json file?

17706.6 -> Right?

17707.4 -> First of all,

17708.2 -> it launched an ec2 instance then install Linux

17711.5 -> then install MySQL it configured it settings

17715.1 -> and inside MySQL it gave you a database, right?

17719.3 -> So this is awesome guys.

17720.873 -> So this gives you the whole control

17723.1 -> of AWS just through Json script.

17725.7 -> Right and this is the power of cloud formation.

17728.6 -> Now if you want this infrastructure

17730.625 -> or whatever you have created right now to be replicated again

17734.2 -> to some other instance

17735.7 -> that can be done with a single click of button,

17738.4 -> right and it is actually pretty awesome

17741.1 -> because if you were to install this lamp stack

17743.8 -> on a server or on AWS again,

17746.2 -> if you launch ec2 instance with the Linux OS installing

17750.1 -> Apache MySQL and PHP may take time.

17752.8 -> It actually takes time.

17753.868 -> We can you have to open the console.

17755.549 -> All you have to open the terminal you have

17757.6 -> to enter the commands

17758.835 -> and depending on your internet speed you

17761.129 -> will install all those packages.

17763 -> So this is neat.

17764.1 -> It does everything for you automatically, right?

17767.1 -> So guys, this is what cloud formation was all about.

17770.544 -> So I'll close the session.

17772.6 -> Let me go back to my style.

17774.188 -> All right, so guys we are done with the lamb stock demo.

17782.2 -> Today's session is going to be on auto scaling and load.

17785.5 -> And so so today I'm going to tell you

17787.435 -> how you can order scale your resources

17789.446 -> so that they become highly available and this is

17792 -> what we're going to do today.

17793.3 -> All right.

17793.8 -> So with that guys,

17794.5 -> let's start with today's session with the agenda for today.

17798.2 -> So guys, this is

17799 -> what we are going to do today first.

17800.452 -> We're going to see

17801.2 -> what are snapshots and am I so these are

17803.9 -> basically the entities using this using which you will be

17807.793 -> or scaling your resources.

17810 -> So once you know,

17811 -> what are snapshots in Amis will move on

17812.9 -> to why do we actually need or scaling and what?

17815.4 -> Is auto-scaling exactly after that we're going to see

17818.243 -> what is a load balancer and towards the end.

17820.593 -> We'll be doing a Hands-On

17821.773 -> which is going to be very interesting

17823.45 -> because I don't think there's a demo out there

17825.5 -> which can show you the kind

17826.668 -> of demo that I'm going to show you today.

17828.4 -> All right, and if you think about a guy's if you're

17830.992 -> if you're thinking about moving to the cloud industry order

17834 -> scaling our load balancing out the very important topics

17838.7 -> in this in this in this domain,

17841.2 -> right so you should know about them.

17843.2 -> So if you have been so

17845 -> if you About them please pay attention today

17847.312 -> because you're going

17848.249 -> and going to go and gain a lot of knowledge today.

17850.7 -> All right moving on guys.

17851.9 -> Let's start with the first topic which is snapshots

17854.5 -> and am is so let us see

17856.4 -> what are those so I guess most of you are aware

17860.2 -> of what an ec2 instances of for those of you

17863.098 -> who are not an ec2 instance is just like a row,

17866.2 -> so it's in fresh piece of computer

17868.5 -> that have just bought is just like that, right?

17871.4 -> So on that computer,

17872.8 -> you can choose any operating system that you want.

17875.415 -> Want so once you have the operating system,

17877.655 -> you can install any kind of software on it.

17879.918 -> All right, so you have to install every time you

17882.6 -> launch a new in an ec2 instance.

17884.557 -> You have to install all the required software's on it.

17888 -> All right, but there's a workaround

17890 -> what if you want a specific configuration

17893.2 -> of ec2 instance a want five easy to servers

17895.9 -> which are exactly like this like each other, right?

17899.171 -> So one way of doing

17900.3 -> that would be to launch a new instance every time

17903.4 -> install the required packages.

17905.5 -> Daytime and going about it,

17907.495 -> right the other way

17908.9 -> of doing it would be to actually create an image of

17913 -> once you will be configuring your ec2 instance.

17915.588 -> And after that you'll be creating an image

17918 -> of your ec2 instance.

17919.385 -> And that using that image you can actually deploy

17922.552 -> for more easy to do servers.

17924.4 -> All right, so this image is basically what is

17927.6 -> and am I so am I

17928.9 -> which is an Amazon machine image is nothing

17932 -> but an executable image of your already existing.

17935.505 -> You do instance, right?

17937.1 -> But before an am I

17938.3 -> can be created there is a thing called snapshot

17941.005 -> now what a snapshots snapshots are nothing

17943.6 -> but the copy of the data the data the copy of the data

17947.4 -> that you have on your hard drive.

17950 -> So basically if you have your C drive,

17952.9 -> right and you want to copy your C drive

17954.905 -> you copy a CD drive on to some external drive

17957.27 -> so that becomes a snapshot

17958.8 -> but if you can boot from that external drive,

17961.973 -> so that has to your whole operating system comes up.

17965.536 -> Some other machine then it becomes an Ami.

17968.4 -> So this is basically

17969.4 -> the difference between the two a snapshot is

17971.7 -> not a bootable copy and Ami is a bootable copy that you have.

17975.7 -> Alright, so I hope you got the difference

17978.6 -> between what is in am I and what is the snapshot?

17980.9 -> So I'll repeat it again

17982.3 -> and you use an Ami to basically replicate an easy two wins

17986.557 -> is easy to instance again,

17988.5 -> so that you don't have to do the configurations

17991.4 -> all over again, right?

17993.4 -> So now you'd be Oh,

17995.4 -> we were we were to talk about what is auto scaling.

17998.4 -> What is load balancing?

17999.7 -> Why do we need EMS

18000.818 -> but be patient you would be clear with everything

18003.758 -> with the session.

18004.846 -> All right moving on guys, let's now discuss.

18007.599 -> Why do we need auto-scaling now before the right.

18010.901 -> Now the way I will be going

18012.636 -> through the session is I'll be explaining you each topic

18016.227 -> and then I'll show you it in the AWS console.

18019.1 -> All right, so we just discussed what are snapshots

18022.9 -> and what are a mere am I so let me quickly show you

18025.5 -> How you can configure our

18027 -> how you can create an Ami of an already

18029.147 -> existing ec2 instance in the AWS console.

18031.7 -> So, let me give me a second.

18033.1 -> So give me a second.

18034.1 -> I'll just go to my browser and my AWS console.

18037.455 -> So guys, this is my AWS console.

18039.486 -> I hope it's visible to you.

18041.3 -> So the first thing

18042.7 -> that you'll be doing is you'll be going on

18044.8 -> to your ec2 console or all right.

18047.6 -> So in your easy to console you will have all your servers

18051.4 -> that are running right now, right?

18053.74 -> So for the for the Sake of Simplicity I have deployed.

18057.5 -> I've already deployed to servers which are server 1 and server

18061.415 -> to now I have configured them both with a purchase

18064.4 -> so that they can have your they can host a website.

18068.5 -> Uh, let me quickly show you

18069.941 -> how the website actually looks like.

18072 -> So if I go

18072.8 -> to this particular IP address of server 1 This is in part.

18082.6 -> So what one right so this is

18085.4 -> how the website looks like right similarly

18088.4 -> for my server to if I go to go into my server to this is

18092.023 -> how my server to be look like.

18100.4 -> Here it is.

18102.1 -> All right.

18102.6 -> So these are my two servers.

18104.162 -> Now.

18104.4 -> What I want is I

18105.5 -> will create an exact copy or the of these servers

18108.9 -> so that they can be replicated.

18111 -> All right.

18111.621 -> So when I say replicated everything from software's

18114.835 -> to this website will be copied onto an image

18117.6 -> and that copy or that image

18119.6 -> when I will deploy it.

18121.221 -> It will be deployed inside one more.

18123.8 -> He should do server in which I don't have to do anything.

18126.6 -> This website will be there.

18127.9 -> I just have to go to the IP address

18129.9 -> and I can see this website.

18132.1 -> All right.

18132.8 -> So now what I'll be doing is I'll be creating an Ami

18135.8 -> of both the server.

18136.902 -> So let's create an EMF or server one first.

18139.579 -> I'll select the server one.

18141.3 -> I'll go to actions.

18142.6 -> I'll go to image I click on create image

18145.525 -> and all I have to do is give an image name for it.

18149.2 -> So let me give the name as live server one, right?

18153.7 -> This is my image name.

18154.8 -> I click on create image and that is it.

18157.857 -> It takes in your request for Eating an Ami

18161.04 -> and it does that right pretty simple now similarly.

18164.6 -> I will be doing it for server to as well.

18166.6 -> I'll select server to I go to image.

18169.853 -> I'll create an image

18171.688 -> and I'll name the image say live server

18175.4 -> to So once I've done

18178.7 -> that you can see the images in your am I tab?

18183.3 -> So if you look at over here

18185.984 -> in the images section you can look at Ami is

18189.205 -> if you go to your aim is you can see there are two images

18193.4 -> which are just being created

18195.06 -> which are in the pending State as of now and they are live.

18198.5 -> So one and lives over

18199.882 -> to Now using these images you can create any kind of server

18203.7 -> that you can create the exact same server

18206.052 -> with just a click of a button.

18208.5 -> All right, you don't have to configure anything much.

18211.37 -> Alright, so this is how you create a new map

18213.9 -> pretty straightforward guys.

18215.8 -> Let's move on and discuss.

18217.6 -> Why do we need auto-scaling now?

18219.4 -> So you learned how to create an Ami, let's go ahead

18222.5 -> and stand auto-scaling and see

18224 -> how they are connected to Ami is all right.

18226.684 -> So say you have an application you have a website

18229.77 -> and every machine now this website is hosted

18232.498 -> on server guys,

18233.523 -> right and so was a nothing

18235.3 -> but machines now every machine has Has its limitation right?

18240.13 -> For example say there's this machine is say around

18243.9 -> 8GB + C i5 processor.

18246.3 -> So say it can host on hundred people.

18249.7 -> Right only a hundred people can come to this website

18252.7 -> and easily and navigate inside the website.

18255.2 -> But if more than a hundred people comes in this computer

18258.9 -> or the server becomes slow.

18261.1 -> All right, so say there are a hundred people as of now

18263.903 -> and they are trying to access your website

18266.111 -> and they can easily access.

18267.7 -> Sit now your website becomes a hit overnight.

18270.5 -> All right, and now a lot

18272.346 -> of people are trying to access your website

18275.7 -> which make sure server overburdened now

18279.3 -> in this scenario you can do only one thing

18281.9 -> that is deploy more servers

18283.482 -> and distribute the traffic equally among those servers

18286.6 -> so that the requests can be handled.

18289 -> All right.

18289.712 -> Now this thing is a manual task

18291.921 -> and manual is a big No-No in the IT world guys.

18295.116 -> So we invented a service call.

18297.2 -> Old Auto scaling and using order scaling

18299.4 -> what happens is it sees it

18301.563 -> it actually analyzes the kind of load

18304.3 -> which is coming in right

18306 -> and it deploys the server's according to that.

18308.475 -> So say around 300 people are coming in and it sees there

18311.5 -> that you need three servers to handle those kind of requests.

18314.8 -> It will do that automatically, right?

18317.454 -> And that is where your am I comes in guys

18320.277 -> because the new servers

18321.9 -> that you will be launching those new servers

18324.629 -> have to be taken out of some template right

18327.3 -> so The first server has to be the exact copy of the sorry.

18332.2 -> The second server has to be the exact copy

18334.5 -> of server 1 the third server as well has to be the exact copy

18337.833 -> of server one, right?

18339.013 -> And that is where the am I comes in.

18340.976 -> So what is what basically happens is in the order

18343.8 -> scaling service you basically attach your Ami

18347.045 -> which you created

18348.3 -> and using that Ami it deploys most servers, right?

18352.1 -> This is why am I is significant

18354.221 -> or this is how am I is related to Auto scaling

18357.3 -> and And this is why do we need auto-scaling?

18360.3 -> Let's move ahead and just give us a definition that

18363.907 -> what auto-scaling exactly is.

18366 -> So like I said,

18367.118 -> whenever you your load increases and you have

18370.31 -> to scale automatically up and down you use Auto scaling,

18374.3 -> so it's not only about scaling up

18376.182 -> that is when you load increases a three or four

18378.67 -> so as you have deployed and never when you load decreases

18381.7 -> Still Force, I was up there to sitting I'd write

18384.721 -> so that is not the case with auto-scaling you can So

18387.788 -> skilled down as per your needs you can configure everything

18391.2 -> which you can imagine about scaling up

18394 -> and scaling down in the auto scaling properties.

18396.8 -> All right.

18397.3 -> So this is why we need auto-scaling.

18399.701 -> Now one more thing

18400.9 -> that you need with auto scaling is

18403 -> if you would have noticed I said the number of servers it

18406.201 -> deployed gets deployed in the order scaling.

18408.7 -> So there are they there are four servers

18411.1 -> which get with get deployed you during order scaling right now.

18415.342 -> The traffic has to be distributed.

18417.6 -> It equally right.

18419.1 -> So this traffic which has to be distributed

18421.9 -> has has nothing to do with auto scaling.

18424.381 -> It has to be done by a separate entity.

18426.9 -> And that is what we are going to discuss in the next section.

18429.9 -> But before that,

18430.9 -> let me show you how you can configure

18432.803 -> or how you can configure the auto scaling properties

18435.5 -> and attach the related am I

18437.4 -> so that the related servers are launched right?

18440.4 -> So let me go to my AWS console.

18443.2 -> So here am I and

18444.6 -> as you can see the aim is have already been created.

18447.833 -> They are lives over one and live server to now

18450.654 -> what I'll be doing is I'll be creating auto-scaling groups

18454.138 -> or I'll be configuring the auto scaling properties

18457.19 -> so that these servers can be Auto scaled as

18459.858 -> and when required right?

18461.321 -> So before that I

18462.262 -> actually have to create a launch configuration.

18464.9 -> Now, what is the launch configuration?

18467 -> So if you look at the a my guys you have only specified

18470.2 -> what kind of data should be there in your server.

18472.9 -> What you have not specified is what kind of machine you

18476.3 -> should launch every time there's a need right?

18478.947 -> So that is exactly what you do in launch configuration.

18481.978 -> So you have the data but you

18483.599 -> don't have the information about the kind of machine

18486.6 -> that you want to launch so

18487.928 -> that that that kind

18488.9 -> of stuff you will be specifying in the launch configuration.

18491.9 -> So what I'll be doing is I'll click

18493.6 -> on create launch configuration

18495.871 -> and now it will give me a wizard as same as that of any issue.

18500.564 -> So right in the ECU server.

18502.9 -> I had to choose an operating system,

18504.823 -> right so same it'll give me the wizard

18507 -> but I don't have to go here.

18508.836 -> I'll have to go to a separate tab,

18511 -> which is called my m is right,

18513.136 -> so I'll select my mice

18514.74 -> and now I'll select the newly created a match

18517.836 -> which is the Mi which I just created

18520.3 -> which is say we are creating a launch configuration for us

18523.825 -> over one right now.

18525 -> So I'll select the lives of A1.

18527.2 -> I'll click on select

18529 -> and now it will ask me the kind of the configuration

18532 -> that I want for my So right so I need attitude or micro

18535.786 -> because we are doing a demo today,

18538.2 -> right so we don't need much of of computing power.

18544.5 -> So we just have to select

18546.6 -> E2 dot micro and will name a launch configuration a thing.

18550.4 -> So let's name it as life.

18553.1 -> So one.

18556 -> Right and the I am role is not required and

18559.7 -> I click on next now.

18561.4 -> It will ask me for adding the storage so easy be is enough

18564.863 -> for anyone to machine.

18566.215 -> I'll go to configure security groups.

18569.1 -> Right?

18569.894 -> And in this regard to groups.

18571.6 -> I just have to add the HTTP rule

18573.386 -> because I have to connect to all the instances

18575.9 -> that I'm launching.

18576.7 -> Right?

18577.5 -> So I'll select the HTTP rule from here right

18584.3 -> and I click On review

18588 -> so that is it guys.

18588.882 -> Nothing else has to be configured you.

18591.2 -> All right, and it is asking me to check everything

18595.7 -> that I've just configured everything seems fine.

18598.5 -> I click on create launch configuration.

18600.8 -> Now it last me for the keeper.

18602.7 -> Right?

18603.028 -> So every server

18603.838 -> which will be launched it will be associated

18606.16 -> with the with a key pair which will be specifying here right?

18609.4 -> You can create a new one

18610.6 -> if you don't have already I already have a key pair.

18614.3 -> So let me choose my my keeper

18616.5 -> so that is a month underscore to and I acknowledge

18620.4 -> that I have this keep your

18621.739 -> and I'll create the launch configuration.

18624 -> It just takes a second or two to do

18626.2 -> that and we are done.

18627.6 -> Alright, so now we have created a launch configuration.

18630.4 -> We have specified what kind of machine we want.

18632.7 -> We specified what kind of data should go into that machine now,

18636.1 -> we'll be creating the auto scaling group

18638.2 -> in which will be specifying in which cases we want

18641.082 -> to Auto scale.

18641.9 -> All right, so let's create an auto scaling group now.

18645.5 -> All right.

18646 -> So it has automatically picked up the launch configuration

18649.6 -> that we have just created that it's life.

18651.6 -> So one right let's name this group as live server one group.

18658.7 -> Right.

18659.6 -> And what is the initial size

18661.8 -> that you want in your launch configuration?

18663.651 -> That is the minimum number of servers that you want.

18665.9 -> So let it be 1 and remember guys.

18668.028 -> This is the most important part

18670.2 -> when you are creating a launch configuration in sure

18674.1 -> that you're doing it in your default VPC to be

18676.989 -> on the safe side

18678.012 -> because there are a lot of settings

18680.185 -> that you have to do

18681.5 -> if you create a VPC on your own and that becomes a hassle.

18685.4 -> All right, so if you accidentally

18687.1 -> delete your default VPC,

18688.5 -> which I did right so you have to contact the AWS support team

18693.4 -> and they'll help you out with it.

18695.6 -> They'll basically create one for you.

18697.6 -> You cannot create one on your own.

18699.7 -> All right.

18700.288 -> So always ensure

18701.2 -> that you are in a default VPC whenever you're creating

18704.2 -> an auto scaling group.

18705.6 -> Alright, so now I will be specifying the subnets.

18708.176 -> So basically you have to select a minimum number

18710.7 -> of to subnets right?

18712.1 -> I'll need not getting into what I said Nets

18715 -> because then it will be like a three-hour session.

18719.163 -> I will click

18720.2 -> on configure scaling properties now over here.

18723.6 -> You can specify the properties that I was talking about that.

18727.3 -> When do you want your server to scale?

18729.942 -> Right so over here you can specify

18732.2 -> the average CPU utilization.

18734.1 -> Now, what do you mean by average PT CPU utilization?

18737.2 -> So there are four servers running as of now, right?

18739.7 -> So it takes the average of all the four servers.

18743 -> All right,

18743.7 -> and if the average goes beyond whatever number

18746.5 -> you're specified here say I specified.

18748.8 -> 70 over here, right?

18750.3 -> So in that case whenever the average pcpd utilization

18753.893 -> will go beyond 70 it will launch one more server similarly.

18757.962 -> If it goes I can configure one more property here,

18761.4 -> which says if it goes below 20% like scale down from one server.

18767.7 -> All right.

18768.2 -> So if there are five servers

18769.6 -> in there and see people ization has gone less than 20 percent

18774.6 -> it will it will it will scale down from one.

18778.4 -> Seven and come down to four servers.

18780.6 -> All right, and you can also set

18783 -> how many seconds should it paid say the traffic

18787.2 -> is spiking down and up like to frequently, right.

18791.4 -> So for that what you can do is you can set a time.

18794.1 -> So if the 20% Mark has been not cross still say

18798.805 -> like five minutes,

18800.4 -> then it will scale down a server

18802.282 -> or if the seventy percent Mark of the CPU utilization

18804.9 -> has been crossed over five minutes.

18807.1 -> It will then scone.

18808.5 -> Scale up, it will not scale up

18810.3 -> with at only once for only one second.

18812.7 -> It becomes 71 person.

18814.8 -> All right, so you can specify all of that over here.

18818 -> But since I cannot load test my instance over here,

18821 -> I'll just keep it

18822 -> at its initial size with just means

18824.4 -> that it will even

18825.707 -> if I delete my instance

18828.3 -> that is I one instance has to be there in any case

18832 -> if I delete the instance it will automatically launch it again.

18835.7 -> Alright, so let's will select the keep this group at an edge

18839.4 -> at its initial size and we'll go to configure notifications.

18843.2 -> So I don't want to configure the notifications neither the tags,

18846.7 -> I click on review

18847.7 -> and I'll click on create auto scaling group.

18850.7 -> Alright, so I've successfully created an auto scaling group

18854.8 -> for my life server one.

18856.8 -> All right.

18857.5 -> Similarly.

18858.2 -> I will do the same steps for my server to as well.

18861.297 -> I'll click on create auto scaling group

18863.7 -> and I'll select a launch configuration

18867.7 -> which was there.

18868.6 -> For my so to so not done that so let's create

18872.861 -> a launch configuration first for us over to will go to a mice

18877.5 -> and we'll select the server to part here.

18881.2 -> Alright, so I've selected server to I do the same steps

18885.3 -> that I did earlier.

18887.4 -> Right.

18888.2 -> So let me give it the name as live server to group.

18894.101 -> I click on add storage configure Security Group over here.

18898.509 -> I'll add the HTTP rule.

18901 -> Click on review

18902.042 -> and launch configuration select the key pair.

18905.9 -> Acknowledge it create lawn configuration doing

18908.789 -> the same steps Kuiper not doing any new thing here.

18911.8 -> I've traced launch configuration.

18913.4 -> Now.

18913.6 -> I create the auto scaling Group,

18915.5 -> which is life's over to group.

18919.4 -> Right and then the vpz

18922 -> as I said should be default subnet minimum gruesomeness.

18926.23 -> You should select You'll click on scaling properties.

18930.3 -> I keep it at initial size configure review and create

18934.8 -> the auto scaling group.

18936.3 -> All right, nothing much guys.

18938.2 -> So same things that I did for my server one.

18941 -> I've done for my server to as well.

18943.3 -> All right, so

18944.064 -> since I've created or or an auto scaling group,

18946.9 -> if you go to your ec2 dashboard,

18949.033 -> you would notice that two more servers

18952.3 -> are now being deployed, right?

18957.4 -> So you can actually identify them over here.

18960.8 -> See these two servers are being initialized with Eva.

18963.858 -> These have just been created by your auto scaling group

18966.624 -> because we specified

18967.7 -> that a minimum number of one server should be there

18970.2 -> at all times right now.

18972.189 -> If you try to go

18973.42 -> to the IP address of this server.

18978.269 -> Right, you will see

18980.111 -> that it will have the exact same settings

18983.3 -> for my easy Tucson's instance.

18985.5 -> So this is my sober one.

18990 -> Right.

18990.3 -> So as you can see a new instance

18992.001 -> called created but with the exact same settings,

18994.5 -> I hadn't had to do anything it automatically

18997.7 -> created an instance with the same settings.

19000.1 -> All right, and same is the case with server to as well guys,

19003.3 -> if I go to my server to and try to access it.

19007.1 -> I'll see the same things over there as well.

19010 -> So I'll Show you a bit Yeah, so this is my server to alright,

19016.7 -> so my auto scaling group is functioning fine.

19021.5 -> So let us come back to our slide now.

19023.8 -> So we are done with auto-scaling now.

19026.1 -> Like I said,

19027.1 -> you need to have an entity which will equally divide

19031.723 -> the traffic between the servers that have just deployed right

19036.5 -> so they say in I've created to Auto scaling group Skies as

19040.56 -> of now write the

19041.7 -> and why I have created a second Auto scaling group.

19044.4 -> I will tell you in a bit,

19045.725 -> but for now understand that there is an auto scaling group.

19048.8 -> All right and inside

19049.976 -> that auto scaling group say there are Five servers and

19053.2 -> if a person is coming in or a customer

19055.6 -> who has logged onto your website is coming

19058.2 -> in How would how would his traffic be treated?

19061.749 -> How would he know which server to go to right?

19065.194 -> So there comes in the third entity

19067.5 -> which is called the load balancer.

19069.712 -> So what load balancer does is a load balancer your customer

19073.9 -> will basically basically be coming to your load balancer

19077.1 -> and the load balancer will decide based

19079.4 -> on the usage of yourself.

19081.2 -> Others that which server is

19083.02 -> more free and then we'll give the connection to that server.

19086.8 -> All right.

19087.3 -> So this is basically the role of a load balancer.

19091.1 -> So like I said a load balancer is a device

19093.511 -> that acts as a proxy and distribution Network

19096.126 -> or application across a number of servers now,

19098.8 -> I've been saying it repeatedly

19101 -> that your your servers are actually sorry.

19104.9 -> Your traffic is actually distributed equally

19107.664 -> among the servers right but in a few moments, I'll tell.

19111.244 -> That there is one more one more way of Distributing

19115.253 -> your traffic, right?

19116.54 -> So before that,

19117.439 -> let me again stress on the point

19119.3 -> that this was your auto scaling group guys.

19121.291 -> This is just the example that I took in the beginning, right?

19124.291 -> So there are like these set

19125.7 -> of users and they're trying to access your website

19128.966 -> and they are being routed to these server.

19131.7 -> So this routing is actually done by a load balancer right now.

19136.7 -> Like I said the traffic

19138.8 -> which is distributed it is distributed

19140.977 -> in in two types, right?

19142.262 -> The first time would be to equally distribute them

19145.4 -> among the number of servers like say there are five server.

19147.9 -> So it will distribute it among the file servers.

19150.9 -> But if there are say there are two kind of servers now

19156.2 -> and so your load balancer

19158.397 -> can identify what kind of request is being made by a user

19163.8 -> for example in your website

19165.7 -> on in your application you have you have a part

19169.382 -> where in you can process the Mitch

19172.5 -> right and you have a part

19173.924 -> where you can where you have the your blogging section.

19177 -> All right.

19177.6 -> So if you want to process the image,

19179.446 -> you want your traffic to go to a different set of servers

19182.405 -> which are order scaled

19183.7 -> at their own in their own Auto scaling group.

19186.4 -> Right?

19187.1 -> And if you have the blogging section,

19189.2 -> you have a different order scaling Group,

19191.2 -> which is auto scaled

19192.5 -> at a different weather different Auto scaling group,

19196.7 -> but you want everything to go from one single link.

19200.5 -> So the way to do that is using an application load balancer.

19204.285 -> So let me just repeat what I just said.

19206.8 -> So the say the this set

19208.377 -> of servers they host your image processing part.

19211.6 -> They do all your image processing

19213.482 -> and these set of servers

19214.8 -> that they host your blog's that you have on your application.

19218.6 -> All right, a user comes in.

19220.493 -> He just logs onto your website and he goes to a URL

19224.1 -> which says say Eddie record or KO / image.

19227.4 -> All right.

19228.3 -> If you go / image your load balancer, we'll see.

19231.5 -> Okay, he's asking for the image kind of content.

19234.998 -> So he should go to this set of servers

19237.666 -> because this this service of the image purpose and

19241.2 -> if you go to a Dirac array card

19243.3 -> or KO / blog your load balancer identify.

19246.266 -> Okay, this user he is asking for the blog content.

19249.9 -> So you should go to this set of servers.

19253.2 -> All right.

19253.7 -> So all of that is done using your load balance or

19256.55 -> if you compare it with a classic load balancer it

19259.4 -> is it does not have that kind of Of intelligence, right?

19262.767 -> What it will do is basically all the traffic

19265.4 -> that it has got in coming to it.

19267.5 -> It will equally distributed among the number of servers

19270.825 -> that are under it.

19271.9 -> All right,

19272.5 -> but with application load balancer you have this option

19275.4 -> where in you can divide

19277.1 -> the traffic according to the needs of the customers?

19281.6 -> All right.

19282.2 -> Now when you have divided the traffic again the same thing

19285.63 -> will happen here as happens in classic load balancer

19288.7 -> that at this point it will equally Traffic

19291.871 -> among the number of image servers, right

19294.9 -> and similarly the people

19296.6 -> who want to access the blog it will equally

19298.8 -> distribute the traffic among the number of people

19301.902 -> who want to access the blog server.

19304.3 -> All right.

19305.1 -> So this is what an application load balancer is all about.

19308.192 -> So classic load balancer was something

19310.2 -> which was invented earlier

19311.9 -> and these days nobody uses the classic load balance anymore.

19315.4 -> People are using application load balancer, right?

19318.8 -> And that is

19319.4 -> what our demonstration is going to be.

19321.354 -> All about today.

19322.2 -> All right, so enough of talks.

19324.5 -> Let's move on to the hands on that is the demo part.

19327.4 -> So let me quickly show you

19328.638 -> what we are going to accomplish today.

19330.5 -> So basically a user will come in.

19332.633 -> He will have the address of your load balancer.

19335.8 -> And if he asks for the image path

19338.9 -> or say server one in our case,

19341.4 -> he will go to the auto scaling group of server 1

19345 -> if he asks for server

19346.479 -> to he will go to server

19348.1 -> to but all of them will have the same at Is

19351.5 -> that is using your address of your load balancer?

19355.2 -> All right.

19355.7 -> So this is what we are going to accomplish today.

19359.2 -> Now for those of you who didn't understand

19361.5 -> that why did we create to order scaling groups is

19364.1 -> because we want these servers

19366.7 -> that is the image processing service to be skated as well.

19370.1 -> And as as at the same time,

19372.1 -> we want the Blog shows to scale as well.

19375.1 -> Right?

19375.9 -> So that is the reason

19377.481 -> we want we created to Auto scaling group.

19380.39 -> So I dated a server one,

19382.136 -> which you can imagine is for your image processing

19385.9 -> and I created an auto scaling group for server

19388.655 -> to which you can imagine is for your blogging section.

19391.9 -> Right having said that guys now,

19394.284 -> let's move on to my AWS console and go to our load balancers.

19401 -> All right.

19401.5 -> So what I've been doing now is I'll be creating

19404.969 -> a new load balancer

19406.8 -> and that load balancer

19408.2 -> would be of the type application load balancer.

19411.128 -> You can see I have two options here.

19412.976 -> I either I can create a classic load balancer

19415.3 -> or I can create an application load balancer.

19418.1 -> So I'll go on with application load balancer

19420.9 -> and I will name it

19423.2 -> as life load balancer and the scheme

19428.938 -> is internet-facing.

19430.4 -> So since mine is a website

19432.3 -> that I want you guys to access right

19434.8 -> so it could be internet-facing.

19436.7 -> Otherwise you if you are working in a company

19439.727 -> and that company wants.

19441.248 -> A load balancer for their internal websites

19444.321 -> that the companies have you can actually opted

19447.5 -> for an internal internal load balancer as well.

19451.2 -> But since as we have a website and we want

19454.011 -> that to be used via we will use the internet

19456.96 -> facing load balancer,

19458.5 -> right and the listeners,

19460.242 -> it's HTTP, that's fine and the availability zones.

19463.9 -> Like I said,

19464.527 -> you have to select a minimum of two availability zones

19467.3 -> and you click on configure security settings.

19470.7 -> All right.

19471.9 -> So now you'll be specifying the security group, right?

19474.836 -> So in Security Group,

19476 -> you'll it's better to create a new Security Group.

19478.6 -> Remember guys don't include the default Security Group

19482.6 -> for your load balancer.

19483.953 -> It's a good practice to always create a new security group

19487.412 -> so that you can customize customize your rules

19490.343 -> according to your needs.

19491.9 -> All right, so I'll create a new security group

19494.6 -> and specify the HTTP Rule and I click on next.

19499.6 -> And now comes the part

19501.3 -> where in will be specifying the targets.

19504.1 -> All right.

19504.6 -> Now what our targets now

19506.278 -> in application load balancer guys targets

19509 -> are basing basically but or scaling groups, right?

19512.3 -> So Target one would be your or scaling group

19514.9 -> one your target to would be Auto scaling group to Target

19517.844 -> three Target for you can have as many targets

19520.2 -> as you want.

19520.938 -> But in this wizard,

19521.9 -> you have to specify a minimum number one, right?

19524.8 -> So we'll create a new Target group will call it

19527.1 -> as say Just killing a life or two one.

19532.8 -> All right,

19533.9 -> and the protocol is HTTP Port is 80 will click on next

19539.792 -> and I'll review everything.

19541.9 -> I think everything is fine

19544 -> and I'll create this load balancer,

19547 -> right so we have not done all the settings guys.

19549.1 -> I'll show you how to do all the settings for now.

19551.5 -> We are just created a plane load balancer.

19554.3 -> All right, so I have created a load balancer

19557.3 -> which is pointing toward Target group.

19559.43 -> Group one and that Target group

19561.158 -> is not pointing to my auto scaling group as of now.

19564.1 -> All right, we will do that now in this part

19567.3 -> so we have created.

19568.926 -> I just created a Target group called live Auto one.

19572.9 -> I'll create one more Target Group

19574.861 -> which will be called live Auto

19576.7 -> to for my second Auto scaling group.

19579.4 -> All right, so I will create this and done.

19582.7 -> So I now have to Target groups

19584.9 -> that is live Auto one and live Auto to now these two.

19589.3 -> Get groups have to point

19590.861 -> to my auto scaling Group C respectively.

19593.499 -> All right.

19594.1 -> Now the way to do that you cannot appoint them here.

19597.199 -> You have to go to your auto scaling groups, right?

19600.9 -> And in your auto scaling groups,

19602.5 -> you have to select the auto scaling group

19604.888 -> that have just launched.

19606.319 -> So it is live server one group and lies over two groups.

19609.6 -> So you I will go to live so one group and go to details

19614.4 -> and over here you click on edit.

19617.5 -> All right, and inside edit you have this option

19620.662 -> for Target groups.

19621.9 -> You don't have to specify anything in the load balances.

19624.924 -> This option is only for classic load balancer,

19627.4 -> but we are creating

19628.35 -> an application load balancer, right?

19630.1 -> So we'll be specifying everything in the Target groups.

19632.952 -> So for live server one group

19634.6 -> will be specifying the demo server one.

19637.5 -> So demo server one has already been sorry.

19643.3 -> Sorry, it will be live Auto One the target group

19646.844 -> that I just created

19648.224 -> and live Auto One is connected to your load balancer.

19652 -> So basically your load balancer will point to your target group

19655.1 -> and your target group is now pointing

19656.8 -> to your auto scaling group one which are pointing

19659.6 -> to your instances.

19661.2 -> All right.

19661.7 -> So this is how it the visibility comes in

19665 -> so I save it.

19668.057 -> The target group one is live server one group

19672.265 -> and the target group 2.

19675.3 -> I'll be specifying in the second Auto scaling Group,

19677.9 -> which is here that is live or two to write.

19682.5 -> I'll save it and let me quickly verify

19685.6 -> if I've done everything, right?

19688.6 -> So this is a lifesaver one group and this is live Auto One Fine.

19694.2 -> This is lice over to group and it is live or to to fine.

19699.6 -> So my load balancer can now see the auto scaling groups

19703.6 -> that I've just configured.

19704.9 -> So let me quickly go to my load balancer.

19713.5 -> Now comes the part guys wearing I'll be specifying

19716.9 -> when to go to auto scaling Group 1 and when to go

19720.2 -> to auto scaling group to like I said will be specifying it using

19725 -> the using the kind of request

19728.4 -> that the that the user has made, right?

19730.3 -> So the way to do

19731.378 -> that is using is by first selecting your load balancer

19734.95 -> and going to listeners.

19736.8 -> So once you go to listeners guys,

19739.1 -> you will reach this particular page now in this you have

19743.33 -> to click on view or edit rules.

19751 -> Alright.

19751.459 -> So once you click on view or edit rules,

19753.7 -> you will reach this page which is kind of an if else

19758.2 -> which is kind of FL structured.

19760.5 -> So now what will you do is so you can see

19762.993 -> that there is a default rule as of now

19765.272 -> that anything any requests

19766.802 -> which is made it will go to live Auto one.

19769.2 -> All right, which means any requests at which is made

19772.2 -> it will straight away pointed to the auto scaling group one now,

19776 -> we'll specify if the request is our is

19778.5 -> if the user is asking for sir.

19780.8 -> To he should be pointed to server to so let us do

19783.807 -> that the way we'll do it is

19785.5 -> like this will click on ADD rules will click

19788.4 -> on insert Rule

19789.6 -> and now I'll specify so you have two options here either.

19793.6 -> It could be the routing could be based on your host.

19798.4 -> That is the address

19799.861 -> of your of your website or it could be based on the path.

19804.2 -> Now.

19804.7 -> What is the difference say Eddie record or Co this is

19808.666 -> the host name right now if I try

19810.8 -> If I type in resources dot Ed u--

19812.9 -> record or go it is still point to my domain.

19818.3 -> But if I have specified resources dot ID record or go

19822.5 -> and if I write it over here

19824.111 -> and I specify it has to go to server

19826.2 -> to it will go to server to otherwise if you type

19829.1 -> in resources or Daily Record or code nothing will happen

19831.35 -> because now if you have not configured anything,

19833.9 -> right, so that is the host path with paths the difference.

19837.6 -> Is that say you right Eddie Ricardo Coast.

19841 -> - block right.

19842.92 -> So that's / blog becomes the path.

19845.8 -> But with host the thing is the difference is

19848.955 -> resources dot edu record orko.

19851.067 -> So that becomes one host name, right?

19853.6 -> But with path you're basically putting a slash

19856.029 -> and you are going into a particular folder.

19858.8 -> All right, so you can specify the path here, right?

19861.3 -> It doesn't matter

19862.3 -> if you have not specified in a server for different

19866.1 -> for different say you could the way you could have done.

19870.7 -> The image processing and block the other way round

19873.317 -> rather than having it on two servers was

19875.4 -> that you have you could have configured it inside to servers

19878.4 -> in your root directory, right?

19880.036 -> It could be server one for your image processing

19882.6 -> and server to for your blog's but I don't want

19886.115 -> that because you're as distributed as a system.

19889.7 -> Is it becomes more reliable, right?

19892.1 -> And that is the reason we have two different servers

19895.1 -> for two different set of things.

19897.5 -> So the way you can route your traffic to body servers is

19901.1 -> by typing in the path.

19903.176 -> So say if I have to go to server one.

19906.4 -> I'll type in server 1 / star so star basically

19909.861 -> means anything after server one could can be accepted

19914.269 -> but it has to go

19915.5 -> to the request will be forwarded to live Auto one.

19920.9 -> All right, so if I

19921.8 -> have server one in my path anywhere in my path,

19924.609 -> it will go to live Auto one.

19926.256 -> So I'll save this rule.

19928.2 -> Similarly, I say that if it has a server to in its path

19934.8 -> and anything after that.

19937.6 -> It has to go to live Auto to write and save it.

19943.742 -> And that is it guys now my load balancer has now

19947.8 -> has saved its settings.

19949.7 -> Let's hope for the best and try executing it.

19953.1 -> So this is the Ling guys,

19955 -> right if you just type in this link,

19957.853 -> it will by default go to server one.

19962.1 -> Right.

19962.788 -> So if I go to this link,

19964.211 -> you can see it is going to server one as of now,

19967.2 -> but if I specify /

19969.2 -> server 1 it will go to my server 1 and

19974.4 -> if I specify / server, too.

19980.8 -> It will go to my second server.

19982.4 -> Now.

19982.6 -> You might be wondering

19984.1 -> that he meant you might have a different directory

19987.2 -> in your same server.

19988.575 -> So let me clear your doubt according to that.

19991.6 -> So what I'll do is I will go to my ec2 dashboard, right

19996.33 -> and so you have to server one.

19999.6 -> And I'll quickly show you.

20002.296 -> If what happens if I type in server to hear?

20006.4 -> All right, so this is the IP address, right?

20009 -> So if I type in this IP address,

20010.916 -> I'm going to server one.

20013.4 -> If I type in / server

20015.9 -> to it will give me a photo for because there is no folder

20019.764 -> called server to write same is the case here.

20023.4 -> So if I go to is IPL, you can see Server one.

20025.6 -> If I don't specify anything

20027.3 -> after my address it will still go to the same server

20030.479 -> that is here.

20031.339 -> That is this.

20032.2 -> IP address right

20033.9 -> but if I specify /

20036 -> over two over here It will not be able to do so

20041.3 -> because this is not a load balancer.

20043.2 -> It is directly your IP address,

20044.9 -> but over here if I specify server to.

20048.5 -> It will redirect me to the second server one second.

20055.2 -> Right, it will redirect me to the second server and

20057.7 -> that is all that I need.

20059.171 -> All right.

20059.759 -> So with one address you are actually pointing to two servers

20063.2 -> which be solving your to problems.

20064.974 -> Now the real life you skate.

20066.5 -> Like I told you it could be four different kind of task say

20069.705 -> you have a blogging section on our website

20071.923 -> and you have an image processing section on our website.

20074.9 -> If you want

20076 -> to different servers to host your two different Services,

20079.4 -> you can do that easily using a load balancer.

20083.5 -> Alright guys.

20084.6 -> So with this I conclude my session

20087.6 -> for today today in this session.

20094.5 -> We'll be talking about Cloud security

20096.7 -> without making any further Ado.

20098.3 -> Let's move on to today's agenda are to understand

20100.779 -> what all will be covered in today's session.

20103 -> So we'll start of the session by discussing the why and what

20106.551 -> of cloud security after that.

20108.296 -> We'll be seeing

20109.178 -> how we can choose between a public or private

20111.9 -> and hybrid cloud.

20113.3 -> For that we'll see

20114.298 -> whether Cloud security is really a concern among companies

20117.46 -> who are planning to make a move on the cloud.

20120.1 -> So once you have established a cloud security

20122.3 -> is really important.

20123.441 -> We'll see how secure should you make

20125.5 -> your application after that?

20127.1 -> We'll be looking into the process

20128.649 -> of troubleshooting a threat in the cloud after that.

20131.488 -> We'll be implementing that process in AWS.

20133.9 -> So guys, this is our agenda for today.

20136.239 -> Let's move on to the first topic of today's session

20139.4 -> that white cloud security is important.

20142.3 -> So let's take an example here

20143.872 -> and talk of three very popular companies linked in Sony

20146.8 -> and iCloud so LinkedIn in 2012 experience the cyberattack.

20150.904 -> We're in 6.5 million usernames and passwords

20154 -> for made public by the hackers after that soon experience

20158.2 -> the most aggressive Cyber attack in history

20160.9 -> where in their highly confidential files

20163.302 -> like the financials their upcoming movie projects

20166.489 -> were made public by the hackers, right?

20168.853 -> And this made a huge impact on the business front of Sony.

20173.1 -> ICloud which is a service

20174.724 -> from Apple also experienced a Cyber attack

20177.4 -> where in personal or private photos

20179.751 -> of users were made public by the hackers, right?

20182.892 -> So guys now in all these three companies

20185.5 -> you can see there's a breach in security

20187.8 -> which needs to be addressed.

20189.2 -> Right?

20189.7 -> So Cloud security has to be addressed.

20192.238 -> It needs to be there in the cloud computing world.

20196.2 -> So since now we've established that cloud security

20199.082 -> is really important.

20200.356 -> Let's move on to understand what cloud security actually is.

20204.1 -> So what is cloud security?

20206.4 -> So it is a use of latest Technologies

20209 -> and techniques in programming to secure application,

20212.2 -> which is hosted on the cloud or the data,

20214.6 -> which is hosted on the cloud and the infrastructure

20217.1 -> which is associated with the cloud computing.

20219.4 -> Right and the other part

20220.858 -> of this is that whatever security techniques

20223.783 -> or whatever techniques or technology

20226 -> that Using to secure application should be updated

20229.7 -> as frequently as

20230.831 -> possible because every day

20232.591 -> new threats are coming up right everyday.

20235.3 -> There are new work around two problems.

20237.655 -> Right and you should be able to tackle these problems

20240.921 -> or these workarounds and hence.

20242.995 -> You should upgrade

20244.2 -> your security as frequently as possible Right Moving ahead.

20248.4 -> Let's understand how we can choose

20250.6 -> between a public a private and a hybrid Cloud.

20253.463 -> So we have understood

20254.8 -> that what cloud security charity actually is now

20257.8 -> let's talk in terms of security and understand

20260.8 -> how we can choose between a public private

20264.012 -> and a hybrid Cloud.

20265.5 -> So if you were to choose between these three infrastructures,

20268.9 -> what should be our basis

20270.36 -> of judging which Cloud we should choose right?

20273.1 -> So you would offer a private Cloud

20275.238 -> when you have highly confidential files

20277.7 -> that you want to store on the cloud platform right now.

20280.876 -> There are two stories or there

20282.8 -> are two ways of thinking a private infrastructure.

20286.103 -> You can either offer private servers

20288.392 -> or private infrastructure on your own from Isis

20291.4 -> or you can look up for servers dedicated servers

20294.683 -> by a cloud provider.

20296.08 -> Right?

20296.5 -> So that all comes under the private infrastructure.

20299.4 -> Then we have

20300 -> the public Cloud infrastructure in public Cloud infrastructure.

20303.6 -> You would basically use websites that are public facing.

20306.658 -> So say if you have a products page

20308.6 -> where you have application

20309.821 -> which can be downloaded by the public

20311.658 -> so that can be hosted on the public Cloud

20313.7 -> because there is nothing that has to be seen.

20316.2 -> Secret over there, right?

20317.8 -> So things like websites things like data

20320.64 -> that is not confidential and you don't mind

20323.377 -> public seeing it can be hosted on your public Cloud.

20326.8 -> The third infrastructure is the most important infrastructure,

20330 -> which is the hybrid infrastructure.

20331.7 -> And this is the set of

20333.1 -> that most companies go for right?

20335.413 -> So what if there's a use case wherein you have private files

20339.577 -> of Highly confidential files and a website as well, right?

20343.9 -> So if you have this kind of use case Might go

20346.704 -> for a hybrid infrastructure,

20348.4 -> which is kind of Best of Both Worlds,

20350.6 -> you get the security or the Comfort

20353.2 -> or the private infrastructure

20355.2 -> and the cost effectiveness of the public Cloud as well.

20359 -> Right?

20359.623 -> So you your hybrid cloud is basically

20362.5 -> if you want your highly confidential be stored

20365.636 -> on your own from Isis

20367.1 -> and your website be hosted on your public Cloud.

20370.6 -> This infrastructure would be a hybrid Cloud infrastructure.

20374.2 -> So basically you would choose a private Cloud

20376.799 -> if you have a highly confidential files,

20379.093 -> if you choose a public Cloud

20380.599 -> if you have files that are not that important or files

20383.4 -> that you don't mind people seeing and you would choose

20386.189 -> a hybrid Cloud infrastructure if you want Best of Both Worlds,

20389.4 -> right?

20390 -> So this addresses how we can choose

20392 -> between a public private and hybrid Cloud moving on.

20395 -> Let's understand whether Cloud security is really a concern.

20398.218 -> So we will discussed

20399.394 -> that white cloud security is important we've discussed

20402.4 -> what is cloud security, right?

20404.3 -> Now let's talk about whether this really makes sense.

20407.7 -> Right?

20408.2 -> So if we say

20409.2 -> that cloud security is really important in this is no one

20412.094 -> who is actually thinking about it.

20413.8 -> There's no point, right?

20415.4 -> So let's see

20416 -> if companies were making a move to the cloud actually think

20419.3 -> about Cloud security.

20420.7 -> So here's a gardener research on companies

20423.563 -> who are making a plan to move to the cloud

20426.33 -> or who has not moved to the Cloud yet, right.

20429.3 -> So what are their concerns?

20431 -> Why not they're doing so so

20433.1 -> the topmost First reason listed by these companies was security

20437.47 -> and privacy concerns, right?

20439.4 -> So as you can see these companies

20441.565 -> who want to make a move to the cloud are also worried

20445.086 -> about the security on the cloud infrastructure.

20448.5 -> And this makes it clear

20450.4 -> that cloud security is actually very important right now.

20455.9 -> We have understood

20456.886 -> that cloud security is very important.

20459.062 -> We have understood that companies are looking

20461.502 -> for cloud security are actually following.

20464 -> The practices for cloud security,

20465.6 -> but now how secure should you make your application?

20469.5 -> Right?

20470.241 -> What is the extent

20471.326 -> to which you should make an application secure?

20474.6 -> So let us start with this line.

20476.643 -> So it is said

20477.5 -> that cloud security is a mixture of Art and Science right

20481.5 -> why let's see that so it's a science

20484 -> because obviously you have to come up with new technologies

20487.7 -> and new techniques

20488.954 -> to protect your data to protect your application,

20492.3 -> right?

20492.6 -> So it's a science.

20493.9 -> Because you have to be prepared with the technical part,

20497.672 -> but it is art as well.

20499.115 -> Why because you should create your techniques

20502.2 -> or you should create new technologies in such a way

20505.215 -> that your user experience is not hindered.

20507.683 -> Let me give you a guy's an example suppose you make

20510.838 -> an application right

20512.1 -> and for making it secure you think okay

20514.596 -> after every 3 or 4 minutes,

20516.34 -> I'll ask the user for a password right

20518.729 -> from the security point of view.

20520.724 -> It seems okay,

20521.638 -> but from the users point of view it Actually hindering

20525.1 -> his user experience.

20526.573 -> Right?

20527.035 -> So you should have that artist in you

20529.434 -> that you should understand when to stop or till

20532.8 -> where should we extend your security techniques

20536.148 -> and also you should be creative as to what security techniques

20540.435 -> can be implemented

20541.7 -> so that the user experience is not ended.

20544.075 -> For example, there is a two-step authentication you get there

20547.604 -> when you're logging into your Gmail account, right?

20550.545 -> So if you know your password

20552.1 -> that is not enough you should have Have an OTP as well to log

20556 -> into your Gmail account, right?

20558.053 -> So this might be hindering with user experience

20561.1 -> to some extent but it is making your application secure as well.

20565.5 -> Right?

20566.3 -> You should have a balance between your science

20569.3 -> and the art part

20570.3 -> that you're applying on cloud security moving on.

20573.376 -> Let's now discuss the process of troubleshooting a threat

20577.265 -> in the cloud.

20578.1 -> So let's take an example here.

20580.041 -> So like you're using Facebook right

20582.192 -> and you get a random message from Person saying there is

20585.785 -> some kind of stories like you usually get

20588.329 -> that by using Facebook right

20590.1 -> that such and such thing happened and click here

20592.9 -> to know more right you get the similar kind of message here

20596.2 -> and by mistake you actually click on that link.

20599.2 -> You didn't know that it's a Spam and you click on that link.

20602.3 -> Now what happens is all the users

20604.7 -> that are there are all your friends on the Facebook

20607.2 -> Chat gets that message,

20609.4 -> right and they get furious as

20611.504 -> to why this kind of spam messages.

20613.9 -> They're in their inbox, right

20615.687 -> and you get scared.

20616.851 -> Now you get angry as well

20618.223 -> and you have to bring your frustration out on Facebook.

20621.4 -> So you contact Facebook and it get to know

20623.586 -> that they already know the problem

20625.356 -> and they're already working on it and then near to this leash.

20629.1 -> Now.

20629.389 -> How did they come to know

20631.2 -> that there is this kind of problem

20633.321 -> and needs to be solved.

20634.9 -> Right?

20635.6 -> So basically Cloud security is done in three stages.

20639.3 -> So the identification process

20641.4 -> or the thread identification process is done.

20644.2 -> Three stages the first stage is monitoring data.

20647.827 -> So you have ai algorithms,

20649.827 -> which know what a normal system behavior is

20653.034 -> and any deviation

20654.3 -> from this normal system Behavior creates an alarm

20657.8 -> and this alarm is then monitored by the cloud experts

20661.1 -> or the cloud Security Experts sitting over there.

20663.8 -> And there's a thread they see there's a thread they go

20667.296 -> to the next step

20668.257 -> which is gaining visibility, right?

20670.374 -> So you should understand what caused that problem right?

20673.8 -> And Or who caused that problem precisely.

20676.363 -> So your Cloud Security Experts look for tools,

20679.5 -> which give them the ability to look into the data and find

20683.198 -> or pinpoint that statement or pinpoint that event

20686.312 -> which caused this problem.

20688.9 -> Right, so that is done using gaining visibility stage.

20693.4 -> And once we have established, okay.

20695.828 -> So this is the problem

20697.399 -> then come stage 3 which is managing access.

20700.6 -> So what this basically will do is it will give you a list

20703.923 -> of users in case we are tracking the

20706 -> who will give you a list of users who have access

20709.5 -> and we will pinpoint the user who did that,

20712.6 -> right and that user can be wiped

20715 -> out of the fit system using the managing exist age.

20718.7 -> Eight.

20719.7 -> So these are the stages

20721.4 -> which are involved in Cloud security Now

20725.1 -> if you were to implement these stages in AWS,

20728.01 -> how would we do that?

20729.4 -> Let's see that

20730.8 -> so the first stage was monitoring data, right?

20733.835 -> So if you have an application in AWS and you are experiencing

20737.738 -> this same kind of thing,

20739.323 -> what will you do for monitoring data?

20741.8 -> So you have a service in AWS called AWS Cloud watch now,

20745.7 -> what is AWS Cloud watch?

20747.422 -> So basically it's a Monitoring tool

20749.881 -> so you can monitor your ec2

20751.755 -> and your other AWS resources on cloudwatch

20754.6 -> how you can monitor them.

20756.071 -> You can monitor the network in network out of your resource

20759.491 -> and you can also monitor the traffic

20761.429 -> which is coming on to your instance, right?

20763.9 -> You can also create alarms on your Cloud board.

20766.9 -> So if there's deviation from normal system Behavior,

20770 -> like I said,

20770.728 -> so it will create an alarm for you.

20772.723 -> It'll escalate the event and alert you about that thing

20776.078 -> so that you can go on around and see See what

20779.227 -> that problem actually is, right.

20781.3 -> So this is cloud the monitoring tool, right?

20784.3 -> So this was about AWS Cloud watch.

20786.662 -> Let me give you a quick demo of how the AWS Cloud

20790.3 -> watch dashboard actually looks like Okay.

20793.7 -> I said this is your ews dashboard.

20796 -> So now for accessing cloudwatch,

20798 -> you can go under the management tools here is cloudwatch

20801.437 -> Will click on cloudwatch.

20804.3 -> Now over here you can monitor anything right?

20806.9 -> We'll go to Matrix.

20808.9 -> And you can see there are three Matrix over here.

20811.9 -> You can monitor your EBS.

20813.5 -> You can monitor your ec2.

20815.148 -> You can monitor your S3 right now suppose.

20818.251 -> I want to monitor my ec2.

20820.7 -> So as you can see,

20821.765 -> so I have two instances running in my easy to one is called

20825.2 -> for batch instance.

20826.6 -> And the other is called WPS instance right now.

20829.5 -> These are all the metrics which are there

20832 -> so I can check Matrix for my WPS instance

20834.952 -> for network in I can check the disk read Ops.

20838.2 -> So let me select the network out metric

20841.1 -> and they'll be a graph over here so I can see this graph

20845 -> and as you can see between six o'clock and 6:30,

20849.274 -> I experienced.

20850.6 -> Search in my traffic, right?

20854.4 -> So basically this is

20855.9 -> how you monitor your instance in cloudwatch.

20859.1 -> And you have all these default metrics to check

20862.8 -> how your instance is doing and you know AWS, right?

20868 -> So this is what cloud watches.

20870.215 -> You can also set alarms here, right?

20872.8 -> So if you go to alarms click on create alarm.

20877.1 -> You go too easy, too.

20879.6 -> And you can select your metric

20881.1 -> from over here now select a discrete bite.

20883.9 -> So we're now once I do that will ask me

20886.516 -> if there's a Time range

20888.1 -> to which I want to monitor that instance, right?

20892.2 -> Okay, let's not set.

20893.2 -> Any time Ray.

20894 -> Let's click on next.

20895.5 -> So when I click next you will be prompted with this page

20898.761 -> so you can set your alarm name.

20900.6 -> You can set your alarm description here and then

20903.3 -> you can specify that for what read rights number.

20906.5 -> You should get this alarm for right?

20908.1 -> So you'll be setting that.

20909.4 -> Over here after that we will go to actions.

20912.2 -> So once an alarm is triggered.

20914.3 -> We should that alarm go who should that alarm go to right?

20917.652 -> So you can see as I said over here.

20919.6 -> Now whenever the state is alarm, right?

20922.5 -> What should we do?

20924 -> So when the state is alarm

20925.529 -> you can send you a notification to your SNS topic now,

20928.4 -> what is this nation SNS?

20929.805 -> So basically it's a notification service

20932.2 -> will be discussing what SNS is in the next session.

20935.8 -> Don't worry if you don't understand so basically for now

20938.4 -> what you can understand Is that SNS is a protocol

20941.2 -> where a new set

20942.1 -> if you get a notification

20943.4 -> what to do with that notification or whom to send

20945.8 -> to that notification, right?

20948.205 -> So if there's a topic called notify mean SNS,

20951.669 -> so in notify me,

20952.7 -> I have configured an email address.

20954.4 -> That is my email adress

20955.8 -> that whenever a notification comes to the SNS service

20960.3 -> or the notify me topic to be precise.

20963.3 -> It sends an email to me right with that message.

20966.6 -> So I will get a message with this alarm.

20969.113 -> Such and such thing that has happened in cloudwatch.

20972.469 -> Now you do whatever is required.

20975.1 -> The other thing

20975.85 -> that you can do over here is in the same as soon as topic.

20978.9 -> You can also configure

20980.4 -> Lambda function to be executed right now

20983.2 -> what that Lambda function will do so say suppose

20986.3 -> I configure the metric to be of CPU usage.

20989.5 -> Right and I say

20990.643 -> whenever 40-person metric is crushed create an alarm

20994.435 -> or like go to an alarm State and it notifies the SNS know

20998.9 -> Or if I mean topic about this in the notify me topic,

21002.358 -> I can configure a Lambda function to clear

21004.9 -> all the background processes in that easy ruins, right?

21008.469 -> So if I do

21009.13 -> that the CPU usage will automatically come down, right?

21012.7 -> So this becomes a use case

21014 -> that you want to launch a Lambda function,

21016.4 -> wherever your CPU uses goes beyond 40 percent, right?

21019.496 -> And hence.

21020.296 -> This is the way you would do it.

21022.029 -> So this was about cloudwatch.

21023.619 -> There's nothing much to it.

21025.1 -> You create alarms and you monitor metrics, right?

21028.4 -> Moving ahead and let's move on to the second process

21032.2 -> which is gaining visibility.

21035.4 -> So for gaining visibility,

21036.7 -> basically, you have to track your whatever activity

21040.579 -> is happening in your AWS account.

21043.6 -> So this is service in AWS called Cloud trade, right?

21047 -> So the cloud rail service is basically a logging service

21050.5 -> where in each and every log to each

21053.115 -> and every API call is made now.

21055.83 -> How is it useful?

21057.3 -> Let's talk about the security perspective.

21059.711 -> Right?

21060.5 -> So your hacker got access to your system,

21063.1 -> so you should know how he got eggs.

21065.3 -> Your system.

21066.1 -> So if you have a timeframe say he got access to your system

21069.8 -> or you started to face the problem say

21072.1 -> around four o'clock,

21073.1 -> right so you can set the time between two o'clock

21075.811 -> and whatever the damage right now and monitor

21078.4 -> what all has been going around and hence.

21081.127 -> You can identify the place

21082.9 -> where that hacker got access to your system right now.

21086.7 -> This is the part

21087.673 -> where you will get to know who that person actually is

21090.9 -> or you can isolate the problems or which calls

21094 -> that so if you take Q from our Facebook example over here.

21098.217 -> You can actually pinpoint

21100.066 -> who is responsible for those spam messages

21103.5 -> because you all have those logs right you will see the origin

21106.5 -> of those messages now,

21108.4 -> once you've done

21109.5 -> that the next step is managing this guy out of the system

21113.517 -> or wiping this guy out of the system.

21116.1 -> But before that let me show you guys

21118.2 -> how cloud trail actually looks

21120 -> like so let's go back to our ews dashboard

21124.4 -> and go to Cloud tree service.

21127 -> So I again under the management tools.

21129.6 -> You have the cloud forest service you click

21131.8 -> on the cloud resources and you will reach this dashboard.

21135.2 -> All right.

21135.7 -> So here you have the logs.

21138 -> So as you can see you can set the time range here,

21141 -> but I'm not doing that.

21142.215 -> I'm just showing you the logs.

21143.8 -> So even for logging into my console it is showing me

21147.7 -> that I'm logged into my console at this time

21150.961 -> on this date, right?

21152.5 -> So every event is logged guys.

21154.9 -> Every event that is happening

21156.6 -> on your ews console is being blocked.

21160.051 -> So let's talk about the S3 bucket.

21162.7 -> So somebody deleted a bucket

21164.576 -> and that has again been locked, right?

21167.162 -> So it happened at 7:30 8:00 p.m.

21169.4 -> On 28th of March 2017, right?

21172.7 -> So any activity any kind of activity,

21175.469 -> which happens in AWS would be logged where?

21179.6 -> Okay guys, so this is about Cloud Trails.

21181.9 -> Let's go back to our slide and move ahead and play session.

21184.9 -> So like I said,

21185.9 -> so now you have identified who is responsible

21189.3 -> for your problem.

21191 -> Right?

21191.5 -> So now the next step is managing access, right?

21194.9 -> So now you should be able to throw that person

21198.4 -> or remove that person from the system.

21200.9 -> So most of the times what happens is like

21203.252 -> if we take our Facebook use case,

21205.1 -> so basically there was a user who triggered that problem right

21208.981 -> so too Things that you have to do is first of all,

21212.1 -> you have to remove that spam from a system.

21214.8 -> So you've got to know where it originated.

21217.1 -> So now you start wiping it after that.

21219.854 -> You have to D by that user from doing it again, right?

21223.8 -> So from The Source,

21225.11 -> you'll get to know who that user is now using managing access.

21229.4 -> You will actually get access to do all that right?

21232.9 -> So if you talk about AWS this service is called AWS.

21236.741 -> I am so what AWS I am does

21238.7 -> is It basically authenticates that particular service.

21242.2 -> Now, you are a root user.

21243.681 -> Right so you can do anything.

21245.4 -> But what if you have employees

21246.9 -> and obviously all employees will not have all the rights right.

21250.751 -> Now.

21251 -> What if you want to give granular permissions to

21253.9 -> your employees now for like in our example,

21256.5 -> what if one specific employee

21258.571 -> is capable to track down this problem right or track down

21262.497 -> what has to be done?

21263.9 -> So you can give that particular person the rights

21266.9 -> how using I am right?

21268.853 -> So I M is used to provide granular permissions.

21272.6 -> It actually secures your access

21274.915 -> to the ec2 instances by giving you a private file

21278.7 -> and also it is free to use right.

21281.3 -> So, let's see how I am is used.

21284.5 -> So let me go back to my AWS console.

21289.3 -> Okay.

21289.604 -> I said this is my AWS dashboard.

21291.589 -> I will go to the security identity and compliance domain

21295 -> and then click on I am.

21297.5 -> Right now over here.

21299.7 -> I'll click on rolls.

21301.5 -> Now.

21301.8 -> I can see all the roles

21303.4 -> which are there in my I am right?

21305.733 -> So since I would have

21307.232 -> identified which role is creating a problem,

21310.3 -> so I'll go to that role.

21312 -> So for example,

21313.4 -> I have a problem in save AWS elastic Beanstalk easy to roll,

21317.8 -> right I click on this now

21321.6 -> once I click I will be getting this screen.

21324.76 -> So now I can see the The trust relationship success advising

21329.2 -> the revoke sessions, right?

21331.2 -> So I'll go to revoke sessions and I click

21333.2 -> on the book active sessions.

21335.1 -> And hence.

21335.9 -> I will be able to wipe out that user from accessing

21338.9 -> my AWS resources, right?

21340.715 -> So this is how you use I am guys are now one more thing

21344.8 -> that you can do over here is you'll go back

21346.9 -> to your dashboard go to Rose.

21349.2 -> Now I get told you guys you can actually create

21351.5 -> a role for a person

21353 -> who would be able to access restricted things on.

21357 -> Your AWS account, right?

21358.5 -> So let me quickly show you how you can do that.

21361.055 -> So you will click on create new role

21363 -> and you will give you a roll some name.

21365 -> So let's give it hello over here.

21366.7 -> Right click on Next Step go to roll for energy provider access.

21371.9 -> Right, and now you can select

21374 -> how that user of yours will be accessing your AWS account.

21377.9 -> Right?

21378.2 -> So allow users

21379.108 -> from Amazon Cognito Amazon Facebook Google ID.

21382.1 -> All right, so let's select this now.

21384.5 -> Let us select Facebook and let's give it some random

21388.332 -> application ID, right?

21389.9 -> So anyways not going to create this role.

21392.3 -> I'm just telling you guys how to do it.

21394.2 -> Right?

21394.52 -> So basically you get an application ID

21396.5 -> by Facebook over there.

21398.1 -> You'll be since you are using Facebook thoughts.

21401.5 -> Educate that guide to your AWS account.

21404.6 -> You'll get an application ID

21406.072 -> by going on to graph at facebook.com.

21407.965 -> You can do all of that over there.

21409.7 -> Okay, so that is not the concern you'll enter the application ID

21413.3 -> and click on next step.

21415.3 -> Right?

21415.5 -> So you get the policy document.

21417.3 -> So whatever you configured

21418.6 -> in your text boxes has actually been created in a Json file,

21423.1 -> right so you don't have to edit anything over here.

21425.8 -> Click on next step.

21427.8 -> Now you have to attach a policy now,

21429.936 -> what are the policies of policies basically

21432.5 -> what all permissions you want to grant that user.

21435.5 -> Right?

21436 -> So if you want to Grant him the execution role

21438.875 -> for Lambda you can do that.

21440.599 -> You can grant them the S3 execution roll, right?

21443.6 -> So whatever policy

21444.609 -> that you create you can actually create a policy near I am right.

21448.2 -> I'm not going much in details of this

21450.7 -> because all of this is covered in your I am session,

21454.236 -> but I'm showing you guys

21455.9 -> because I just told you guys This can be done

21458.561 -> to let me show you how it can be done.

21460.9 -> Right?

21461.4 -> So you'll select whatever policy want

21463.747 -> and click on next step and review it

21466.1 -> and create that rule.

21467.6 -> This is it guys right so you can actually select a policy

21471.851 -> whatever policy you want that role to have and hence.

21475.9 -> So policies basically

21477.1 -> a permission that you want that role to have.

21479.5 -> So if you get the permissions it to just review your instances,

21483.337 -> he'll be only able to review your instances.

21486 -> Okay, one more thing.

21487.122 -> I want to make Make clear is

21488.684 -> that you don't have to give your security credentials

21491.6 -> to that kind anymore

21492.8 -> because now you'll be specifying

21495.6 -> that user can will be able to connect to Facebook.

21498.3 -> Okay.

21498.8 -> So also you have a part here wherein you can specify

21503.3 -> what specific user can access it right

21506.564 -> so I can type in my name here.

21510.399 -> And if I'm being logged in

21512.4 -> through Facebook is my username is him

21514.701 -> and Shauna only then I will be able to connect

21517.5 -> to my AWS account right now.

21520.6 -> This is ID right I can also set the local parameter.

21524.8 -> Right so idea

21525.774 -> I think is fine wherein you will be adding the ID of the guy

21530.2 -> whom you want this AWS account be accessed by right?

21534.3 -> So you all have Facebook IDs, right?

21536.6 -> So you all have to just punch in your Facebook IDs.

21539.3 -> We're here click on next step

21540.9 -> and then you'll be able to access this AWS account.

21543.841 -> If I create this role right now with the policies

21546.6 -> that I will be attaching to your role.

21548.6 -> Right?

21549.1 -> So this is how you use I am guys.

21551.267 -> Let us go back to our session.

21553.8 -> Okay.

21554.2 -> So these are the three services guys.

21556 -> So you have I am you have cloud trail

21558.386 -> and you have cloudwatch using which you can control

21561.7 -> or you can actually see

21563.415 -> what is going on in your AWS account.

21569.2 -> So let's go ahead

21571.4 -> and start with today's session with the first topic

21573.7 -> which is why do we need access management?

21576.505 -> All right, so to discuss this topic,

21578.9 -> let's understand it using an example say you have a company

21582.9 -> in which you have a server

21584.2 -> and the server has everything in it.

21586.5 -> It has all the modules in it and it gives you

21589.3 -> the it gives different users the permission to use

21592.6 -> the different servers right now in your company.

21596 -> First of all,

21596.65 -> you should have an administrator which will have all All

21599.6 -> the rights to to access the server, right?

21603.2 -> So nobody in the today's

21605.5 -> it World works on the root account, right?

21607.598 -> So there has to be an administrator account.

21609.8 -> So first we will create an administrator account

21612.344 -> with all the permissions now tomorrow say

21615 -> a UI developer comes

21616.2 -> into your company right now A UI developer will only work

21619.8 -> on the graphical tools, right?

21621.6 -> So he should only be allowed the graphical tools

21624.029 -> and not some other tools.

21625.6 -> Maybe he shall not be given the internet access.

21629.4 -> Or something like that, right?

21630.9 -> Maybe he's not giving the PowerPoint access.

21633.1 -> Maybe he's not given

21634.247 -> some folders access some drives access anything like that.

21637.6 -> So all of that can be defined in the server by the administrator

21641.9 -> and specific rights

21643.252 -> will be given to a UI developer right similarly if to

21647.466 -> if after that a business analyst comes in

21650.4 -> so he should only be able to access the analytics module

21654.5 -> which is there in your soul, right?

21656.1 -> He should not be able to get into the UI development.

21659.3 -> In part, or he's not be able to see the other aspects

21663.1 -> of what is there in your server?

21664.7 -> Right?

21665.123 -> So each and every user each every rule

21668.535 -> will have specific rights assigned to them.

21671.6 -> Right?

21672.252 -> And this is done by policies

21673.9 -> which are in turn given by administrators.

21677.1 -> Right?

21677.682 -> So this is what access management is

21679.9 -> that giving each role the specific rights

21682.708 -> that they deserve and this is

21684.6 -> what we are going to accomplish today in AWS, right?

21687.815 -> So this this is We need access management.

21690.405 -> Let's go ahead and understand.

21692.3 -> How can we accomplish this in AWS?

21694.6 -> Right?

21694.978 -> So as to accomplish this in AWS,

21697.038 -> you need a service called I am you have a service called I am

21700.9 -> which uses this concept of access management

21706.4 -> and allows you to give it to your users who are going

21710.155 -> to use your account.

21712.1 -> All right.

21712.8 -> So what is I am

21714.8 -> so I am is basically a service from AWS using

21718.291 -> which you can give permissions to different users

21721.911 -> who are using the same AWS account

21724.449 -> that you have created, right?

21726.68 -> So in a company like in any company be it,

21730.5 -> you don't have to have two or three AWS accounts.

21732.9 -> You can have one AWS account

21734.7 -> on which a number of people can work.

21736.9 -> Right?

21737.2 -> For example, you can Define

21739.4 -> that maybe a developer would like to Work

21742.4 -> on your AWS account

21743.8 -> and he should only have the ec2 instances

21746.4 -> or you should only work on the ec2 instances

21748.63 -> you decide that

21749.447 -> right?

21749.8 -> So you can only Define you can define a policy like that

21752.865 -> that only the devel

21754.042 -> the developers will only be able to access the ec2 instances

21757.7 -> on AWS account.

21758.9 -> Similarly if say database administrator comes in

21763.32 -> so you should be able only able to access DB instances

21766.859 -> on your AWS account

21768.094 -> and so on right so all of that is possible using I am

21771.4 -> but what I am is not only

21772.9 -> about creating users and creating policies.

21775.402 -> It's more there is more

21776.664 -> to I am right and hence will be discussing the different

21779.9 -> components of I am now

21781.5 -> so let's go on and see what are the different components.

21784.3 -> So there are basically four different components

21787.065 -> in I in the I am service.

21788.41 -> So the first service is user then we are groups

21790.874 -> then we have Rose

21791.737 -> and then you have policies right?

21793.44 -> So the way we are going to go about these are first

21796.1 -> I'm going to explain you each role on each service

21799.2 -> in I am each component

21800.5 -> and I am and then we're going to see how Can execute them

21803.4 -> or create them and the AWS console,

21805.61 -> right?

21806 -> So let's start with the users.

21808.4 -> So the very first time you actually create a AWS account

21813.1 -> that is basically the root account

21814.75 -> that you have created, right?

21816.4 -> So there is no user inside it.

21818.5 -> So why do we basically need a user you need a user

21822.9 -> because you are supposed to give permissions to someone right?

21827 -> So say I first of all want to give administrator Rights

21832.3 -> to a user right?

21833.6 -> So you understand you have to have an entity first

21836.615 -> to which you can assign permissions, right?

21839.2 -> So these entities are called users on E. Wa so any person

21842.854 -> who wants to access your AWS account has

21845.4 -> to be added as a user in I am

21847.3 -> and then you can attach different policies

21849.7 -> on to that user.

21850.6 -> Right?

21851.171 -> So this is what user is all about.

21853.1 -> Let me go to my AWS Management console and show you

21856.9 -> how you can create a user in I am.

21860.2 -> All right, so give me a All right guys,

21865.3 -> so this is my AWS sign sign in page.

21869.4 -> All right.

21870.082 -> So this email ID when you log in through your email ID

21873.578 -> and your password

21874.7 -> that is basically your root account.

21876.866 -> So what I'm going to do right now is I'm gonna log

21879.9 -> in using my root account

21882.1 -> and first create a admin account for myself.

21885.8 -> Alright guys, so you should never work in your root account.

21888.9 -> You should always have an administrator account

21891.6 -> through work in the root account should only Used

21894.8 -> when there is an emergency say you have been locked

21897.6 -> out of our administrator account

21899.417 -> only then you should be using your route accounts.

21902.3 -> The first thing that you should do

21904 -> when you enter the root account is go to I am

21907.5 -> which is just right here go to I am and then you will have

21911.9 -> this dashboard thing right over here.

21914.408 -> You can see there is a thing called users.

21917.437 -> You will click on users and you will click on add user.

21921.8 -> All right, so now it will ask you for the The username

21924.837 -> so you can provide a username

21926.5 -> say I'll add my name first

21928.4 -> so that be hemanth, right and what what kind

21932.4 -> of access do I want to give to this particular user?

21935.9 -> So there are basically two kinds of access

21938 -> that I can give first is the AWS Management console axis,

21941.7 -> and then we have the programmatic access, right?

21944.6 -> So what is these two so

21946.4 -> if you want to so there are basically

21949.073 -> two ways you can access the AWS resources right?

21952.633 -> You can either access.

21954.315 -> Using apis that is using

21956.4 -> your code say you have created an application

21959.4 -> which is interacting with your AWS resources.

21962.4 -> Right?

21962.771 -> So in that case

21963.7 -> if you're interacting with the apis using the API is

21967.366 -> that is called the programmatic access,

21969.8 -> right secondly is

21970.933 -> the AWS Management console access that is

21973.6 -> when you are using

21975.1 -> the AWS website to actually deploy resources or create

21979.8 -> or create or remove policies or whatever, right?

21983.415 -> So that That is called the AWS Management console axis.

21987.483 -> So for my user I'd be giving it both the accesses

21991.1 -> that is programmatic axis and the Management console axis.

21995.6 -> Also, there is

21996.443 -> when you enable the programmatic access programmatic access,

22000 -> basically you get the access key and the secret key as well.

22003.8 -> What are these I will be explaining you in a bit.

22006.5 -> All right, so we have selected both of these options

22009.4 -> and then move ahead to choose the password.

22011.8 -> So do you want an auto generated password?

22014.023 -> A custom password.

22015.023 -> I'll choose a custom part for password

22017.2 -> since I'm creating account for myself, right?

22021.4 -> So I'll choose a custom password

22023.6 -> and do I want to reset the password on the first login?

22026.776 -> No, I don't want that.

22028.117 -> So I'll click on next permissions, right?

22030.673 -> So what kind of permissions

22032.4 -> do I want my account to have I will become drink configuring

22036.386 -> that over here.

22038 -> So as of now there are no groups,

22040.461 -> there is no existing user that I can copy from.

22044 -> So I'll attach existing policies.

22045.834 -> And since I want to attach the administrator access

22048.7 -> that is the first policy over here.

22050.7 -> I'll select that and click

22052.516 -> on next right so you can review all the settings

22055.8 -> that you did over here and click on create user.

22060.1 -> This will create a new user in your AWS account.

22063.453 -> So as you can see,

22064.7 -> I have got my access key ID and a secret access key now guys,

22069.6 -> the secret access key.

22070.934 -> You only get to see

22072.144 -> one time only one time when Created your account.

22075.166 -> So it is essential

22076.3 -> that is tore your access key and secret access key

22079.4 -> once you get this page.

22081 -> All right, let me store it quickly.

22084 -> So this is my access key ID why we are copying it.

22088.2 -> You'll get to know during the session.

22091.5 -> Don't worry and my secret access key,

22093.9 -> which is this let me copy this and paste it in the notepad.

22098.8 -> All right, so don't worry.

22100.348 -> You might be thinking

22101.6 -> that I've exposed my secret key to you.

22104.148 -> So I will be deleting this account afterwards

22107.1 -> so you don't have to worry about that.

22109 -> All right, so I've got my access key ID

22111.8 -> and my secret access key.

22113.567 -> So that is done.

22114.642 -> Now.

22114.929 -> What I'll be doing is I'll be logging out

22117.8 -> from my from my root account and logging in this user account

22123.687 -> that I just created.

22125.225 -> All right.

22125.725 -> So one more thing that you have to be very careful of

22128.784 -> that you will not be logging in through the same login page

22131.951 -> that is just saw right so you'll have to log

22134.3 -> Through a different login page now and the URL

22138.4 -> for that is this right?

22140.7 -> So you will be logging in through this link as a

22144.276 -> from now on so what whenever you create a user

22147.7 -> if you want them to log into your account,

22151.1 -> you have to give them this link to log into right?

22154.853 -> So let us copy this link over here and log out

22158.3 -> from a root account.

22163.5 -> All right.

22164 -> So I've logged out I'll close this and I'll come here

22168 -> and go to this particular link.

22175.5 -> All right.

22176 -> So once you reach this particular link,

22177.865 -> it will be asking

22178.7 -> you the account name which will be self filled by your link.

22181.8 -> Right?

22182.1 -> So you have to give your username now,

22184.1 -> which is hemant and then

22185.9 -> the password so I'll type in the password that I've given it.

22191.3 -> and click on sign-

22192.3 -> in So now I have basically

22199.8 -> signed in two months to mature to the user

22202.8 -> that I've just created on my route account.

22205.2 -> Right?

22205.5 -> So I no longer have to use my root account.

22208.4 -> I can basically lock away my root account

22211.002 -> for emergency purposes.

22212.5 -> I'll be using my administrator account from now

22215.3 -> on I can do everything

22216.8 -> from administrators on that could be done

22218.9 -> from a root account as well.

22220.7 -> But there are cases

22221.933 -> where in you get locked out from your administrator account

22225.8 -> in that cases you will be Notable success rate

22229.761 -> so moving on guys,

22231.2 -> so I'll go to I am not

22232.9 -> so as you can see we have created a user

22236.1 -> and we have logged in to that user.

22238.4 -> And if I go to I am now you can see

22241 -> that it will show that one user has been created.

22246 -> That is here.

22247.2 -> All right, so let's get back to our slide

22250.6 -> and discuss the next component.

22252.9 -> All right, so we've discussed

22254.3 -> what our users let's move on to the second component

22257 -> which are groups.

22258 -> All right.

22258.6 -> So whenever you create users they can also

22261.7 -> be combined into groups.

22263.6 -> Now, why do we need groups?

22265.4 -> We need groups because say let's take an example.

22268.678 -> So say you have five users

22270.4 -> and these five users have to be given identical axis.

22273.3 -> Right say these five users belong to the development.

22275.9 -> And the developing team has to have some common access

22280.1 -> that they all will have right.

22281.814 -> Now one way of doing this would be

22283.7 -> that I would go to each

22285.217 -> and every user and attach a policy

22287.4 -> that they need right the smart way to do this

22290.434 -> would be to to include them inside one group

22293.4 -> and to that group.

22294.617 -> I will once only

22295.7 -> once I will attach the policy and it will apply

22298.791 -> to all these five users, right?

22300.794 -> So these are why groups are very important now

22303.7 -> how we can create groups.

22304.95 -> Let me shed a light on.

22306.1 -> On that so you will go

22308 -> to you can see you can click on groups over here.

22311.1 -> And what you'll do is basically is you'll click

22313.5 -> on create new group, right?

22315.8 -> So, let me give the group name as live demo.

22320.603 -> All right, and I click on next step.

22324.784 -> Now lastly the policy

22326.4 -> that I want to attach to this particular group.

22329.305 -> All right, so say for example,

22331.2 -> I just want this group to be able to access

22334.4 -> the S3 service from AWS.

22336.9 -> So what I'll do is I will select the policy

22339.4 -> which says Amazon S3 full access and I'll click on next step.

22344 -> Now this policy basically tells you that you

22346.8 -> can only use the S3 service in the Management console

22350.717 -> and no other service.

22352.4 -> All right, so I'll click on create.

22354.6 -> Whoop and now whatever whichever user I will be putting

22359.1 -> in putting inside.

22360.5 -> This group will have this property.

22362.9 -> All right, so I don't have to configure the policy

22365.9 -> for any user now.

22367.2 -> So what I'll do is I'll create a new user now.

22370.8 -> So say I create a new user saying test.

22374.5 -> All right,

22375.3 -> and then I'm not giving him the programmatic access.

22379 -> I'm just giving him the Management console axis.

22381.8 -> All right, I'll click on this and I'll give

22384.8 -> it a custom password.

22387.202 -> And then I don't want him to reset his password

22390.74 -> and click on next.

22393.5 -> Right, and now it is asking me

22395.6 -> whether I want to include it inside a group.

22398.4 -> So yes, I do.

22399.21 -> I want to include it inside the group

22401.365 -> that I've just created and I'll click on next

22404.4 -> and review all the settings are adjusted

22406.7 -> and click on create user.

22410.8 -> All right.

22411.388 -> So the test account has just been created now

22413.9 -> as you can see guys in the case of my account,

22417.3 -> which I created.

22418.1 -> I got an access key and a secret access key, right?

22421.5 -> So in this case,

22422.3 -> I'm not getting any

22423.3 -> because I didn't select the programmatic access only

22426.3 -> when you select the programmatic access it will give you the key

22429.1 -> so that your application can actually interact

22431.35 -> with the services that you have launched.

22433.3 -> All right,

22433.978 -> so I have have created a test user successfully.

22437.165 -> Let's log into this test user.

22441.3 -> so I will type in the URL that has been given to me.

22453.5 -> Right now when I reach this page,

22456.4 -> I'll enter the username as test and the password as

22460.3 -> what I have entered right and I click on sign in.

22465.907 -> Now with this you can see that.

22469.8 -> I will now be able to see the Management console

22472.564 -> the Management console will exactly look like

22475.1 -> how it was used to see

22476.7 -> how I used to see it in my root account

22479.578 -> or my administrator account.

22481.8 -> But when you will try to access say a service,

22485.3 -> which you have not been assigned to say,

22487 -> for example, I only have access to S right now

22489.56 -> because I've deployed it

22490.925 -> in the group where it has only the access to S3.

22493.6 -> If I try to go inside easy to let's see what'll happen.

22501.438 -> Right.

22501.9 -> So it says you are not authorized

22503.9 -> to describe running instances.

22505.8 -> As a matter of fact,

22507.046 -> I'm not authorized to see anything on my ec2 page.

22510.3 -> Alright, so that is

22511.9 -> because I cannot I don't have access to the ec2 dashboard.

22517 -> But let's see if I can see the S3 dashboard.

22520.2 -> So I'll quickly go to S 3 and if I have the S3 axis,

22526 -> I will be able to see all the buckets which are there in -

22529 -> 3 And yes, I do.

22532.1 -> So let me go inside a bucket

22534.8 -> and delete something so that all right.

22539 -> Let me delete an object from this particular bucket.

22544.7 -> So yes, I can lead it.

22546.73 -> All right, so let me check if what if what happens

22550.6 -> if I delete or II detach this particular policy

22556.084 -> from that group?

22558 -> All right.

22558.8 -> Let's see what happens.

22560.607 -> So I will go to I am and I will go to groups.

22565.4 -> I'll go to this particular group and I can see

22568.549 -> that the policy is listed over here.

22571 -> What I do is I click on detach policy and let's see

22574.927 -> what happens now, right?

22576.828 -> So I'll go to Management console.

22580.3 -> So on if now I try to exercise 3.

22584.7 -> It will show me that access is denied.

22587.434 -> Right so I no longer have access

22589.758 -> to the S3 service on my AWS console.

22592.4 -> So this is how you can control access to different users.

22596.6 -> You can revoke access you can include access

22599.6 -> right you can do all of that and I am right.

22602.6 -> So let us come back to our slide to discuss our next component or

22606.6 -> as we've discussed

22607.535 -> what our users we have discussed.

22609.2 -> What a groups now let's come back come down to rules.

22612.4 -> All right, so rules are Similar to users

22616.1 -> but roles are actually assigned to Applications.

22618.8 -> All right, so users are actually assigned to people right?

22621.8 -> So whenever you have a developer in the company,

22624.225 -> you will have sine M the developer rules, right

22626.6 -> but when you have

22627.8 -> rules rules are basically assigned to Applications,

22630.8 -> how let me explain you say you create an ec2 instance and

22635 -> inside that needs,

22635.912 -> you know instance you're hosting your web application.

22638.6 -> Now that web application has been has been designed

22641.1 -> in such a way

22641.875 -> that it has to interact with your S3 service.

22644.5 -> Is for example that will be doing to a will be

22646.318 -> I will be showing you the demonstration today for this.

22648.5 -> Right.

22649 -> So say that application has to interact with the S3 service.

22653.5 -> Now if I want to want

22655.3 -> that application to interact with the S3 service,

22657.7 -> I have to give it permissions and to give it permissions.

22661 -> I will use rule

22661.949 -> so I will create a rule wherein I will specify

22664.8 -> that this role can access the S3 service

22667.399 -> and I will attach this particular role

22669.9 -> to that particular e0 instance in which

22672.474 -> my application is hosted

22674.136 -> and in Kiss my application will be able to interact

22677.6 -> with the S3 service, right?

22679.43 -> It might sound complicated guys,

22681.6 -> but it is very easy to implement.

22683.8 -> Let me show you how so

22685.323 -> what I'll do now is I'll go back to my Management console

22689.202 -> which is here.

22691.1 -> All right, I'll go to the dashboard and say

22695 -> I will go to rolls now.

22699.1 -> All right, so I'll create a new role now roles can be assigned

22703.8 -> to any either Lewis service which is listed here.

22707.3 -> What I'll do is I'll assign it to I'll create a rule type

22711.388 -> of easy to write

22712.555 -> so I will select Amazon ec2.

22714.8 -> And what type of role do I want to apply

22718.3 -> to I want to say have the access to S3.

22723.5 -> Right?

22724 -> So I'll select Amazon S3 full access over here

22727 -> and I'll click on next step.

22729.5 -> So, it'll ask me the role name.

22731.15 -> So let me specify the role name

22732.8 -> as Eddie Rekha underscore one right

22735.497 -> and I'll click on create role.

22738.4 -> So with this role has now been created

22741 -> but mind you guys are not attached this role

22743.887 -> to any easy to instance.

22745.5 -> Right?

22745.8 -> So what I'll do now is I'll go to my ec2 console so over there.

22751.758 -> I already have built an issue instance.

22754.8 -> It is stopped.

22755.755 -> So I'll start it and attach this particular policy

22759.1 -> to that ec2 instance.

22762.6 -> Alright, so my ec2 instance name is hemant underscore one.

22766.935 -> So here it is.

22768 -> I go to actions I start this particular instance.

22774 -> Right.

22774.8 -> And what I can do is I can attach the policy

22778.084 -> using instance test settings.

22780.3 -> It says attach or replace.

22782.3 -> I am roll.

22783.55 -> I'll go here.

22784.9 -> I will go to the drop-down and select the role

22788.1 -> that I just created which is a lyric underscored one.

22791.891 -> I'll select that and I'll click on apply.

22795.2 -> Now with this

22796.2 -> what will happen is my rule is now my sorry.

22800.007 -> My ec2 instance is now configured to interact

22804.053 -> with the S3 service in this particular account.

22808.3 -> Alright, so any application

22810.081 -> that I deploy in this ec2 instance will be able

22813.116 -> to interact with the S3.

22815.3 -> Okay, so I don't have to specify any access key

22818.546 -> any secret access key.

22820.3 -> If you're still confused with that be patient.

22822.903 -> We are getting onto where do we actually use these keys?

22826.099 -> And where do we not?

22827.1 -> All right.

22827.9 -> So this is what your roles are all about.

22832.7 -> Right so roles.

22833.7 -> Like I said,

22834.3 -> they are for resources in AWS users are

22837.7 -> for people roles

22839 -> and uses a similar things

22841 -> you attach polled policies on to them

22843.4 -> and they basically identify Particular instance

22846.376 -> or a particular person

22847.8 -> as the owner of that particular service, right?

22851.2 -> So we've discussed what roles are let's move

22853.4 -> on and discuss policies.

22855 -> So if you think about it guys,

22857.1 -> we've actually been dealing with policies,

22859.4 -> right so policies and nothing but permissions

22861.9 -> that you give to your with whatever role

22865.9 -> or user or group that you have created, right?

22868.5 -> So, for example,

22869.571 -> I want to give the ec2 instance axis,

22871.903 -> right so that ec2 instance access is basically a Policy

22875.4 -> that I will be attaching to the user or to the rules.

22878.5 -> All right.

22879.3 -> Let's see how we can create policies guys.

22881.565 -> So I'll go to my Management console.

22883.6 -> I'll go to I am Right.

22887.992 -> So the you can either create policies or you can actually

22892.2 -> use already existing ones.

22894.1 -> So there are a couple there are a couple of policies

22896.5 -> that have already been created in your AWS account,

22900.6 -> but you can go ahead and create your own policy as well.

22904.519 -> Alright, so let me show you how.

22908.7 -> So say for my test account,

22911.3 -> what I'll do is I will go inside test account.

22916.726 -> All right, and I will add permissions.

22921 -> And I will attach existing policies.

22925.3 -> Directly and here I am guys.

22928.5 -> So now you can you can create policies as well.

22932.1 -> So you see the tab over here guys,

22934.4 -> it says create policy.

22935.9 -> So if you feel you're the kind of policy

22937.9 -> that you want to create is not listed over here

22940.2 -> in the default policies.

22941.4 -> You can actually create one

22942.7 -> and creating a policy is very easy guys.

22944.888 -> You just click on create policy and you will see this page.

22948.6 -> All right, so you'll have three options.

22950.6 -> You can either copy and AWS managed policy.

22953.295 -> That is a default policy.

22954.9 -> Can create our own policy by just typing

22957.5 -> in the Json code and if you're not comfortable with coding,

22960.911 -> what you can do is you can use the policy generator.

22963.61 -> Now.

22963.829 -> What is policy generator?

22965.46 -> Let me explain you.

22967.8 -> So with policy generator,

22969.296 -> you just have to select what effect do you want poor?

22972.508 -> Do you want it to allow it or do you want it to deny it?

22975.8 -> Right?

22976.4 -> So say I want to allow the easy to service

22980.7 -> to this particular test account?

22983.7 -> All right, so I'll go too easy, too.

22990.6 -> Right, here.

22991.4 -> It is.

22992.1 -> I selected easy to what kind

22993.567 -> of actions can he perform say I want to give him all

22996.241 -> the actions you can do anything with these two

22998.7 -> and the show's name is basically a particular resource.

23002.1 -> So where they are and you can identify a particular resource.

23005.1 -> So I don't want a particular resource to be assigned to him.

23008.1 -> I want PE can access every resource in easy to write

23012.5 -> so I just add star for all of them right

23015.615 -> and click on Next Step.

23018 -> So with this you

23019.18 -> as you can see it has Automatically created

23022.265 -> a policy document for you.

23024.174 -> All you have to do now is click on create policy.

23029.1 -> And it will create the policy for use

23031.2 -> as you can see there are 18 customer managed policies

23034.2 -> that are now 19 so I can go here and select.

23041 -> T' the policy a policy over here.

23044.7 -> Alright, so if I go to my user now,

23049.8 -> which is test I'm going to permissions.

23056 -> I will just click on add in line police policy.

23060 -> Click on select again Guru ec2.

23066.8 -> select actions all actions right and pull it to Star.

23074.1 -> So I click on ADD statement click on next step

23077.3 -> and click on apply policy.

23079.3 -> So a policy has been applied on the test user

23082.7 -> that it can actually access the ec2 instances now,

23086.359 -> so if I go to my test user now

23088.6 -> which in which I was not allowed to access the ec2 instances,

23093.4 -> I can actually use easy to instances now,

23096 -> so if I go too easy,

23097.3 -> too You can see the Lord give me the access denied thing,

23101.5 -> right so I can access all the instances over here

23105.1 -> as if I was using the root account,

23107.397 -> but only for the ec2 service right?

23109.7 -> If I go to S 3 you can see I will still have

23112.631 -> the access denied page.

23114.9 -> Because I'm not been assigned the access

23117.441 -> to this particular service.

23119.6 -> Alright, one more thing is if what if you add an allow

23123.7 -> and Adonai policy together inside a group

23126.9 -> what will happen then?

23128.336 -> So in that case so since I have allowed easy to access

23131.7 -> what I'll do is I'll deny is you access as well

23134.635 -> in this particular user.

23136.207 -> So I'll click create one more policy

23138.5 -> and I'll say deny I'll select ec2.

23145.711 -> Right as like the actions as all actions.

23148.9 -> I will give the resources all at the statement and click

23152.782 -> on Next Step apply the policy.

23156.2 -> So now I have denied ec2 instances as well

23160.6 -> and created and allowed ecd instance ec2 instances as well.

23164.6 -> What do you think will happen now?

23166.5 -> So if now I try to go too easy, too.

23172.3 -> Let's see what will happen.

23173.888 -> So it will say you're not authorized to use Easy

23176.4 -> to anymore because whenever you creating policy guys,

23180.9 -> you either get the along option or the deny option.

23184.9 -> If you have selected both of them,

23187 -> it will always prefer

23188 -> the least permission that you have given.

23189.9 -> So in our case that is the deny option,

23191.9 -> right so it will always deny the case.

23194.1 -> Even if you have allowed it in the same user,

23196.7 -> right if you have mentioned

23198.319 -> that that particular service has to be denied

23200.96 -> to that particular user.

23202.6 -> Alright, so this was about policies guys.

23206.9 -> Let me come back to my slides.

23208.3 -> So we have discussed what our users

23210.3 -> what a groups for a rose and what apologies let's go

23213.4 -> ahead and discuss the very important part of authentication

23218.7 -> which is called the multi-factor authentication.

23220.997 -> So what is multi-factor authentication guys,

23223.7 -> so multi-factor authentication is basically something like OTP

23228.2 -> that you get when you log into your Gmail account, right?

23231 -> So you enter a Gmail Email ID you enter your password

23234.261 -> and when you click on continue,

23236.2 -> it will ask you for your OTP, right?

23238.204 -> So same as the case here as well.

23240.086 -> You can configure your AWS account in such a way

23242.694 -> that you will enter username.

23244.4 -> You'll enter your password.

23245.852 -> And when you click on login,

23247.5 -> it will ask also ask you for a code

23250.9 -> that has to be given to it.

23252.886 -> Now that code is basically

23254.8 -> the multi-factor authentication thing that we document

23257.528 -> so there are basically two layers of security Now

23260 -> one layer is a password and second layer.

23262.3 -> MC code that will be entering right now with AWS.

23267.2 -> There is an application called the Google Authenticator right

23271.7 -> which you can use to create

23273.463 -> a virtual multi-factor Factor authentication device.

23276.778 -> Now for those of you

23278.074 -> who already are using multi-factor authentication

23281.183 -> in your company's you so there's a thing called gemalto, right?

23285.2 -> So people who work from home

23286.6 -> and they have to connect to the company's Network

23289.2 -> the way you connect it is using a gemalto token.

23292.8 -> And so those of you

23294.1 -> who are from the IT background you can relate to it.

23296.7 -> Right but if you

23297.8 -> want to go through to through a simpler way,

23300.629 -> you can actually create

23301.9 -> a virtual multi-factor authentication device

23305.7 -> and to create that in your AWS is pretty simple.

23310.3 -> You just have to download an application called

23312.6 -> the Google Authenticator on your phone

23314.705 -> and you have to connect that application to your AWS account.

23318.14 -> And that is it now.

23319.18 -> It might sound tough, but it's very simple.

23321.85 -> Let me show you

23322.7 -> how so you you will basically go to your AWS Management console

23327.1 -> and you will go to the particular user

23329.2 -> that you want

23330.2 -> that multi-factor authentication to be assigned to.

23333.5 -> All right.

23334 -> So for example,

23335.1 -> I wanted to be assigned to the test user right.

23338.166 -> So what I'll do is I'll go to users.

23341.8 -> I'll go to test right and in the security credentials tab,

23346.5 -> I will have this page which says assigned MFA device.

23350.3 -> So it says no as of now,

23352 -> so I'll assign it a device I click on edit

23355.1 -> and now it'll give me an option between a virtual MFA device

23358.8 -> and a hardware MFA device.

23360.504 -> Now.

23360.79 -> I have to choose among the two.

23362.907 -> So since I said,

23364 -> you can create a virtual MFA device very simple easily.

23367.145 -> So I'll select the virtual MFA device.

23370.1 -> And now it's basically asking you to install

23372.6 -> the application on your phone.

23374.1 -> So we have already done that.

23375.624 -> Let's click on next step

23376.886 -> and now you'll be presented with this screen.

23379.6 -> So basically now what you have to do is you

23382.041 -> would be logging in to your Google Authenticator app,

23385.161 -> and you will be scanning this barcode from your phone.

23389.3 -> So let me show you

23390.5 -> how let me connect my phone to the computer

23394.1 -> so that you can see the screen.

23396 -> Give me a second.

23406.7 -> Alright, so this is the screen to my phone guy.

23410.1 -> So what I have what I have to do now is I have to go

23413.479 -> to the Google Authenticator app.

23415.6 -> I'll ask me to create an account.

23417.975 -> So I click on begin and once I have

23421.2 -> that basically now I'll have to scan the barcode from my mobile.

23426.8 -> So the way to do

23427.9 -> that is I'll click on scan a barcode

23430.823 -> and then I'll scan this barcode over here.

23438 -> Right, it might take some time.

23440 -> So be patient.

23441.1 -> Yeah, so it's done now, you're all set.

23444 -> Right.

23444.8 -> So you just click on done

23446.8 -> and now you have to enter two codes

23449.1 -> that you are you will be receiving on your

23452.5 -> on your Google Authenticator.

23454.584 -> So basically these codes change from every 30 seconds, right?

23458.9 -> So I have to endure these codes over here.

23461.9 -> So it's 2 0 4 and then 3 5.

23465 -> Sorry 0 2 0 & 3 5 3 Zero two zero three five three,

23469.6 -> and I have to enter the next code as well.

23473 -> So let's wait for the next code and it's

23476.769 -> 1 2 7 8 9 1 so I'll enter that over here as well.

23480.7 -> So it's 1 2 7 8 9 1 and that is it guys.

23484.9 -> So now I'll click on activate virtual MFA

23489.323 -> and it says the MFA device was successfully Associated.

23493.565 -> So I'll click on finish

23495.7 -> and that is it guys you're done, right?

23497.9 -> so now if I log out from my test account

23502.8 -> that is From here, right?

23507.6 -> This is my test account.

23509.253 -> So if I log out from here right now.

23524.3 -> And try to login again using test.

23547.4 -> So I come to my normal login page, right?

23550.5 -> So I'll enter my username and my password.

23556.1 -> Which is this and now I'll click on sign in so now it will ask me

23561.4 -> for the MFA code.

23562.533 -> So let's see.

23563.4 -> What is our MFA code as of now.

23566 -> So it has changed to seven three four five five two.

23569.9 -> So let us enter that seven three four five five two.

23575.93 -> And click on submit.

23580.2 -> So with this I will now be able to log

23582.8 -> into my AWS console using the test account

23585.7 -> which are configured using the administrator account

23588.7 -> in I am right so it's very simple guys.

23591.6 -> It's you can actually get a world-class security

23595.5 -> with the click of a button using I am alright,

23599.1 -> so we have seen how we can do multi-factor authentication.

23606 -> Let's move on to the Hands-On part now,

23608.6 -> so this is what Is you guys have been waiting

23611.734 -> for so just give me a second?

23614.4 -> So that I can configure everything on my end.

23624.9 -> All right.

23625.5 -> So what we'll be doing now is I have created an application

23629.6 -> which can interact with the S3 service.

23632.7 -> All right.

23633.2 -> So using that as the service now.

23636.7 -> We will be.

23640.3 -> Uploading files to RS3 console

23644.1 -> and how will we are going to do that first?

23646.2 -> We are going to do that using Local Host and that is

23649 -> where our secret keys and my accesskey comes in

23652 -> and then we will be

23653.3 -> we have assigned role to are easy to instance.

23655.329 -> Right?

23655.645 -> So we'll be accessing that website using easy

23658 -> to without the access key and the secret access key

23660.8 -> and we can

23661.437 -> and we'll see do we get the access

23663.542 -> to our SEC service or not?

23665.2 -> Alright, so let us do that.

23667.276 -> So now what I'll do is I will go to my local host application.

23673.2 -> So guys this is basically my application.

23675.3 -> What I have to do is I'll choose a file upload a picture

23680.9 -> from any sample pictures

23682.7 -> and then it will upload it to a particular bucket

23685.644 -> that I've defined in S3 and

23687.3 -> that the bucket looks something like this.

23692.957 -> It show that buckets name is quarantine demo.

23696.4 -> So let me show you the bucket.

23698.1 -> So as of now, I think there are some objects.

23701.8 -> So let's delete those objects.

23707.223 -> So here it is.

23708.3 -> This is the bucket quarantine demo.

23710.5 -> So I have like three objects over here as it's now.

23713 -> So let's delete these objects.

23719.5 -> Alright, so now

23720.8 -> what I'll be doing is this is the code

23723.7 -> for my application guys.

23725.9 -> All right.

23726.8 -> So in this code as you can see,

23729.9 -> I'm not specified the key and the secret key as of now,

23733.3 -> so I'll get the key

23734.7 -> and the secret key from here, right?

23737.5 -> So let me quickly.

23740.5 -> So let me show you without the secret can access key.

23743.9 -> How is this localhost website functioning?

23746.7 -> So if I try to upload a file as it is now See,

23750.8 -> this is the file that I want to upload I

23753.094 -> click on upload image and I will get an error

23756.123 -> right because it is not authenticating

23758.3 -> itself to the service that I want to go to.

23762.8 -> So now I'll add the credentials

23765.4 -> that that is a key and the secret key.

23767.6 -> Now the way to do that is like this so I'll copy it.

23773.1 -> And I'll paste it here.

23776.7 -> I'll delete this

23778.3 -> and this is well not required and now I'll paste my key

23782.9 -> and my secret key,

23783.8 -> which is this right so I'll copy the key.

23790 -> Over here and then my secret key as well.

23797.2 -> over here and now I'll save it

23802.207 -> if I try to access my Local Host website now,

23806.5 -> I should be able to upload a file right so

23809.7 -> if I try to upload the file now.

23814.5 -> It says well done S3 upload complete.

23817 -> So these credentials

23818.313 -> that have just entered our basically credentials

23821.353 -> for my him and account.

23822.841 -> So if you want to see

23824.6 -> where did I get these credentials from again?

23827.6 -> You can basically go to users you can go

23831 -> to your user and you can go at security credentials

23835.4 -> and over here.

23836.281 -> It will last you the access key ID lot list

23838.925 -> you the secret access key

23840.5 -> because it is only available once you can only use it once.

23844.9 -> Copy it once you will not be able to see it again.

23847.9 -> And if I make this particular key inactive from over here,

23854.4 -> and if I try to Upload anything again.

23860.8 -> I will again get an error

23862.723 -> because without the keys my account will not be.

23870 -> I will not be authenticated to the S3 Service

23872.4 -> as you can see it says invalid access key

23874.8 -> because it is not valid anymore.

23876.9 -> All right, so I can make it active again,

23878.9 -> but that is not required as now.

23880.8 -> So what I do now is I have already configured

23883.8 -> this website on the ec2 console.

23886.2 -> All right, so let me go to my easy to Right, here.

23893.5 -> It is.

23894.3 -> So remember in this starting of the session we created a role

23898.5 -> for S3 full access, right?

23900.776 -> So that role has been attached to my ec2 instance.

23905 -> So let me show you the website.

23913.9 -> Here it is.

23917.2 -> All right, so I can access the website on my ec2.

23920.3 -> Now if I choose a file as of now and I try to upload the file.

23926.7 -> I'll be able to do so

23928.1 -> because my policy has been attached now.

23930.9 -> Let's see what happens if I d-- attach the policy.

23937.084 -> All right, so I'll go

23938.7 -> to this and I'll select no role click on apply.

23943.6 -> Yes detach.

23945.8 -> And now if I try to upload a file again.

23954.5 -> As you can see I see a blank page with basically means

23958.111 -> that an error has occurred.

23960.2 -> All right, so I am not able to upload any file

23964 -> because my role has been detached from my ec2 instance.

23967.9 -> So if I wanted to be working again,

23970.1 -> I'll just simply go here go to actions settings.

23973.723 -> Attach the rule.

23976.526 -> That is this click on apply and it will again work.

23982.9 -> Right, I'll choose a file see this file upload the image

23986.8 -> and your work again works like a charm, right?

23990.034 -> So that is it guys.

23991.4 -> You don't have to configure much.

23993.3 -> You just have to have the knowledge of I am

23995.7 -> and with that you

23996.625 -> can do complex procedures with the click of a button

23999.4 -> and you don't have to swear about it, right?

24002.624 -> You might want to you

24004 -> might be wondering did I change anything in the code

24007 -> when I uploaded to easy to

24008.4 -> so you don't have to do anything guys.

24010.5 -> You just have to delete the Choose key and secret

24015.3 -> and you will upload the code

24017.2 -> as it is you don't have to change anything it will

24020.3 -> if it doesn't have the key mentioned

24023.1 -> in this particular function,

24025.2 -> it will basically get those keys from the metadata of easy to

24029.223 -> and metadata is the place

24030.859 -> where your role is actually assigned or your role

24034.2 -> is actually attached right?

24035.629 -> So if it doesn't find the key in the code,

24037.84 -> it basically goes

24038.757 -> to the metadata and picks the key from over there.

24041.8 -> All right.

24042.8 -> So guys that is it

24044.3 -> for the demo part in this session.

24052.5 -> We will be discussing about Amazon redshift

24055.168 -> the most popular cloud-based data warehouse.

24057.9 -> So let me run you through today's agenda quickly.

24060.3 -> We will Begin by taking a look at traditional data warehouse

24063.817 -> will be discussing its underlying architecture

24066.501 -> and the disadvantages of using traditional data warehouse,

24069.854 -> and then we'll move on to our today's topic

24072.2 -> which is I'm redshift here will be discussing

24075.2 -> its architecture its key Concepts its unique features

24078.99 -> and the advantages of using Amazon redshift.

24081.98 -> And finally,

24082.851 -> we'll be doing a demo on Amazon redshift in this demo.

24086.7 -> We'll see how to import data from Amazon S3

24089.92 -> to Amazon redshift

24091.3 -> and perform queries on this data very easily.

24094.128 -> So I hope that was clear to you guys.

24096.309 -> Let's get started.

24097.44 -> I'm sure you know,

24098.57 -> what a data warehouses you can think of data warehouse

24101.9 -> as a repository.

24102.7 -> Story that data generated

24104.354 -> from your organization's operational systems

24107.2 -> and many other external sources is collected transform

24110.803 -> and then store you can host this data warehouse

24113.881 -> on your organization's Mainframe server or on cloud,

24117.2 -> but these days companies

24118.7 -> are increasingly moving towards cloud-based data warehouses,

24122.208 -> instead of traditional on-premise systems and to know

24125.351 -> why we need to understand the underlying architecture

24128.388 -> and the disadvantages of using traditional data warehouses.

24131.8 -> So let's begin By looking at architecture,

24134.2 -> but it is important to understand where the data comes

24137.4 -> from traditionally data sources are divided into two groups.

24141.3 -> First.

24141.8 -> We have internal data that is the data

24144.263 -> which is being generated

24145.718 -> and Consolidated from different departments

24148.189 -> within your organization.

24149.633 -> And then we have external data that is the data

24152.4 -> which is not getting generated in your organization.

24155.4 -> In other words.

24156.37 -> That is the data

24157.405 -> which is coming from external sources.

24159.8 -> So this traditional data warehouse follows,

24162.6 -> It's a simple three-tier architecture to begin

24165.498 -> with we have bottom tier in bottom tier.

24168.074 -> We have a warehouse database server

24170.208 -> or you can say a relational database system

24172.897 -> in this jar using different kind of back in tools and utilities.

24176.829 -> We extract data from different sources

24179.201 -> and then cleanse the data

24180.751 -> and transform it before loading it into Data Warehouse

24184.166 -> and then comes the middle tier

24186.1 -> and middle tier we have olap server.

24188.5 -> Olap is an acronym for online analytical processing

24192.346 -> this Oily performs multi-dimensional analysis

24195.73 -> of business data

24196.9 -> and transforms the data into a format such

24199.8 -> that we can perform complex calculations for analysis

24203.493 -> and data modeling on this data very comfortably.

24206.9 -> Finally.

24207.444 -> We have top-tier.

24208.6 -> The stopped here is like a friend

24210.675 -> and client layer this jar holds different kind of query

24214.165 -> and Reporting tools using

24215.749 -> which the client applications can perform data analysis query

24219.581 -> reporting and data mining.

24221.13 -> So to summarize

24222.023 -> what we have Vlad till now traditional data warehouse as

24225.4 -> a simple three tier architecture in the bottom curve.

24228.1 -> We have back in tools using which we collect

24230.776 -> and cleanse the data and then in mid 80 or we have tools

24234.2 -> which is olap server using

24236 -> which we transform the data into the wavy Ward

24238.7 -> and then finally dropped your in which using different query

24242.023 -> and Reporting tools.

24243.2 -> We can perform data analysis

24244.889 -> and data mining moving on to the disadvantages

24247.641 -> of traditional data warehouse concept there.

24250.22 -> Is this leading us Business Service Company.

24252.9 -> And this company is running

24254.6 -> a commercial Enterprise data warehouse this data warehouse

24258.174 -> as data coming

24259.029 -> from different sources across different regions.

24261.958 -> The first problem that this company faced was

24264.358 -> when it was setting up a traditional data warehouse

24267.3 -> as we discussed earlier,

24268.8 -> the architecture of traditional data warehouse

24271.4 -> is not very simple.

24272.7 -> It consists of data models extract transform

24275.9 -> and load processes,

24277.261 -> which we call ETL and you have bi tools sitting on top.

24281.072 -> So this US based Denis had to spend lot of money

24284.369 -> and resources to set

24285.777 -> up a traditional data warehouse data warehouse,

24289.065 -> which was initially 5 terabytes is growing

24291.898 -> over 20% year-over-year and it was expected

24295 -> that the might be higher growth and future.

24297.8 -> So to meet this continuously increasing storage

24300.708 -> and compute needs the company had

24302.661 -> to continuously keep upgrading the hardware again this task

24306.28 -> of upgrading the hardware continuously involves lot

24309.4 -> of money Manpower and so many resources so,

24312.6 -> To scaling and traditional data warehouse is

24315.1 -> not an easy concept and

24316.512 -> since the company could not meet all the storage

24319.382 -> and compute needs easily.

24320.914 -> It was facing a lot of performance issues as well.

24324 -> And finally the company had to deal

24326.144 -> with increasing cost initially

24328.063 -> that to spend a lot on setting up data warehouse

24331.1 -> like that to spend on Hardware Manpower

24333.7 -> electricity security real estate

24336.1 -> and deployment cost and many other and

24338.8 -> as their data warehouse grew they had to spend again to meet

24342.7 -> Courage and compute needs

24344.386 -> so to sum it up setting up a data warehouse

24347.206 -> and deploying it

24348.335 -> and managing it later involves lot of money

24351.199 -> and resources moreover

24352.7 -> auto-scaling in traditional data warehouse is not an easy concept

24356.7 -> because of all

24357.526 -> these reasons many companies are increasingly moving

24360.526 -> towards cloud-based warehouses instead of

24362.879 -> traditional on-premise systems.

24365.1 -> So guys in this session,

24366.8 -> we'll be dealing with one of the most famous

24369.2 -> cloud-based data warehouse provided by Amazon,

24372 -> which is arms,

24372.9 -> And redshift and simple what's Amazon redshift is

24376.345 -> a fast scalable data warehouse

24378.5 -> that makes it simple and cost-effective

24380.874 -> for you to analyze all your data across your data warehouse

24384.4 -> and data leak guys.

24386 -> I have a definition which is put up on the screen

24388.072 -> and I have few words,

24389.122 -> which I have highlighted over there.

24390.637 -> So as we progress through the course

24392.387 -> of the session will know what those words exactly mean.

24395 -> So let's ignore them for now,

24396.43 -> but there are certain key Concepts which you

24398.592 -> should be aware of

24399.478 -> when you're dealing with Amazon redshift.

24401.552 -> So we'll discuss them now.

24402.9 -> Now Amazon redshift data.

24404.37 -> Where is a collection of compute resources,

24406.7 -> which we call notes and these notes

24409.174 -> when organized into a group they become clusters each

24412.5 -> of these clusters run an Amazon redshift engine

24415.603 -> and it contains one or more databases.

24418.068 -> So this cluster has a leader note

24420.2 -> and one or more compute nodes as for the leader node,

24423.352 -> it receives queries from Klein applications.

24426.043 -> And then it passes these queries

24427.997 -> and develops a suitable query execution plan and then

24431.241 -> it coordinates the power.

24432.771 -> Execution of these plants with one or more compute nodes

24436.118 -> watch the compute nodes finish executing this plan.

24439.246 -> Again, the leader node

24440.569 -> Aggregates the results from all this intermediate compute nodes

24444.3 -> and then sends it back to client application.

24446.888 -> Then we have compute nodes you can think of this compute nodes

24450.3 -> as a compute resources

24451.594 -> that execute the query plan

24453.004 -> which was developed by leader node,

24455.004 -> and when they are executing this plan,

24456.9 -> the transmitted data

24457.9 -> among themselves to solve many queries.

24460.52 -> These compute nodes are further.

24462.648 -> Added into slices

24463.817 -> which we call note slices each of this note slices receive part

24467.938 -> of memory and disk space.

24469.6 -> So the leader node distributes data and part of user query

24473.224 -> that receives from Clan application to this note slides

24476.564 -> and all this note splices walk in parallel to perform operation

24480.4 -> and increase the performance of your redshift data warehouse.

24484.1 -> So to say we have leader node,

24485.997 -> we have compute nodes and nodes slices.

24488.4 -> But how do they interact with line application?

24490.7 -> That is the question here.

24492.1 -> So I This line applications

24493.964 -> basically bi tools or it can be any other analytical tools

24497.9 -> which communicate with Amazon redshift using drivers like jdbc

24502.5 -> and odbc jdbc ref is to Java database connectivity driver.

24506.9 -> It is an API for programming language Java.

24510.032 -> Then we have odbc

24511.3 -> it refers to other database connectivity driver

24514.311 -> and it uses SQL to interact with leader node.

24517.286 -> So basically using this drivers client application

24520.508 -> sends a query to lead a new read a note

24523.038 -> on receiving the client applications queries.

24525.914 -> It passes these queries

24527.341 -> and develops a suitable execution plan.

24529.7 -> Once the plan is set up compute nodes

24531.825 -> and compute slices start

24533.237 -> working on this plant the transmitted data

24535.649 -> among themselves to solve this queries.

24537.783 -> So once the execution is done leader node

24540.026 -> again Aggregates the results from all this intermediate totes

24543.205 -> and sends it back to client application.

24545.429 -> So this is the simple explanation of Amazon

24547.9 -> redshift Concepts moving on

24549.9 -> when you launch a cluster you need to specify the know.

24552.8 -> But basically we have two types of nodes then storage notes.

24556.686 -> These are storage optimized

24558.384 -> and I used to handle huge data workloads.

24560.989 -> And basically they use hard disk drive

24563.4 -> or HDD type of storage

24565 -> and then we have dense compute distance compute nodes

24568.347 -> are compute optimized

24569.7 -> and they are used to handle high performance intensive workloads

24573.3 -> in the mainly use solid-state drive

24575.6 -> or SSD kind of storage,

24577.2 -> but there are three things that you should keep in mind

24579.719 -> when choosing one among them firstly you should be aware.

24582.8 -> If the amount of data

24583.9 -> that you want to import into your Amazon redshift

24586.5 -> and then the complexity of the queries

24588.854 -> that you run on your database

24590.653 -> and the need of Downstream systems

24592.7 -> that depends on the results of these queries.

24595.288 -> So keeping this three things in mind,

24597.531 -> you can choose either Den storage nodes

24599.9 -> or dense compute nodes.

24601.5 -> So guys that was the architecture

24603.577 -> and its key Concepts now,

24605.2 -> we'll take a look at few reasons as to why

24607.8 -> Amazon redshift is very popular

24610 -> as we discussed earlier setting up a You

24612.6 -> smell data warehouse involves lot of money and resources,

24615.9 -> but it's very easy to setup the deploy

24619.4 -> and manage a suitable data warehouse using Amazon redshift

24623.4 -> on Amazon redshift console.

24626.1 -> You will find create a cluster option.

24628.8 -> When you click on that option

24630.5 -> Amazon redshift ask you for certain details,

24633.212 -> like the type of node.

24634.6 -> You want to choose the number of nodes the VPC in which you

24637.845 -> want to create your data warehouse user ID password

24640.786 -> and many other details.

24642.4 -> Once you feel that you have given the right set

24644.4 -> of details you have an option

24645.955 -> which says launch the cluster

24647.557 -> and one click your data warehouse is just created.

24650.439 -> So with one click you can easily create a data warehouse

24653.674 -> in Amazon redshift.

24654.9 -> Once your data warehouse is set up Amazon redshift automates

24658.792 -> most of the common administrative tasks

24661.3 -> like managing monitoring

24662.835 -> and scaling your database.

24664.3 -> So you don't have to worry about managing

24666.3 -> or scaling your database needs.

24668.3 -> So that's how easy it is to develop

24671.008 -> or set up a data.

24672.507 -> Using Amazon redshift.

24674.2 -> We also learned

24675.204 -> that auto scaling is difficult in traditional data warehouse,

24679.338 -> but you can scale quickly to meet your needs

24682.3 -> and Amazon redshift.

24683.7 -> Well, we already know that a cluster node as a leader note

24687.052 -> and one or more compute nodes.

24688.814 -> So if you want to order scale an Amazon redshift,

24691.637 -> all you have to do is resize your cluster size

24694.284 -> as we know this compute nodes are like compute resources.

24697.304 -> So if you want to scale up,

24698.893 -> you can increase the number of compute notes similarly

24701.6 -> if you want to scale.

24702.45 -> Held up you just have to decrease the amount

24704.8 -> of compute nodes alternatively.

24706.504 -> We have something called single note

24708.59 -> and multiple new and single

24710.2 -> node cluster one node takes the responsibilities of both leader

24713.961 -> and compute functionalities

24715.6 -> and the multi node cluster contains one lead in node

24718.6 -> and user specified number of compute nodes.

24721.09 -> So suppose you want to resize your cluster

24723.247 -> and you are using a single mode cluster,

24725.301 -> then you can change from single node cluster

24727.7 -> to multi-node kirsta.

24728.82 -> Similarly.

24729.337 -> You can change

24730.107 -> from multiple node cluster to single node cluster.

24732.8 -> Of a need so that's how easy it is to scale up

24735.998 -> and down and Amazon redshift moving on.

24738.7 -> We learned earlier

24739.6 -> that while using traditional data warehouses.

24742.301 -> It's possible

24743.1 -> that the performance of your data warehouse might decrease

24746.6 -> but with Amazon redshift,

24748.2 -> you can get ten times better performance than any other

24751.376 -> traditional data warehouse.

24753 -> It uses a combination of different strategies,

24755.7 -> like columnist storage

24757.039 -> and massively parallel processing strategies

24759.659 -> to deliver high throughput and response times.

24762.4 -> So let's discuss the strategies one by one will first we

24765.758 -> have columnar data storage to understand what

24768.499 -> that is first.

24769.327 -> We should know row storage most

24771.088 -> of the traditional data warehouse and database is used

24774.1 -> this row storage in row storage.

24776.049 -> All the data about the record is stored in one row.

24779.095 -> Okay.

24779.4 -> So let's say I have this database here.

24781.3 -> I have three columns and two rows

24783.4 -> the First Column contains the unique number associated

24786.261 -> with student the second column contains the name of a student

24789.5 -> and the third column contains the edge

24791.5 -> as we already know.

24792.7 -> Data is stored in form of blocks in databases

24795.633 -> or data warehouses.

24796.9 -> So as you can see in row storage the block

24799.418 -> one contains all information.

24801.2 -> There is about a particular student has SSN his name

24804.785 -> and then age.

24805.7 -> So basically it stores all the information

24808.3 -> that there is in a single Loop.

24810 -> So in the first block you have information about first student

24812.83 -> and in the second block you have information about second student

24815.8 -> and it goes on now the columnist storage again.

24818.6 -> I'm using the same database again.

24820.65 -> I have three columns and two rows.

24822.7 -> Rose but Colin storage stores data by columns with data

24826.9 -> for each column store together.

24828.923 -> So again, we have blocks

24830.414 -> but the first block here has all the data

24832.9 -> that is there in First Column.

24834.7 -> So you have all assistant stored in first block

24837.405 -> and all named store

24838.523 -> in second block and all the ages Stone in third block.

24841.6 -> So it goes on there are a lot

24843.4 -> of advantages of using this column storage firstly

24846.623 -> since and column storage a single block contains

24849.571 -> same type of data.

24850.7 -> You can achieve better data compression.

24852.8 -> As you can see columnist storage

24855.081 -> can hold values 3 times the records

24857.394 -> as robe a storage because of

24859.3 -> this the number of input/output operations decreases

24862.501 -> and thirdly by storing all the records

24864.804 -> for one field together columnar database can query

24868.097 -> and perform analysis

24869.375 -> on similar type of data far quicker than row storage.

24872.7 -> So this is how the concept of columnar storage

24875.2 -> which is used by

24876 -> Amazon redshift provides us a better performance.

24879 -> And then we have massively parallel processing.

24881.305 -> I'm sure you might have or of parallel processing

24883.705 -> and computer science.

24884.8 -> It's just

24885.329 -> that number of different processors walk together

24888.1 -> or compute together or in Palin similarly

24890.6 -> massive parallel processing

24892.23 -> in Amazon redshift is nothing

24893.981 -> but cluster we have already discussed this earlier.

24897 -> We have a cluster

24898 -> and this cluster has a leader node

24900.075 -> and one or more compute nodes

24901.9 -> and this compute nodes is further divided into something

24905.2 -> called note slices.

24906.361 -> So when this leader node receives a query it

24908.968 -> develops execution plan and this compute nodes and computes.

24912.659 -> Isis walk together or in

24914.084 -> parallel to execute this plan and later.

24916.4 -> Thus leader node sends the results back

24918.4 -> to client application.

24919.5 -> So basically this compute slices

24921.8 -> and compute nodes work

24923.5 -> in parallel to achieve better performance moreover

24927.4 -> Amazon redshift is also able to smartly recognize the data

24931.096 -> or notes before running a query

24933.019 -> which dramatically boost the performance.

24935.5 -> So that's how we can get our ten times better performance

24938.6 -> using Amazon redshift

24940.1 -> and then the cost and traditional data.

24942.435 -> A bear houses people had to spend a lot

24944.47 -> of money to set up

24945.564 -> and then later to maintain the data warehouse.

24948.3 -> But Amazon redshift

24949.6 -> is the most cost-effective cloud-based data warehouse.

24952.753 -> If you remember in traditional data warehouse,

24955.464 -> they had to spend on Hardware real estate man,

24958.18 -> power electricity

24959.18 -> and deployment cost and many others and

24961.472 -> as their data warehouse grew they had to spend again

24964.6 -> on meeting the storage and compute needs

24967 -> but an Amazon redshift.

24968.708 -> We don't have to pay any upfront cost.

24971.455 -> So Amazon, Redshift is most cost effective

24974.5 -> and it cost one tenth of traditional data warehouse.

24977.7 -> You can start small fishes point two five dollars per hour

24981.012 -> without any commitments and you can gradually scale up later.

24984.5 -> If you need in addition to all those advantages

24987.747 -> Amazon redshift allows you to query data

24990.446 -> from data leak data leak is a storage repository

24993.7 -> that holds a vast amount of raw data in its native format

24997.469 -> until it is needed.

24998.668 -> So in data Lake you have data

25000.504 -> in different formats you can Can load data

25003.4 -> from Amazon S3 into your Amazon redshift cluster

25006.378 -> for analysis very easily

25007.95 -> that is from data leak you can store easily

25010.7 -> 20 or Amazon redshift but it needs more effort

25013.762 -> and cost the first

25014.981 -> because loading data into Amazon redshift cluster involves

25018.702 -> extract transform and load

25020.4 -> which we simply called ETL process and this process

25023.409 -> is very time-consuming

25024.809 -> and compute intensive and it's costly

25027.3 -> because uploading lots of data cold data

25030.152 -> from Amazon S3 for analysis.

25032.2 -> Is growing your clusters,

25033.738 -> which is again costly and requires a lot of resources.

25037 -> So as a solution,

25038.2 -> we have something called Amazon redshift Spectrum,

25041.3 -> which acts as the interface between your Amazon S3

25044.4 -> or data Lake and Amazon redshift.

25046.692 -> So you can directly query data stored in Amazon S3

25050.2 -> or data lake with this red shift Spectrum without need

25053.839 -> for Unnecessary data movement.

25055.968 -> I hope that was clear and finally with Amazon redshift.

25059.744 -> Your data is safe and secure it offers.

25062.389 -> Backup and recovery.

25063.737 -> So as soon as data is created

25065.623 -> or stored in Amazon redshift a copy of that data is made

25069.261 -> and through secure connections a snapshot of it a sin

25072.885 -> to Amazon S3 for later.

25074.4 -> So suppose you lose your data

25075.979 -> or if you have deleted the data from Amazon redshift by mistake,

25079.685 -> you can restore the data easily

25081.3 -> from Amazon S3 service Amazon redshift also

25084.3 -> provides you with an option to encrypt your data.

25087.179 -> So when you enable this encrypts option all

25089.7 -> the data in your cluster in your leader node,

25092.4 -> and Compute nodes and nodes slices is encrypted.

25095.3 -> And this way your data is very safe and secure.

25098.16 -> So Guys, these are all the advantages

25100.308 -> of using Amazon redshift.

25101.8 -> So now you have a basic idea of its architecture.

25104.627 -> Its various key Concepts,

25106.1 -> like clusters nodes leader node note slices now,

25109.4 -> it's time to work on a demo in this demo.

25112 -> We'll see how to transport data

25114 -> from Amazon S3 to Amazon redshift data warehouse

25117.048 -> and perform simple queries.

25118.8 -> So I hope that was clear to you guys.

25120.799 -> Let's get started

25121.8 -> the first First thing there are certain software's

25124.25 -> which you need to pre-install

25125.8 -> so that you can start working on Amazon redshift first suppose.

25129.188 -> You want to perform queries on the data on Amazon redshift.

25132.689 -> Then you need a SQL work bench

25134.5 -> where you can perform your queries and

25136.676 -> as we learned earlier the client application

25139.1 -> need a connection to communicate with redshift.

25141.8 -> So we need to install a jdbc driver

25144.1 -> and for that jdbc driver to run we need to have

25147 -> a Java runtime environment.

25148.7 -> So we have three things to install your now I'll show you

25151.6 -> how to install it.

25153.6 -> And I have this Java runtime environment download link

25157.2 -> by Soft tunic.com.

25158.7 -> So it says free download and you click on that.

25161 -> It will be downloaded.

25162.149 -> You can store it anywhere and once you're done

25164.9 -> with that search for Amazon redshift documentation.

25168.3 -> So here it is.

25170.3 -> Okay, not that not that just one

25174.2 -> and when you scroll down it says Amazon redshift

25177.1 -> get started click on that and in the step one,

25179.9 -> we have prerequisite UPS.

25181.7 -> Okay, scroll down

25183.216 -> and Chase in the Step 2 you have an option

25186.5 -> where you can download a go to SQL work bench website

25190 -> and download it.

25191.1 -> So click on that and here it says build current version

25195.6 -> and you have download generic packages for all systems.

25198.5 -> You can download it.

25199.5 -> Once you click on

25200.279 -> that it'll start downloading and there is one more thing

25203.2 -> which is jdbc driver.

25204.364 -> Go back to documentation part scroll down in the step 4,

25207.6 -> you can see configure a jdbc connection click on

25210.9 -> that it will take you to a page where you have.

25213.473 -> I've jdbc drivers of different version.

25215.6 -> You can download the first one click on this

25217.7 -> and it will be downloaded.

25218.817 -> So once all these three things are downloaded stored them

25221.25 -> in a file of your choice.

25222.5 -> Well, I have stored them on my desktop.

25225 -> I have this AWS folder

25226.7 -> and in that which ifft so here's my workbench.

25229.966 -> Zip file.

25230.6 -> It was a zip file.

25231.597 -> So extracted all the files and then I have my jdbc driver

25234.8 -> your well Java runtime environment as in download,

25238.168 -> so that's okay.

25239.2 -> So I hope that was easy to just install all these things

25242.239 -> and you are set to go

25243.5 -> And your backdoor Amazon Management console?

25246.2 -> I have previously used the Amazon redshift.

25248.3 -> So I have this Amazon redshift in recently visited Services.

25252 -> Anyway, you can search for Amazon redshift here your it is

25257 -> whether it's taking time to load.

25259.4 -> Okay.

25259.9 -> This is my Amazon redshift console page and you have

25262.605 -> different kind of options on your navigation pane

25265.2 -> on the left side

25266.141 -> and there are two ways to create a launcher cluster first.

25269.397 -> You have quick launch cluster option

25271.456 -> and launch cluster option.

25272.846 -> This is the very easy way to launch a cluster

25275.16 -> but suppose you want the freedom to specify

25277.375 -> all the details as in the vp's.

25279.199 -> He's the security groups different type of notes

25281.89 -> username password and all that.

25283.6 -> You can go for launch clustered option.

25285.529 -> Let's go ahead an Explorer.

25287.2 -> So first it asks for a name.

25288.6 -> Let's say my cluster and database day T1.

25293 -> And the poor this is default Port 5 4 3 9 is a default Port

25296.4 -> which would be handled by Amazon redshift you

25298.6 -> then the master user name.

25300.2 -> Let's say AWS user and password.

25304.4 -> That's it and confirm your password and click

25307.938 -> on continue option.

25309.5 -> So cluster details are done

25311.2 -> and dusted then you have note configurations.

25313.547 -> Well for the free tire,

25314.9 -> you only have DC too large but suppose you have

25317.4 -> a premium membership.

25318.5 -> Then you can choose any of this for this DC to large.

25321.487 -> This is the CPU capacity memory and storage

25324.2 -> and the input output performance has moderate you can go ahead

25327.25 -> and choose the cluster type.

25328.489 -> We discussed this.

25329.389 -> We have multi node and single load and single node.

25331.658 -> We have both the leader and the compute nodes.

25333.7 -> Note responsibilities handled by single note the multi node.

25336.499 -> We have a single leader node and use a specified number

25339.2 -> of compute notes click on continue

25341.7 -> and then here it asks for the VPC details parameter group

25345.3 -> in suppose you want encryption or not and all the details.

25348.652 -> So basically in this launch cluster option,

25351.1 -> you have the freedom to specify all the details,

25353.6 -> but for this demo,

25354.558 -> I'm going to use quick launch cluster option.

25357 -> So again as for the free tire,

25358.6 -> I'm using DC too large and again for the free tier.

25361.3 -> I'm using DC to large type it says Our to compute

25364.5 -> nodes and let's retain the same cluster name as

25367.626 -> for the master user AWS user now.

25369.8 -> Let me give the password.

25372.9 -> And the default Port is 5 4 3 9

25375 -> and last option we have to choose among the viable.

25378.4 -> I am users or IM roads,

25380.2 -> but the question is why we need our I am role here in this demo.

25384.1 -> I said that we're trying to import data from Amazon S3,

25387.449 -> but you need certain set of permissions to access data,

25390.8 -> which is stored in Amazon S3 for that.

25393.174 -> We need to create a I am roll.

25395.1 -> So let's go back to I am service.

25398.011 -> Let me close all the steps.

25400.4 -> Okay, here you have roles option.

25402.7 -> You can click on that and click create true.

25406.2 -> And since we're dealing with Amazon redshift

25408.6 -> select red shift,

25409.605 -> let's shift customizable and click on next permissions.

25413.7 -> So we want Amazon redshift to access data from Amazon S3.

25417.4 -> So search for S3 of and you have a permission

25420.34 -> which says Amazon S3 read-only access well for this demo,

25423.7 -> this is an if but there is one more permission,

25425.8 -> which is Amazon S3 full access

25427.3 -> so you can perform read

25428.382 -> and write operations as well as for this demo.

25430.529 -> I'm going to choose this permission,

25432.2 -> which is Amazon S3 read-only

25433.661 -> access provides read-only access to all the buckets

25436.294 -> and Amazon S3 and click on next to view give you a role in name.

25440.2 -> Let's say my redshift role to and click on create rule.

25444.4 -> So now our Amazon redshift database as permission to access

25448.043 -> data from Amazon S3.

25449.3 -> Let's go back to redshift console.

25451.2 -> Okay, let me refresh this and now it's showing the role

25454.461 -> which has been created by showing your so

25456.51 -> as you can see unlike other launch option

25458.671 -> in this I didn't have to specify

25460.4 -> By much details just the node type the number of notes

25463.37 -> and then the master user name cluster identifier and password

25466.899 -> and the default database port

25468.605 -> and you can click on launch cluster option.

25470.9 -> So with one click you have easily deployed a database

25474.2 -> on Amazon redshift.

25475.515 -> If you remember

25476.522 -> when we try to use this launch cluster option

25479.4 -> we had option to select a default database or use

25482.5 -> or create our own database,

25484.1 -> but when you use this quick launch cluster option

25486.723 -> a default database called death will be created for us.

25490.6 -> So guys this cluster has been created.

25493.5 -> So before we connected to your SQL work bench.

25496.2 -> Let's try to explore here.

25497.706 -> You need to make sure

25498.941 -> that the database health status

25500.508 -> and in maintenance state is everything is in green color as

25503.827 -> for the cluster a cluster status.

25505.5 -> It should be available.

25506.7 -> And for the database Health,

25508.1 -> it should be healthy only then you can make

25510.3 -> a perfect connection with your SQL work bench.

25512.682 -> So you have this icon here click on that.

25514.8 -> Well, you get all the information there is

25516.7 -> about your cluster

25517.626 -> or you can just go ahead and click on this cluster.

25521 -> So this is the end point this tells me all about

25523.64 -> how to make a connection with this cluster.

25526 -> I have this when I click on that it says publicly accessible.

25529.3 -> Yes in the username as AWS user and the security groups.

25532.879 -> Apparently, it just shows the TCP rules

25535.168 -> which are set so

25536.127 -> that's about the end point then

25537.974 -> the cluster name you have cluster type node type

25540.769 -> and it shows the nodes and the zone and the date and time

25544.1 -> when it was created

25545.3 -> and you have cluster version as well on the right side.

25548.4 -> You have cluster status,

25549.6 -> which is why Syllable database health healthy.

25551.9 -> So is it currently in maintenance mode?

25553.8 -> No, and then you have parameter group apply status

25556.2 -> which is in sync

25557 -> with your database and there are few other features as well.

25560.7 -> But here you can see this VPC group click

25563.4 -> on that go for inbound and make sure it is set for TCP.

25568.1 -> Okay edit make

25569.948 -> this custom TCP Rule and here are five four three nine.

25574.723 -> Custom that's it and click on Save option.

25578.1 -> So that's the default port

25580.2 -> with which you can access the redshift and it's go back.

25586 -> Clusters.

25587.6 -> Okay, where were we we will change

25589.949 -> the default group of a PC.

25591.8 -> So this is the URL

25593.1 -> with which you can connect to the SQL work bench.

25595.9 -> So let's copy this and paste it in our x

25598.641 -> file I pasted over there.

25600.4 -> Well, if you using odbc connection

25602.368 -> and you can use this URL

25603.9 -> when you scroll down you have capacity details

25606.4 -> of your entire cluster,

25607.8 -> it's DC too large.

25609.546 -> So seven easy to compute units

25611.9 -> total memory storage and platform, okay.

25615.746 -> Let's go back to the I am role

25618.3 -> but I should have an IM roll option here.

25620.3 -> Let me see check it out.

25622.3 -> Okay, there's an option.

25624 -> It's acim rules.

25625.7 -> You can copy this entire thing and paste it again the editor

25631.1 -> so that while connecting it will be easy

25633.2 -> for us to find it.

25634.3 -> Okay, then so now we have cluster has created

25637.1 -> your database or data warehouse is set up now.

25639.518 -> You can just connect it with SQL work bench

25641.741 -> and start working on it.

25643.035 -> So let's go back to the folder

25644.8 -> where I stored my Workbench here it is.

25647.1 -> When you scroll down there's a file

25649.1 -> which says SQL work bench executable jar file.

25653.3 -> Open so here it is.

25656.4 -> It's asking for a default profile name.

25658.8 -> Let's say new profile one.

25661.4 -> Okay, then driver

25663.6 -> that was Amazon redshift driver only jdbc driver.

25666.9 -> And this was the yarol.

25668.5 -> We copied it earlier in the editor.

25670.2 -> So I'm going to paste it over here.

25672 -> Now.

25672.5 -> This is the URL control C

25675.6 -> and pests AWS user in the password.

25680.2 -> Okay, that should work make Sure

25682.644 -> that you select this order commit save it

25685.7 -> and then click on OK it says connecting new database now,

25689.4 -> it's successfully connected so I can easily perform queries.

25693.4 -> Now first.

25694.2 -> Let's create some tables.

25695.8 -> Well, I'm using the sample database from Amazon S3.

25699.1 -> So you have this AWS redshift documentation.

25703.6 -> Go back to that and here it says get started

25707.3 -> and in the step 6 you have this default SQL queries

25710.942 -> and tables provided.

25712.4 -> You can go ahead and use that I have it stored

25715.2 -> in my data.

25716.2 -> So I'm going to copy first.

25717.704 -> I'm going to create all the tables.

25720.3 -> Control C and paste it over there.

25723.1 -> Let's check what tables are there first we have user table.

25726.5 -> Well, this is like an auction data schema.

25729 -> So you have user table many users.

25731 -> When you have category users

25732.6 -> the category different categories to which users belong

25735.4 -> to then you have

25736.5 -> a date date on which a particular event occurred.

25739.5 -> Then you have even table all the details

25741.794 -> regarding an event listing as in the items,

25744.138 -> which are being sold are listed

25745.961 -> here all the details about the items.

25748 -> Then you have sales as in which user is Sighing

25750.7 -> how much which item in on that details?

25752.6 -> So basically we have six to seven tables.

25755 -> I'm going to select all that and say run option.

25757.9 -> So here it says table users created table

25760.9 -> when you created category date event listing and sales.

25764.547 -> So all the tables are easily created now as

25767.379 -> for the next part,

25768.593 -> we need to copy the data or the data for the database

25772.2 -> from Amazon S3 to Amazon redshift.

25774.7 -> Let's go back to the editor and I have this copy command.

25778.494 -> I'll explain you the format.

25781 -> Control C.

25782.9 -> And let's paste it at herb.

25785.9 -> Okay, let's explore this copy command.

25788 -> It says copy to the table users,

25789.973 -> which you just created from this path that is from the file,

25793.655 -> which is toward an S3 bucket.

25795.465 -> But this is the credential AWS.

25797.4 -> I am role which we copied to the editor the earlier.

25800.6 -> Apparently, we just giving a permission

25802.835 -> to access the data from S3.

25804.3 -> So we need to copy this I am rollio

25806.6 -> and then we have delimiter

25807.997 -> as then let me go back to a return show you an example.

25810.9 -> Amber Okay, let's say I've added all the child's name.

25816.1 -> Archana space some h b. Hobbies so you can see the straight line

25825.9 -> This is the delimiter as in the thing

25827.7 -> which are using two separate.

25829.15 -> All the fields are the columns.

25831.6 -> So going back.

25834.3 -> So that's delimiter which separates the data

25836.7 -> and this is region in which you are S3 bucket is located.

25840 -> So that's it.

25841.184 -> We have to replace diam roll.

25844.3 -> This is the AR and if the role I'm going to copy it

25847.3 -> and wherever this is you need to just paste it ctrl-v.

25856.6 -> Can the dawn last one so select everything

25861.3 -> and click on the execute button.

25863.6 -> It might take a while

25865.2 -> because the data set which was stored

25867 -> in Amazon S3 might contain large number of rows.

25869.764 -> So it might take a while as far as you can see it states

25872.8 -> executing statement here.

25877.1 -> It says one out of seven finished

25879.472 -> so we have six more to go.

25884.9 -> So this is good work bench has successfully executed

25887.35 -> all the script which we have written here.

25889.4 -> Let's go and start performing some simple queries.

25892.6 -> Let's say I want to extract the metadata of user table.

25897.5 -> I have this query OK select star from page table definition.

25902.1 -> So since we are extracting metadata from table name,

25905.446 -> let's say users and click on execute option.

25909.723 -> So you have so many columns.

25912.9 -> You ought to taste First Column user ID

25915.3 -> of type integer and coding Delta.

25918.1 -> Then you have user name first name last name city state email.

25922.3 -> So basically that's the metadata or the structure of user table.

25926.492 -> So we have sales ID list ID seller ID by your ID

25930.4 -> and many other details.

25932 -> Let's execute another command.

25933.8 -> Let's say I want to find total sales on a given date.

25937.2 -> Okay some the count your have some function.

25942 -> Which will count the number of sales from sales and date

25946 -> where the sales data is date ID

25948.317 -> and the date on which I want to calculate a specified here

25952.578 -> and then click.

25955.9 -> Okay the summit at your number.

25964 -> Let's just walking on it that is not working.

25966.5 -> I've selected the user table

25967.9 -> and I've asked them to display all the all

25969.893 -> that dairies in the user table.

25971.4 -> So this has the data say select star from users.

25975.4 -> So I want to extract the names of people

25977.9 -> who are from let's say some states.

25980.5 -> Let's consider some State.

25982.8 -> Let's take an edge so s Tage Like

25988.4 -> and hatch it should work now it is executing statement.

25992.6 -> So these are the people who are from State and Edge.

25995.22 -> So basically once you

25996.3 -> if the perfect connection from your SQL work bench

25999.265 -> to your Amazon redshift,

26000.718 -> you can perform whatever queries you like.

26003.2 -> So let's go back to our Amazon redshift console.

26006.4 -> Well, So this is the cluster.

26009.4 -> I'm going to click on this here you have queries

26011.8 -> when you click on that all the queries,

26013.652 -> which you performed till now will be shown.

26015.7 -> So this is the query

26016.8 -> so it says first name from users was from State NH.

26020.2 -> This was the query which we performed earlier.

26022.847 -> So you have all the data

26024.258 -> or all the information regard the queries

26026.4 -> which are executed.

26027.5 -> Well, that's all about Amazon redshift.

26030.2 -> So guys, this is

26031.2 -> how easy it is to create a data warehouse using

26033.5 -> Amazon redshift go ahead

26035.1 -> and explore different many other features of Amazon redshift.

26038.2 -> Well, I've just showed a part of them here.

26040.3 -> So go ahead and create a database perform

26042.3 -> various queries and have fun.

26049 -> So when you talk about software development,

26051.2 -> you have to mention develops.

26052.9 -> Now.

26053.154 -> Let's try to understand why to do that.

26055.507 -> Let me give you this basic definition first.

26058.101 -> So it is nothing but a set of practices intended to reduce

26061.5 -> the time between committing the change to a system

26064.3 -> and the change being placed into normal production

26066.9 -> while ensuring high quality.

26068.8 -> Yes, very text bookish and again for people

26071.652 -> who do not know

26072.6 -> what devops has this might seem a little way.

26075.4 -> So let me just simplify this definition for you people again.

26079.062 -> See an image here

26080.1 -> what you see is you see a developer.

26082.169 -> You see an operator and there is a deployment wall

26084.9 -> which none of these two is ready to take responsibility

26087.877 -> of they're pushing the responsibility on someone else.

26090.9 -> So yes, this is what the scenario is

26093.7 -> when you talk about software development again,

26096 -> let me give you a little more idea about this particular term.

26099.062 -> So let's try to understand how developers work

26101.312 -> and how operators work and when you talk about developers,

26104.1 -> their responsibility is to create code to update

26106.63 -> this code whenever required wait for the next releases and

26109.7 -> if there are any changes commit those changes submit

26112.257 -> those changes and again move it to the production environment

26115.257 -> where the operators take care of it then wait for the feedback

26118.307 -> from The Operators

26119.2 -> if there is any

26120.014 -> and then again go through the changes

26121.985 -> if there are any likewise wait

26123.549 -> for newer software is newer products to work on.

26126 -> So, yes, this is what their responsibility is create

26128.4 -> code create applications, right?

26130 -> So what happens here is when you do create a software,

26133.2 -> so there are constant releases that you need to focus on.

26136 -> We all know that every now

26137.125 -> and then you'd be getting a Windows update

26138.9 -> or Our mobile phone update saying that okay,

26141 -> you have a new operating system new release new version updated.

26144.25 -> So this is how the technology is working.

26145.9 -> Everything gets updated every now and then so the reason this

26148.9 -> is happening is people want to stay competitive in the market.

26151.424 -> The software company is at least and they want to ensure

26153.9 -> that the product has the latest features.

26155.7 -> So this puts burden on the developers

26157.5 -> because they have to constantly update the software now

26160.2 -> once they update a particular software.

26162.1 -> It has to go and work in the production environment,

26164.392 -> but at times it does not work in the production environment

26167 -> because the developer environment And the production

26169.429 -> environment might be a little different.

26171.379 -> So something that works in the developer environment

26173.698 -> might not work in the production environment.

26175.7 -> So again, some changes are thrown back by The Operators

26178.4 -> and developers again get stuck.

26180.1 -> So they have to wait

26181.1 -> till they get the response from The Operators and

26183.2 -> if it takes a longer while their work is stuck.

26185.203 -> Now if you take a look at it from The Operators perspective

26187.8 -> the job is to ensure

26188.8 -> that whatever is working in the developer environment.

26191.467 -> It has to work in the production environment as well.

26194.067 -> They deal with the customers get their feedback and

26196.549 -> if there are any changes which need to be implemented.

26199.199 -> At times the implemented themselves

26200.937 -> if there are any core or important changes

26203.032 -> that are required those have to be forwarded to the developers.

26206.2 -> So yes, what happens at time says what works

26208.4 -> as I've already mentioned works in the developer environment

26211 -> does not work in the production environment

26213.188 -> and operators might feel

26214.6 -> that this was the responsibility of the developer

26216.702 -> which they did not do and probably they are facing problem

26219.2 -> because of it again the customer inputs.

26221.3 -> If those are forwarded back to the developers team.

26224.3 -> The operator team has to depend

26225.863 -> on the developers to make those changes, right?

26228.183 -> So as you can you see these two teams are

26230.2 -> interdependent on each other and at times they feel

26232.7 -> that somebody else's work.

26233.9 -> The developers work is pushed upon the administrators

26236.299 -> or the developers feel

26237.4 -> that the administrators teams work is pushed up on their side.

26240.8 -> So there is this constant tesl with the company owners have

26243.9 -> to take care of they have to think as an okay

26246.1 -> if this goes on how can I generate

26248.3 -> or produce new releases new software's every now

26250.9 -> and then this could be a problem, right?

26253 -> So this is what devops does as the name suggests.

26255.5 -> It is deafplus Ops that means it combines the operation.

26259.05 -> Team and the devops team

26260.6 -> when I say combined they bring in this approach

26263.2 -> where integration and deployment and delivery.

26265.7 -> It happens continuously and the fact

26267.808 -> that these things happen continuously.

26269.937 -> We do not see the tussle between these two teams.

26272.7 -> So yes as you move further develops helps you unite

26275.558 -> these two teams and they can work happily together.

26278.5 -> So this is what happens

26280 -> in devops you code your plan you release this deployment.

26285 -> There's operations.

26286.094 -> There's monitoring this testing everything happens in a Pipeline

26289.8 -> and these are some of the popular devops tools

26292.5 -> that let you take care of all these things.

26295.3 -> But now again this is the warps

26297.204 -> in general you have get you have puppet you have Chef

26300.316 -> you have ansible saltstack

26301.867 -> that help you automate this process of integration

26304.79 -> and deployment of your software,

26306.7 -> but the fact

26307.452 -> that everything is moving to Cloud these days we

26310.4 -> are thinking about how can we do all these things from cloud.

26313.246 -> Do I need to move in these many tools

26315.1 -> if you want definitely you can move all these tools

26317.8 -> but a platform.

26318.9 -> Ew s which is a popular cloud service provider

26321.691 -> what they have done is that ensured

26323.8 -> that all the requirements of develops can be taken care

26326.731 -> on the platform itself and you have various services

26329.5 -> that are made available to you

26331 -> that help you in this process now say for example,

26333.5 -> you have easy to write instances.

26335.7 -> Now you can launch servers

26337.9 -> at your will you can launch instances at your will so

26341.02 -> if your concern is scaling up and down,

26343.255 -> aw takes care of it you have various Services,

26345.8 -> which help you monitor your process.

26347.7 -> So monitoring is something that is taken care of.

26350.149 -> There's auto-scaling their various other services

26352.664 -> which this cloudfront

26353.9 -> which actually lets you create content delivery networks.

26356.7 -> I mean, you can have temporary caches

26358.7 -> where you can store your data and stuff like that.

26361.4 -> So there are various AWS services

26363.9 -> that actually help you carry out the divorce

26366.6 -> or the CI CD process with a lot more ease and

26369.812 -> that is why it develops an AWS.

26372 -> They form a very good combination or a combo, hence.

26375.6 -> We are talking about this term today.

26377.3 -> That is AWS develops.

26378.802 -> Not that we have some idea about what AWS is what devops

26382.603 -> is let's try to understand

26384.4 -> how continuous integration delivery and deployment

26387.7 -> work with AWS and

26389.1 -> how they incorporate the devops approach to do that.

26392.7 -> Lets try to understand continuous integration

26394.9 -> and delivery first.

26396 -> So let's take a look at this diagram

26398.201 -> to understand this process.

26399.9 -> So these are the four steps

26401.452 -> that are there you have split the entire chunk

26404.1 -> of code into segments.

26405.4 -> So guys think of it as more

26406.9 -> of your mapreduce kind of an action.

26408.5 -> I mean, I mean what happens is

26409.815 -> in your continuous integration and delivery.

26411.965 -> We are trying to bridge the gap between the developer team

26414.7 -> and the operations team, right?

26416.5 -> So we try

26417.054 -> and automate this process of integration and delivery.

26420.321 -> So the fact

26421 -> that continuously you have various software updates,

26424 -> which I just mentioned right?

26425.5 -> So what if I have like 50 or maybe a hundred developers

26428.8 -> who are working parallely now,

26430.564 -> there are certain resources

26432.1 -> that need to be used by everyone.

26434 -> Right?

26434.4 -> So what problem it creates is suppose

26437.2 -> if I'm working on a particular code.

26438.957 -> I work on that piece of code.

26440.4 -> And if somebody else is working on that piece of code

26443.1 -> and we have this Central system

26445 -> where the data needs to be stored.

26446.673 -> So I'm working on this piece of code.

26448.5 -> I make a particular change and I store it there now

26451.095 -> someone else is working on this piece of code

26453.487 -> and that someone makes a change and he

26455.5 -> or she stores it there, right?

26457.339 -> So tomorrow if I come back probably I need a fresh copy

26460.516 -> of this piece of code.

26461.8 -> What if I just start working on the piece of code

26464 -> that I'm working and then I submit that code there

26466.583 -> so there would be an ambiguity right whose coat to be accepted

26469.8 -> who's codes copy should be made

26471.5 -> so we need this Central system to be so smart that each time.

26475.567 -> I submit a quote it updates.

26477.369 -> It runs tests on it and see is

26479.3 -> whether it's the most relevant piece and

26481.627 -> if someone else submits

26482.984 -> that deputies of code then tests are run on that piece of code.

26486.631 -> This system should be able to ensure

26488.712 -> that each of us next time

26490.183 -> when we go and pick the piece of code.

26492.318 -> We get the latest piece of code

26494.088 -> and we get the most updated one are the best piece of code.

26497.5 -> So this process of meeting the code putting in that piece

26500.887 -> of code and automating this whole process so that

26503.71 -> as it moves further,

26504.843 -> it also gets delivered and deployed to the production

26507.902 -> in the similar manner with the tests

26510 -> that need to be conducted is called as continuous integration

26513.2 -> and delivery now integration

26514.802 -> as I've mentioned here the continuous updates

26517.59 -> in the source code or the code

26519.2 -> that I'm building the code is built compiled and

26522 -> when I talk about delivery and deployment the pieces of code

26525.055 -> once they're ready to move to the production environment,

26527.943 -> those are continuously he deployed to the End customer

26530.693 -> now deployment seems a very easy process, right?

26533 -> I mean picking up the code and giving to the End customer.

26535.6 -> No, it's not that easy deployment actually involves

26538.8 -> taking care of all the servers

26540.25 -> and stuff like that and spawning up.

26542.149 -> These servers is a difficult task.

26543.86 -> So automating this process becomes very important.

26546.4 -> And if you do it manually you're going to suffer a lot.

26549.2 -> So yes, this is where continuous integration

26551.588 -> and delivery comes into picture code.

26553.5 -> It is continuously generated.

26555.2 -> It is compiled it is built and compiled again then tested.

26558.7 -> And then delivered and made sure

26560.582 -> that it gets deployed to the End customer

26562.783 -> the way it was supposed to be so you can see

26565.097 -> that there are certain steps are it says split the entire chunk

26568.5 -> into codes or into segments keep small segments,

26571.568 -> of course into manageable form

26573.4 -> basically integrate these segments multiple times a day,

26576.4 -> which I mentioned

26577.192 -> that there should be a central system

26578.9 -> and then adopt a continuous integration methodology

26581.4 -> to coordinate with your team.

26583.4 -> So this is what happens.

26584.622 -> I mean you have a source code repository

26586.607 -> where the developers work they continuously.

26588.75 -> Submit their pieces of code now repository think

26591.1 -> of it as a central place

26592.29 -> where the changes are constantly committed.

26594.516 -> Then you have a build server

26596 -> where everything gets compiled reviewed tested integrated

26599.856 -> and then packaged as well.

26601.6 -> Finally certain tests

26602.86 -> final tests are run to go through the final integrity's

26606.1 -> and then it goes to the production environment

26608.8 -> where this process the building the staging

26611.839 -> and the committing process it

26613.744 -> gets kind of automated to reduce your efforts.

26616.7 -> So guys when you talk about a double Dress

26619.177 -> in particular you have something called as AWS code pipeline,

26622.8 -> which lets you simplify this process.

26625.6 -> It lets you create a channel

26627.748 -> or a pipeline in which all these processes

26630.753 -> can be automated.

26632 -> So let's take a look at those processes as well first.

26635.2 -> Let's get through the definition part.

26637.194 -> Let's see what it has to say.

26638.9 -> I wouldn't be blankly reading this thing

26641.175 -> and then promptly

26642.2 -> we'd be having the explanation part that follows.

26645.1 -> So as the definition says it is a code pipeline

26648.3 -> which Is nothing but a continuous

26650.029 -> delivery service we talked about continuous delivery already

26653.5 -> and you can use the service to model visualize

26656.8 -> and automate certain steps

26658.2 -> required to release your software something

26660.223 -> that we've already

26661.1 -> discussed in continuous integration and delivery.

26663.6 -> So this is basically a continuous delivery service

26666.2 -> which lets you automate all these processes.

26668.7 -> So as I mentioned automating these processes

26670.9 -> becomes very important.

26672.4 -> So once you do use the service,

26674.5 -> these are some of the features it provides

26676.337 -> you it lets you monitor your processes in real-time

26678.649 -> with Comes very important

26679.9 -> because we are talking about deploying software's

26682.6 -> at a greater pace.

26683.9 -> So if this can happen in real time,

26685.6 -> I mean if there is any change and

26687.2 -> if it is committed right away probably just saving a lot

26689.8 -> of time right you ensure consistent release process.

26693.5 -> Yes as I've told you deploying servers is a difficult task

26697.3 -> and time-consuming task.

26698.756 -> If this can be automated a lot

26700.624 -> of effort is saved speed of delivery

26702.887 -> while improving quality.

26704.3 -> Yes, we've talked about this as well

26706.19 -> and will pipeline history details monitoring becomes.

26709 -> Very important guys.

26710.176 -> So what court pipeline does is actually lets you take a look

26713.647 -> at all the processes that are happening.

26715.7 -> I mean if your application is built,

26718 -> it goes to the source,

26719.328 -> then it moves to the deployment.

26721.2 -> All these processes can be tracked in the pipeline.

26723.8 -> You get constant updates as a new cat.

26725.564 -> This happened at this stage.

26726.9 -> If anything failed you can detect

26728.6 -> as know K. This is the stage

26730.034 -> where it is feeling maybe stage number 3 stage number

26732.7 -> four and accordingly you can edit the stuff

26735.2 -> that has happened at that stage only so weaving the pipeline.

26738.745 -> Details actually helps a lot

26740.4 -> and this is where code by plane comes into picture.

26743.1 -> So this is what the architecture of Code by plane looks like.

26746.7 -> It's fairly simple guys.

26748.2 -> So some of this might seem a little repetitive to you people

26751.293 -> because the concepts are similar the concepts

26753.6 -> which we discussed those can be implemented

26755.812 -> by using Code pipeline.

26757.02 -> So ESF talked about these things,

26758.706 -> but let's try to understand

26760.076 -> how the architecture works

26761.376 -> and we will be using some other terms

26763.176 -> and discuss some terms in the future slides as well,

26765.6 -> which we've already talked about but each

26767.816 -> of these Isis they do this task a little differently

26770.658 -> or help you automate these processes hence the discussion.

26773.835 -> So, let's see

26774.4 -> how much level can we keep it unique and let's go ahead

26777.1 -> with this discussion as well.

26778.7 -> So, let's see how the code pipeline Works.

26780.8 -> Basically there are developers

26782.3 -> as I've already mentioned these developers would be working

26784.8 -> on various pieces of codes.

26786.52 -> So you have continuous changes and fixes

26789.028 -> that need to be uploaded.

26790.713 -> So you have various Services.

26792.7 -> One of them is code commit which lets you have

26795.717 -> a initial Source management system kind of a

26798.6 -> Which lets you basically take care of repositories

26801.323 -> and stuff like that.

26802.5 -> So it lets you directly connect

26804.283 -> with get I would be talking about get

26806.362 -> what get is but for people who know what get is

26809.068 -> if you have to manage your git repositories,

26811.434 -> you have a service called as code commit.

26813.659 -> So this is what happens

26814.901 -> if there are any changes those

26816.524 -> go to the source developers can commit those changes there

26819.423 -> and then it goes into the build stage.

26821.488 -> This is where all the development happens.

26823.925 -> Your source code is compiled

26825.624 -> and it is tested then it goes to the twist aging phase.

26828.846 -> Where it is deployed

26830.022 -> and tested now when I say tested these are some final tests

26833.3 -> that have to be implemented

26834.682 -> before the code gets deployed.

26836.323 -> Then it has to be approved.

26837.8 -> Manually.

26838.3 -> It has to be checked manually whether everything is in place.

26841.3 -> And finally the code is deployed to the public servers

26844.071 -> where customers can use it again if they have any changes

26846.995 -> as I've mentioned those can be readily taken from them

26849.878 -> and it goes back again to the developers

26852 -> and the cycle continues

26853.485 -> so that there is continuous deployment of code.

26856.456 -> This is another look at it.

26858.2 -> It is very Simple

26859.2 -> but this is more from AWS perspective.

26862 -> So if there are any changes

26863.615 -> that developers commit those go to the source now,

26866.497 -> your data is stored in a container called as S3

26869.182 -> that is simple storage service in the form of objects.

26872.3 -> So if there is anything

26873.743 -> that has to happen the data is either fetched

26876.605 -> from the storage container,

26878.3 -> which is S3 and the changes are built and then again a copy

26882.6 -> of it is maintained in the form of zip

26884.515 -> as you can see here.

26885.515 -> There are continuous changes

26886.929 -> that are happening and those get stored.

26888.9 -> In the S3 bucket now S3 should preferably be

26892 -> on the region or in the place where you are pipeline.

26894.6 -> Is that helps you carry

26895.844 -> out the process of continuous integration and delivery

26898.6 -> with he's in case

26899.6 -> if you are concerned with multiple reasons,

26901.8 -> you need to have a bucket at each reason

26904.2 -> to simplify these processes.

26905.911 -> So again here to the code gets to the source.

26908.6 -> It is probably submitted to the build stage

26910.755 -> where the changes happen a copy is maintained at S3.

26913.621 -> And then it goes to the staging again a copy is maintained

26916.55 -> and then it gets deployed.

26917.964 -> So this is

26918.477 -> how the Quarter pipe line works and to actually go ahead

26921.609 -> and Implement all the actions of quarter pipe line.

26924.2 -> You have a service or the services

26926.5 -> that is your code deploy built and code commit in AWS.

26930.2 -> So these Services actually help you carry out some

26933 -> or most of these processes that are there.

26935.1 -> Let's take a look at those services

26936.8 -> and understand what do they do?

26938.3 -> So first and foremost you have your code deploy code built

26942.1 -> and code commit.

26943.3 -> So this is not the order

26944.706 -> in which you deal with these things.

26946.535 -> Now these things actually help you in Automating

26949.103 -> your continuous delivery

26950.457 -> and deployment process they have their individual commitments.

26953.9 -> Let's talk about them one by one first.

26955.902 -> Let's talk about code commit which is last in the slide.

26958.8 -> So basically I talked about moving a piece

26960.979 -> of code to a central place

26962.558 -> where you can continuously commit your code and get

26965.6 -> the Fresh store the best copy.

26967.409 -> That is their right so code commit

26969.6 -> what it does is it helps you manage?

26971.658 -> Your repository is in a much better way.

26973.9 -> I mean think of it as a central repository.

26976.37 -> So it also lets you connect

26977.9 -> with get Which itself is a central storage or a place

26981.4 -> where you can commit your code you can push

26983.5 -> and pull that piece of code from their work

26985.7 -> on it make own copy of it submitted back

26988.1 -> to the main server

26989.321 -> or your main or Central operating place

26991.9 -> where your code gets distributed to everyone.

26994.54 -> So that is get and what core come it

26996.598 -> does is it lets you integrate with get in a much better way

26999.8 -> so you do not have to worry about working

27001.8 -> on two different things.

27003 -> It helps you not Ematic authorization

27004.595 -> pulling in the repositories

27005.796 -> that are there in your gate account

27007.496 -> and a number of other things.

27008.7 -> He's so yeah,

27009.5 -> that is what code commit as then

27011.1 -> you have something called as code built

27013.3 -> as the name suggests.

27014.308 -> It helps you automate the process of building your code

27016.9 -> where your code gets compiled tested

27018.958 -> certain tests are performed.

27020.6 -> And again, making sure

27022 -> that artifacts of the copies of your code are maintained

27024.9 -> in your S3 and stuff like that.

27026.598 -> So that is what code billed as and then you have code deploy

27030.133 -> as I've already mentioned deployment is not an easy task.

27033.3 -> I mean if we are stuck in a situation

27035.335 -> where we are supposed to manage the repositories

27038.1 -> we're supposed to On quite a few things in that case

27041.111 -> if we are forced to kinda take a look at the servers as well

27044.6 -> for new instances pain new piece of servers

27047.202 -> that could be a tedious task.

27049 -> So code deploy helps you automate

27051.114 -> these processes as well.

27052.7 -> So this was some basic introduction to these things.

27055.7 -> Let's just move further and take a look at the demo

27057.7 -> so that we can talk about some of these terms and the terms

27060.6 -> that we've discussed previously in a little more detail.

27063.35 -> Now in one of my previous sessions.

27064.986 -> I did give you a demo on continuous integration

27067.2 -> and delivery I believe

27068.7 -> If they were certain terms

27070 -> that people felt were taken care of in a speedy way hope

27073.8 -> that I've explained most of the terms

27076.1 -> with more finesse this time and in more detail

27079.5 -> as we go through the demo to

27080.769 -> I will try and be as low as possible so that you understand

27083.4 -> what is happening here.

27084.6 -> So let's just jump into the demo part guys.

27086.8 -> So guys, what I've done is I've gone ahead

27088.9 -> and I've switched into my AWS console for people

27092.229 -> who are new to AWS again.

27094 -> You can have a free tier account with AWS.

27096.269 -> It's very easy.

27097.1 -> You have to go and sign input A credit card

27099.15 -> or debit card details a free verification would happen

27102.1 -> and probably you would be given access to these Services most

27105 -> of these services are made available to you

27107.1 -> for free for one complete year

27108.4 -> and there is certain limitation on these services.

27111 -> So you have to follow those limitations

27112.9 -> if you cross those limitations,

27114.303 -> maybe you'd be charged but that happens rarely.

27116.603 -> I mean if you want to get started

27118.109 -> definitely this one year free subscription is more

27120.449 -> than enough to get Hands-On on most of the services.

27123 -> So I would suggest

27123.774 -> that you create this free tier account.

27125.422 -> If you've taken a look at my previous videos,

27127.377 -> you know that how to create a free to your account.

27129.649 -> If not, it's fairly simple.

27131 -> Just go to your browser

27132.372 -> and type AWS free tier and probably you would be guided

27135.586 -> as in what details have to be entered.

27137.763 -> It's not a complex process.

27139.351 -> It is fairly simple and it happens very easily.

27141.8 -> So we just have to go ahead and do that.

27143.674 -> Once you do that again,

27144.851 -> you'd be having access to this console guys.

27147.034 -> So once you have an access to this console,

27149.168 -> you have all the services that you can use.

27151.1 -> So in today's session we would be working on a similar demo

27154 -> that we worked in our one of the previous sessions here.

27156.94 -> We would be creating an application.

27158.834 -> In a pass application platform as a service application

27161.8 -> and we would be deploying that application using

27164.241 -> our core pipeline.

27165.3 -> So there would be talking about other terms as well.

27167.375 -> Like code commit code different code built.

27169.173 -> So do not worry we would be discussing those as well.

27171.4 -> So this is what the demo is for today's session.

27173.5 -> So guys, let's start by creating a pass application to do that.

27176.84 -> We would be using elastic Beanstalk,

27178.73 -> which lets you have a ready to use template and using

27181.5 -> which you can create a simple application

27183.56 -> at this being a demo guys.

27184.9 -> We would be creating a very simple and a basic application.

27187.907 -> So just Come here and type elastic Beanstalk.

27191.6 -> So when I come to this page guys,

27193.328 -> if you've created an application,

27195.011 -> it would show you those applications,

27196.811 -> but the fact that

27197.609 -> if you're using it for the first time,

27199.459 -> this is the console that you'd be getting

27201.4 -> that is why I have created this demo account.

27203.7 -> So that probably we get to see

27205.464 -> how you can start from the scratch.

27207.4 -> So if you click on get started

27209.2 -> as creating an application here is very easy,

27212.088 -> like extremely easy you have to enter in certain details

27215.7 -> only it takes a while to create an application under Stan double

27219.3 -> I would tell you why it takes the time but once it happens,

27222.341 -> it happens very quickly.

27223.6 -> So all you have to do is give your application name.

27226 -> Let's call it say deployment tap.

27229.2 -> I'm very bad at naming conventions.

27231.2 -> Let's assume that this is good.

27233.7 -> You can choose a platform guys.

27235.25 -> You can choose whatever platform you want.

27237 -> Say PHP is

27237.514 -> what I'm choosing right now as I told you it's a pass service

27240.6 -> past that is platform as a service means

27242.6 -> that you have already to use platform guys.

27244.9 -> That is why you can just choose your platform and your elastic.

27248.547 -> In stock would ensure

27249.7 -> that it takes care of all the background activities.

27252.09 -> You do not have to set up your infrastructure.

27254.2 -> It takes care of it.

27255.376 -> So once I select the platform I can use the sample application

27258.65 -> or use the code if I have in this case,

27260.885 -> I would be using a sample code

27262.5 -> that AWS has to offer and I say create.

27266.6 -> There you go guys.

27267.595 -> This thing is creating my application.

27269.796 -> So whatever is happening here,

27271.5 -> it shows that these are the processes now,

27273.803 -> it is creating a bucket to store all the data

27276.391 -> and stuff like that.

27277.568 -> So it would take care of all these things guys.

27279.9 -> It might take a couple of minutes of meanwhile.

27282.2 -> Let's just go ahead and do something else.

27284.3 -> Let me just open it up loose console again.

27287.573 -> Somewhere else.

27288.8 -> I hope it does not ask me to sign in again.

27290.649 -> I've already signed in.

27291.8 -> So meanwhile that application gets created.

27293.97 -> Let me just go ahead and create a pipeline guys.

27296.4 -> So code pipeline again as fairly simple guys.

27300.1 -> What happens here is very easy.

27302.2 -> I just go ahead and put in certain details here as well

27304.9 -> in my pipeline would be created.

27306.5 -> So do you want to use the new environment

27308.6 -> or wanna stick to the old one?

27310.1 -> You can click on Old right

27311.7 -> and you can go back and create it the way it was done

27314.8 -> or you can use the previous environment.

27316.542 -> I'm going to stick.

27317.391 -> And I was very comfortable with that.

27319.271 -> So let's just stick with it.

27320.5 -> If you want you can use the new interface.

27322.3 -> There's not a lot

27323.1 -> of difference certain little are minor differences.

27325.8 -> So you can just come here and add in the name

27328.4 -> of the pipeline that you want to creates a demo pipeline.

27333.7 -> I see next Source provider guys.

27336.5 -> I would be using GitHub here

27338.129 -> because I want to basically pick up a repository from GitHub

27341.626 -> that helps me in deployment.

27343.264 -> So I need to connect together for that.

27345.5 -> It would ask me to authorize if you have an account.

27348 -> You can always do that so

27349.335 -> that it can basically ringing all the repositories

27351.961 -> that you have.

27352.864 -> So just say authorized if not,

27354.8 -> you'll have to sign in once so my account has been added

27358.8 -> here guys repository.

27360.1 -> I need to pick a repository.

27361.5 -> This is the repository that I would be picking.

27363.7 -> Do not worry.

27364.464 -> I would be sharing this piece of cord or is

27366.9 -> what you can do is you can just go to GitHub and type AWS -

27370.6 -> Cole pipeline - S3 - code deploy -

27373.628 -> Linux now it is a repository given to you by AWS

27377.3 -> if you take a look at it,

27378.6 -> and if you type it just the way it is named here from AWS.

27381.9 -> You should get that repository in GitHub.

27383.9 -> You just have to go ahead and Fork it

27385.9 -> into your GitHub account

27387.345 -> and probably you

27388.286 -> would be able to import that repository directly.

27391.109 -> You can see that repository has been fought.

27393.6 -> Here into my GitHub account.

27395.34 -> You just type the name hear this name search it

27398.2 -> and probably there would be an option your fork.

27400.5 -> I fucked it.

27401.1 -> So it does not activate this option for me in your case.

27403.85 -> It would be activated.

27404.804 -> You have to just click on it and the repository

27406.8 -> would be forked into your account.

27408.5 -> So I am getting or importing a fork from my GitHub.

27412 -> I was authorized my account and then I can just go ahead

27415.3 -> and do the stuff Branch Master Branch.

27417.9 -> Yes, and just do the next step build provider no build here.

27422.7 -> I don't have Teenager to build so I don't need to go ahead

27425.717 -> and provide a bill provider.

27427.2 -> You can use code build right guys,

27429.167 -> if you want to move

27430.3 -> or basically deploy your code to ec2 instances.

27433.7 -> You can use code build.

27435.089 -> If you want in this case.

27436.6 -> I have an application

27437.9 -> in which I have an ec2 instance and stuff like that.

27440.302 -> So I don't need to go ahead and do any building stuff.

27442.8 -> Hence no build for me.

27444 -> So I say next deployment provider in this case.

27447.951 -> My deployment provider would be my EBS

27450.865 -> so we have that option.

27452.988 -> Yes.

27453.295 -> Yes select EBS elastic Beanstalk.

27456 -> Naughty BST b stands for elastic block storage.

27459 -> That is a different thing guys.

27460.299 -> Elastic Beanstalk.

27461.2 -> Make sure you do that application name deployment

27463.666 -> a pause the name, right?

27464.9 -> Yep, and the environment.

27467.1 -> This is the environment.

27468.3 -> It creates the environment on its own.

27470.2 -> I believe that it has created the environment.

27472.847 -> It says it is starting.

27474.2 -> I hope the environment has been created.

27476.247 -> So guys, let's just see

27477.6 -> whether our application is up and running

27479.648 -> so that probably I can pass in the details.

27481.8 -> Yes, the application has Been created guys.

27485 -> So let's just go back and select this say next

27489.6 -> now create an IM role is already saying so let's say sample.

27496.2 -> Okay guys, so

27497.095 -> what happens normally is and I am user gets created each time.

27501.3 -> You create a role.

27502.753 -> So in this case it is asking me to create one taxes create a new

27507.6 -> item role database code pipeline nice shell of successful.

27512.1 -> So role has been In created next step now.

27515.4 -> It gives me the details guys.

27517.4 -> Basically it would tell me what are the stuff

27519.6 -> that I've done.

27520.379 -> So everything is here.

27521.479 -> I don't think I need to cross check it.

27523.347 -> You might just cross check the stuff

27525.05 -> that has happened and say create a pipeline.

27527.2 -> So guys, the pipeline has been created here

27530.43 -> as you can see.

27531.6 -> These are the stages that have happened.

27534.1 -> If you want you can just go ahead and say release

27536.7 -> a change now these things are happening guys,

27539 -> and let's hope the deployment also happens successfully.

27542.123 -> We've just created an eye.

27543.6 -> User let's see whether it falls in place.

27545.952 -> Everything is in place.

27547.311 -> As far as the source part is concerned it has succeeded

27550.6 -> and now the deployment is in progress.

27552.509 -> So it might take a while.

27553.6 -> Meanwhile just go back and take a look at this application.

27556.5 -> So if I open this application guys It would give me

27559.7 -> an overview of what has happened with this application guys,

27563 -> as you can see,

27564.1 -> these were the steps that were implemented.

27566.5 -> Now the application is available for deployment.

27569.1 -> It successfully launched the deployment environment.

27571.651 -> It started with everything

27573 -> that it was supposed to do like create

27575 -> or launch an ec2 instance and stuff like that.

27577.576 -> So everything is mentioned here

27579.4 -> what happened at what time so this is a passive is guys

27582.9 -> and it works in the background.

27584.25 -> I mean if you actually go ahead

27585.8 -> and launch an instance on your own configure,

27588.152 -> I am users can As you go to groups,

27590.053 -> it takes a longer while

27591.212 -> but what the service does is it automate that process.

27593.882 -> It understands that you need an ec2 instance.

27596.2 -> It launches that instance.

27597.5 -> It assigns security groups.

27598.8 -> We PCS and stuff like that.

27600.3 -> All you have to do is run your application on top

27602.7 -> of it as simple as that.

27604.113 -> So it has taken care

27605.291 -> of everything and run a PHP application for me.

27608.1 -> So yes, this is what has happened here.

27611.2 -> If I just go back here.

27612.911 -> Meanwhile, let's see

27614.349 -> whether our code has successfully run you can see

27617.8 -> what has happened here.

27619.2 -> I am released the change as

27620.7 -> well and you can move the pipeline history.

27622.8 -> If you want you can click on this icon and all the details

27625.2 -> would be given to you what happened in what stage.

27627.6 -> So these are the things

27628.923 -> that have happened till time now guys,

27631.1 -> let's just go back and take a look at something

27633.5 -> that we could so I'm going to come here and say

27636.5 -> service easy to because my app launched an ec2 instance.

27640.4 -> So there should be an instance created

27642.4 -> by elastic Beanstalk C1 instances running.

27645.9 -> It has a keep your attached to it as well.

27648.2 -> So He's any details guys.

27650.123 -> I have a public IP associated with it.

27653.169 -> If I copy it.

27654.2 -> There you go copy this IP

27655.973 -> and I say run this IP you have successfully created a pipeline

27660.336 -> that retrieved this source application

27663.093 -> from an Amazon S3 bucket

27664.7 -> and deployed it to three instances.

27666.9 -> It did not deploy

27667.923 -> to three instances using Code deploy.

27670.142 -> It deployed it to only one instance.

27672.3 -> You see this message

27673.6 -> that it deployed it to three instances is

27675.917 -> because the code or the repository that I used it.

27678.8 -> Supposed to deploy two different instances

27680.939 -> if there are multiple instances and hence.

27683.148 -> This message would have made more sense than but the fact

27686.112 -> that we've deployed it to only one ec2 instance.

27688.6 -> It should actually display that message.

27690.55 -> So the message

27691.211 -> that you're supposed to give you can actually come back here

27694 -> and make change to the piece of code that you worked on.

27697.119 -> If you go to the readme MD file,

27699.7 -> I think this is where the piece of code is.

27702.5 -> There you go not here.

27705.7 -> Where is that file that needs to be edited?

27707.8 -> Let me just take a look at.

27709.201 -> Some other files as well.

27710.451 -> Yeah.

27710.746 -> This is the file.

27711.648 -> Sorry.

27711.968 -> So if you go to the index dot file here is the message guys,

27715.2 -> so you can probably make a change to this message instead

27718.3 -> of seeing three you can say one here edit this piece of code

27722.6 -> and then you submit the code again.

27724.6 -> So when you do launch or type

27726.533 -> in this IP address probably that change would be reflected.

27730.4 -> So guys, what we've done is we've actually gone

27732.7 -> ahead and created a pipeline successfully

27735.2 -> and in that process we've actually gone ahead and move.

27738.8 -> Move or deployed our application from here.

27741.526 -> So guys in case

27742.3 -> if I do go ahead and commit changes to the code

27744.6 -> that I just talked about those

27746.4 -> would get reflected right away in my history

27748.929 -> when I talk about this pipeline.

27750.8 -> So it does give you a continuous integration and deployment.

27754.2 -> So, I hope

27754.7 -> that this session made sense to you people

27757.5 -> and we've talked artist upon most of the stuff

27760.208 -> that I wanted to talk about.

27761.861 -> And as far as the session goes guys,

27763.811 -> I would be resting it here.

27770.3 -> So let's start with the first question.

27773.1 -> Now I first question says I have some private servers

27776.6 -> on my premises.

27777.9 -> Also.

27778.3 -> I have distributed some of my workload

27780.5 -> on the public Cloud.

27781.5 -> What is this architecture called?

27783.1 -> So basically our workload has been divided

27785.4 -> between the public cloud and the private Cloud now,

27788.181 -> they're asking me what is this architecture called?

27790.963 -> It's a pretty basic question guys,

27792.8 -> but if you look at the options are quite confusing,

27795.816 -> the first option is a virtual private Network

27798.404 -> then We have private Cloud,

27799.9 -> which is obviously not there.

27801.5 -> Then we have a virtual private Cloud could be the option

27804.9 -> and then we have hybrid Cloud.

27806.6 -> All right guys.

27807.391 -> So what do you think?

27808.5 -> What do you think is the right answer for this?

27811.1 -> Come on guys,

27811.971 -> let's be more interactive in this session

27814.546 -> because if it's a two-way thing then

27816.8 -> it's going to be interesting for you and for me as well.

27819.55 -> So let's make it as interactive as

27821.4 -> possible and let's get the most out of this session today.

27824.6 -> Alright, so a she says it's

27826.5 -> either virtual private cloud or hybrid cloud.

27829.588 -> So as usual,

27830.707 -> it's actually only one out of all the for

27833.784 -> so give one answer.

27835.7 -> Okay, I can see some

27837.5 -> of you are saying the right answer some are confused.

27841.6 -> It's okay.

27842.346 -> I shall clear your doubts.

27844.217 -> Alright guys, so the answer is hybrid Cloud now,

27847.6 -> why hybrid Cloud because okay.

27849.407 -> So let's actually discuss the first three options

27852.3 -> which are actually not the right answer.

27854.4 -> So it is not a virtual

27855.825 -> private Network because a virtual private Network.

27859.027 -> Is something that you use to connect your private cloud

27862.4 -> and your public, right?

27863.702 -> So to connect between your private cloud

27865.997 -> and the public Cloud you actually have

27868.2 -> to make a connection

27869.603 -> and that connection is done using a virtual private Network.

27873.726 -> Alright, then we have private clouds

27876.173 -> or private cloud is something

27878.2 -> where in you have your own servers

27880.5 -> on your own premise, right,

27882.2 -> but in our case we have public Cloud involved.

27884.9 -> So it is obviously not private Cloud virtual private cloud is

27888.429 -> not the As well

27889.326 -> because a virtual private cloud is basically

27891.9 -> a logical isolation kind

27893.572 -> of thing wherein you isolate your instances

27896.5 -> from the rest of the instances on your AWS infrastructure.

27900.2 -> And this logical isolation cloud is called

27903.1 -> a virtual private cloud and then you have hybrid Cloud

27906.5 -> which I think fits aptly by its name as well.

27909.5 -> We're in it's a mixture of your public cloud

27912.023 -> and your private Cloud infrastructure,

27914.5 -> right?

27915 -> So, let's see the answer.

27916.8 -> So the answer is hybrid cloud and the nation is like this

27920.379 -> because we are using both the public cloud

27923 -> and you're on from Isis servers,

27925.3 -> which is a private Cloud be called

27927.744 -> and hybrid architecture,

27929.5 -> right and it says here that if you want to be better

27933.1 -> if your private and public Cloud were all

27935.2 -> on the same network, right?

27937 -> So basically when you connect your public cloud

27940.337 -> and private Cloud together using virtual private Network,

27944.4 -> you basically are accessing one network and you feel

27947.663 -> that all your resources.

27949.4 -> Is it says dead on the public cloud

27951.1 -> and the private Cloud are actually there

27953.6 -> in one network, right?

27955.1 -> So it seems It's a virtual private

27957.4 -> and virtually you feel

27958.9 -> that you are on the same network,

27960.782 -> but it's they are actually two different resources

27963.747 -> or two different locations

27965.161 -> from where you are accessing your resources.

27967.5 -> Alright guys,

27968.3 -> so guys any questions regarding to the first question

27971 -> that we have discussed anything that you're not clear

27973.6 -> whether it was a very basic question,

27975.838 -> but then we are getting a very lot of Concepts.

27978.8 -> Here, we have a virtual private Network concept then we have

27982.3 -> the virtual private Cloud concept, right

27985.113 -> so it can be confusing

27986.7 -> and this is how they asked to you in interviews as well.

27990 -> Right?

27990.352 -> So you have to be very clear in your answer.

27992.731 -> You have to be very clear in your thoughts

27995.034 -> that what shall be the right answer.

27997 -> All right, so I can see

27998.5 -> that people are giving me a go there all clear.

28000.8 -> Okay guys, so let's move on to the next question then

28004.6 -> so our next question starts with our Section 1 which is easy.

28008.9 -> Questions, so it's from here.

28010.9 -> We'll be talking all about AWS.

28013.011 -> So let's start with the question first.

28015.746 -> So we have a video transcoding application

28018.9 -> and the videos are processed according to work you

28021.849 -> with the processing of a video is interrupt in one instance.

28025.4 -> It is resumed in another instance.

28027.454 -> Okay, good enough.

28028.585 -> Then currently there is a huge backlog of videos

28031.414 -> which needs to be processed.

28033.1 -> But this you need to add more instances,

28035.5 -> but you need these as mrs.

28037.1 -> Only until their backlog is Oost right.

28039.5 -> So once your backlog is reduced you don't need

28042 -> those many servers.

28043.1 -> So which pricing option should be the efficient

28046.445 -> should be the most cost efficient for this?

28049.7 -> Okay guys, so first of all,

28051.7 -> when you have question like this,

28053.9 -> a lot of things are added into it to make it confusing.

28057.293 -> So first of all,

28058.349 -> the things is the first line reads that it's

28061.073 -> a video transcoding application.

28063.104 -> So it is not relevant to your question, right?

28065.854 -> It is not relevant to what is being asked

28068.3 -> so you Discard that out

28069.538 -> and then it says

28070.414 -> the videos are processed according to work you again,

28073.311 -> it's their confuse.

28074.371 -> You don't the first thing that you should look out

28076.956 -> into a question,

28077.8 -> which are trying to men are trying to figure out

28080 -> an answer is the important part.

28082.4 -> What is important

28083.5 -> in the question you should be able to unfair

28085.7 -> that so according to me.

28087.344 -> The thing that is important is

28089.4 -> that there is a huge backlog of a video.

28091.871 -> So there is a lot of pending work

28094 -> and this pending work has to be reduced right and one.

28098.7 -> Is it is reduced we

28100 -> will not be needing those many servers.

28102.177 -> So basically we are increasing our number of servers

28105.1 -> to actually reduce the number of backlogs that we have.

28108.8 -> And once we have reduced

28110.058 -> that we have an application wherein we don't need those too

28113.1 -> many servers anymore

28114.276 -> so we should get rid of them.

28115.8 -> Right?

28116.1 -> So now it is asking me which pricing option

28119 -> should be efficient for this seller.

28121.3 -> Now, you have three kind of pricing options you have

28125.1 -> on demand pricing then you have spot pricing.

28128.8 -> And then you have reserved place, right?

28131.608 -> So you spot pricing is basically used

28134.2 -> when you want servers at the minimum cost.

28137.3 -> So basically what happens is

28139.3 -> why spot pricing has an introduced is because of this

28143 -> that new AWS has centers, right?

28146.3 -> It has service zones

28147.9 -> where it has a lot of servers now not all the time

28151.5 -> that the servers are actually being used.

28154.13 -> Some of the times are idle, right.

28156.3 -> So in times like this

28157.35 -> when the servers are ideal, what eight?

28159.1 -> SS does is it gives you a discount that

28161.5 -> since no server is being used.

28163.264 -> I shall give you a discount.

28165.081 -> If you want to use my servers now in this case

28167.863 -> you use pot pricing.

28169.1 -> So if you are going for spot pricing you

28171.5 -> see these reduced rates from AWS whenever their servers are idle

28176.094 -> and you should bid rate, right?

28178.267 -> So say example servers are being offered

28181 -> at some particular price.

28182.675 -> And you say Okay.

28183.765 -> I want these many servers, but I can only afford $10.

28187.1 -> So as long as the server And be allotted to me for $10.

28190.8 -> I shall use them.

28192.1 -> Right so you set your price a $10

28194.8 -> and then you use the service

28196.696 -> but the moment the demand increases

28199 -> in that particular server location the prices go up again.

28202.5 -> All right,

28203.1 -> and if the price crosses $10 your server shall be shut down,

28207.9 -> right you will not be able to access that server anymore.

28212.2 -> Right?

28212.6 -> So this is what spot pricing is you basically bid

28215.8 -> for the minimum price and whenever the price.

28218.902 -> Co-

28219.1 -> op your server is taken from you right then

28221.801 -> second type of pricing is called reserved pricing.

28224.9 -> When you reserve your servers for a particular amount

28228.399 -> of time say a one-year term or a three-year term, right?

28231.831 -> So it the application for this could be

28234.237 -> when say I have a company right?

28236.263 -> And my company has a website.

28238.1 -> So my website is hosted on AWS.

28240 -> Now, my website is going to be there

28242.6 -> till my company is there right?

28244.1 -> So it makes sense

28245.1 -> for me to actually reserved the instances

28247.472 -> for like maximum Dome.

28248.717 -> Possible because I have no plan to sell my company

28251.768 -> and hence take down my website right now.

28254.355 -> The reason people offer reserved instances is

28257.143 -> because as compared to the on demand pricing

28259.877 -> the reserve pricing is actually pretty cheap, right?

28263.421 -> So if you reserve your instances for a longer term,

28266.8 -> you get discounts from AWS, right

28269.3 -> and then we have on demand pricing

28271.403 -> where and we can get as many servers

28273.754 -> as you want at the time

28275.3 -> what we want as per your requirement

28277.79 -> at whatever time you Choir

28279.565 -> and the pricing for them are standard right?

28282.5 -> I'll not say they are high but they are standard

28284.854 -> but they are more than reserved pricing

28286.786 -> and your spot pricing.

28288.692 -> Now.

28289 -> Our question says

28290 -> that we have to reduce the backlog and once

28293.3 -> a backlog has been reduced.

28295.1 -> We'd have to get rid of the service.

28297.2 -> So obviously will not be using reserved instances

28299.9 -> because we cannot save

28301 -> and our backlog will be ending right?

28303.2 -> We cannot be using spot prices

28305.026 -> because we want that backlog to be reduced as soon as possible.

28308.8 -> So what we'll do is we'll be using

28310.8 -> on-demand instances or on demand pricing and using

28313.918 -> that we will reduce the workload

28315.954 -> or will reduce the backlog of the videos.

28318.5 -> And once it's been reduced we will reduce the server size

28322.199 -> for our instance.

28323.2 -> Right?

28323.5 -> So the answer for this should be on-demand instances

28326.8 -> and if you read the explanation,

28328.6 -> you should be using an on-demand instance for the same

28331.36 -> because the workload has to be processed now

28333.51 -> meaning it is urgent.

28334.5 -> Secondly you don't need them.

28335.843 -> Once you have a backlog is cleared.

28337.513 -> Therefore is evidence is out of the Picture and

28339.813 -> since the work is urgent.

28341.049 -> You cannot stop the work on engines just

28343 -> because the spot price by right.

28344.731 -> So therefore spot price in can also not be used

28347.207 -> and hence will be using on demand has.

28349.208 -> All right guys,

28350.091 -> so any doubt in this question anything that you're not clear

28353.2 -> with by are we using on demand pricing?

Source: https://www.youtube.com/watch?v=k1RI5locZE4