Pass HashiCorp Terraform Associate Exam in First Attempt Easily

Introduction

1. Introduction to the Course and Certification

Hey, everyone, and thanks for subscribing to the Hashicorp-certified Terraform Associate Certification-based Video Course. I am ZEEL, and I am going to be an instructor throughout the course. Now, before we proceed, I would like to share my own personal journey of how I came across Terraform and why I started to love it at first glance. So let's get started. Now, TerraForm is one of the great tools on which I have been working for a long time. Now, my own personal journey began with implementing the AWS hardening guidelines. So generally, while I work as a consultant for multiple organizations, one of the primary responsibilities as far as security is concerned is to implement the AWS hardening guidelines. And if you would observe the AWS hardening guidelines, there are more than 100 pages of guidelines. Initially, everything was done manually, and it took two to three days to complete the entire hardening in one AWS account. Now, before we proceed further, let me actually show you one of the hardening guidelines for security in AWS. This is one of the benchmark for hardening in AWS. So if you would observe over here, these are all the rules that you will have to implement. And if you look into the amount of pages, close to around 150. And if you go down, you will see each of the hardenings in detail as they are associated with the description and the things that need to be done. Now, if you try to implement this manually, initially it might be a little difficult, but at a later stage, things might be a little easier. Because first what you have to do is go ahead and read things in detail, see what steps it is trying to perform, and then do the steps manually in each AWS account. So initially thing seems to be good primarily because accounts were little less. But one of the new plans that I had had more than 35 AWS accounts, and implementing multiple hardening guidelines across these accounts was really hard. So that was the time when I decided to stop things manually and look out for an infrastructure-as-code tool. And that is when I arrived at TerraForm. I experimented with it, and I started to love it. So from that point on, I converted all the hardening guidelines to a TerraForm code. So if you would look into this TerraForm code, all of these are part of the CIS benchmark, and there are various other custom benchmarks that I have used for the implementation of security in AWS. So once I converted the hardening guidelines to TerraForm code, it just took around 30 minutes to implement it in AWS. And that all I had to do was run one command, and it would do everything automatically for the next 30 minutes. So, primarily after working in Terraform for a long time and looking into how amazing this tool is, I decided to launch a dedicated course for it. Now, because of the popularity of TerraForm in today's organisations, Hashicov has also officially released the TerraForm Associate Certification. So one important part to remember is that this is a certification-specific course with the primary intention to cover all the topics that are part of the HashiCorp Certified TerraForm Associate Certification. Now, let me quickly show you the certification's official page. So this is the hash of "certified TerraForm associate." And these are the basic prerequisites. So all you need are basic terminal skills and an understanding of on-premise and cloud architecture. So even if you are aware of a single cloud provider like AWS, that is more than enough. This TerraForm Certification is now valid for TerraForm versions 0 to 12. Now, in the exam preparation section, we'll go over the exams in detail and what they entail. But let's look into the exam objective at a high level overview. So within the exam objective, there are multiple high-level categories over here. So you have "understanding infrastructure" as a code, then "understanding terrain purpose," and so on. So in total, as of now, there are nine categories based on which the topics are divided into the Certification Blueprint. Now, one important point to note here is that the arrangement of topics that are part of this course is a little different from the exam blueprint to make sure that the course remains beginner friendly. So just to understand that in detail, it means that we are not following the exact chronology based on which the topics are defined. So it's like "three A, three B, and three C." So we do not follow everything sequentially, although we have all the topics covered, but I have arranged it systematically so that anyone who is new to TerraForm will be able to learn it in the best and easiest way possible. So, discussing the things that we cover in this course So we begin our journey from scratch with Terra Forma, and then we move ahead with the advanced topics. So these are the sections that we have as part of the course, and you will have to go through each one of them, preferably in a sequential way, so that you do not really miss any important topic. Now, one of my favourite sections of the entire course is this Exam Preparation Section, where we go ahead and discuss in detail what exactly this exam is all about. And we also look into some of the important topics that are part of the official exams. Aside from that, we now have a TerraForm Beginner GitHub repository to advance. So, this GitHub repository contains all of the code for the practicals that we'll be doing throughout the course, so you can go ahead and try them out on your workstation. Also, the things are arranged section wise. So the First Section is deploying infrastructure with TerraForm. So if you open one of these, you will see the associated video. And if you need to find the code associated with this specific video name, all you have to do is click here, and you will get the important notes and all the codes and commands that we enter in that specific video.

