AWS DevOps Full Course [ 2026 ] | AWS DevOps Tutorial For Beginners | AWS DevOps Training | Edureka

Key Takeaways

Hello everyone and welcome to this full course on AWS DevOps. AWS DevOps combines cloud computing and DevOps practices to help organizations build, deploy, and scale applications faster and more efficiently. This AWS DevOps full course is designed to guide you from the fundamentals of DevOps to implementing complete CI/CD pipelines using Amazon Web Services. In this course, you will learn how AWS services support automation across the entire software delivery life cycle from source code management and continuous integration to deployment, monitoring, and security. You will work with the key AWS and DevOps tools such as Git, Genkins, Docker, Kubernetes, Terraform, and AWS services. By the end of this course, you will understand how to design, automate, and manage scalable DevOps workflows on AWS. Whether you're a beginner, developer or IT professional, this course will help you gain practical AWS DevOps skills, work on real world scenarios and prepare for industry relevant roles and certifications. So before we begin, please like, share and subscribe to Idura's YouTube channel and hit the bell icon to stay updated on the latest content from IDA. Also accelerate your DevOps career with our industry-leading advanced DevOps certification training with Gen AI designed by industry experts to help you build complete end to-end DevOps expertise. This program provides extensive hands-on learning through 15 plus real world projects, 25 plus hands-on demos and 10 plus industry use cases, ensuring you gain practical and job ready skills. You will also master 30 plus essential DevOps tools including Docker, Kubernetes, Terraform, Genkins, GitHub actions and Prometheus while learning how to implement AIdriven DevOps automation, AI ops and intelligent monitoring to build smarter and more efficient pipelines. Enroll now to become a certified DevOps professional and fasttrack your journey toward high demand DevOps roles. So check out the course link given in the description box below. Now let us get started by understanding what AWS DevOps is. So first of all let's talk about DevOps. So what is DevOps? Now as most of you all might know by now DevOps is basically a methodology. It's a set of practices to ensure faster delivery of software deployment. To stay relevant in the market these days companies are expected to deploy quality software in defined timelines. Hence the roles of software developers and system admins or the dev and the ops team have become extremely important and a lot of juggling of responsibilities happen between the two teams. Programmer or a software developer is responsible for developing the software. So basically he's supposed to develop a software which has new features, new security patches or upgrades and bug fixes from the previous installment. But a developer may have to wait for several weeks for the product to get deployed which is also known as time to market in business terms. So this delay may actually put pressure on the developer because he or she is forced to readjust his dependent activities like pending or old code, new features and products. Also when the product is put into production environment, the product may or may not exhibit some unforeseen errors. This is because the developer writes code in a certain development environment which might be different from the ones of the product environment. So from the point of view of an ops person or the operations team who are basically responsible for maintaining and assuring the uptime of production environment something that has been sent to them to test which has been confirmed runs is not running on their systems. When the code is deployed, the operations team is also responsible to handle these minor changes or minor errors on the code. At time, the ops team may feel pressured and it may seem like the developers have pushed their set of responsibilities to the operation side of the responsibility wall. But as we all know, it's all happening due to the inconsistencies in the environment and no team is actually up to blame. Now, as the company keeps investing more time and money into products and services, the number of servers admins have to take care of also keep growing. And this gives rise to even more challenges because the tools that were used to manage the earlier amount of servers may not be sufficient to cater to the needs of the upcoming and growing number of servers. So, we all are in a fix, right? But what if these two teams could work together? They could break down the sillos, share responsibilities, erase inconsistencies in the environments, start thinking alike and work as a team. Well, this is exactly what DevOps does. It helps you get software developers and operations teams in sync to improve productivity. And if I pull out an official definition, DevOps is the process of integrating developers and operations team in order to improve collaboration and productivity. And all of this is achieved through automation of workflows and productivity and basically continuous everything starting from development to delivery to deployment as well as monitoring of an application. DevOps focuses on automating everything and lets developers write small chunks of code that can be tested, monitored, and deployed in hours, which is different from writing large chunks of codes that takes weeks to test and deploy. Now that was all about DevOps. Now let's talk a little bit about DevOps and cloud or DevOps on cloud. Why do we need DevOps on cloud? Now understand that DevOps and cloud go hand in hand. They can be implemented individually of course but DevOps becomes twice as much efficient and beneficial when clubed with the cloud. It can help an organization deliver new software features much faster in a more effective manner. Many organizations try to fix their application development processes by shifting from waterfall to DevOps. Now they have this understanding that DevOps alone won't be that effective. So public and private cloud solutions are now evolving together with DevOps. This brings in products at a faster rate to the market through quick access to development environment and streamline developer processes. Infrastructure as code and automation together reduces the cloud complexity and maintenance of servers and resources which our ops team previously was very concerned about. The security also highly increases with automated repeatable processes that serve to eliminate error that can cause further issues and even more importantly it builds security controls from the very beginning to the very end of the process. Now, because you don't have any servers and your continuous operations are cloud-based, it also eliminates a lot of downtime. And last but not the least, scalability, which is one of the most important factors for applications as they are developed. When DevOps and cloud are clubed together, it reduces the cost of infrastructure and global reach also increases with this. Now that you know why you need a cloud platform, let's go ahead and look at our cloud platform of choice today which is AWS. So what is AWS? Now back in the day, handling and storing data was way different than it is now. Companies preferred storing data using private servers and that was obviously for security reasons. But however, with better usage of the internet, the trend has seen a paradigm shift for industries as they are moving their data to the cloud. Now this enables companies to focus more on core competencies and stop worrying about storing and computation. For example, back in the day if a streaming platform or a search engine platform, anything with a high volume database suffered a corruption, it would take days before their operations resumed. They would face problems scaling up and only then would they realize the need for a highly reliable, horizontally scalable and distributed system is what they need. But now with cloud services and public cloud platforms, this wouldn't be a problem. Now since every company has started to adopt cloud services, it can be claimed that the cloud is the talk of the town and AWS in particular is the leading cloud service provider in the market. AWS which stands for Amazon Web Services is an Amazon.com subsidiary which offers cloud computing services at an extremely affordable rates. Therefore, its customer base is strong and it targets everyone from individuals to startups to tech joints running the IT landscape. If you might wonder what cloud computing is, is basically the use of remote servers on the internet to store, manage and process data as opposed to an actual physical server or a personal computer to do the same. As we are talking about AWS, it is kind of an AAS or infrastructure as a service which basically gives you a server in the cloud that you have complete control over. In IAS, you are responsible for managing everything starting from the OS completely up to the application you are running. So now that we have discussed about DevOps in AWS, let's move on to our CI/CD pipeline. Now what is a pipeline or CI/CD pipeline? It's nothing but a series of steps that must be performed in order to deliver a new version of the software. At its bare bones, at its most basic, you have your build, test, and deploy stage. The CI/CD basically stands for continuous integration and continuous deployment. So CI is basically continuous integration which basically means bringing together all the developers working copies to a shared mainline. All the developers working on parallel branches of a certain upgrade of an application merge their changes into one main branch. And CD stands for continuous delivery and deployment. Now while the CI includes building and testing of your application, continuous deployment is about the processes that have to happen after the code is integrated for the app to be delivered to the users. These processes involve testing, staging and deploying the code. So at the end of this session, what we aim to do is build a CI/CD pipeline for our demo app on AWS. So for that we will have to look at a few components of AWS. So DevOps when implemented on AWS becomes a lot more efficient and effective for a productive life cycle. And the steps that are involved in AWS DevOps are code commit, code pipeline, code build, code deploy and optionally code start. So first of all we have AWS code comet which is a fully managed source control service somewhat like GitHub that hosts secure and highly scalable gitbased repository without the need of operating the system. It's mainly designed for developers who are supposed to store and version their code securely and reliably. For example, you have your IT administrators that store their scripts and configurations and your web designers who can store their HTML pages and images etc. The code comet is fully managed, has great availability, is secure, scalable, and pacens up your development life cycle. For people not aware of code comet, think of it as versioning in your S3. But how it's different is that S3 supports versioning but not collaborative file tracking features which code commit obviously does. It manages batches of changes across numerous files made by multiple developers parallelly. How it works is that you create a repository in AWS code service via the console or CLI and later using git from the development machine. You can run git clone to connect the local repository and the AWS code commit repo. You can then modify your files on your development machine via the local repository and then run git add git commit and push it to the AWS code commit repository as you do with GitHub. again like git even a git pull can be used here to synchronize the files in AWS code commit repository with your local repo which ensures that you're working with the latest version of the files. Next on our list we have AWS code pipeline which is a combination of continuous integration and continuous delivery services for a quicker and more reliable infrastructure and application updates. It automatically builds, tests and deploys a user code whenever there is a code change and it is completely based on userdefined release process models. It also integrates with AWS services like AWS code come Amazon S3 code deploy elastic beanto ops works and AWS Lambda. You can configure the pipeline either with your CLI or your graphical user interface. And like most services on AWS, even with Pipeline, you only have to pay for what you use. All of this is great and all, but why should you use code pipeline? Simple. By automating your software build, test, and release processes, AWS code pipeline enables you to increase the speed and quality of your software updates by running all new changes through a consistent set of quality checks. It automates your release process. It speeds up your delivery with quality. It allows you to choose your tools of choice. Establish consistent release processes and provide a pipeline history detail as your source of truth. Code pipeline basically breaks up your workflow into a series of stages like your source, build, test, and deploy and gives you a revision option as a deployable content. Each stage can process only one revision at a time even though multiple revisions can be processed in the same pipeline. And each stage will have at least one action to be performed which is some kind of task performed on the artifact. Once all of the actions that are configured in a stage is complete, the stage is considered as complete. After a stage is complete, it transitions the artifacts created in that stage to the next stage of the pipeline where you can manually enable or disable it. So it prevents changes from running through an entire pipeline. An approval action is granted only by the AM user and if an action fails, it does not transition to the next action or stage at all. So when a developer completes working on his code, he or she commits it to the source repository and code pipeline automatically detects the changes and builds those changes. After that, the build code is deployed to the staging server for testing and then additional tests such as integration or load tests are run by the code pipeline. Once all of the tests are run, if the code receives manual approval, then AWS code pipeline deploys the tested and approved code to the production instances. Also, every time when a user creates a pipeline, the code pipeline creates a folder for that pipeline in an S3 artifact bucket in that particular region to store input and output artifacts. Next on our list, we have AWS code build. Now, this is a fully managed build service in the cloud which compiles your source code, runs unit tests, and produces artifacts that are ready to deploy. It eliminates the need to provision, manage, and scale your own build servers. It provides prepackaged build environments for the most popular programming languages and build tools and scales automatically to meet your peak build requests. Now one prerequisite is that you must provide the AWS code build with a build project which should include information as to where to get the source code from build environment build commands and where to store the build output. How it works is that the code build will use the build project to create a build environment. AWS code build then downloads the source code from the build environment and performs tasks that you would specify in the build specifications. If there is any build output, the build environment uploads its output to the S3 bucket. And while the build is running, the build environment sends information to code build and cloudatch logs. You can use the code build console, AWS CLI or AWS SDKs to get summarized build information from code build and detailed build information from cloudatch logs as well. Now that was all about code build. Now finally let's talk about code deploy. Now AWS code deploy is a service that coordinates your application deployment and updates across the fleet of AWS EC2 of any size. It automates your code deployment to any instance, handles the complexity of updating them. It also avoids downtime during application development and rolls back automatically if failure is detected. Apart from that, it also integrates with thirdparty tools and AWS to make your job easier. It has six primary components to be specific. You have application revision, compute platform, deployment group, deployment configuration, and the code deploy agent. Now, the basic skeleton of how your deployment workflow pursues is as you can see on your screen. You basically create an application with a unique name and set up a deployment group by specifying the instances to which you want to deploy your application and the deployment type. If you're using the Lambda platform, you just deploy your deployment group's name, followed by which in your deployment configuration, you specify the success or failure condition of deployment and to how many instances you want to deploy parallelly. Then you upload the application specification file to the S3 and deploy your application as specified with the help of your code deploy agent which is running on each instance on an EC2 platform or as specified in your specification file to the deployment group when you're using a lambda platform. And finally, you check your deployment results and if you face any bugs or issues, you can always roll back and redeploy. Finally, let's discuss a little bit about CodeStar, which is basically a cloud-based development service that provides tools that you need to quickly develop, build, and deploy applications on AWS. It's basically a very templatized format where you start developing on AWS in certain minutes and you could choose from a variety of project templates. All of the software delivery is easily managed and you can work across your team very securely using the code stuff. And apart from all of this, you also are provided with a project management dashboard to monitor your application continuously. All you have to do as an AWS codear admin is create a project and add users. Your users or team members will commit changes which in turn will be built and deployed and through consistent monitoring of the application. If there are any updates required or any bugs, the developers take a decision, make updates, fix bugs, and then the loop closes back in on the team. And that's about it. The development process takes little to no time using codear. Now that we have spoken about all of these different components of AWS DevOps, I hope building the CI/CD pipeline would seem a tad more tangible to you. If you're new learners, you can always sign up for a free tier which is free for the entire year. Obviously, there are limitations to all of the services beyond which you shall be charged, but that rarely happens. So, if you're starting out with AWS and want to try out all of its features and services, the free tier is a pretty good idea. We already have a video on how to create a free tier on the AWS console. If any of you want to know how to create a free account, you can just go ahead and check that out. So, we're going to be building a CI/CD pipeline using AWS using code pipeline. And I'll try to be as slow and verbose as possible, as comprehensive as possible so as to help you guys to follow me each step of the way. So what we'll be doing here is that we'll be creating a demo application platform as a service application and we shall be deploying it using the code pipeline. So let's go ahead and create our application first. So to create an app we will be using the Amazon elastic beanto which basically has a bunch of templates ready for you. Now since this is a demo about code pipeline and not web development, we'll be creating a pretty rudimentary app. So let's go ahead and type elastic beantock. Using elastic beantoalk we can make simple apps very very quickly. And if you have already created an application created a few applications they are going to appear right here on your screen. But since we have created no applications using this particular account. This is a screen that will greet you. So we're going to go ahead and click on create application. So let's call this deployment app. We're not very original, are we? We're not going to put in any application tags. You could put them if you like, but currently they are completely unnecessary. On platform, let's pick PHP. And it automatically fills up the platform branch and version with the latest ones available. Then I'm just going to be using the sample application code and click on create application. Now this is a platform as a service app. So basically once I click on create application I wouldn't have to worry about any background processes or creating the infrastructure. Elastic beanto is going to do that for me on its own and here it's going to show you all of the steps that are taking place like create environment is starting using elastic beanto as Amazon S3 storage bucket for environment data so on and so forth. Now, this will take some time. So, let's go ahead and parallelly do something else. I'm going to open another tab, another AWS console. Okay, thankfully it did not ask me to sign in again. So, while my app gets created, what I'm going to do is I'm going to create the pipeline. So I'm going to type in code pipeline and the fun is simple even here guys. You're just going to put in certain details and your pipeline will be created for you. Now this is your dashboard. This is where you all of your recent pipelines will appear. Since in this free tier we have no pipelines created hence you have no results to display. So first things first I'm going to create a pipeline. So click on this big orange button which says create pipeline. going to give the pipeline a name. Let's just call it demo pipeline. So, as a default, I'm just going to fill in a role name AWS code pipeline service role US East demo pipeline then click on next. So for source provider I'm going to use GitHub and for that I'll have to connect to GitHub and ask me to authorize the code suite. Okay. Okay. Once you have successfully authenticated the account, you can go ahead and search for the repository. Here I'm going to choose the demo code deploy app which is actually a sample app I have forked from the AWS code pipeline repository. You can go ahead and look for it as well. It will be available in the AWS code pipelines GitHub account. Yeah. And in the branch, let's select master branch and click on next. Now we move on to the build stage. Because I have nothing major to build, I'm just going to go ahead and pick skip build stage. Then you will be prompted with a notification which will ask you if you're sure to skip your build stage. Now since I have nothing major to build, yes, I am going to skip this build stage. And for deployment here, we are going to choose a deploy provider. So here I'm going to use elastic beantock and put in my application name and my environment name. Now our application name was deployment app and our environment name would be deployment app environment. This is something which gets created automatically. So we're going to go ahead and click on next. And finally we are at the review stage where you can go ahead and review all of the details that you have just put in for your code pipeline. And I am just going to create this pipeline. It's pretty simple to do. Now this might take a few moments so kindly be patient. And then you are greeted with a notification which says success. Congratulations your pipeline has been created. Now here you can go ahead and release changes if you want. Our IM role is in place that we had created earlier. Our pipeline is a success. Now all we have to do is wait for our application to get created and then we can go ahead and deploy our application. All right, with that our application has been created. It has okay health and you can see the platform here. You can see the running version. You can see all the details, all the recent information regarding the app. Now this is a platform as a service. It basically runs all of your processes in the background. Now if you would have gone ahead created this app, configured your IM user, configured everything else that was needed, this would have taken you a lot of time. But because you are using a platform as a service feature of AWS, this entire process is automated and your work is simplified. So if you go down and look at the recent events, one thing you can see is your instance deployment is completed successfully. Just in the line above that, you can see that your new application was deployed to running EC2 instances. So basically an instance is running on EC2. So let's go ahead and go to EC2. Click on instance is running. There is one instance running. Obviously we all know which one that is. And this is your deployment app. Now if you go ahead and click on it here you can see the instance state it's running and your pipeline your source has succeeded your deployment has succeeded. You go here you can go down take a look at your IM role your subnet ID. So with that your instance has been deployed and you realize that your demo pipeline has worked. So what exactly is AWS? Well AWS is Amazon Web Services and it is one of the best cloud service providers in the market. Well, it is a complete software suit or a cloud service provider which is highly secure. It provides you with various compute, storage, database and any number of other services which we will be discussing in further slides as well. And when we talk about the market, it is the best and it has various reasons to be the best in the market. One being its flexibility, its scalability and its pricing. Other reasons being its compute capacity. Now why is it so important the compute capacity? Well, if you talk about the compute capacity, you need to understand one thing. If you take all the other cloud service providers in the market and you combine their compute capacity that is you leave out AWS and you take all others into consideration the space would be somewhere equal to say X. And if you compare it with AWS it is 6X. So AWS has more compute capacity which is six times more than all the other service providers that are there in the market. So that is a huge amount. So these are the reasons that make AWS one of the best in the market and let's try to find out what are the other reasons about AWS that make it so good. What are the services, features and its uses basically. So I would be discussing some use cases. Now if you're talking about a manufacturing organization now their main focus is to manufacture goods but most of the businesses they focus so much on various other services or practices that need to be taken care of that they cannot focus on the manufacturing goal. Now this is where AWS steps in. It takes care of all the IT infrastructure and management. That means businesses are free to focus on manufacturing and they can actually go ahead and expand a lot. architecture consulting. Now their main concern is prototyping and rendering. AWS takes care of both the issues. It lets you have automated or speed up rendering. As far as prototyping is concerned and that is why architectural business benefit a lot when you talk about using AWS or any cloud provider but AWS being the best in the market again their services are the best media company. Now as far as a media company goes their main concern is generating content and the place to dump it or to store it. Again as takes care of all these situations or both these situations. Large enterprises when you talk about large enterprises their reach is worldwide. So they have to reach their customers and their employees globally or across different places. So AWS gives you that option because it has a global architecture and your reach can be very wide as far as these points are concerned. Now advantages of AWS as I've mentioned I won't say advantages exactly I would say features as well flexibility now as far as AWS is concerned it is highly flexible now there are various reasons to support it and one of the major reasons is it's very cost effective let us try to understand these two points together rather now when you talk about flexibility the first concern you should have is you are dealing with big organizations they have a lot of data that needs to be managed deployed and taken care of now when you talk about a cloud provider if it is flexible all these things are taken care of. The second thing is it is highly cost effective. Now when I say cost effective AWS takes care of almost every aspect. If you are a beginner or a learner they have something called as a free tier. That means you have sufficient resources to use for free and that took for one long year. So you would have sufficient hands-on without paying anything. Plus it has something called as pay as you go model. Now when I say pay as you go model what it does is it charges you only for the services which you're using and only for the time being you're using them. Again that lets you scale up nicely and hence you end up paying very less since you are paying very less and since you have so many options when you are actually buying it services what that does is that gives you a lot of flexibility. Scalability again the first two points are related to this point. Now how is that? Now when I say scalability, what happens is as I've mentioned it is very affordable. So you're paying on hourly basis. If you're using a particular service for 1 hour, you'll be paying it only for 1 hour. That is how flexible it is. And what that does is that gives you a freedom to scale up and even scale down. Since it is easy to scale up, it is always advisable that you start with less and then scale as for your needs. Plus there are quite a few services that are there which can be automatically scheduled. Now what that means is you'll be using them only when there is an uptime and in downtime you can mean those get automatically shut down. So you do not have to worry about that as well. So when you talk about scalability scaling up and down is very easy as far as AWS goes. Security again uh now security has been a topic of debate when you talk about cloud services especially but AWS puts all those questions to rest. It has great security mechanism plus it provides you with various compliance programs that again help you take care of security and when you talk about real-time security even that is taken care of you can take care of all the suspicious activities that are there and not you AWS takes care of all those things and you're let free to focus on your business rather so these are the advantages which I feel that AWS adds value to and apart from that there are quite a few other points like we have automated scheduling which I just mentioned you have various integrated APIs Now these APIs they're available in different programming languages and that makes it architecturally very strong to switch from one programming language to another. So these are some of the features I feel that make AWS a wonderful wonderful service provider in the market. So let's move further and try to understand other things as far as AWS is concerned. It's global architecture. When you talk about AWS as I've mentioned it is the best service provider in the market. So what makes AWS this popular? One of the reasons is its architecture. Now when I talk about its architecture, it is very widely spread and it covers almost every area that needs to be covered. So let's try to understand how it works exactly. Well, if you talk about AWS architecture, now the architecture is divided into two major parts that is regions and availability zones. Now when you talk about the regions and availability zones, regions are nothing but different locations across the world where they have their various data centers put up. Now as far as one region goes, it might have more than one data center and these data centers are known as availability zone. You being a consumer or an individual, you can actually access or access these services by sitting anywhere in the world. To give you an example, if I'm sitting in some part of the world, say for example, I'm in Japan right now. I can actually have access to the services or data centers that are there in US right now. So that is how it works. You can choose your region and accordingly you can pick your availability zones and use those. So you do not have to worry about anything. Domains of AWS. Now when you talk about its domains, the first domain that we are going to discuss is compute. And when you talk about compute, the first thing that should come to your mind is EC2. Now when I say EC2, it is elastic cloud compute. And what it does is it lets you have a resizable compute capacity. It's more of a ROS server where you can host your websites. And it is a clean slate. Now what do I mean by this? Say for example, you go ahead and buy a laptop. It is a clean device where you can have your own OS. You can choose which OS you want and all those things. accordingly your EC2 is again a clean slate and you can do so many things with it. Now next you have elastic beanto which lets you deploy your various applications on AWS and the only thing you need to know about this thing is you do not have to worry about the underlying architectures. Now it is very similar to your EC2 and the only difference between the two is as far as your elastic beanto is concerned. You can think of it as something that has predefined libraries whereas your EC2 is a clean slate. Now when I say predefined libraries say for example you want to use Java as far as EC2 goes now this is just an example don't take it literally you'll have to say for example install everything from the beginning and start fresh but as far as your elastic beanto is concerned it has this predefined libraries and you can just go ahead and use those because there's an underlying architecture which is defined let me say it again I just gave you an example don't take these sentences literally So next we have migration. When you talk about migration, you need to understand one thing. AWS has a global architecture and there would be a requirement for migration. And what AWS does is it lets you have physical migration as well. That means you can physically move your data to the data center which you desire. Now why do we need to do that? Say for example, I'm sending an email to somebody. I can do that through internet. But imagine if I have to give somebody a movie. So instead of sending it online, I can actually go ahead and give it to someone if that person is mean reachable for me and that way it would be more better for me. My data remains secure and so many other things. So same is with data migration as well. And when you talk about AWS, it has something called as snowball which actually lets you move this data physically. Now it's a storage service and it actually helps you in migration a lot. Security and compliance. Now when you talk about security we have various services like I have IM we have KMS. Now when I say IM it is nothing but your identification and authentication management tool. We have KMS which lets you actually go ahead and create your own public and private keys and that helps you keep your system secured. Then we have storage. Now when I talk about storage again AWS has quite a few services to offer to you. We have something called as your S3. Now S3 it works as a bucket object kind of a thing. Your storage place is called as a bucket and your object which you store in are nothing but your files. Now these objects have to be stored in their root files which act as the buckets basically. And then we have something called as your cloudfront which is nothing but your content delivery network. We have something called as glacier. Now when you talk about glacier you can think of it as a place where you can store archives because it is highly affordable. Next we have networking. Now when you talk about networking we have services like VPC, direct connect, route 53 which is a DNS. Now when I say VPC it is a virtual network which actually lets you move or launch your resources that is your AWS resources. Basically when you talk about direct connect you can think of it as a least internet connection which can be used within AWS. Next on this list we have something called as messaging. Yes AWS assures secured messaging and there are quite a few applications to take care of that as well. Now we have something called as cloud trial. We have ops works. All these things they help you in messaging or communicating with other parties. Basically databases. Now storage and databases are similar but you have to understand one difference. When you talk about your storage that is where you store your executable files. So that is the difference between the two. And when you talk about databases, we have something called as your Aurora which is something which is very SQL like and it lets you perform various SQL options at a very faster rate and what Amazon claims is it is five times faster than what SQL is. So yes when you talk about Aurora again a great service to have. We also have something called as Dynamob which is a non relational DBMS. Now when you talk about non relational DBMS I won't be discussing that but this helps you in dealing with various unstructured data sources as well. Next on this list we have the last domain that is the management tools. Now when you talk about management tools we have something called as cloud watch which is a monitoring tool and it lets you set alarms and all those things. So this was about AWS and its basics as in the points which we just discussed that is what it is its uses its advantages its domain its global architecture. So yes guys what I've done is I've gone ahead and I've switched into my AWS account. The first thing you need to understand is what AWS does is it offers you a free tier. Now while I was talking about these things I just rushed through it because I know that I was going to give you a demo on these things. So and I wanted to discuss this thing in detail. Now when you talk about AWS if you are a beginner this is where you start. Now what AWS does is it provides you with its free tier which is accessible to you for 12 months and there are quite a few services which we just discussed which are available to you for free. And when I say free, there's certain limitations on it as in these many hours is what you can use it for. And this is the amount of memory or storage you can use in total and all those things and its capacity and everything. Based on that you have different instances which you can create and all those things. Now what AWS does is it gives you these services for free and as long as you stay in the limits that AWS has set, you won't be charged anything. And trust me when it is for learning purposes that is more than enough. And let's quickly go ahead and take a look at these services first and then there are few other points which I would like to discuss as well. But firstly the free tier services. Now say this is what it has to offer to you. 12 months of free and always free products. When you talk about EC2 which is one of its most popular compute services 750 hours and that is per month. Next you have Amazon quicksite which gives you 1 GB of spice capacity. Now I won't get into the details of these things as in what spice capacity is and all those things. When you have time I would suggest that you go ahead and explore these things as in what do these things do. Today we are going to focus more on the EC2 part. So for now let's quickly take a look at these one by one first. Amazon RDS which is again which gives you 750 hours of your T2 micro instance. Amazon S3 which is a storage which again gives you 5GB of standard storage and AWS Lambda 1 million free requests per month. So there are some of the videos here actually which would introduce you to these things that would help you get started with how to creating an account and all those things and this is the other important point which I would like to mention when you do create an AWS account the first thing you need to consider is they'll be asking you for your credit card details. So how does the login process work? Firstly, you go there, you've given your email id and your basic details as in why do you want to use it and all those things. Next, what it would do is just to verify your account. It would ask you for your credit card details. Even the debit card details work. I've actually tried those. So, you can go ahead and give your credit card or debit card details. And when you do that, what it does is it subtracts a very small amount from your account. I did this in India and I know that uh I was charged 2 rupees which is fairly less and that was again refunded back to me in two to three working days. The only reason they cut those two rupees was just for the verification purpose that my account is up and running and I am a legitimate user. Now as long as you stay in the limits you won't be charged anything but if you do cross those limits you'll be charged. Now you might be worried as in what if I do cross the limit would I be charged? Yes, you would be. But the fact is you actually won't go beyond it. And even if you do, you'll be notified saying that you are going above the limit or above the limit. Even when your free subscription ends, you're notified saying that do you want to enter your billing details and do you want to start billing? And if you say yes, only then you'd be charged for the subsequent months. And that is a very stringent process. You don't have to worry about it. That is you won't be losing out on any money as long as you follow these rules. So if you do not have an account, my suggestion would be you go ahead, you would log into AWS and create your free tier account which is a very easy and two to three-step process. Once you've done that, these are the services that are available to you and you can go ahead and use all of these services on your own. Next we have something called as your simple monthly calculator. Now this is a very useful app to have. What it does is whatever service which you are going to use, you can enter in the detail and accordingly you'll be given the price as well. Now this is something for use after your free tier ends. So that you know that if I have to use these services, how much would I be charged and this thing will tell you in total. Now if you can take a look at here you have these services say for example I want to add an EC2 service. An instance gets added here. I can put in the description. Now it is Linux T1.micro instance and this is what my monthly cost is. I can go ahead and I can change the number of instances here to suit my need and accordingly everything would get verified as in okay um this is the cost and all those things. So if I enter these values my AWS calculates all the values accordingly for my storage for my compute and there the other details which you can go ahead and fill in here. And once you've done that, you can actually come here and you can check your estimate monthly bill because once you save those details there or once you calculate those details, here would be your monthly expense because you'll be dealing with more than one instances. So your different costs are added together and a total is given to you here and you can actually go ahead and save it and share it with others because yes, you might be required to exchange these details with some of your colleagues or whatever it is. And to do that you have an option here as well which is provided by AWS. There was a query on stack overflow once as in can I do that and AWS quickly responded by going ahead and solving this issue and giving them with this save and share button. So yeah this is your calculator your monthly AWS calculator which lets you take care of your usage and gives you the bill accordingly. So if you're worried about as in how much you're going to spend by using AWS or its services, you can always come here and calculate that as well. Now that being said, let's quickly move to the demo part and see what all we can do with the AWS. Now I have my account here and I've logged in actually. So these are the services that are there at my disposal rather. So I'm just going to go ahead and open one of these. Say for example, I open my EC2 service. My internet is little slow today. So, yep, as you can see, I have one running instance. I have one key pair. I have three security groups. As we move further, we would be dealing with these and we would be implementing or creating new instances and all those things. So, firstly, what I want to do is I want to go ahead and create a key pair. Now, why do I need to do that? The first thing you need to understand is when you create a key pair, uh what you're doing is you're actually going ahead and you're creating your SSH key. Now when I say SSH key that is something but a secure shell key. Now this key is very useful when you talk about certain OSS because that helps you establish your connection. When you talk about Windows you do not need to do that. So but still you would be needing an SSH key. Now you might wonder why. The reason you'd be needing it is because given on the longer run even if you're using Windows you'd be required to put in an admin login and for that you'd be requiring this key anyways. If you are on using this application on your Linux OS in that case it is a must that you generate the key first. One more thing you need to understand is once you generate this key you need to take care that you do not lose it because once it's gone it's gone forever. So that is one precaution you need to take. So let's first start by creating a key pair here and as we move further you'd understand why did I create one. So I say create my second key because I believe I've created a key in this account prior to this second key. I say create and there you go. I have a key. Now my second key is something which I basically have it here. I'll just cut it from here and I'll paste it in one of my folders basically. So let's say I'm here and I say I need a new folder. I come here I say AWS demo and I put my key in here. I would be needing this. That is why I'm doing it. Now you can see that the extension here is PM. You might get other extensions depending upon the system which you're using and the oss that it's running or using. So depending on that this extension might vary. It's preferable that it is PEM. So yep we have this key now and let's see what we can do with it. I'm going to go ahead and select this key and select this for now. And I have all the information as far as this key is concerned. Now as I've already mentioned that security is very important when you talk about your cloud services. So it is very important that you define a proper security group to take care of all these things. So before we create an instance let's quickly go ahead and create a security group first. I come here. I've actually gone ahead and created a security group. So I would want to go ahead and create one more. So I would say create. Now when I do that I need to give a name to it. say this security for today's demo. I say security demo description for reference sake is what I would say. There you go. And uh we'll be going ahead and adding in rules here as where do I want certain rules because you can go ahead and define certain rules. How do you want to give access to your system and all those things? So I say as far as my accesses are concerned I'd be wanting an SSH rule. See the port range is given to you because uh you can communicate with the system through these ports basically and uh then I can go ahead and add more. I can say HTTP. There you go. I say I would be needing HTTP S as well. And since I'm using Windows, I would go for RDP. Now these are the different port names that are there. Now as far as these groups are concerned, so you can see that this has 000000 security because you would be wanting these ports to be available to others as well because why you're dealing with data exchange and all those things. So these are the ports that need to be active. Now you have your SS and your RDP. Yes, for now they are secured here. I can actually go ahead and change it here for the simplicity sake. If I have it something like this or maybe like this, this is how it would look like. And for the sake of being easy to use, I'd be having it like this. But as far as you are concerned, you need to consider better practices for this. You have different sources here. Why? Because you have an option to customize it. You can go ahead and customize those because there are certain services which you would be wanting to use differently and it is very important that your system is secured because uh since certain services would be accessing your data, it is important that access is denied to them in certain cases where it's not required and that is why you need to consider your security practices. Now as far as this demo goes, this is a basic thing which we are doing and we can ignore our security policies here. This is just for the demo second. I would be creating a simple uh security group. So this sources bear with it for now. Now I say create and there you go. My security group is created. It is security demo here. That is the name. Now let us move further and go ahead and create one of the instances that we can do. So I say to I go to services. I say EC2 and I say launch an instance or create an instance. Now there are quite a few instances here. have Linux and all those things. I would be going for Microsoft Windows. Let me just go ahead and pick one. We can actually go ahead and pick any. The only thing we need to consider is whether it's eligible for you. Now, when I say eligible, I mean eligible for your free tier basically. So, let us go ahead and pick one of these. I would say base 2012 server. Let us see whether it's doable for us. Yep. Now this is selected by default because it's free tier eligible and we can we're actually going to go ahead and use it. Now when you are creating an instance you need to understand one thing. These are the details that are there about the instance and these are some of the points you need to consider. When you say review and launch you can just click on it. You would directly be taken to the last step and all the by default admits are given to you. But now that we are doing it for the first time here I would want to do it step by step. There's nothing we are doing. We are just selecting the by default thing but I just want you to see what all it has to offer to you. Say for example when you pick a general purpose T2 instance number of CPUs one your memory 1 GB basically and uh these are the other details as the network performances low to moderate and all those things in next the details which I can enter in as in the number of instances purchasing options network subnet and all these things is there an IM rule and all those things. So yeah, for now I'm not going to make any changes again here and I'm just going to say next. As you can see the size I have 30 GBs of total available with me and these are the details about it. I ops and all those things. So you can just go ahead and say next. Now you have an option here whether you want to go ahead and add a tag and all those things and you can do that or you can just go ahead and say next. Have your wizard here and there you go. I have my seven step where I can go ahead and launch my instance. You can see I have a notification here saying that improve it security. As I've mentioned that we are doing it for the demo sake and I've chosen few basic ones. So I do not have to worry about anything. My ports are open and those are accessible. So the thing is my AWS is warning me as in you should not have it that way. So when you do go ahead and implement it on larger scales, you need to take care that your security groups are well defined and properly defined. For now let's go ahead and say launch. Now it would ask you to pick a key pair. As I've mentioned that key pair is important whether you're using it on Windows or not. But you need to go ahead and define a key pair. So I would go ahead and select an existing one because we created one. Proceed with a key pair. Okay. I say I acknowledge and I say launch. And it says that your instance is now launching. So what I'm going to do is I'm going to go ahead and view the launch log. And it gives me details as in what are inbound rules and all those things are mentioned here. How do I connect to my instances and all those things there's an information here. I can just go ahead and say view instances and there you go. I have both of my instances here and the details are given to me as in what are the details. Now I've gone ahead and I've stuck with this availability zone as far as I'm concerned which is Mumbai for my case. You can go ahead and pick an availability zone for your sake but make sure you stay consistent with it because that would be more convenient for you. That is for your different instances. Status checks. As far as this goes, everything is okay here. This was the instance which I launched yesterday. This is the one which I've launched today which is still initializing. So there you go. You have one here. Yeah. So this was about going ahead and creating an instance as far as AWS is concerned. Now what we can do is we can go ahead and try and do other things as far as your AWS is concerned. Now the other points which we need to discuss are can we connect this instance to a server and the answer to this question is yes we can do that. Meanwhile what I want is I want my instance to refresh first and everything needs to be in place before we do that. Yeah. So there you go. Now as you can see the status checks as far as the checks are concerned it is complete and we can go ahead and we can connect to a server now. So I was talking about the different service servers that uh you can go ahead and connect to. Now if you're using a Linux machine you need to understand one thing that you have to go ahead into your terminal and then you have to connect to your server. But when you talk about Windows the process is a little different. Let us see how we can do that using Windows. Say for example I select this instance here the second one. I say connect. So what I'll have to do is I'll have to go ahead and download a remote desktop file for that. And how do I do that? I do this. I say connect. It would be asking me for my admin password here. It would give me an error because I need the password here. And I guess uh I missed out on the password. Just bear with me. Let me just generate the password and I'll get back to you on this. Okay. So, how do I do that? What I'm going to do is I'm going to get into my previous instance this one. And I'm just going to connect or try to connect it because I have one here already. So, as you can see, I have this option here which says get me a password. As far as my administrator or username is concerned, it is administrator. And when I say get password, I'll be clicking here and it would be asking me to choose a file. Say for example I go ahead and I choose one of the files. Now I had downloaded the password last time or the key rather. Now that is why you need the key. Uh when you store it at some place you'd be asked for this key and you have to enter it here. And when you say decrypt password there you go. You'll be getting your password here which is this. Now I would be copying this password for my reference sake. Ctrl C. Just to give you a demo again I'll download it. I'll close it and I would say connect. It would ask for the admin password and I say take this. Do you want to connect despite these certification errors? Yes. And there you go. I've connected to the server here. And this is the file which I created the last time. There you have it. So this is how you go ahead and actually create your instance and connect to the server. You can go ahead and create another files here. You can say new. You can have your options. It's just like your nice operating system where you can do so many things. Yes, it's more of a clean slate and you are fully it's fully available to you to go ahead and edit it the way you want to. So this is what we did right now. We've actually gone ahead and we've created an SSH key. The reason we did was because we wanted to login here. Second thing we went ahead and we created a security group. Yes, it wasn't great but you can actually set security rules as per your needs. Then you can go ahead and launch a instance and then you can connect to a server you want to. Now this is what I have here. I can actually go ahead and do other things as well. What are the other things that I can do? Well, I can go ahead and I can set alarm for my systems. And how do I do that? Now I have something called as my cloud watch here under my management tools. Now when I come here, I can go ahead and set alarms as well. What kind of alarms? Say for example I want to monitor my system and I want to make sure that the usage as far as my system is concerned it does not go above maybe say 70%. And if it does go above 70% and that happens for five continuous minutes I want my system to throw in an alarm for me. So can I do that? Yes I can actually go ahead and do that. I can create an alarm and I can do that accordingly. I click here on alarm. I say my EC2 metrics basically or I just type EC2 here. All the services are here. And uh since we are creating an alarm for utilization. Let's select that. You get all the details here as in how much is the usage and all those things. You can come here and define the alarm name say CPU usage greater than 70%. See, and you say throw an alarm when usage exceeds 70%. There you go. 70. And I move down and I say notify me. How do I do that? Send notification to new list. Suppose I enter in some email ID. Now take this for example. I suppose I go ahead and use this account here and I say create an alarm. There has to be a name as well. Say VPT for example. And congratulations, your alarm has been created. It says insufficient data because there's pending information here. You need to understand one thing. When you do create an alarm, the email id you enter in AWS would go ahead and it would give in a message to the email id or in the email id saying that this is something that is trying to happen here. Do you want to be notified when the usage goes this far? And if the user says yes or he or she confirms that that can be done in that case AWS would configure this status saying that yes it is no longer pending and the status would be displayed here and this would turn to green. So this is how you actually go ahead and create your own alarm as far as AWS is concerned. Let me ask you a quick question. Have you ever thought about how companies like Netflix, Airbnb or Spotify manage their data, run their application and scale so efficiently? The secret lies in the power of the cloud. And for many top companies, AWS is a backbone of their success. With 63% of IT professionals finding it tough to recruit cloud talent, AWS certifications are your gateway to a high demand career. Salaries for AWS roles in India are around 10 lak rupees and in US they reach up to $120,000. Cloud jobs are set to grow by 28% in the next 5 years. According to Gartner, by 2025, 51% of IT spending will shift to the public cloud. So, if you're looking to futureproof your career, AWS certification could be the ultimate step forward. With that said, hello everyone. Let's dive into AWS certifications and explore how they can help you boost your career in the cloud computing world. In this video, I'm giving you deep knowledge on 12 AWS certifications across four different categories, covering the essentials like exam format, question count, and the idle candidates for each certification. We'll also highlight newly added certifications, including the AI practitioner for foundational AI skills and machine learning specialtity. Stick around till the end to discover which certification best aligns with your experience and goals and the key skills you'll need to master to succeed in each exam. So, let's understand what exactly is AWS certification. Now AWS certification is a program designed to validate your skills and expertise in using Amazon Web Services or AWS. The leading cloud computing platform powering businesses and applications worldwide. AWS offers a wide range of cloud services from storage and computing power to machine learning and artificial intelligence. And AWS certification shows that you have the knowledge to leverage these tools effectively. Now we'll understand why is AWS certification important. So, why should you care about AWS certification? Well, it's industry recognized and highly valued by employers. Getting certified proves to potential employers that you have the skills needed to design, implement, and manage cloud-based solutions using AWS. And trust me, that can set you apart from other candidates. Whether you're looking to switch careers or advance your current role, AWS certification can open doors to new job opportunities, career advancements, and even higher salaries. Next, let's explore the various AWS certification levels and what they entail. AWS offers a total of 12 certifications across four levels: foundational, associate, professional, and specialtity. Each level cers to different expertise from beginner to advanced cloud professionals. Here's a quick breakdown of each category. First, we have the foundational level. This is a knowledgebased certification for those who want a foundational understanding of AWS cloud. The best part, no prior experience is needed for this level. There are two certifications here, the AWS certified cloud practitioner and the AWS certified AI practitioner. These are perfect for beginners looking to get started with AWS. Next is the associate level. These are role-based certifications that showcase your knowledge and skills on AWS. Helping you build credibility as an AWS cloud professional. While no AWS experience is needed, some prior cloud or strong on-remises IT experience is recommended. This level includes five certifications. AWS certified CISOPS administrator associate, AWS certified developer associate, AWS certified solutions architect associate, AWS certified data engineer associate and AWS certified machine learning engineer associate. Moving on to the professional level, these certifications validate advanced skills needed to design secure, optimized and modern applications on AWS as well as to automate processes. For this level, AWS recommends at least 2 years of prior cloud experience. Here we have AWS certified solutions architect professional and AWS certified DevOps engineer professional. These exams are for advanced users who can handle complex AWS environments. Finally, there's a specialtity level. This level lets you dive deeper and become a trusted adviser in specific strategic levels. For these certifications, check the exam guides on AWS sites for the recommended experience. Specialtity certifications include AWS certified advanced networking specialty, AWS certified machine learning specialtity and AWS certified security specialtity. Each of these focuses on a particular field within AWS, giving you an edge in specialized roles. Whether you're just starting or looking to specialize, there is an AWS certification that's right for you. So first let's see the foundational level certification. Let's dive deep into the details of the AWS certified cloud practitioner certification. Starting with the category. This certification falls under the foundational level. It's aimed at individual who want to get a higher level understanding of AWS cloud. Even if they are new to IT or cloud computing. Then we have the exam duration. You'll have 90 minutes to complete the exam. Exam format is that the exam consists of 65 questions. You'll see a mix of multiplechoice and multiple response questions. The cost of the exam is 100 USD. Remember, pricing may vary slightly with foreign exchange rates. So, check AWS exam pricing for up-to-date details. Then, where to take the test? You can take the exam at the Pearson VUE testing center or through a online proctor exam. The certification is accessible in multiple languages including English, Japanese, Korean, etc. Now we'll cover what the AWS certified cloud practitioner exam tests on you. You will need to know these points as well. First explain the value of the AWS cloud and how it benefits organizations. Understand the AWS share responsibility model to know what responsibilities lie with AWS and what remains with the customer. Understand security best practices for keeping data and also application secure. Understand AWS cloud costs and billing practices to effectively manage and forecast cloud expenses. Describe core AWS services like compute, network, database, and storage. Lastly, identify AWS services for common use cases to solve different business problems. To prepare for the AWS certified cloud practitioner exam, here are the key concepts you should have the basic understanding of. First AWS cloud concepts for a broad understanding of the cloud. Security and compliance in AWS including best practices to safeguard data. Core AWS services that are most commonly used. And last is economics of AWS cloud to understand costs and also value. Now let's see the job tasks that are out of scope. For this exam, you are not expected to perform technical tasks like coding, designing cloud architectures, troubleshooting, implementing or load and perform testing. And that's the overview of AWS certified cloud practitioner certification. It's an ideal starting point for anyone looking to build foundational cloud skills and understand AWS at a higher level. Now, let's see the AWS certified AI practitioner. Let's take a structured look at AWS certified AI practitioner certification, especially if you're aiming to validate your skills in artificial intelligence and machine learning on AWS. The category is the certification fails under the foundational level. It's meant for individuals who work with AI and ML technologies on AWS even if they're not directly building solutions. The exam duration is 90 minutes. The exam format is you'll encounter 65 questions covering multiple choice and multiple response types. The cost for the certification is 100 USD. As always, check AWS official pricing page for any variations based on exchange rates. And then intent candidates. The certification is perfect for those who may not necessarily build a IML solutions but are familiar with these technologies on AWS. Testing options are you have flexibility here. You can take the exam at the Pearson VUE testing center or through an online proctor exam. Next, language is offered. The exam is available in English, Japanese, Korean and so on. The certification validates your understanding of in demand concepts in artificial intelligence, machine learning, and generative AI. This can sharpen your competitive edge and position as well for your career growth and better earning opportunities. Now, let's get into what this exam covers. Candidates are expected to demonstrate the ability to understand AI, ML, and generative AI concepts, methods, and strategies, particularly how they apply on AWS. Ask relevant questions within their organization to determine the best uses of a IML technologies. Determine the correct type of a IML technologies for specific use cases. Lastly, use a IML and generative AI technologies responsibly to ensure ethical and effective deployment. Next, let's see the recommended AWS knowledge. Although you do not need extensive AWS experience, familiarity with a few key areas can be helpful. Those are core AWS services like Amazon EC2, S3, AWS Lambda, and SageMaker. An understanding of AWS's shared responsibility model, especially around security and compliance, AWS identity and access management for resource access control. Lastly, knowledge of AWS's global infrastructure and service pricing models. Now, let's move on to job tasks that are out of the scope. For this exam, you won't be expected to perform technical tasks such as developing a IML model, conducting data engineering, hyperparameter tuning, and implementing security protocols for AI systems. The certification focuses on more practical a IML knowledge rather than hands-on development. Now, let's look at the exam content. The exam includes a mix of question types to assess your knowledge such as multiplechoice and multiple response questions where you'll pick one or more correct answers. Ordering questions where you'll arrange responses in the correct sequence. Matching questions where you'll match items based on prompts. Lastly, case studies where you'll analyze a scenario with multiple questions to assess your applied knowledge. And that's a structured look at the AWS certified AI practitioner certification. Perfect for professionals seeking to deepen their understanding of AI and ML concepts on AWS and to start their AI journey on a solid foundation. Now, let's dive into the AWS certified solutions architect associate certification. This is one of the most popular AWS certifications and an idle choice if you're looking to deepen your cloud architecture skills. The category of the certification is at associate level, perfect for those with foundational AWS knowledge or IT experience. Whether in the cloud or on premises, the exam duration is you will have 130 minutes to complete the exam. The exam format includes 65 questions, mostly multiplechoice or multiple response. The cost is 150 USD. Be sure to check AWS's official pricing page for any regional cost variations. The testing options are you have the option to take this exam at the Pearson VUE testing center or through an online proctored exam. The languages that they offer is this exam is available in English, French, German, Italian and so on. This certification is designed for those who want to architect cost optimized high-erforming cloud solutions on AWS. Let's cover the core skills the exam assess. Candidates should be able to design solutions with AWS services to meet current and projected business needs. Develop architectures that are secure, resilient, higherforming, and cost optimized. Lastly, review existing solutions and identify areas for improvement. And next, target candidate description. The ideal candidate should have at least one year of hands-on experience designing cloud solutions using AWS services. Now, understand the exam content. There are two main question types on the exam. Multiple choice where you'll select the one correct answer. Multiple responses where two or more answers may be correct out of five or more options. One more important thing is unanswered questions are scored as incorrect but there are no penalty for guessing. Remember the exam includes 50 scored questions and 15 unscored questions. AWS gathers data from these unscored questions to evaluate them for future use and they won't affect your overall score. Next about the exam results. The exam is scored on the scale from 100 to,000 with the minimum passing score of 720. This compensatory scoring model means you do not need to pass each section individually, only the overall exam. Your results will include a classification of your performance in each section, giving you insight into your strengths and areas to improve. Some sections carry more weight, meaning they have more questions and can impact your score more heavily. Moving ahead, let's explore AWS Certified Developer Associate Certification. This is a key certification if you are looking to enhance your skills in AWS cloud development. The category is the certification is at associate level ideal for developers who are ready to showcase their cloud development skills and understand AWS environments. The exam duration is 130 minutes long. The exam format is it consists of 65 questions including multiplechoice and multiple response formats. The cost of this exam is 150 USD. Check AWS's pricing page for additional regional cost details. The testing options are you can take this exam at a Pearson VUE testing center or through an online proctor option. The languages offered are this exam is available in English, Japanese, Korean and so on. The AWS Certified Developer Associate Certification validates your skills in developing, optimizing, packaging, and deploying AWS applications. It's great for anyone starting out in AWS or working in IT or cloud development roles. This exam is designed to assess the skills like we'll break down what skills the AWS certified developer associate exam is designed to assess including developing and optimizing applications on AWS, deploying applications using CI/CD workflows, securing applications code and managing data protection, identifying and resolving application issues. The target candidate description is ideally candidates that have oneplus years of hands-on experience developing application using AWS services. Now let's see the recommended AWS knowledge. You should know how to develop and secure applications using AWS service APIs, the AWS CLI and the SDKs. Use a CI/CD pipeline to deploy applications on AWS as well. Now let's see out of scope tasks. This exam doesn't cover some tasks like designing architectures. Let's understand exam content. The questions are a mix of multiplechoice and multiple response types where you need to choose one or more correct answers. There are 50 scored questions that affect your final score and 15 unscored questions to evaluate your future use. Moving forward, let's dive into the AWS certified CISO ops administrator associate certification. This certification is perfect for those in a cloud operations role and looking to prove their skills in monitoring and maintaining AWS workloads. The category is the certification is at associate level ideal for system administrators or those focused on AWS cloud operations. The exam duration is 130 minutes long. The exam format includes 65 questions with multiplechoice and multiple response types. The cost for the exam is 150 USD. For additional pricing details, check the AWS website. The testing options are you can take the exam at the Pearson VUE testing center or online through a proctor exam. The languages that they offer is the exam is available in English, Japanese, Korean, and simplified Chinese. The AWS certified SIS ops administrator associate certification validates your expertise in monitoring AWS workloads, implementing security controls, and applying networking concepts. It's idle if you are in an IT role involving AWS cloud administration. Now, we'll walk through the core areas this exam covers, including supporting and maintaining AWS workloads based on AWS well architectured framework. Operating workloads using the AWS management console and CLI. Implementing security controls for compliance. Monitoring, logging, and troubleshooting AWS systems. Applying networking concepts like DNS and TCP IP. Lastly, performing business continuity and disaster recovery procedures. The target candidate description is ideally candidates have one year of hands-on experience managing AWS workloads with skills in networking security and troubleshooting. The recommended AWS knowledge and experience are candidates should have at least one year of experience with AWS technology, proficiency with the AWS management console and CLI and an understanding of the AWS well architectured framework. Now about the exam content, the questions are a mix of multiplechoice and multiple response with 50 scored questions that impact your score and 15 unscored questions that AWS uses for future testing. Now the another certification so-called AWS certified data engineer associate exam. If you are looking to prove your skills in managing data on AWS, the certification is for you. The exam is an associate level certification. So it's perfect for those with some experience in data engineering but not quite for experts. You have 130 minutes to complete the exam which is about 2 hours and 10 minutes. There are 65 questions in total. Some will be multiple choice and some will be multiple response. The cost is 150 USD. Now let's see where you can take it. You can take the exam either at a Pearson VUE test center or online with a proctor watching you from home. The exam is available in English, Japanese, Korean, and simplified Chinese. Basically, the certification is all about working with data on AWS. The exam checks your skills in tasks like ingesting and transforming data, getting data ready for use, creating data pipelines, that is orchestrating how data moves and changes, designing data models, making sure data is organized in the right way. Lastly, maintaining data quality, keeping your data clean, secure, and properly governed. The exam also tests your ability to monitor and optimize data pipelines, ensuring things run smoothly and cost effectively. Who should take the exam? The exam is meant for people with about 2 to three years of experience in data engineering and at least 1 to two years of hands-on AWS experience. What you should already know, you should know how to set up and maintain ETL pipeline that is extract, transform, load for data. Use basic programming concepts to build these pipelines. Understand how to use git for version control and data links for storing data. Lastly, have a general understanding of networking, storage, and computing. In AWS, you should know how to use AWS selden manage data pipelines. This includes things like encryption, data protection, and logging. You should also be able to write SQL queries on AWS services to analyze data. Moving ahead, understand about the certification exam. This exam will have two types of questions. multiple choice in which one correct answer is given. Multiple responses where you'll need to pick more than one correct answer. Next we have is AWS certified machine learning engineer associate. All right, let's break down what you need to know for AWS certified machine learning engineer associate exam. The duration and questions are you'll have 130 minutes to complete 65 questions. The cost of the exam fee is 150 USD. Where to take the exam? You can choose to take the exam either at a Pearson VOE test center or online with the proctor. The exam is offered in English, Japanese, Korean, and simplified Chinese. The certification is aimed at individuals with at least one year of experience using Amazon Sage Maker and other machine learning tools on AWS. If you're a back-end software developer, DevOps engineer, data engineer, MLOps engineer, or data scientist, this is for you. Now the target candidate should have a year of experience using Sage Maker and also be familiar with related AWS services. Here's what you should already know before taking the exam. A basic understanding of common ML algorithms and when to use them. Knowledge of data engineering like how to ingest and transform data for ML pipelines. Experience with CI/CD pipelines and infrastructure as a code. Lastly, familiarity with software engineering best practices for creating clean, reusable code. Now, on the AWS side, make sure you also know how to use SageMaker for building and deploying models. Work with AWS data services for preparing data for ML models. Deploy applications and infrastructure on AWS. Use monitoring tools for logging and troubleshooting ML systems. Set up automated CI/CD pipelines using AWS services. Lastly, understand AWS security best practices for identity management, encryption, and data protection. Now, let's dive into the AWS certified solutions architect professional exam. Here's what you need to know. This is for professionals with at least 2 years of hands-on experience designing and deploying cloud architecture on AWS. Before you dive into the exam, you should be comfortable with the tools like AWS CLI, AWS APIs, AWS Cloud Formation, and the AWS management console. Plus, knowing a scripting language and having experience with both Windows and Linux environments is a plus. You should also have the skills to provide best practice guidance on architecture across multiple applications and enterprise projects. Map business goals to architectural needs. Make architectural recommendations for implementing and deploying applications on AWS. Design hybrid architectures using AWS technologies like VPN and AWS direct connection. Lastly, set up continuous integration and deployment processes on AWS. We look at the format, question types, and also everything you need to know. You'll have 180 minutes to answer 75 questions which will be in either multiple choice or multiple response format. The exam costs 300 USD. You can take the exam at a Pearson VUE test center or choose it on online proctored exam. To earn the certification, you need to pass SAP C02 exam. And don't worry, there is an exam guide to help you prep. Now, let's dive into the AWS certified security specialtity exam. Who should take this exam? This exam is for professionals working on security roles. If you're securing AWS products or services, the certification is for you. I know you will be having the doubt of experience level, right? The idle candidate should have 3 to 5 years of experience in designing security solutions with at least 2 years of hands-on experience securing AWS workloads. Before you take this exam, you should have a knowledge of the AWS share responsibility model, security controls on AWS environments, logging and monitoring strategies, vulnerability management and security automation, integrating AWS security services with third party tools, disaster recovery controls like backup strategies. Lastly, cryptography key management and identity access management. Now let's talk about the AWS certified DevOps engineer professional exam and how it can level up your career in cloud engineering. Who should take this exam? This exam is designed for individuals at least having 2 years of experience working with AWS environments. It's for professionals who want to demonstrate their expertise in provisioning, operating, and managing distributed systems on AWS. Before you take the exam, you should be familiar with programming that is experience in at least one highlevel programming language. Infrastructure automation, building highly automated infrastructures. Next is operating systems, administering different operating systems, DevOps methodologies, understanding modern development and operation processes. Next comes continuous delivery systems. Implementing and managing continuous delivery systems on AWS. Security and governance. automating security controls, compliance, validation and governance processes. Last is the monitoring and logging defining and deploying monitoring metrics and also logging systems on AWS. Now let's understand about the exam. You'll have 180 minutes to answer 75 questions in multiplechoice and multiple response formats. The exam costs 300 USD. And about location, you can take the exam either at a Pearson VUE test center or online with a proctor. Next, here's the key knowledge you need before taking the exam. Two plus years of experience provisioning, operating, and managing AWS environments. Experience with software development life cycle and programming or scripting. Automating infrastructure and understanding modern development processes. Lastly, securing AWS infrastructure is also recommended knowledge. The exam consists of two types of questions. Multiple choice where one correct answer and three distractors. multiple responses, two or more correct answers from a list of five or more options. Now, let's dive into the AWS certified security specialtity exam and see how the certification can set you apart in cloud security. The exam category is a specialtity level certification. Perfect for those who want to showcase expertise in AWS security solutions. I know you'll have a doubt of how exam is like. You'll have 170 minutes to complete 65 questions in both multiplechoice and multiple response formats. The exam costs 300 USD. Where can you take this exam? You have two options for taking the exam. An in-person test at Pearson VUEE testing centers or an online proctored exam. This exam is offered in six languages like English, Japanese, Korean and so on. Now let's see what is the certification about. The AWS certified security specialtity validates your skills in creating and implementing secure AWS solutions. It tests your knowledge of data classification and AWS data protection mechanisms, data encryption methods and how to implement them on AWS. Lastly, secure internet protocols and AWS mechanisms for securing data transfers. Who should take this exam? If you're in a security role, this certification is a great way to validate your skills. The exam is designed for candidates who have a solid understanding of data classifications, encryption, and secure internet protocols. Two or more years of production deployment experience in AWS security services. Lastly, the ability to make the trade-off decisions regarding costs, security, and deployment complexity. What knowledge should you have? Candidates should have the following experience and understanding of AWS share responsibility model and its practical application. Security controls for AWS environments, logging and monitoring strategies, vulnerability management and security automation, how to integrate AWS security services with third party tools, cryptography, key management and identity access management. Lastly, thread detection and incident response strategies. The exam consists of two types of questions that is multiple choice where one correct answer with three distractors. Next, multiple response. Two or more correct answers from a list of five or more options. And remember, unanswered questions are scored as incorrect. So there is no penalty for guessing. Ready to become AWS certified? The certification is great way to validate your security expertise and gain confidence in your ability to secure AWS solutions. Now we are diving into the AWS certified machine learning specialtity certification designed for anyone serious about ML development in the AWS cloud. What does this credential do? It's designed to help organizations identify and grow talent for critical cloud initiatives. If you are into building, training, tuning, and deploying machine learning models on AWS, the certification can be a gamecher. Who is this exam for? The certification is perfect for developers and data scientists with over two years of hands-on experience in machine learning or deep learning on AWS. You should also be comfortable with the intuition behind ML algorithms, basic hyperparameter optimization, familiarity with ML and deep learning frameworks. Lastly, best practices in model training, deployment, and operations. How do you earn the certification? To earn the certification, you'll need to pass the EWS certified machine learning specialtity exam. The test includes 65 questions with a mix of multiplechoice and multiple response formats. What about the logistics? You'll have 180 minutes to finish the exam. It costs 300 USD and is available at both Pearson VUE testing centers and as an online proctored exam. The exam is offered in four languages, English, Japanese, Korean, and simplified Chinese. Now, let's see what knowledge will you be tested on. The exam validates a candidate's ability to select the right ML approach for a business problem. Choose the right AWS services to implement ML solutions. Lastly, design and implement scalable, cost-effective, secure ML solutions on AWS. Let's see the idle candidates. Those who have two plus years of experience in developing, architecting and managing ML workloads on AWS are the best fit. Additionally, target candidates should understand basic ML algorithm intuition, hyperparameter tuning, frameworks for ML and deep learning. Lastly, best practices for training, deployment, and operations. Next, let's see how are the questions structured. The exam has two types of questions. Multiple choice where one correct answer with three distractors and then multiple response two or more correct answers out of list of five or more. As same for every certification there is no penalty for guessing. So if you're unsure go ahead and make an educated guess. Moving forward let's explore the last certification that is AWS certified advanced networking specialtity certification. Idle for those ready to make their networking skills to next level with AWS. Now let's see what is the certification about. This credential is designed to validate expertise in designing and managing network architecture across AWS services helping companies identify professionals with the right skills for complex cloud networking tasks. We will also see who should consider taking this exam. The certification is aimed at individuals with 5 years of hands-on experience in networking, specifically in architecting and implementing network solutions. Recommended experience includes in-depth knowledge of AWS technologies and security best practices. Similarity with advanced networking architecture like IPVPN, MLS and WPLS. experience with automation tools for designing, implementing and optimizing network architectures including routing and multi-reion setups. Lastly, knowledge of CIR, subnetting, AWS, WAF, IDS, IPS, DDoS protection, and EDOS mitigation. Now, let's see how do you earn the certification. To achieve this, you'll need to pass the AWS certified advanced networking specialty exam. It consists of 65 questions in both multiplechoice and multiple response formats. What's the exam logistics? You'll have 170 minutes to complete the exam which cost 300 USD. You can take it at a Pearson VUE testing center or through online proctoring. The exam is available in English, Japanese, Korean, and simplified Chinese. Let's see the skills that will be assessed. The certification will validate your ability to design and implement hybrid and cloud-based networking solutions using AWS. Operate and maintain network architectures for AWS and hybrid environments. Use AWS tools for deploying and automating networking tasks. Lastly, secure AWS networks using native AWS networking tools and services. Now, let's see what kind of candidate is the best fit for the certification. Ideally, candidates should have at least 5 years of networking experience and two plus years in cloud and hybrid networking. Key knowledge areas include AWS networking details and how they integrate with other AWS services. Security best practices for AWS. Lastly, understand of AWS compute and storage options. How are the questions structured? You'll encounter multiple choice questions with one correct answer and three distractors. multiple response questions with two or more correct answers among five or more options. So if you're serious about building secure, reliable network architectures on AWS, the AWS certified advanced networking specialtity certification can be an invaluable credential for your career. So that wraps up our overview of all the AWS certifications. So if you got your certification, you'll have access to great career opportunities. Now let's go to the credit opportunities. You could work as a cloud architect, solution architect, devops engineer, data engineer, or security specialist. The pay will depend on your experience and where you are based. But these roles offer excellent career growth and good salaries. Let me tell you some exam preparation tips. Once certified, you'll have an amazing career opportunities. But before you go, here are some quick exam preparation tips. First, use AWS free training. Hands-on labs and practice exams are the must. Apply AWS tools. Practice using AWS in real world scenarios. Next, take practice exams. Familiarize yourself with the exam format. Then, focus on core concepts. Pay attention to key topics like security and costs. Lastly, AWS forums. Get tips from the community. With these tips, you'll be ready to pass the exam and boost your career. Why do we need AWS? So the first thing we see is that it helps scale your operations. Now basically scalability is extremely important when it comes to business agility because the more you scale your operations, the more profits you have and the more efficient you get, right? So there are services such as elastic load balancer which helps you scale or certain services computational services are there which helps you scale your resources. Then we come to reliability. Now the fact that AWS basically is extremely reliable because it is very secure and it is global in nature. So the infrastructure of AWS is global and can be accessed from anywhere. Right? So the fact that it is so global and so widespread makes it extremely reliable because it is used all over the world. Next we come to cost effective. Now cost effective is extremely important when it comes to AWS because more than 80% of companies have been using AWS right now and the fact that they have moved to AWS is because uh of the fact that it is extremely cost effective and helps save them a lot of money thereby scaling their operations and then meeting their business goals as well or financial goals that they have. So all of these things are interconnected right now. Next we talk about business agility. Now business agility is all about being efficient. Now the more efficient you get the more agile your business will be. Now efficiency can be in terms of productivity, can be in terms of financial stability and it has to improve your company's overall revenue. Right? So the last one is high-speed deployment. Now every service that you have on AWS will basically have high-speed deployment. So it doesn't really take a long time to create a service from scratch and deploy it on AWS so that you can use it from anywhere around the world. Right? So next we come to the various AWS services that are there. Now these can be grouped into various ones such as compute. So that there are computational services that AWS provides users. Then we see that there are storage services as well. Now storage services are extremely in use and one of the most popular ones after compute. Then there is database services that are there. Now these can be NoSQL databases or relational databases as well. And then there is networking services that are there. Now networking services are extremely important mostly because of the web hosting and as well as tracking your website and stuff like that. if you need that as well. And finally, we have analytics. So, analytics is also extremely important to basically see how your resources on AWS are doing. Now, there are various other services, but these are like the five pillars of AWS, right? So, let's talk about these services. The first service is basically a compute service called Elastic Compute Cloud. So, the EC2 is basically a service that offers its users the compute platform they need. So it has an option of 4 475 various instances and choices of processor that the user can have as well as storage and networking as well with an option of which operating system you want to run it on as well. So it has extremely wide range of options that it provides its users and it's most in use and it's probably one of the most used uh services on AWS. So the next thing we see is AWS Lambda. So the AWS Lambda is basically a serverless eventdriven compute service that lets you run code for virtually any sort of application or backend service that you have, right? And you do not have to provision separate servers for that. So that is what lambda helps you do. It's basically something that is a compute service for any sort of backend application service that you have or manager service. So the next thing we see is storage. Now storage is basically extremely important. It comes right after compute. And the most popular storage service is the AWS S3 which is the simple storage device. Now the AWS S3 is basically an object storage service. So you could store data in it which can be anything starting from a picture to let's say a text document right. It offers its users very high scalability right and extremely high data availability and security. So it offers its users the option for making public access blocked or available. It offers its users the chance to create policies so that you can access or not access, delete or not delete certain things that you store in the S3. Right? Next, we talk about the elastic file system which is the AWS EFS. Right? Which is basically it helps you automatically grow or shrink as you add or remove files in it. Right? So that is why it's called the elastic file system. It can basically dynamically allocate certain data storage in it. You basically need to specify a certain limit and it can dynamically allocate the resources within itself. Right? So next we talk about the database services that are there. The basically there is Dynamo DB. So next we come to Amazon Dynamob. Now Dynamob is a NoSQL database. Now that is basically something that has no relational tables and attributes as such but it has data in it. Right? Now what Dynamo DB does is basically it is very serverless and it has got based on key value. Right now it is very high performance and it can get any application back to scale which is why it is extremely in use when it comes to database services in Amazon. Right. So the next thing we talk about is the Amazon Aurora. Now the Amazon Aurora is another database service but instead of NoSQL unlike Agile Mode DB it is based on MySQL and progress SQL right. So these are two basic compatible SQL servers that you have and after that you need basically a compatible relational database built for the cloud that combines the performance and the availability of traditional databases. Right? So it's extremely cost effective and open source as well. So this is very easy to use and change because you can always change anything that you do on an open-source service or a software. So then we talk about the networking services. Now when it comes to networking services we have Amazon virtual private cloud which is the VPC. Now this VPC gives you full control over your virtual networks or the environments that you have. So this includes the resource placement, security, all of this right. So after this we talk about the Amazon API gateway. Now Amazon API gateway is a fully managed service that makes so it is not managerless or serverless. So it makes it very easy for developers to create publish or maintain an API repeat or maintain an API at any scale as such. So it's extremely easy to use and it's one of the most popular networking AWS services that are there. So then finally we come to analytics. So we have the Amazon Athena. Now the Amazon Athena is a very interactive query service that AWS has and it's very easy to use and analyze data that you have in certain other services that are integrated into it such as the S3 and basically you use standard SQL give these commands and it is always pay only as you use right so you only have to pay for the queries that you run and you don't have to pay for anything else when you use Amazon Athena So then we look at AWS EMR. So EMR is a cloud big data platform which is used for running large scale distributed data processing jobs. Right? So interactive SQL queries are used basically along with ML applications and this is how you basically use EMR. Now you can use other frameworks such as Apache Spark, Hive, Presto etc. And it's basically used for big data analytics and you can use a bit of NLP a bit of ML in that and mostly it's used for data processing and you integrate a bit of SQL in that as well. So up next we come for the demo for AWS services. So basically what you do is you create an account on AWS and when you do that you can login with your password and your credentials as well and this is what you come to the AWS management console right. So what you can see here is you have a various options of various services that are there. Now these services can be different from analytics to application integration VR and compute and these are various other services. So let's check out some of the services right. So the first thing we check out is let's say Dynamo DB. So you type Dynamob here. So this is Dynamob. It's basically a service basic for databases. So you can create a table without actually using having to use any SQL as such. So you can just give the table name. I can give it as table one. Right? So the next you specify the partition key that you have to have. Partition key is basically the primary key. So the primary key is always something that is uniquely identified with. So in here instead of primary key it's just called partition key. So let's just keep the partition key which is basically different primary key here as number. So it's going to be a number type or we can keep it as yeah we can just keep it as number. So next is about sort key. Now sort key is something that allows you to sort all of the data that is there using the same primary key. So that is used as sorting which is an optional feature. So we can or cannot do it. So we'll just use default settings which is the fastest way to do it. And there can or cannot be tags. Now basically tags are optional values that you add that you can basically assign to certain data that you have in the table. Right? So what you can do right now is just create table and your table will be created. It will take certain amount of time do that because AWS takes a bit of time but it should be done in about 5 minutes. So as you can see here the table has actually been created with the name of the table being table one. Uh the status is active because it has just been created. And partition key is basically the primary key that is there that is going to have some sort of number in it which is going to be unique for every sort of data that we enter which is why it is the partition key. And you will basically have to see the read and write capacity mode. So we can just enter this table right here. Right. And check out what is there. So here is the general information that is there. So the partition key, the sort key if it was there, if we checked it. So there are no active alarms that we have set and it is active. So item summary. So there are no real items, right? So we have to add an item. So let's do that. Let's add items. So we can just go to explore table items. So this is a table that we have. So what we can do is we can just go to create item because there are no items here in the table. So this is going to be let's say 17 and that is the primary key that we have. Now let's say there's going to be a string attribute that you need. So let's say the number was the role number of a student. And now what you can do is you can just add another attribute here just like when you do with relational databases as let's say name and it's type string. So you can add let's say jig for example and you can add another value if you need. Now this can be different if you want. It can be binary. It can be string set anything. So this is basically another attribute that we can add. So this is the type which is list. Now the list can be different. Now we can have different types of things in a list. Now this list can be third language let's just say right so we can insert any sort of field here and this can be string right so you can just add string here all of these will have let's just say first will be Hindi this will be English And we can have another field of string let's say Pjabi. Yeah. So repeat you can have Hindi, English and you come to the third one and you basically have Punjabi let's say and you create these items right and you create the first item. So this is literally one item that is there in your table right now. So you can just check what is there in your table and you can see this is the only items that's there as number 17 which is the primary key which is basically the partition key. This third language which is basically a string and a list of different things such as Hindi, English and Punjabi and the name is J. Now what you can do here is you can create another item because that's just one item and you cannot really have a primary key if you don't have another item. Right? So let's just say this is 26 right and after that you'll have to add a new attribute. So this one is also let's say name and let's say name is same with is Jake and for example if we do something different if this is the same and it's nonredundant and then we basically go and do the same with this we go to list insert a few fields like Hindi English And let's say for this one we change it to body. So this is basically two different things. So this is added as a new different attribute because I hadn't put it under third language. Right? So if I had put it under third language, it would have come under this. So these two would have been together. But since the name is basically the same attribute for both items that are there. So this is basically under the same name and you have another attribute here which is new value. Right? So what you can do here is you have various things you can do here. Right? You can edit the entire thing. You can set it as let's say 19 and save those changes. Okay. And right after that if you basically recreate this item it is updated and set as 19. Right? So basically what you can do here is you can basically carry out any action. So we can just see about the updation. Now after updation we can basically see there are various actions we can do. We can just delete item and since that item has been selected 19 is now deleted and the only thing that is there is 26. So this is how Dynamo DB works. Up next we come to basically Amazon S3 right. So, Amazon Dynamob was a database service and S3 is a storage service that we're going to talk about. Now, Amazon S3 is all about creating buckets. Now, buckets are basically used to store information. They're used as storage, right? This is a storage service. So, what you can do here is you can go to create bucket. Now, what you can do is you can name your bucket. Let's say I name it one right after that. So you can basically choose the region you're from. So I'm here in India, I'll be choosing Mumbai. And if you don't have an existing bucket and if you don't have settings for your bucket, you can basically choose any existing bucket that you have. But since I do not really have an existing bucket, I cannot choose an existing bucket to have settings from. So we this is our first bucket they're making. Now the next thing we see is ACL. ACL is basically related to account ownership, right? Object ownership in the account. So you can choose to block public access in your bucket, right? So and versioning is basically anything to do with multiple versions or variants of your bucket. So basically it is used to recover, right? So when you lose a certain file or a bucket or certain data, if you have versioning enabled, what will what it will help you do is it'll help you get a certain copy of the same data that you had. And tags like one before is help you to associate to your bucket. See this is optional. You can or cannot. So you can choose to enable encryption which is basically used to encrypt and protect your data or you can choose to disable it. And it is delayable right now. So let's just create this bucket which is going to be called product one and we go create bucket. So basically you've created this bucket right now. Right. So if you go check out this bucket what you can see is this is the bucket that is there. Right? So you can upload any sort of object that you have. Okay let's say for example. So basically this is one of the data that you can have in your bucket. Now this can be used as destination and you can upload this and it has basically been uploaded successfully. Now what you can see here is this S3 bucket has this file in it. Right? So this file has this 6 KB download 3PNG file in it. Right? So this is how you can store data in S3. Right? Now if you basically go back to buckets, what you can do here is see that there is some sort of data in the bucket. Right? And you can see the kind of storage it has. that gives you an option of standard storage or other parts of stoages. So then we come to permissions. Now permissions is basically something that you use to to authenticate users in your system. Now users in your system will basically have to be authenticated before they access any content or data that you have in your bucket. So basically what you can do here is you can change public access. So public access the moment you have blocked nobody can access your data that is there in the bucket and you could basically edit this and to confirm this you just have to write confirm right so public access is on so there is no such bucket policy right So you can add certain bucket policy. So you can just go here and you can see the policy that is there in your system and this is the policy that is there which has allowed public access and what you can do is you this are this is basically the rules that you set. After that you can just go to management. Now what management does is basically so this can use show you different things that you can do with S3 such as life cycle status. Life cycle status is something that you use when you want to store a certain bucket or a certain amount of data in a bucket for a certain point of time and then migrate it to another bucket or migrate all the data in existing bucket to another bucket or delete the bucket or something like that but the data has to migrate. So what you can do is you create life cycle rule. So you can name all of this and you can basically choose a scope for the rule and you can type all of this basically the type of filter you want. So any type of filter that you want in your life cycle thing which is basically making it easier for the destination to be chosen and you can also have tags. Now basically you can add actions or rules that you can have and after that you can just create the rule that you have with create rule and your life cycle rule is created. So after that we see there's replication. So this is about data replication. So data replication is basically you want to basically add a certain set of rules to a more than one data in some bucket. Okay. So what you can do here is you can have another name for it. Let's say 098, right? And after that you can choose the source bucket. So this is my bucket that I've chosen. So this is the source bucket and the limit. Also you'll have to have the destination bucket but I don't have destination because I've created just the one bucket. All you have to do is create another bucket and you can just store that there. And what you can do after that is you create this. Now after this you could what you can see is encryption. Encryption is something which is extremely important when it comes to data redundancy because when you're coming to replicate data for basically storage purposes or recovery purposes. Encryption is extremely important because it it maintains the integrity of the data. Right? So all of this and then we talk about the access points. Now access points is basically the different points you can access your data or the S3 bucket in. So access point is different policies that you can have. So what you can see here is these are the different policies that you can have for access points that are there. Right? So let's just check it out. Now this is very optional when it comes to the security which is the public access right now right and we are creating access point which is let's say access point so this is the name of the bucket that you have for access point uh which is mine and this is the region that we have which is Mumbai here so this is virtual private cloud So you will have to mention the ID of the virtual private cloud right. So if you have created a VPC you will have to be creating that and then after that you can just save it once you have that HTML policy that you need to basically set the rules and then you can just create the access point. Right? So up next we come to AWS cloud trail. So this is something that is used for logging. Now logging is something that you do when you want to monitor your account activity. So what you do in cloud trail is you help create trails and let's see here you create a trail and this is the name of the trail which is management events let's say right and you just create the trail okay so this is basically one management event which is a trail now what you can do here is you can do various things which is it is logging data and this shows you where the location of the logs are being stored. This is basically SNS which is simple notification delivery service which is being disabled but you can always enable that. What you can do is just stop logging data or start logging data. I will just stop it for now and you can always choose to edit this. Right? So let's go here. What you can see is the details. The name of the trail is management events. Let's say what you do here is you go to S3, you create a new S3 bucket. Since I don't have it, I so I'll be creating one. This is the name. But you can just use an existing S3 bucket if you have it. So you can have encryption which is something which is important for maintaining the integrity of the data. And apart from that which we have log file, SNS or all of that here, right? So let's just see that. So what you can do here is that you can go to cloud trail. You can go here to the dashboard that is there right. So over here what you can see is this is the name of the trail that you've made which is management events which is off which is not logging data right now. So this is the event history tab which is basically a tab which shows you all of the things that has happened inside cloud trail and all of the things that the user has done and other certain things in services which are associated or integrated with AWS is also visible. So here you can see that stop I have stopped logging. So that has been here it's been logged the data has been logged right. So apart from that we can see start logging all of the things that you can see here let's say create trail right so all of this is there and you can see put bucket policy and you know d register scalable things so these are all username is root which is my user now this is s3 which is an integrated service with cloud trail so you could see what is going on inside S3 as well in cloud trail. Now this is extremely useful for users because it is something which helps them keep track of their services which they have running on AWS. Right? So this is an overview of some of the services that AWS provides us with. So in conclusion, what we can see is that more than 80% of organizations have moved to the AWS cloud and as of 2021, it accounts for over 13% of Amazon's yearly revenue. Right? So AWS makes sure your organization's operations run very smoothly and much more scalably and secure. So cloud is definitely the future and AWS is something which is proof of that, right? AWS is basically taking over the entire computer industry and it is basically here to stay for the long run. AWS management console is a web interface for managing AWS resources. It provides access to all the various services offered by AWS. It also provides information related to our account like billing. The AWS management console provides easy access to services and resources and does not require prior expertise in APIs and SDKs. Firstly, let us know how to set up an AWS account. Since I have already signed up for an AWS account, you can see that I only need to sign in. But if you're a firsttime user, you need to sign up for the AWS account first. To set up an AWS account, follow these step. First, navigate to the given URL. In step one, enter your email ID and password. In step two, enter your debit card detail. Now, AWS does not charge for services and resources used up to the free limit. We enter the debit card details as it wants to ensure that you're a legit user with a legit bank account. Next, enter your phone number to receive the verification code. Next, enter the verification code you have received. AWS provides four support plans. Basic, developer, business, and enterprise. Since we are just beginning, I have chosen the basic support plan. You can choose any support plan and complete the signup process. This is how we set up our AWS account. Now, you must be thinking, what if you exceed the free usage limit? In that case, you also have the option to set up alarms before free usage exceeds. You can keep a check on the charges of AWS services. The charges for AWS services are estimate and sent several times daily to Cloudatch. The alarm can be set for a userdefined threshold limit. When the charges exceed this limit, the alarm alerts the user. Before we set up alarms, we need to enable the billing alerts. To enable billing alerts, you must be signed in to the AWS management console. For consolidated accounts, the user can view the billing information for each of the linked accounts if he is logged in as the paying user. You cannot view those members accounts billing information which are part of the Amazon partner network as billing matrix for APN accounts are not published to cloudatch. It is important to note that once enabled, the billing alerts cannot be disabled. To enable billing alerts, follow the steps as shown. Navigate to the Cloudatch console. In the navigation pane, select alarms. Since I've already enabled alarms, but you need to check the check box for receive billing alert and click on save preferences. The billing alerts will be enabled. To create billing alarms, follow the steps as shown. Navigate to the Cloudatch console and change the region to North Virginia that is US East. In the navigation pane, select matrix, then all matrix, then select billing and total estimated charge. Check the check box next to US dollars. Go to the graph matrix tab and click on the create alarm icon. The create alarm page is displayed. Choose the threshold type and whenever estimated charges is as what you want. Then define the threshold limit. I have defined it as $200. Then click next and we reach the step two. Select the alarm state trigger and select an SNS topic. Enter the email ID where you want to receive your notification. Then click next. Enter the name and description for your alarm and click next. In the preview and create page, verify this information and conditions and click on create alarm. The alarm will be created. As you can see, to delete a billing alarm, follow the steps as shown. Open the cloudatch console and ensure that the region is US East that is North Virginia. In the navigation pane, choose all alarms and check the check box next to the alarm you want to delete. In the actions drop-down, click on delete and in the prompt box, click delete again. The alarm is deleted. Now, let us talk about the services offered by AWS and ways to access those. There are three ways to access the AWS services. The first one is through the search box. In the search box, type the service that you need. The next is through the recently visited section. The services accessed recently appear in the recently visited section on the homepage. You can access a service from there. The third is through the services option. Click on the services option on the screen and see all services. There are range of services offered which are classified into different categories. As you can see, you can access any service from here. Next on the navigation pane, we have the search box. As we have already seen in the search box, you can type for the service or resource that you need. Next on the navigation pane, we have the AWS cloud shell. It is a browser based shell that enables the user to manage the AWS resources. Some cloud shell features include direct access to command line, pre-installed development tools, and sharing of files. Now let us look at some advantages of cloud shell. They include that it works well with AWS management console functions. It is automatically updated. There is no cost for up to 1 GB of storage and environment can be customized and retained. AWS also provides us with some tutorials. For example, you can learn how to launch a virtual machine. As you can see, there are some tutorials of small durations that help you perform different tasks through the AWS management console. All these are available under the build a solution title on the homepage. Some common tutorials include launch a virtual machine, build a web app, build using virtual servers, register a domain, connect to an IoT service, and start migrating to AWS. Next, on the navigation pane, we have the bell icon. Any issues, schedule changes or other notifications appear when we click the bell icon. It has the following feature. Open issues, schedule changes, other notifications and event log. In the account option on the navigation pane, the information related to your account is available. My account displays the details of the user. If the user is connected to several other users, they are arranged in an organization and the organization's details are displayed. You can also view service quotas, billing dashboard and security credentials. Next, you have the option to choose your country and region. Certain services are global, which means they are available globally from anywhere, while there are a few other services that are excluded to a particular region only. AWS management console also provides you help and support for your problems and queries. Support center is available where we can resolve our doubt. We can seek expert help. There are forums where we can discuss our queries. There's documentation, training, and getting started resource center. You can also view details related to your account's billing information. You can view bills, orders and invoices, credit, purchase orders, cost and usage reports, cost categories, etc. So, how does one choose a service? Well, there are quite a few parameters which one needs to consider. As far as the best service providers in the market is concerned, they consider these parameters. Customer friendly. It is very important that a service provider is customer friendly because different businesses have different needs and if the customer needs are met then the customer would be happy and as far as the service provider is concerned that is what the aim is. If you talk about Amazon, it has the best customer service and Amazon proudly claims that if you've ever used one of their services, you would know that we are the best service providers in the market. Next, we have transparency. Now, it is very important that a service provider is transparent. Now, what do I mean by this? What happens is most of the times people are forced to pay money upfront and then they're given access to the services. This does not give them any time or have any kind of demo with the services that are provided by the service provider. This is where AWS is different. What it does is it offers you free tier. Now what this free tier does is it lets you use all of its services for free and that too for one year. So you have sufficient demo or access to the services which AWS has to offer to you and then you can take a call whether you want to go ahead and pay for these services or not. Pocket friendly. AWS is highly pocket friendly. Why am I saying this? Say for example, you have to go ahead and buy a server. Now AWS lets you have a server for 1 month at a meager price of $5 only. And this is highly affordable. So these are few of the important points which people need to consider when they go ahead and pick a service and when you talk about AWS, it meets all of these needs. So let us move further and try to understand the different pricing fundamentals which AWS has. Now AWS considers these three fundamentals that is compute, storage and data transfer. If you talk about compute, what AWS does is it charges you on hourly basis. That is you can use their compute and their processing services at a very less price and also you' pay only for those resources which you've used. And again when you talk about time constraint, if you're using those services only for 1 hour, you'd be paying only for 1 hour. Next we have storage. What AWS does is it charges you per GBTE. That is even if you use very less space, you'd be paying only for that space. And since it is almost as less as 1 GB, that is you have to pay only for 1 GB. What this does is you don't have to worry about scaling because if you're using more resources, you'd be paying accordingly. So yes, when you talk about storage, this is a very important point and AWS has it covered. Next, we have data transfer. Now when you talk about data transfer again AWS charges you per GBTE and it charges you only for the data that goes out. So yes this again is an important point and based on all these points what AWS has done is it has gone ahead and it has built various pricing models. So let us move further and take a look at those pricing models one by one. Now AWS has these three pricing models that is pay less as you get more, pay as you go and save when you reserve. Let's first talk about pay as you go. As I've already mentioned, AWS has a very flexible pricing model. Now, what do I mean by this? AWS charges you on basis. Plus, it charges you only for the compute capacity and the resources which you are using. So, if you need a particular resource for 1 hour and you need n number of or n amount of compute capacity, you'd be paying only for that thing. Say for example, your requirement is 40 GB for first month. But what happens is you end up only using 10 GB. Now in this case your 30 GB of space is wasted and this is when you pay upf frontont. But if you're paying on hourly basis and only for the resources which you're using, you're actually saving up all the cost which you would otherwise pay. Secondly, we have something called as pay less as you get more. Yes, more the services you use as far as AWS is concerned, it charges you fairly less. You have a chance of saving up to 70% of your total cost and that is a very nice feature to have. You also have something called as save when you reserve. Now if you know how much resources and the compute capacity that you're going to use in near future, what you can do is you can go ahead and reserve these services in advance. Now in that case AWS charges you fairly less compared to the other models. So let us go ahead and take a look at these one by one. Firstly, we have no upfront costs. Now, what this means is uh you can go ahead and reserve your resources and your services in advance, but you're not paying anything. But what happens here is you are paying an amount which is lesser than the previous two mentioned models that is pay as you go and pay less as you use more. But this thing is still costlier compared to the other subtypes of this model that is partial upfront cost and full upfront cost. Now when you talk about partial upfront cost, you're paying a partial lump sum amount which is less than the total amount and you're reserving all your instances and all those things. But this is comparatively affordable when you compare it with no upfront costs. It is however costlier than the last one that is full upfront payment or costs. In the last point that is full upfront costs. What you do is you decide okay these are the amount of resources which I'm going to use and this is the compute capacity which I need and accordingly you book all those resources and you make an upfront payment. Now since you're making an upfront payment this is the most affordable of all the pricing models that are there but for this you need to be assured that these are the minimum resources which I'm going to use and if required I will have to scale up but not scale down. So this is about different pricing models as far as AWS is concerned. So let us move further and try to understand the next point. Now how does one go ahead and calculate the savings which one makes? Well, AWS has provided you with an AWS calculator. Now what does this AWS calculator do? It lets you calculate your monthly expenses. That is the services which you've used and all those things. Hence you can keep a track of all the money which you're supposed to invest. Apart from that it also provides you with various templates which lets you appraise your complete solution. There's one more variant as far as the calculator is concerned. It is called as TCO that is total cost of ownership. Now it is little different than the normal AWS calculator. What it does is it basically lets you calculate or compare one services price with the other service. It also lets you compare the infrastructure solution which AWS has to offer to you. And this might vary from business to business. So when you talk about the total cost of ownership for which you might invest, this is the calculator which you should go for. Now when you talk about the AWS calculator or the TCO calculator, I would be giving you a small demo or once I walk you through the AWS website, I would be telling you as in how do these calculators work. I hope this point is clear to all of you. So let's move further and try to understand the next point. Now AWS also has to offer you a free tier which I mentioned in the past. So let us move ahead and try to understand what this is exactly. Now as I've mentioned AWS has various services to provide to you and those services will have the subtypes as well. So all these services are available to you for free for one year and this is the access which AWS provides to you. Say for example you have a service called as Amazon elastic cloud compute. This is one of the most popular services as far as AWS is concerned. And when you talk about its access, what AWS does is it lets you access 750 hours of this service on any of your oss. Whether it's your Linux, whether it's your Windows, you can have access to this thing. And when it comes to using this service, 750 hours is sufficient if you're trying to get started with AWS. Then you have other services like elastic load balancer, you have elastic block storage, you have Amazon web services. And based on the usage, they have different capacities which are made available to you for free. Now AWS won't charge you for any of these things. And when you need a demo, I feel these resources are more than enough. Again, once I switch into the website, I would be talking about the free tier as well. So let's do one thing. Let's actually go ahead and first take a look at these resources or these services one by one. That is let's try to understand what free tier is and what these calculators are with the help of the AWS website. So what I'm going to do is I'm just going to go ahead and switch into the AWS website. So yeah, what I've done is I've actually gone ahead and I've opened AWS free tier. Now this is what it looks like. And basically these are all the resources which it has to offer. But before we do that, what you need to understand is you need to create an account here. To do that, you'll have to go ahead and enter your debit card or credit card details. Now AWS won't charge you as long as you use all these services in the limits which AWS has mentioned and to be honest those are fairly large limits. So you won't be exceeding that if you are just using or having a demo of these services. So how does one do that? One goes ahead and gives in their credit card or their debit card details. AWS will charge you $1 that is 1 USD for some verification purpose and within 10 minutes that amount would be refunded back into your account again. So this is only for the verification purpose and after that if you overuse the resources then AWS would charge you. So what you have to do is you have to just go ahead and create an account here. Now these are the free tier services which AWS has to provide. It has something called as elastic cloud compute that is EC2 and as I've mentioned it has 750 hours of it. You have Amazon quicksite which is used for analytics basically and it is available in 1GB of your spice capacity. Now I won't get into the details of what spice capacity and all those things are. You have something called as Amazon RDS which is for storage and again it provides you with a capacity of 750 RS per month which is again very high. You have Amazon S3, you have Amazon Lambda. Now these are fairly popular services and as far as the space or the capacity which is mentioned here, it is more than enough or sufficient. AS also provides you with various tutorials that will help you get started here. So if this is your concern, I would suggest that you just go ahead and log into AWS's website. Have an account there and you're good to go. As far as once you sign in how it looks, I'll show you that as well. You can just go ahead and log in. Now I have an account already on AWS for some reason. My internet is very slow today. There you go. It takes eternity. Yes. So once you log in, this is how it looks like. You can go ahead and you can actually create your own instances and all those things. Say for example, you have something called as EC2. You can go ahead and you can specify all the details as in this will show you how many instances are running and all those things. For now, there's nothing that is running here. So there's zero instances that are running. So you can actually go ahead and create your instances and do all those things. You can launch a instances say for example and you get to select as in what OS and what all do you need to do for it. So yes but then this is not the discussion for today. So I'll just go ahead and skip this part and I will switch to something called as the calculator. As far as the free tier is concerned these are all the services that are available to you and you can actually go ahead and use those. Now next we have something called as our simple monthly calculator or AWS calculator. Now it gives you your monthly estimate as in for all the services which you've used. All you have to do is you have to go ahead and add the details as in what is the description, how many instances are you using, its usage and the type of the instance. Now the T1 and all those the micro instances and all those these are the details that have been covered in a session called as AWS tutorial by EDA. If you want to have details about those, you can actually go ahead and view that video as well. Now this is where you talk about the billing option whether it's on demand and all those things. You're free to go ahead and choose a plan for you. As you can see, it's visible here. And once you do that, once you've filled in all these details, your storage, your compute capacities, your elastic IPs and all those things, you finally need to come here and you just need to say that there's an option here which actually lets you submit all these values. And once you do that, you'll have the final result as in okay, this is your usage till time and this is the predicted usage and all those things. Then you have something called as your TCO. Now, this is more global or more general kind of an application. Now this is something that deals with your interim expenses and all those things. This is for the overall expenses as in the total cost of ownership. You can select the currency here as in you have an option of paying in different currencies. Since it's a global leader, you have options to pay in different currencies as well. Say for example, you're somewhere in India, you would be paying in rupees and you can select that option here as well. Apart from that, what is the environment which you need to compare it against? Because yes as I mentioned that you can compare different architectures. So you can go ahead and select that as well. You have various other features. Say for example you can go ahead and put in the details for the servers whether those are physical servers, virtual servers and all that your storage. Now there are storage types here. Say for example you have SAN, you have NAS, you have object. You just need to fill in these things and then you need to calculate your TCO as well. And you'll have the total cost of ownership too. So these are different calculators and this is how the free tier as far as AWS is concerned works. So you are actually free to go ahead and explore these things because it is available to you freely and you can just have access to this and get the knowhow as in how AWS works. I hope this is clear to all of you. So let's move further and continue with our discussion as far as the pricing video is concerned. Now that we've understood what the AWS free tier is, let us move further and consider this final point of discussion that is cost optimization. Now this is a very important point as I've already mentioned that money is very important when you talk about businesses. It is also very important that you are able to optimize all the money that you are investing in various projects. Now this is where AWS is very good because it helps you optimize your cost a lot. Yes, it has great pricing models but apart from that it also lets you use those wisely so you can optimize your cost. Let us take a look at these points one by one. Right size your services. Now as I've mentioned it is easier to upscale but it is not easy to downscale. So it is always wise to start with lesser resources and lesser compute capacity. So this is where right sizing becomes very important and AWS lets you do that. Since I've mentioned that it has highly flexible pricing model, you can actually go ahead and choose minimum resources, start with small and then upscale according to your needs. We also have something called as reservation benefits which I've again discussed in the past. You can go ahead and choose the models which actually meet your requirements and you can actually go ahead and reserve few of the resources up front which you are very sure about and yes you end up paying less again. Elasticity benefits. Now what AWS does is it provides you with various tools. It also provides you with something called as scheduler. Now these timeulers what they do is they let you switch off and switch on your various resources that might fluctuate when you talk about their usages. Say for example you have services like EC2, RDS. Now these are instance-based services and when you talk about their usage that might not be constant throughout the various hours of the day. So you can decide to switch off and switch on these resources so that they're used optimally and you end up paying only for the hours for which you've used those services. So this is where time scheduulers do come into picture and this is where AWS has great elasticity or great flexibility. Finally in this list we have something called as track and manage services. Now AWS provides you with various tools and softwares that actually go ahead and let you keep track of all the realtime usage and measurements that you're concerned with. Now what this does is this actually helps you optimize your usage. How? Because there are tools that let you build realtime dashboards and all those things. Now since you have those you can analyze all the traffic all the data and all the resources which you're using and thus you can cut down on lot of cost or you can just go ahead and optimize a lot of money and cost that you are investing in your projects. So these are the points that are very important when you consider cost optimization and this was probably the last point when you talk about today's session that is AWS pricing. So if you're concerned about going ahead and picking a proper cloud service provider, I would say that choose AWS and it would definitely ensure that you sleep with a lot of cost optimized. Now moving on to our first topic. What is Amazon VPC? Amazon virtual private cloud is a service that lets you launch AWS resources in a logically isolated virtual network that you define which means you'll have a part of AWS cloud that can be used only by your AWS resources and can be accessed only by you or the people you permit to access. Now these people could be your business partners, your employees or anyone you want. You will have complete control over your virtual networking environment which would include selecting your own IP addresses range creating of subnets and configuration of route tables and network gateway. I will explain all this term in some time. Now Amazon VPC allows you to create multiple layer of security including security groups and network access control list which will help you control access to your Amazon EC2 instances in each subnet. You can use IPv4 and IPv6 for most resources in your virtual private cloud which will help you ensure secure and easy access to resources and applications. Now that you have some idea about what exactly is AWS VPC, let us move on to our next topic and see how does it work. But before we get into the working part, I would like to explain the terms which I mentioned before. So if you're wondering what are subnets, these are logical subdivision of a larger network. You can launch your AWS resources into a specified subnet. And when I say AWS resources, I mean your EC2 instances and so on. There are two types of subnet, the public and the private. You use a public subnet for resources that must be connected to the internet. And with the private subnet, the resources won't be connected to the internet. Now another interesting point is IP addresses of all the subnet in a network will start with the same prefix. Next we have is a route table. Now a route table contains a set of rules called route that are used to determine where the traffic in a VPC is directed. You can explicitly associate a subnet with a particular route table. Otherwise the subnet is implicitly associated with the main route table. Each route in a route table specifies the range of IP addresses where you want your traffic to go which is the destination and the gateway which is the network interface or connection through which to send the traffic which is the target. Now as I've mentioned about public subnets and private subnet let us see the difference between them. So in a public subnet resources are exposed to the internet using the internet gateway. They make use of both public and private IPs and are mainly used for external facing applications like web servers where you want to information to be visible to the users. Whereas in the public subnet resources are not exposed to the outer world and it uses only the public IPs. They're mainly used for back-end applications like database and application servers. Now that you have some idea about subnet and route table, let us move on to the working of VPC and understand it. Now, if your account was created after 4th of December 2013, your account comes with a default VPC that has a default subnet in each availability zone. We will see this in the demo part. Now your default VPC includes an internet gateway and has the benefits of advanced feature provided by EC2VPC and is ready for you to use. Now if you launch your instance in a default VPC and do not specify a subnet where to launch your instance, the instance is automatically launched in your default subnet which is a public subnet. You can also create your own VPC and configure it as you want. This is known as a non-default VPC. Now the subnets that you create in your non-default VPC and any additional subnet that you create in your default VPC are called as non-default subnets. Now you can see we have something called an internet gateway. Now an internet gateway is a gateway that allows your instances to connect to the internet. You can do this through Amazon EC2 network edge. Each instances that you launch in your default subnet has a private IPv4 address and a public IPv4 address. As you can see here, by default, each instance that you launch in a non-default subnet has a private IPv4 address, but not a public IPv4 address unless you specifically assign it. These instances can only communicate with each other, but cannot access the internet. But you can enable internet access for this instances by attaching the internet gateway to its VPC and associating an elastic IP address with the instance. Now how can you connect your VPC to other VPC or to your on premises network? So for this you can create a VPC piring connection between the two VPCs that enables you to route traffic between them privately. Now instances in either VPC can communicate with each other as if they were in the same network. You can also create a transit gateway and use it as an interconnection between your VPC and your on premises network. The transit gateway acts as a regional virtual router for traffic flowing between his attachment which could include VPC, VPN connection, AWS direct connect gateways and transit gateway puring connections. Now I hope you have some idea about the working of VPC. Let us move on to our next topic and see some of the use cases of VPC. With Amazon VPC you can host a simple web application such as a blog or a simple website with additional layer of privacy and security. You can help securing the website by creating security group rule which will allow the web servers to respond to inbound requests from the internet while simultaneously prohibiting the web servers from initiating outbound connection to the internet. Now what this means is you can control your data traffic in and out of your VPC. You can create a VPC that supports this use case by selecting VPC with a single public subnet only from the Amazon VPC console wizard. With VPC, you can also host multi web application and strictly enforce access and security restriction between a web servers, application servers and databases. You can launch web servers in a publicly accessible subnet while running your application servers and databases in a private subnet. This will ensure that your application servers and databases cannot be directly accessed from the internet. to create a VPC that supports this use case. You can select VPC with public and private subnet in the Amazon VPC console wizard. With Amazon VPC, you can also backup and recover your data after a disaster. By using Amazon VPC for disaster recovery, you will receive all the benefits of a disaster recovery site at a fraction of the cost. You can periodically back up critical data from your data center to a small number of Amazon EC2 instances with Amazon EBS volume. Or you can also import your virtual machine images to Amazon EC2. To ensure business continuity, Amazon VPC allows you to quickly launch replacement compute capacity in AWS. These were some of the use cases of using VPC. Now let us move on to our next topic and see an overview of the other networking concepts in AWS. First let us talk about elastic load balancer. Elastic load balancing automatically distributes your incoming traffic across multiple target. The targets could be EC2 instances, containers and IP address in one or more availability zones. It will monitor the health of your registered target and route traffic only to the healthy target. It scales your load balancer as your incoming traffic changes over time. You can add and remove compute resources from your load balancer as you need changes. It will not disturb the overall flow of request to your application. Now, elastic load balancing offers four types of load balancer. First is the classic load balancer which provides basic load balancing across multiple Amazon EC2 instances and it operates both at request level and the connection level. A classic load balancer is intended for applications that were built within the EC2 classic network. Second, we have application load balancer. It is best suited for load balancing of HTTP and HTTPS traffic and provides advanced request routing which is helpful in modern application architecture including microservices and containers. Third, we have network load balancer which is best suitable for load balancing of TCP, UDP, TLS where extreme performance is required. A network load balancer routes traffic to targets within Amazon VPC and is capable of handling millions of requests per second while managing ultra low latencies. Fourth, we have the gateway load balancer. It is used to deploy, scale and run third party virtual networking appliances. Gateway load balancer is transparent to the source and destination of traffic which makes it well suitable for working with third party appliances for security, network analytics and other use cases. This was about elastic load balancer. Now let us take a look at AWS direct connect. AWS direct connect is a cloud service solution that makes it easier for you to establish a dedicated network connection from your on premises to AWS cloud. Using AWS Direct Connect, you can establish a private connection between AWS cloud and your data centers or your office. You can increase the bandwidth throughput and provide a more consistent network experience than internetbased connections. AWS direct connect is also compatible with all the AWS services and is available in a speed starting from 50 Mbps and can be scaled up to 100 GB per second. It helps you build hybrid environment which allows you to use the benefits of AWS and continue to utilize your existing infrastructure. Now let us move on to our next service which is Route 53. Amazon Route 53 is a highly available and scalable cloud domain name system or DNS web service. It is designed to give developers and businesses a reliable and cost-effective way to route end users to internet applications by translating names into numerical IP addresses. This can be used for computers to connect to each other. Now route 53 performs three main function. First one is it registers your domain name. Every website needs a name be it edure.co or anything like facebook.com. So route 53 lets you register a name for a website of web application known as a domain name. The second function is it routes internet traffic to the resources for your domain. So when a user opens a web browsers and enters your domain name or the subdomain name in the address bar, route 53 helps connect the browser with your website or web application. The third function is it checks the health of your resources. Route 53 sends automated requests over the internet to a resource such as a web server to verify if it is reachable, available, and functional. You can also choose to receive notification when a resource becomes unavailable and choose to route internet traffic away from the unhealthy resources. Now these were some of the networking services in AWS. Now let us move on to a demo part where I will teach you how you can create a VPC, your subnet, your route table and internet gateway. So for our demo, I've logged in into my AWS console. If you do not have an AWS account yet and want to practice AWS services, I would highly recommend you to create an AWS free account where you can access more than 75 AWS services for free for an year. So a point to remember is your VPC will be set in this region. In my case, it is OIO. You can see there are so many regions available here. Your VPC can be set in your selected location. Now let us start a demo. We'll search for VPC. You can just search over here. VPC. Here it is. Now when you click on your VPC, you can see there is a default VPC. As I mentioned before, it will also have a default subnet inside it. So now let us create our own VPC. So I click on create VPC. So it will ask us to name our VPC. Let me name it demo VPC. Now when you create a VPC you must specify a range of IPv4 address for the VPC in the CI block which stands for classless interdomain routing. We will go for the primary C block which is 10.0.0.0/16. Now mention 16 over here which means 16 bits reserved for my VPC network. Now we'll go with the default. I do not want any IPv6 C block. Next we have tenency. Now here you can see we have two option one is default the other one is dedicated. So what dedicated means is you can run your instances in your VPC on a single tenant or a dedicated hardware. So we'll just stick to default here and create a VPC. Then you get a message saying you have successfully created your VPC. This is your VPC ID and this is your VPC name. Now let us create a subnet. Now as I've told you in the theory session a default subnet is created and you see we have three default subnets over here. When I just scroll here you see the three default subnets are created in three different availability zone. So each availability zone has one subnet in it. So now let us create a new subnet. We have to select a VPC from here. This is a VPC. So come down and we'll name our subnet. Let us name it demo subnet. Now we have to select availability zone. We have three availability zones in OIO. We'll just select one of these. Now we also have to mention our IPv4 C block for our subnet. So we'll just set it to 24. So when I type 24 over here, it means 24 bit is reserved for my VPC network. Now the starting of the IP address of the subnet should be the same as the starting address of your VPC. Now after this let us create a subnet. This might take a few seconds and you can see you have successfully created your subnet. This is your subnet ID and this is a subnet name. Next we'll create our internet gateway. We'll get back to route table in a few minutes. Now as you can see there is a default internet gateway but we will go ahead and create our own internet gateway. So here it will ask us to name our gateway. Let's just name it demo internet gateway and just create our internet gateway. It is very simple. Now our internet gateway is created. This is our internet gateway ID but the state is detached. Now you can go attach your VPC to your internet gateway. Just click on attach to a VPC over here and just select a VPC from here. Here is our VPC. So we'll just select it and now attach internet gateway. So here the state is attached. Now let us move on to the next step and create our route table. Now as I've mentioned before route table determines where the network traffic from a VPC is directed. Now these are some of the default route tables but we'll create a new route table. So now we have to name a route table. Let us name it demo route table. And we have to attach a VPC to it. Here is a VPC that is created. We'll get a message saying a following route table was created. And here is a route table ID. We close it. So after we create a route table, we have to associate a subnet to it. So we'll just click on route table over here. Go to subnet association. Edit subnet association. Now select a subnet. So this is a subnet demo subnet. So we'll save it over here. After the subnet association, we have to edit the route to access the internet gateway. So we click on route. Edit our routes. Now let us add another route. So the destination will give 0.0.00. Now this means your traffic can flow anywhere. The target will keep it as internet gateway. So we're trying to access our internet gateway. So we'll select this and then save the route. Now we get a message saying route successfully edited. We close it. Now with this we have created a VPC, a subnet, a route table and internet gateway. Now let us see if we can launch an instance in a VPC. But let me go to new tab EWS management console. Let me tap EC2 over here. I'll go to instances. I'll go to launch instances here. Let me launch in window instance. So I'll select window. Now I'll select this instance and then go to configure instance. Now here under network I'll remove the default VPC network and set my network. I'll change the subnet also. And we also have to change the auto assign public IP to enable. We will enable this to create a public IP. So after this we'll make no changes. Go to review and launch. Before that, let us create a security group. Uh let us just name it demo security group. And now review and launch. We'll use a existing key pair. And now launch our instance. Now let us click on view instance. Now this might take a couple of minute. While our instance is getting created, let us go back to our VPC. You go to VPC dashboard and here you can see there are two VPC. One is a default VPC and the other one which we have created and there are four subnets. Three are defaults and one which we have created. There are two default route table and one which we created. There was one internet gateway which was default and then we created another one. Now let us check our EC2 instance. We'll refresh it. Now you can see 212 status check is passed. So we click on our instance ID. Now this is our instance ID. This is a public IPv4 address. A public IPv4 address. Now when we come down and see the VPC ID over here. You can see the instance was created in our VPC ID. That is the name of our VPC and it is also created in our subnet which is the demo subnet. And you can also see it was set up in the availability zone you had mentioned. Now the instance can be used only by me or the people I permit. A part of AWS virtual cloud was given to me to run my resources. Now again guys if you are completely new to AWS that is Amazon Web Services please go through the other videos that we have in our stack or in our playlist on YouTube. Probably those would hold you in a much better state to understand some of the terms that I would be using as we move further. I would be talking about these terms as well but we won't be getting into the depth of the terminologies here because we assume that the fact that you're here you have some understanding of what AWS is. So let's just move further and try to understand these practices. So when I say EC2 it is elastic cloud compute a computation service offered by AWS. Now what does this service do? Well, basically what it does is it lets you create ROSS servers on which you can host your websites and other applications that you have. So that is what EC2 stands for. So what are the practices that you can do to make sure that your AWS or your account or your infrastructure in general is in a better state. So these are some of the practices. AMI hardening is the first one. Now AMI Amazon machine image what it does is if you have an EC2 server basically what it does is it lets you make a copy of it take an image of it and use it as a template to generate similar kind of instances. So what can you do with this template? Well, the first problem is if you're having an infrastructure or an application that has multiple instances, in that case, replicating your instances each time won't make a lot of sense because you need a secure and a more robust AMI. So, can you define certain properties for it? Yes, you can actually define certain properties and harden your EMIs in a much better way. Say for example you have your SSH which is nothing but your secured shell host. In that case what you can do is you can change these hosts so that your account is more secure. Apart from that you can ensure that you actually have proper IM users and VPC accesses that are given to your so-called instance so that it is secure on a higher level or at a better level. VPC port location. Now when I say VPC port location virtual private cloud as we know what it does is it brings in a number of instances under one umbrella that means you need these instances to communicate with each other as I've already mentioned you won't be dealing with one single instance right so in this case you want these instances to communicate and how do they do that you use VPC but what are the problems with VPC the major problem is security concern who gets to access your VPCs Now basically what you can do is you can limit your IP addresses. It is advised that you block your IP addresses. You do not give any random IP address to access your VPC. But then there are certain VPCs which need to be accessed by certain IP addresses. In that case you can make your ports or your VPCs open for certain IP addresses only. Private subnets. Now all your applications should fall under private subnets. There is an exception. You have your load balancers and stuff like that which do not fall under your private subnets but you have to ensure that remaining stuff it falls under your private subnets and they are properly secured. Micros service architecture. Now what is a micros service architecture? Well microser architecture what it does is it helps you break down your architecture into simpler portions or simpler manageable services. Now to give you an example suppose you have your e-commerce website something like Amazon. So you have so many verticals I mean you have your payment billing your security your front end back end number of verticals that is the products that are sold different products for male female and stuff like that. So all these needs to be arranged into a more manageable system right. So what happens here is instead of having one monolithic architecture for these individual verticals if you can have a different service that caters the need better on longer run why even if one vertical goes down the other verticals are working smoothly that means these verticals aren't dependent on each other so introducing this kind of architecture into AWS would definitely help because if suppose your billing goes down maybe your login credentials or your login form still works So for people who just need to login they can do that and for people who want to build probably they might have to wait but again at least one service is working. So that is what micros service architecture helps you do. So implementing these kind of architectures also becomes important. Environmentbased keys. Now again when you talk about accessing your EC2 you cannot just go ahead and access your EC2. You need to give in some password details. Now how do you have or how do you get in your password details? You do not login with your username and ID. Here when you create an instance with that you create a user key and its password. Those are called as your SSH keys again which are used to log into your instance. So it is important that you have individual keys for your different environments. You have key for your development environment. You have one more key for your administrative environment. What this does is suppose if I have a developer person, I would give him access only to the dev environment because probably he or she is not concerned with the administrative environment and I do not want them to have that access. So this helps me in better organization and keeping my resources safer. So having environment based keys also work well. And finally LDAP authentication. Now if I have a number of environment based keys, I have n number of users and stuff like that. So authenticating these login or these user credentials can be a tedious task. So instead of doing it manually, there is something called as LDAP authentication that helps you automate this process and saves you from the tedious efforts that you would otherwise put in. So yes, this also becomes an important practice when you talk about EC2. So yeah, these are some of the practices. Now let's move further and talk about something else. IM that is identification and access management basically. Now here as the name suggests what you do is you actually manage and govern the access given to the users that are using your AWS services. So let us move further and take a look at some of the practices that ensure that IM is taken care of properly. Roles for teams. Again I talked about the importance of having environment based keys. This is a little similar. You should have roles defined in hierarchy so that you can give proper access to proper people. Suppose I'm creating an IM user. For people who do not know what IM user is, it is nothing but it is a second level login where I do not give root access to everyone. Instead I give access to individuals where they have access to certain resources only. So that is what an IM user is. So my root user would be having access to everything that happens. But my IM user would be having access only to certain resources. So when you do assign these IM roles or accesses to your individuals or employees, if you have roles defined for your teams, you can know how much access to give to which individual. That is why roles for teams actually play in very well. So it is important one has a structured approach and proper roles defined for their teams. Service specific access we've discussed this already. If you are into development probably the services that concern development you should have access to only those services and accordingly should be your IM user access given to you. You should have read only access. Now this is not true always. now but yeah in some cases say for example you are a fresher maybe or somebody who has recently joined in the company and I do not want you as an individual to access all my resources or make changes to those instead I just want you to get a view of those so probably I would give you readonly access so probably you can understand everything that is happening but cannot make any changes to the stuff that is there so read only access also becomes important so when it comes to identification and access management you need to follow these practices There are a couple of more but these are the important ones. S3 practices. So what is S3? S3 stands for simple storage service. Now it is a storage service provided by AWS. And what it does is it takes in your data in the form of objects and stores it in buckets or in containers which are called as buckets. So what are the best practices that you can do or relate to S3. What you can do is you can have content specific names. Now why do we need to do this? What AWS does is it names its services or it not its services rather S3. What it does is in order to create S3 buckets what you have to do is you have to give specific or unique names to your resources. So if there is a name that is already taken you cannot use it. It is not allowed. So in that case you'd be forced to use longer names. To give you an example, suppose if Edureka does not work out, you might be required to enter something like Edureka certification, Edureka training. So depending on that, the size of your name would go much bigger than what you expect. So in that case, having content specific names helps. Say for example, I am talking about an AWS course, maybe a master's course with Edureka. So probably my name should be something like Edureka Masters AWS. So it creates an hierarchy and what it also does is it makes it simple to understand the names. So having this practice is actually a good habit. Create bucket policies. Again this becomes very important. Why is that? Now who needs to access your buckets? It also becomes important. What kind of data are you storing in that bucket and which people do you want to access your particular bucket. So to control these things you need to give proper bucket access as well. Archive buckets to Glacier. Now what is glacier? Let's first understand S3 a little more. Now S3 is a simple storage service which lets you store and retrieve data at standard pace but it is costlier compared to a service called as Glacier. Now Glacier again it lets you store data but it is specific for archival data and it is much cheaper. Why is that? First understand archival data. This data is data that you do not want to access every day. To give you an example, suppose I want my birth certificate. For that, I would have to go to a hospital, right? So, if you remember the old school traditional method where we had everything put in papers, probably if I did go there and tell them that give me my birth certificate after 25 years or my 30 years of my age, what would happen there is probably they would tell me that you have to wait for maybe a couple of days, couple of hours and then come back to take that document because that document is not retrievable right now. So there are certain things where the data that is stored is not required frequently like in the case of my birth certificate right but if it was some medication or prescription that I took maybe from a medical store they would have a copy of it in the system right which I can readily take it right away why because probably that is more required information so try to relate this example with S3 and glacier your S3 is like your medical system where you get your data right away you go there you tell them I need this I had done this or this stuff. So they would give you the data right away that yes this is the record we have. But for my birth certificate it is more or it is similar to glacier where you store in data which you do not require frequently probably once in a lifetime or maybe five times in your life. So similarly the data that you do not need every day I need it maybe once in a while I can put it in glacier. So the fact that I cannot retrieve it right away it is cheaper. So what best practice would be it is to move your S3 data to Glacier in case if you're not using that data every day. That would help you save a lot of money. Version your objects. Yes, this is very important. Again, when I say versioning your objects, what I'm trying to symbolize or lay emphasis on is the fact that if you put in your data into your S3 bucket, you can constantly make updates or keep a fresh copy of the recent update. as in when you create a version you're stating that this is the recent entry to my data. So what that does is in case if you want to go back you can go back to the freshest copy that you've stored. So versioning also helps. So these are some of the practices that concerns S3. So let's just move further and try to understand some of the security practices. Now if you talk about cloud computing people have always doubted whether cloud platforms are secure or not. But that question or that debate has been put to rest a while ago. People know that cloud platforms are very secure and these are some of the practices that ensure that your cloud platforms can be a lot more secure than what you think right now. So what you should do is you should never share your root account credentials with anyone. As I've already mentioned, you have a root account using which you can create different IM users which can be assigned to people who have specific responsibilities. So they would be answering or solving or having access only to those resources that they need. So if you share your root account details with anyone probably they might misuse your resources and that might lead to hampering your overall security of the infrastructure. So make sure that that does not happen. Remove unwanted users. Say for example somebody leaves your company. Now having an IM user with that credential won't be good because if that person still has access to those resources probably he can hamper you again enable two factor authentication yes you can have a number of other devices which generate four to sixdigit codes. So once you do login with the credentials if you are associated with these kind of applications probably this would ensure that the user has to login twice and so that the system stays more secure than what it is already. Use AM login. Yes. Now this again is important. I've already mentioned if you need users to have access to your resources, give them limited access. They need not have to have access to everything that is being used. So this is one practice which again becomes very important. Billing practices. So how can you optimize cost? Well, if you talk about cloud computing, it ensures that you don't pay a lot of money. I mean because you're paying for the resources that you're using and only for the time duration you're using those resources. So the amount is very less but still at times when you talk about huge infrastructures and architectures you might be forced to shell out a lot of money. So how do you prevent or how do you optimize this further? Well there are certain practices. If you do implement those practices definitely you can save a lot of money. One practice that you can do is billing budgets. Now what it does is you can pre-state. Okay, I want to use these many resources for this duration of time. So AWS gives you a predefined budget. Okay, this is the amount you'd be paying and these are the resources you would be using. So if you do set an alarm, AWS would alarm you saying that okay, you are reaching a particular limit of your resources. Keep check of those resources and this is where billing budgets help you a lot. What billing budget also does is it ensures that each individual service it has its own proper billing budget as well. Say for example S3 charges might be different your different services like EC2 and all if you have your certain servers running your databases running. So in that case the charges vary. So if you're using a particular resource you'll be charged only for those resources and accordingly you can set budgets as well. So that helps you in the longer run. AM billing. Yes. Now billing access is given to few users only. You do not have IM billing access in general to start with. But if you want certain users to have access to your billing so that they can help you better plan your expense and maybe help your organization with the finance stuff probably you can have some IM users having certain billing accesses as well. Multiple credit card payments. Now what AWS does is it gives you a facility where you can have multiple credit cards linked with your account. So if you're using a particular credit card and while paying the bill you reach its limit you might switch to the other credit card as well. This again helps in the longer run. Regional taxation. Yes. Now based on the region where you are based in your taxes might vary but in general if you allocate this particular service now there is a tab available in your billing department where you can activate this notion. And once you do that, AWS keeps track of all the resources that you've used and the money you've paid. So when you're filing your ITR income tax returns, that is probably you can always put in the details given by AWS. You can generate a copy of it and say that I have paid my money here. So probably that would help you with the taxation part as well. And finally, you should have multi-account consolidation. Now this is opposite of what we discussed in the third pointer. not opposite but a little contradicting to that point. And how is that? Well, when you talk about multi- account consolidation, what it says is if you have multiple resources or that are linked to each other, if you want to pay them in one go, instead of paying them individually, you can have those resources consolidated in one place and have a consolidated billing account for it. So when a bill is generated instead of paying maybe four or five bills one by one you can do it in one go paying all of them added together. So yeah these are some of the best practices that concern billing and more or less these were the practices I wanted to talk about. What is DevOps? DevOps is basically a combination of two words, development and operations. So what do we get when we combine these two? Simply speaking, DevOps is a culture that implements technology in order to promote collaboration between development and operations team to deploy code to production faster in an automated and repeatable way. The goal of DevOps is to increase an organization's speed when it comes to delivering applications and services. Many companies have successfully implemented DevOps to enhance their user experience. Let's take for example Facebook's mobile app which is updated every 2 weeks effectively telling users you can have what you want and you can have it now. Ever wondered how Facebook is able to do this so smoothly? It's the DevOps philosophy that helps Facebook ensure that its apps aren't outdated and that its users get the best experience. Facebook accomplishes this through a code ownership model that makes its developers responsible that includes testing and supporting through production and delivery for each kernel of code they write and update. It's through policies like this that Facebook has developed a DevOps culture and has successfully accelerated its development life cycle. Industries have started to gear up for the digital transformation by shifting their needs to weeks and months instead of years while maintaining high quality. As a result, we will soon see that DevOps engineers have more access and control of the end user than any other person in the enterprise. So what are you waiting for? Don't be in the sidelines when that happens. To master your skills, enroll in Edureka's DevOps certification program and become a leader. Why do we need DevOps? The birth of DevOps occurred when there were some drawbacks with the existing software development models for application development. The first model we'll be addressing today is the waterfall model. So the waterfall model is a model of software development which is pretty straightforward and linear. So this model follows a top- down approach. As you can see in the image, it has various phases starting with requirements gathering and analysis. So the first phase is where you get the requirements from the client for developing an application. So after this you try to analyze these requirements that you've acquired. Next comes the design phase where you prepare a blueprint of the software. So in this phase you think about how the software is actually going to look like. Once the design is ready, you proceed further with the implementation phase where you begin with the coding for the application. So here the team of developers work together on various components of the application and once the application is developed, it is tested in the verification phase that is the fourth phase. Here there are various tests conducted on the application such as unit testing, integration testing, performance testing etc. After all of these tests on the applications are done, it is finally deployed on the production servers. At last, that is the fifth phase is the maintenance phase. So in this phase, the application is monitored for performance. So any issues related to the performance of the application are resolved in this phase. But unfortunately, this model that is the waterfall model has some major drawbacks. So the first drawback is gathering and documenting your requirements each step of the way can be extremely time consuming. Not to also mention difficult. It is hard to assume things about your product so early into the project. And because of the same reason your assumptions might be flawed and different from what the customer expects. The second drawback is that now if the above case is true your customers are basically dissatisfied with your delivered product. adding changes to the product can be expensive and most of all difficult to implement. So the third drawback is that in general the risk is extremely high with the waterfall approach because the scope for mistakes is extremely high. If things go wrong, fixing them can be hard as you have to go a couple of steps back. The next model is the agile model. So agile is an iterative based software development approach where the software project is broken down into various iterations or sprints. So every iteration has phases like the waterfall model such as requirements gathering, design, development, testing and maintenance. You can see each of these iteration in the image. So each of this iteration generally lasts for about 2 to 8 weeks. So the difference between agile and waterfall model is that you release the application with some high priority features in the first iteration. After its release, the end users or the customers can give you feedback about the performance of the application. So the necessary changes are made to the application along with some new features and once these features are added to this application, it is again released which is in the second iteration. This procedure is repeated until the desired software quality is finally achieved. Now in spite of being used often the agile method has a few disadvantages. The first one is that for the approach to work all the members of the team must be completely dedicated to the project. That is everyone must be involved equally if you want the whole team to learn and do better on the next run. And this is mainly because agile focuses on quick delivery. There might be an issue with hitting deadline. The second drawback is that the approach may seem extremely simple but it is hard to execute. So it requires commitment and for everyone to be on the same page ideally in the same physical space. The third drawback is that documentation can sometimes be ignored because agile methodology focuses on working software over comprehensive documentation. Things might sometimes get lost through each stage and iteration. As a result, the final product can feel different from what it was first planned. So these are the few drawbacks that the agile model or the agile methodology gives us. So in delivering valuable software to customers, development and operation teams are always in conflict with each other. While development wants to deliver its changes to customers quickly, operations want stability which means not changing the production systems too often. So the gap between the development and operations team occurs on three different levels. The first one is the incentives gap. This is because of different goals of development and operations. The second one is the process gap which is the result from different approaches of development and operations and how to manage changes, bring them to production and maintain them there. The third one is the tools gap which results from the fact that development and operations often use their own tools to do their own work. And this is resulting from the fact that development and operations often use their own tools to do their work. As a result from all of these reasons, development and operations often act like silos as they are two distinct teams. So the conflict between development and operations is because of two reasons. The first one is need for change. This is because development results in change. That is they're always working on new features, bug fixes, etc. It wants the change to quickly roll out to production. And the second one is fear of change. Once the software is finally delivered, the operations department avoids making changes to the software to ensure stability. This is the major conflict between both of these teams. So this is where DevOps comes into picture. DevOps links software development to operations. I hope that is clear. That is DevOps bridges the gap between agile software development and operations experiences. It is important to know that DevOps is a set of principles to break down silos. Specifically DevOps is all about culture, automation, measurement and sharing. So the first one is culture. So in culture, people and processes comes first. If you don't have a culture, all automation attempts will be fruitless. The relationship is important in culture because its functions include engage early, engage often, destroy silos, be open to options and stop blaming. And the second one is automation. So once you understand your culture you can simply start with automation right now you can finalize various tools to achieve automation for DevOps that is tools for release management provisioning configuration management systems integration monitoring and control and orchestration becomes extremely important pieces for DevOps. The third is measurement. So if you cannot measure you cannot improve. Makes sense right? A successful DevOps implementation will always measure everything it can as often as it can. Performance metrics, process metrics, people metrics, capacity planning, trend analysis, fault finding etc. All of these have to always be measured. So the last one is DevOps is about sharing. Sharing is a loop back in the cycle. So creating a culture where people share ideas and problems is extremely critical. So exposing ideas can create great open feedback that in the end it helps to improve, share ideas, share metrics, give DevOps shell access, see what technology can be leveraged etc. So DevOps is all about these four particular features. I hope this is clear. So now let's move on to the next part of today's session that is introduction to DevOps. So finally we will address what is DevOps. DevOps is simply a combination of two words. You can see that one is the software development and the second one is operations. So this allows a single team to handle the entire application life cycle that is from development to testing, deployment and finally operations. So DevOps really helps you to reduce the disconnection between software developers, quality assurance engineers and system administrators. that is it basically promotes collaboration between the development and operations team to deploy code to production faster in an automated and repeatable way. So DevOps basically helps to increase organization speed to deliver applications and services. It also allows organizations to serve their customers better and compete more strongly in the market. It can be also defined in another way that is it is also a sequence of development and IT operations with better communication and collaboration. So in the market it has become one of the most valuable business disciplines for enterprises or organizations with the help of DevOps. The quality and speed of the application delivery has improved to an extremely great extent. Organizations that have adopted DevOps noticed a 22% improvement in software quality and a 17% improvement in application deployment frequency. They have also achieved a 22% hike in customer satisfaction. Overall, a 19% of revenue hikes as a result of the successful DevOps implementation has been achieved. Moving on, DevOps workflow is another important concept. So what is a DevOps workflow? So it basically provides a visual overview of the sequence in which input is provided. Also it tells about which one action is performed and output is generated for an operations process. So basically DevOps workflow allows the ability to separate and arrange the jobs which are top requested by the users. Also this workflow gives the ability to mirror their ideal process in the configuration jobs. Moving on, let's see some of the DevOps principles. So the main principles of DevOps are continuous delivery, automation and fast reaction to the feedback. But there are six other principle that we'll be discussing today. The first one is the end to-end responsibility. So DevOps teams need to provide performance support until they become the end of life. It enhances the responsibility and the quality of the products engineered. The second one is continuous improvement. DevOps culture focuses on continuous improvement to minimize waste. that is it continuously speeds up the growth of the products or the services that has been offered. The third one is automate everything. Automation is an essential part of the DevOps process. We'll be discussing about this later on in this session. This is for the software development and also for the entire infrastructure landscape. The fourth one is customercentric action. So the DevOps team must be customer ccentric so that they should continuously invest in products and services. The fifth one is monitor and test everything. The DevOps team needs to have robust monitoring and testing procedures. The last one is work as one team in the DevOps culture role of the designers, developers and testers are already defined. So all they need to do is work as one team with complete collaboration. These principles are achieved through several DevOps practices which include frequent deployments, quality assurance, automation, continuous delivery, validating ideas as early as possible and in team collaboration. Now let's move on to the third topic of today's session. Companies using DevOps. By now you must have figured out that DevOps helps to increase an organization's speed to deliver applications and services. This is exactly why many organizations such as Amazon, Netflix, Etsy, HP, Adobe and many other organizations adopting DevOps and its practices. We will now discuss how Amazon makes use of DevOps to increase their work efficiency. You must be aware that Amazon is one of the biggest e-commerce companies in the world. But way back in time, their website followed a traditional monolithic architecture. So in this type of architecture all the processes are coupled together and run as a single service. Over time as the code and the source files grew it became hard to scale maintain and upgrade the applications on physical servers. So what did Amazon do? Amazon simply solved the problem of the monolithic architecture by moving from physical servers to cloud-based Amazon web services. You all must have heard of AWS. Currently AWS follows a micros service architecture. In Amazon there basically three types of microservices. They are users, threads and posts. Developers here apply frequent but small changes over their code via version control tools like Git and GitHub. Practices like code deployment help fix bugs and adds new features to improve the underlying software application. AWS code deploy is one such service that keeps track of deployments and simplifies the entire software release process. Amazon also uses Apollo. Apollo is a simple one-click internal deployment tool. So Apollo's job is to deploy a specified set of software across a group of hosts. On the other hand, practices like configuration management and infrastructure escode help to monitor and make changes in the software. It keeps track of the systems performance and resources used by developers. So in this way the testing team can identify problems way before in hand and fix them immediately. So this is how Amazon implement DevOps and its practices. Now let's move on and understand one major concept of DevOps that is the DevOps life cycle. So if you're into DevOps from quite some time now, you must have heard at least one of these DevOps phases that is continuous development, continuous integration, continuous testing, continuous deployment, and continuous monitoring. So all of these phases that I just mentioned make up the DevOps life cycle. As you can see on the screen and as I've already mentioned, all of these phases make up the DevOps life cycle. The first phase is the continuous development phase. So this is the phase that involves planning and coding of the software. So the vision of the project is decided during the planning phase and the developers begin developing the code for the application. There are no DevOps tools that are required for planning but there are a number of tools for maintaining the code. The code can be written in any language but it is mainly maintained by using version control tools. So here maintaining the code is referred to as source code management. So some of the most popular version control tools are git, svn, mercurial, CVS etc. Also tools like ant, maven, gradal can be used in this phase for building or packaging the code into an executable file that can eventually be forwarded to any of the next phases. The next phase in the DevOps life cycle is continuous testing. So this is the stage where the develop software is continuously tested for bugs. for continuous testing automation testing tools like selenium testng junit etc are used. So basically the tools that I just mentioned right now allow quality asurances to test multiple code bases thoroughly in parallel to ensure there are no flaws in the functionality. So what automation testing does is it saves a lot of time, effort and labor for executing the tests instead of doing this manually. Right? Also in this phase, docker containers can be used for simulating the test environment. Selenium here does the automation testing and the reports are generated by testng. So this entire testing phase can be automated with the help of a continuous integration tool called genkins. We'll talk about genkins later on in this session. So now let me explain you this with an example. Suppose you've written a selenium code in Java to test your application. Now what you can do is you can build this code using ant or maven and once the code is built it is tested for user acceptance testing. So this entire process can be automated using genkins. Besides that the report generation is a very big plus point. The task of evaluating the test cases that failed in a test suite gets simpler. We can also schedule the execution of test cases at predefined times. Once the entire testing is done, the code is continuously integrated with the existing code. The third phase of this life cycle is continuous integration. So now this stage is the heart of the entire DevOps life cycle. It is a software development practice in which the developers require to commit changes to the source code more frequently. This may be on a daily or a weekly basis. So every commit is then built and this allows early detection of problems if they're present. Building code does not involve compilation but it also includes code review, unit testing, integration testing and packaging. The code that is supporting new functionality is continuously integrated with the existing code. Since there is continuous development of software, the updated code needs to be integrated continuously as well as smoothly with the systems to reflect changes to the end users. As I've already said in the previous slide, Genkins is a very popular tool used in this phase. So whenever there is a change in the git repository, Genkins simply fetches the updated code and it prepares a build of that code which is in an executable file. So once this entire build is performed, it is then forwarded to the test server or the production server. Now let's move on to the fourth phase of the cycle that is the continuous deployment phase. So this is the stage where the code is deployed to the production servers. It is very important to ensure that the code is correctly deployed on all the servers. Now before moving on, let us understand a few things about configuration management and containerization tools. Now these set of tools help in achieving continuous deployment. Firstly, I will talk about configuration management. It is basically the act of establishing and maintaining consistency in an application's functional requirements and performance. So let me put this in simple words. It is the act of releasing deployments to servers, scheduling updates and most importantly keeping the configurations consistent across all the servers. Since the new code is deployed on a continuous basis, configuration management tools play an extremely important role in executing tasks quickly and frequently. Now some popular tools that are used here are Puppet, Chef, Salt Stack, and Anible. Containerization tools also play an equally important role in the deployment stage. Docker is one of the most popular tool used for this purpose. Basically, these tools help produce consistency across development, test, staging and production environments. Besides this, they also help in scaling up and scaling down of instances very swiftly. Basically containerization tools help in maintaining consistency across the environments where the application is deployed, developed and tested. Using these tools, there is no scope of errors or failures in the production environment as they package and replicate the same dependencies and packages used in the development or testing or staging environment. Basically, it makes your application easy to run on different computers. The next stage is the continuous monitoring stage. This is the last stage in the DevOps life cycle. This is a very crucial stage where you continuously monitor the performance of your application. So here vital information about the use of the software is recorded. This information is processed to recognize the proper functionality of the application. The system errors such as low memory, server not reachable etc are resolved in this phase. The root cause of any issue is determined in this phase. It also maintains security and availability of the services also. If there are any network issues, they are resolved in this phase. That is, it helps us automatically fix the problem as soon as they're detected. So now this practice involves the participation of the operations team who will monitor the user activity for bugs or any improper behavior of the system. The most popular tools used for this phase is Splunk, Elk Stack, NGIOS, New Relic and Sensu. So what these tools do is they help you monitor the application's performance and the servers very closely and they also eventually enable you to check the health of the system proactively. Now using these tools, they can also improve productivity and increase the reliability of the systems which in turn reduces IT support costs. Any major issues if found are reported to the development team so that it can be fixed in the continuous development phase. This also leads to a faster resolution of the problems. The stages are carried out on loop continuously till you achieve the desired product quality. Therefore, almost all of the major IT companies have shifted to DevOps for building the products. Moving on, if you want to become a DevOps engineer or be a part of this ideology, it is extremely important for you to be familiar with some DevOps related tools. Today I will be talking about seven important DevOps tools. Now before we understand the tools DevOps engineers use, it is important to understand containers. So what are containers? Containers allow you to package your application and its dependencies together into one manifest that can be version controlled, allowing for easy replication of your application across developers on your team and machines in your cluster. This is exactly why containerbased microservices architectures have profoundly changed the way development and operation teams test and deploy software. Containers really help companies modernize by making it easier to scale and deploy applications. But they have also introduced new challenges and complexity by creating an entirely new infrastructure ecosystem. IT companies are now deploying thousands of container instances daily and that's a complexity of scale they have to manage. How do they do it? Here is where Kubernetes comes to the rescue. Kubernetes is a container management technology developed in Google to manage containerized applications in different kinds of envi