Hide

Getting Started & Setting Up Labs

1. Choosing a right Infrastructure as Code tool

Hey everyone and welcome back. Now in today's video, we'll be discussing the various infrastructure and core tools that are available in the market and how we can select the right one for our organization. Now, in the industry, there are a lot of tools that will allow you to deploy the infrastructure as code. So you have tools like TerraForm. There is cloud formation and possible heat. You also have Salt Stack, Chef Puppet, and others. Although tools like Ansible are primarily responsible for configuration management, they can also be used to build infrastructure. In fact, in one of the organisations that I have been working with for a long time, we used to create the infrastructure in AWS primarily with Ansible. Now, in this process, it is important for us to understand the primary difference between configuration management and infrastructure orchestration. Now, when you discuss tools like Ansible or Chef Puppet, these are primarily configuration management tools, which means that they are primarily designed to install and manage the software on the existing servers that are present. Now, as opposed to that, you have a dedicated infrastructure orchestration tool like Terraform and cloud formation. So this basically allows you to provision the infrastructure like servers, services, and others solely by themselves. Now, do remember that configuration management tools can do some degree of infrastructure provisioning, but the focus here is to look into the tools that are going to be a better fit for a certain type of task. Now, in fact, let me quickly show you this. So this is basically the Ansible documentation, and this documentation is on how you can go ahead and work with the EC2 instance, like how you can launch the EC2 instance in AWS, how you can terminate the EC2 instance in AWS, and so on. So you see that there are a lot of options that are available in Ansible to manage the infrastructure, like EC2 instances and so on. Now in fact, some of the parameters like Count that is available in Angle, you will see the similar one in TerraForm which does the similar purpose. So a lot of things remain very similar if you have used Ansible for infrastructure provisioning. Anyway, if you have not used that, it is fine because we learn it from scratch. Great. So one important learning from this specific slide is that if you have a dedicated configuration management tool like Ansible, just keep it for configuration management purposes. Avoid doing multiple things that it is not primarily designed to do. So if Angle is primarily designed for configuration management, just keep it for configuration management. TerraForm, on the other hand, is primarily designed for infrastructure orchestration, so you can use TerraForm primarily for that. Now, one great thing is that the infrastructure code and configuration management tools are friends. So let's go ahead and understand it. So, on the left, you have a Terraform configuration that creates a new AWS EC2 instance. So once you apply it via TerraForm, TerraForm will interact with the back-end provider. In this case it is AWS to create the new EC Two instance. Depending on that, a new EC2 instance is created, and once created, the message is returned to Terraform. As a result, the message stating that the EC2 instance is running is returned. Now, TerraForm integrates well with configuration management tools like Ansible. So let's assume that you also have an Ansible which is running within your stack. So once the EC has two instances running, Terracot can call Ansible to go ahead and install and configure the application. So once the Ansible receives this message, it can go ahead and configure and install the application or whatever code you have written within the Ansible. So, not only is your server provisioned, but the application within the server is also provisioned automatically. So this is one of the reasons why TerraForm is such a great infrastructure as code tools that are available. Now do remember that not all the infrastructure, including code tools, supports configuration management. Terraform is one of the things that it does natively. So once the configuration of the application is complete, TerraForm will send back a message saying that all the things that you had defined within the TerraForm configuration are complete. Great. So now the question is, which infrastructure as a code tool should your organisation choose? Now, for this, there are four important questions that you need to ask. The first important question is: is your infrastructure going to be vendor-specific in the longer term? So, for example, will your infrastructure be housed in AWS indefinitely? So if the organisation states that yes, our infrastructure is going to be on AWS for the next ten years, So in such cases, the option of choosing a different infrastructure as a code tool can be of advantage. So for example, in AWS, they have a dedicated infrastructure as a code tool called AWS cloud formation that is available. And in fact, cloud formation is also great. Let me quickly show you some of the nice features of cloud formation. So one of the great things that I like about cloud formation is that you can quickly go ahead and design a sample template via the GUI. So let's quickly launch it. I'll show you. So this is basically the designer. Now, depending upon the service that you want to create, what you can do is just select it from the source type and drag and drop it. Let me show you. So within EC2, let's go ahead and create a new EC2 instance. So in order to do that, all you have to do is drag and drop it, and automatically, you see, the infrastructure code has been generated here. So this is great because you can easily drag and drop things, and automatically the code is ready for you. So this is one great feature that I really like about cloud formation. So that is what the first point is all about. Again, it is not necessary that an organisation that is completely on AWS and will be on AWS for the next ten years choose cloud formation. There are a lot of other factors that are also important. In fact, in one of the organisations that I was working with, we had more than 100 database accounts, and we did not use cloud formation. We were completely based on TerraForm. So let's look into the second pointer here, which states that are you planning to have a multicloud, which is a hybrid cloud-based infrastructure? Because this is a very common pattern nowadays, many organizations have AWS plus Azure or AWS plus Google, AWS plus Digital Ocean, and so on. So are you planning to have a hybrid cloud-based architecture? Third, how well does your infrastructure of code-based tools integrate with the configuration management tool? This is a very important question. And fourth is the overall price and the support of a specific tool. So depending upon that, you can choose the appropriate ISEF tool. Now, let me show you. TerraForm works pretty well in all of these. So let's quickly look into it. The first important point, though, is that TerraForm supports multiple platforms. It has hundreds of providers. So if you are in AWS, if you are in Azure, if you're in Google Cloud, or if you are in Digital Ocean, TerraForm supports all of them. And this is the great advantage of TerraForm over cloud formation. So cloud formation is a specific tool for AWS. TerraForm works on multiple platforms, so it is not tied to a single platform. Now, in fact, let me quickly show you this from the documentation. So if you look into the support that TerraForm provides, they have multiple providers. So you have AWS support, you have Alibaba Cloud, you have Akamai, you have Google Cloud Platform, you even have tools like Pager Duty and Grafana, and if you go a bit down, you have support for Kubernetes, you have support for Signal Effects, and so on. So not only does TerraForm support cloud providers like AWS, but it also supports other tools like Kubernetes, Grafana, US Health, and others. All right? So I hope you understood the first point, and primarily because of the first point, it really makes Terraform an amazing tool to work with. A second important benefit of TerraForm is its simple configuration language and faster learning curve. It is much easier to learn TerraForm than other languages. Now, I'll show you an example. So, we had a few interns who were in our organization, and within just two weeks, they learned TerraForm from scratch and started writing good TerraForm code for deploying the infrastructure. So it is quite simple, and you'll really love it in the long term. The third benefit is its easy integration with configuration management tools like Ansible. The fourth is that it is easily extensible with the help of plugins. So you can go ahead and create your own plugins if there are certain things that you see that are not supported or if there are certain things that you want to develop specific to your organization. And fifth, it is completely free, so you can go ahead and try it out.

2. Installing Terraform - Windows Users

Hey everyone and welcome back. Now in today's video, we'll be discussing the various infrastructure and core tools that are available in the market and how we can select the right one for our organization. Now, in the industry, there are a lot of tools that will allow you to deploy the infrastructure as code. So you have tools like TerraForm. There is cloud formation and possible heat. You also have Salt Stack, Chef Puppet, and others. Although tools like Ansible are primarily responsible for configuration management, they can also be used to build infrastructure. In fact, in one of the organisations that I have been working with for a long time, we used to create the infrastructure in AWS primarily with Ansible. Now, in this process, it is important for us to understand the primary difference between configuration management and infrastructure orchestration. Now, when you discuss tools like Ansible or Chef Puppet, these are primarily configuration management tools, which means that they are primarily designed to install and manage the software on the existing servers that are present. Now, as opposed to that, you have a dedicated infrastructure orchestration tool like Terraform and cloud formation. So this basically allows you to provision the infrastructure like servers, services, and others solely by themselves. Now, do remember that configuration management tools can do some degree of infrastructure provisioning, but the focus here is to look into the tools that are going to be a better fit for a certain type of task. Now, in fact, let me quickly show you this. So this is basically the Ansible documentation, and this documentation is on how you can go ahead and work with the EC2 instance, like how you can launch the EC2 instance in AWS, how you can terminate the EC2 instance in AWS, and so on. So you see that there are a lot of options that are available in Ansible to manage the infrastructure, like EC2 instances and so on. Now in fact, some of the parameters like Countthat is available in Angle, you will see the similar one in TerraForm which does the similar purpose. So a lot of things remain very similar if you have used Ansible for infrastructure provisioning. Anyway, if you have not used that, it is fine because we learn it from scratch. Great. So one important learning from this specific slide is that if you have a dedicated configuration management tool like Ansible, just keep it for configuration management purposes. Avoid doing multiple things that it is not primarily designed to do. So if Angle is primarily designed for configuration management, just keep it for configuration management. TerraForm, on the other hand, is primarily designed for infrastructure orchestration, so you can use TerraForm primarily for that. Now, one great thing is that the infrastructure code and configuration management tools are friends. So let's go ahead and understand it. So, on the left, you have a Terraform configuration that creates a new AWS EC2 instance. So once you apply it via TerraForm, TerraForm will interact with the back-end provider. In this case it is AWS tocreate the new EC Two instance. Depending on that, a new EC2 instance is created, and once created, the message is returned to Terraform. As a result, the message stating that the EC2 instance is running is returned. Now, TerraForm integrates well with configuration management tools like Ansible. So let's assume that you also have an Ansible that is running within your stack. So once the EC has two instances running, Terracot can call Ansible to go ahead and install and configure the application. So once the Ansible receives this message, it can go ahead and configure and install the application or whatever code you have written within the Ansible. So this is how not only your server gets provisioned, but also the application inside the server gets automatically provisioned. So this is one of the reasons why TerraForm is such a great infrastructure, as there are many code tools that are available. Now do remember that not all the infrastructure, including code tools, supports configuration management. Terraform is one of the things that it does natively. So once the configuration of the application is completed, then again TerraForm will send back the message saying that all the things that you had defined within the TerraForm configuration is fined within the So now the question is, which infrastructure as a code tool should your organisation choose? Now, for this, there are four important questions that you need to ask. The first important question is: is your infrastructure going to be vendor-specific in the longer term? So, for example, will your infrastructure be housed in AWS indefinitely? So if the organisation states that yes, our infrastructure is going to be on AWS for the next ten years, So in such cases, the option of choosing a different infrastructure as a code tool can be of advantage. So for example, in AWS, they have a dedicated infrastructure as a code tool called AWS cloud formation that is available. And in fact, cloud formation is also great. Let me quickly show you some of the nice features of cloud formation. So one of the great things that I like about cloud formation is that you can quickly go ahead and design a sample template via the GUI. So let's quickly launch it. I'll show you. So this is basically the designer. Now, depending upon the service that you want to create, what you can do is just select it from the source type and drag and drop it. Let me show you. So within EC2, let's go ahead and create a new EC2 instance. So in order to do that, all you have to do is drag and drop it, and automatically, you see, the infrastructure code has been generated here. So this is great because you can easily drag and drop things, and automatically the code is ready for you. So this is one great feature that I really like about cloud formation. So that is what the first point is all about. Again, it is not necessary that an organisation that is completely on AWS and will be on AWS for the next ten years choose cloud formation. There are a lot of other factors that are also important. In fact, in one of the organisations that I was working with, we had more than 100 database accounts, and we did not use cloud formation. We were completely based on TerraForm. So let's look into the second pointer here, which states that are you planning to have a multicloud, which is a hybrid cloud-based infrastructure? Because this is a very common pattern nowadays, many organizations have AWS plus Azure or AWS plus Google, AWS plus Digital Ocean, and so on. So are you planning to have a hybrid cloud-based architecture? Third, how well does your infrastructure of code-based tools integrate with the configuration management tool? This is a very important question. And fourth is the overall price and the support of a specific tool. So depending upon that, you can choose the appropriate ISEF tool. Now, let me show you. TerraForm works pretty well in all of these. So let's quickly look into it. The first important point, though, is that TerraForm supports multiple platforms. It has hundreds of providers. So if you are in AWS, if you are in Azure, if you're in Google Cloud, or if you are in Digital Ocean, TerraForm supports all of them. And this is the great advantage of TerraForm over cloud formation. So cloud formation is a specific tool for AWS. TerraForm works on multiple platforms, so it is not tied to a single platform. Now, in fact, let me quickly show you this from the documentation. So if you look into the support that TerraForm provides, they have multiple providers. So you have AWS support, you have Alibaba Cloud, you have Akamai, you have Google Cloud Platform, you even have tools like Pager Duty and Grafana, and if you go a bit down, you have support for Kubernetes, you have support for Signal Effects, and so on. So not only does TerraForm support cloud providers like AWS, but it also supports other tools like Kubernetes, Grafana, US Health, and others. All right? So I hope you understood the first point, and primarily because of the first point, it really makes Terraform an amazing tool to work with. A second important benefit of TerraForm is its simple configuration language and faster learning curve. It is much easier to learn TerraForm than other languages. Now, I'll show you an example. So, we had a few interns who were in our organization, and within just two weeks, they learned TerraForm from scratch and started writing good TerraForm code for deploying the infrastructure. So it is quite simple, and you'll really love it in the long term. The third benefit is its easy integration with configuration management tools like Ansible. The fourth is that it is easily extensible with the help of plugins. So you can go ahead and create your own plugins if there are certain things that you see that are not supported or if there are certain things that you want to develop specific to your organization. And fifth, it is completely free, so you can go ahead and try it out.

3. Installing Terraform - MacOS and Linux Users

Hey everyone and welcome back. Now in the earlier video, we looked at the high-level steps for the TerraForm installation. We also investigated how we could accomplish it in terms of Windows. Now in today's video, we'll look at the installation step for both Mac and Linux. Now, similar to Windows, the overall installation is very simple. For Mac and Linux, there are only two steps that are required. The first one is to download the TerraForm binary file, and the second is to move it to the right path, and that's about it. So let's quickly explore it. So currently we are within the Download Terraform page over here, and this thing will be exploring both Linux and Mac. So apparently, there is a bird that is singing in the background. It's a great time to record the videos. So, first and foremost, let's look at the Linux steps. So the same step applies for Mac as well. So for Linux, what you have to do is download a binary file. So let's go ahead and let me copy the link address over here. Now, in case if you are running Linux, all you can dois you can click on 64 bit or in case format you can just click on 64 bit and the binary will get downloaded. Now, I have a Linux terminal that is available. So let me go ahead and fetch this specific binary with the help of the Wget command. So now we have our zip file, which was downloaded. Now, since I am connected via the CLI, I do not have the GUI available that can unzip the file. So I'll be using the CLI-specific command. Now, in the case of a Mac or if you're reusing Linux via GUI, you already have tools that can extract the contents of a zip file. Now here, you see that you have a TerraForm binary that is available. So if you do a Terraform, you'll see it works as expected. So this is the first step in downloading the TerraForm file. The next step is to move it along the right path. Now, if you quickly do an echo on the path over here Now the same applies for Mac. You will see that there are multiple paths that are available. So you can use one of the path. So user local bin is one of the paths here. Now all we have to do is move TerraForm to the user's local bin, and that's it. Your entire configuration is done. So even if I move to a different directory here and do a TerraForm, you see, it works perfectly well. Now, apart from the steps that we discussed in today's video, there are alternate ways in which you can quickly configure the TerraForm. So within the documentation of TerraForm, if you look into the installation of TerraForm for Max, it is very simple. All you can do is run the Brienstall TerraForm, and your entire TerraForm installation and the associated configurations like Path will be set. You no longer have to run two commands; all you have to do is run one command, and that's about it. So this is one important part to remember. The thing that we explored today was the manual installation, where we go ahead, we download the TerraForm, we look into the appropriate path, and then we move our TerraForm into the appropriate directory. That is part of the output that we see on the path. Now, one more thing to keep in mind: if you do a Brie install of TerraForm, especially if you're using a Mac, keep in mind that you might not get the most recent version of TerraForm; instead, you might get an older version. This is the primary reason we did not investigate automated installation methods such as Brew install for Windows. Also, you have Choko installed. This is something that we did not explore. We directly explored the manual installation for both the Mac and Windows so that we could get the latest TerraForm binary that is available. So that's the high-level overview of today's video. I hope this video has been informative for you, and I look forward to seeing the next video.

4. Choosing Right IDE for Terraform IAC development

Hey everyone, and welcome back to the Kplash course. So, now that you have Terraform installed, you will almost certainly be going for practicals. As a result, you'll be writing a lot of code related to infrastructure structure development during the practical. Now, during that part, having a good text editor is very important. So generally, if you're using Windows, maybe you can run something like Notepad. So this is a sample TerraForm code. And if you want to edit this, you can edit it in Notepad. So if you are running Linux, you can make use of Vim or Nano. This is quite okay, but this is not that great. It will not give you a very good experience. Especially when writing complex telephone codes. So instead, you can download this editor called Atom. This is an amazing editor—a really wonderful editor—which I really love. And I use it for all of my production TerraForm-related configurations. So when you click on Download, this is quite a big file. So this is a file of size 141 MB. So in my case, I have already downloaded it. So if I do an item, I have already downloaded it so that we can save our time. So let me open up the executable. So this is where the Atom installation takes place. So this takes a little time, sometimes five to ten minutes. The installation part will take place. Now, one of the interesting things about Atom's editor is its plugins. Language Hype and TerraForm are two of Atomeditor's plugins. So this is an amazing plugin. So if you are writing TerraForm code, you should be installing this plugin within the Atom editor. And we're looking into how we can do that once our installation is finished. So let's just wait for a moment for the installation to complete it great. So the installation is completed. So this is what item editing really looks like. So one thing that we have already discussed is its plugin functionality. Now, Atom really has a lot of plugins. One thing we're interested in here is the Hyperterraform language. Because this is where we are going to have our video. So in order to do that, go to Install a Package and click on Open Installer. Now there are a lot of packages available, depending on the requirements. I'll select the language "Hyphen TerraFormPackage," and let's search that. So this is the language Terraform makes available. Now, there are a lot of TerraForm related plugins which are available. We'll be using the first one, and we'll click on first one, and wSo the plugin is installed successfully. So now what we can do is, if you remember, we had created a folder called "Kplashera Form." So what I'll do is add that project folder to my Item Editor. So I'll choose the KP Labshave and TerraForm folder. And you see, this is the folder, and within that folder you have the one TF file. So let me make things much more clean. So if I open this example TF, this is the TerraForm code that is present over here. So that's how you configure item editor for the Windows environment. Now, same goes for because itemeditor actually cross operating system support. It does support other OS as well, and the installation is very similar. So one thing I would like to share is that once you have the item editor now, we have already discussed that TerraForm has a lot of providers. So if I quickly look up a TerraForm provider, it actually has more than 75 providers. So definitely, for our labs, we will not be able to work with each and every provider. As a first step, we'll work primarily with the AWS provider, and we'll investigate various TerraForm functionality with the AWS provider. So in the upcoming lecture, we look into how we can set up the AWS environment. If you already have an AWS environment that is set up and running, you don't really have to go through the lecture. You can skip directly over it. But for those who are new or who might be setting up for the first time, you can go through the upcoming lecture on setting up the AWS labs. And I'll see you at the upcoming lectures. Thanks for watching.

5. Setting up AWS account

Hey everyone and welcome back. Now before we start with our interesting practicals on AWS, one of the first things that is required is that we have to set up our own lab. And in setting up our own lab, the primary step is to create a new AWS account. Now one of the very common questions that generally comes up is: "Do we have to pay for the AWS account that we create and the resources that we create in our AWS account?" And the answer is no, it does not. AWS comes with a free tier of benefits that allows customers to go ahead and use various services within limits. And if you're within the limit, you do not really have to pay for it. So consider it more like a trial account for one year that you can make use of. So let's go ahead and quickly explore that post, which will be looking into how we can create our own AWS account. So currently I'm on the AWS Free Tier page. Let's go a bit down, and one thing that you will see is that it is there for twelve months. So this is one important part to remember. The second thing is that this free tier offers certain benefits based on services. So for example, if you are using the EC2 service, the AWS free tier supports 750 hours per month. So maybe if you run a server 24/7 for one month, it will be covered as part of the free tier. And also note that when you hover over this, it gives you the exact details, like 750 hours per month for LinuxRed or SLDs' T2 micro or T3 microbase instance. So for example, let's say that you have created a new EC2 instance of Windows. Now, Windows is not really supported in this free tier, so immediately you'll be charged for that. So this is one important part that you need to know. So, depending upon the services, there are certain limitations. For S3, they offer five GB of standard storage. If you go above five GB, then you'll have to pay. So this is something similar, and you'll see that there are a lot of services that are supported by the free tier account, and that is really great. Now, for most of the services that we'll be using throughout the course, they'll fall under the free tier. So there's not much to worry about. Now within Google, when you type "create a new AWS account," you'll basically get linked to go ahead and do that. Let's go ahead and open up the link. So it takes us to the free tier. At a later stage, it might take you to a different page, but the primary image we have to look at is how an account is created. So let's click on "Create a Free Account" here. Now within your account, you'll have to specify the email address and the account name. Now one important part to note: make sure that you enter the email address that you use regularly. I have seen people using disposable email. This is like a big no. So since you will be attaching a debit card or a credit card to your AWS account, it is very important to use a personal email that you use regularly. So let's go ahead and add an email address. Let's add a password and the AWS account name. You can give it any name; I'll just call it "Testing," and let's click on "Continue." All right, so it is asking us for verification. Let's quickly do that. Now the next important part is that you have to select personal or business over.All the services that will be available are the same. So let's go ahead and select Personal. Now the next part, and the important part, is the full name, phone number, country, and, basically, it asks you for the address. So let me go ahead and fill in mine, and you can do it for your account as well. Now I am in Dubai for one of our projects, so I'll be using the country of the United Arab Emirates as my address. Let's fill it in. Once you have filled in the details, you can just accept the terms and conditions. Let's continue to the next step. And on the next page, you'll have to basically specify the debit and credit card information once, then you can click on "Verify" and "Continue." Now again, one important part, as also mentioned here, is that although you're using the free tier, you will not be charged, but they'll have a temporary hold on one USB, so let's go ahead and click on Verify and Continue. And the next important part is that you have to confirm your identity, so you'll have to specify the country or region code. Let me go ahead and use the UAE here, and basically they'll send an SMS, so let's go ahead and click on it. All right, so let's look into the verification code here, and yes, I have received a verification code. If you can see it, I'm not sure if you can see it. So this is the SMS where the verification code has come, so let me go ahead and use that, and let's click on Continue. And in the next step, you'll have to choose a support plan. Make sure you choose the basic one here, and you can click on "Complete Sign Up. Perfect. So our account has now been created. Now, from the email address that you had entered, you'll receive an email basically stating welcome to Amazon Web Services, and it also states that for the next twelve months, you'll have free access to the core AWS Services. Now whenever you want to log into the AWS account, you have to open up the AWS Management Console. Now, since we have already created the account recently, it is giving us the link. Otherwise, at a later stage, if you want to open up the management console, you can AWS Management Console" within Google and you should basically see a page similar to that. When conducting a Google search, always verify the URLs specifically. So your AWS Amazon.com appears to be working properly. Let's go ahead and sign into the console. And there are two options within this. root user and their respective users will be logging in with the root user. So just specify the email address that you have used for creating the account. Let's do it next. Let's complete the verification and specify the password that you created during the sign-up process. And great! We are logged into our AWS account.

Hide