Understanding Core AWS Services

18. Auto Scaling

Hey everyone, and welcome back to the Knowledge Portal video series. In the previous lecture, we have already spoken about scalability and the types of scalability that can be performed, which are major horizontal as well as vertical. All of that was more of a theory at this point. Today we will be understanding scalability as far as a practical point of view is concerned. So let's go ahead and understand how we can design a scalable system in an environment. Now, just to revise, scalability is the ability of a system to change in size depending upon its needs. Now, if there is a huge amount of traffic,the server should scale up, and if there is a small amount of traffic, the server should scale down. So this is a very simple example of what scalability is. Remember the rubber band example that we discussed? Now, whenever you design your infrastructure, it should be designed in such a way that it supports scalability depending upon the traffic patterns. So this is a very basic graph that you can see. Now this graph is basically divided in terms of traffic patterns as far as night and daytime are concerned. So during the daytime, you see the traffic patterns are quite high. That means the website is receiving a good amount of traffic during the daytime. But during the night, the traffic is quite reduced. I would say it is less than 30% when compared to daytime traffic. Now, in order to handle this traffic,let's assume you have five servers running. Now the five servers are quite capable of handling traffic patterns during the day, and you are spending a reasonable amount of money on using those five servers. However, since during the night time, traffic is quite low, and since your five servers are running twenty-four seven, you are actually overutilizing your resources when the traffic is less. So this is not quite an ideal architectural design. So the ideal architecture should be that when your traffic is less, you should have a smaller number of servers and when your traffic is more, you should have a larger number of servers. And that is what ideal architecture should be. And that not only helps you from a cost perspective, but it will also help you in terms of traffic spike times. This is where the amazing feature of auto scaling comes in. So auto scaling is one of AWS's features, and it allows us to scale up and down the EC, two instances based on the condition defined by the system administrator or solutions architect. So let's understand this with a use case. Mediumcorp is an e-commerce organisation in India and it is hosted completely on AWS. Now, in the past six months, the AWS bills have skyrocketed, and the CEO has asked you to reconsider the design of your infrastructure. Not only should it support the operation, but it should do it in a cost-effective way. The second important point is that, since it is an e-commerce company targeting Indian customers, the traffic pattern varies drastically during the day and night. So this is a very simple use case similar to what we have discussed in this graph. Now, what really is happening is that the AWS bills have really skyrocketed. One thing that is seen from the graph is that during the daytime the traffic is quite huge, but during the night the traffic is quite less. So now what you can do as a solutions architect is a question and we can explore the auto scaling service. So let's see how we can achieve this. It can now be accomplished depending on the average load of the instance. This is one of the criteria of the auto-scaling group. So let's assume you have an abase instance of two servers. So at any given time during the day as well as during the night, you will have two servers which will run all the time 24/7.If the CPU utilisation is directly related to the traffic, and the CPU utilisation exceeds 70%, the condition occurs twice more. So if you see over here, I have two servers and two servers are capable of handling the average load, which is around 25%. But suddenly there is a huge spike, which reaches 75%. The server will start to timeout if you just have two servers. And thus, whenever you create a condition that the CPU utilisation reaches more than 70%, you add two more servers. So you will have four servers for that specific amount of time. And after that, when a traffic spike goes down, you see the traffic spike go down. So you have one more condition over here which says that if average CPU utilisation is less than 25%, then remove the two instances that were created during the high load period. And these are the policies which you can configure as part of the auto scaling configuration is concerned.So let me just demonstrate in the EC two management console. So if you see over here, I have auto-scaling groups which are configured. Let me show you the settings which are over here. At a minimum, you have one, which means the minimum server should be running at any moment of time. Be it a day or be it a night, it should be one. The maximum instance is three. As a result, the maximum number of instances it can scale horizontally is three. And if you look into the scaling policies, I have two scaling policies depending upon the cloud watch alarms. So if I just go to cloud watch, this shows you that I have two alarms over here. One is high CPU utilisation and the second is low CPU utilization. So what does high CPU utilisation say? You see, if the CPU utilisation is greater than the threshold, which is 70%, or if the CPU utilisation is greater than equal to 70%, then this alarm will trigger off. And there is one more alarm which says "if a CPU utilisation is less than equal to 25%, then this alarm will be triggered." So now we can use this alarm in conjunction with the auto scaling policies. So I have two policies over here, which increase group size and decrease group size. Now in the increased group size, you see in the action column it says add two instances when CPU utilisation is greater than 70%. And there is one more policy called "decreased group size", which basically says remove two instances. Remove two instances when CPU utilisation has decreased to 25%. So this is a very simple policy. When your traffic load increases,your server will increase horizontally. And when your traffic load decreases,your server will shrink down horizontally. Perfect. So before we close this session, let me show you one interesting thing. Now if you see over here, the minimum instance is one. That means one instance will be present all the time. Now if you see over here, I have one instance which is running. Let me go over here and it will direct me to the instance. Now let me terminate the instance. Let's see what happens when I terminate this specific instance. Now, as the auto scaling says that there should be a minimum of one instance all the time and we have actually terminated that one instance, let it shut down. So meanwhile, I'll just open the auto scaling as well. I'll open up the auto-scaling group. And now, if you see the health status has become unhealthy for the specific instance, So what exactly will happen is that once the autoscaling detects that the instance is in an unhealthy state, it will actually start one more instance. So let's just confirm and wait for a minute or two for the instance to terminate. Okay? So now the instance is terminated and what autoscaling should do is verify what the minimum number of instances that should be running at a given amount of time. Since the minimum number of instances is one and since the status of that instance is unhealthy, autoscaling will automatically create one more instance as part of the auto scaling group policies. So let's wait a minute and we'll see. The auto-scaling group will launch one more instance. And now, if you will see, the health status has become healthy and there is one more instance which has been created. So the lifecycle is still pending. Now if I just verify it in the easy console, you will see one more instance has automatically started. And this is the beauty of auto scaling. So this is a demo which I wanted to show you for this lecture. In the upcoming lecture, we'll actually go into much more detail related to how we can configure auto scaling and what the best practises are as far as auto scaling is concerned. So I hope you got the basic concept related to what auto-scaling linguists are auto scaling linguist.And I hope to see you at the next lecture.

19. Introduction to S3

Hey everyone, and welcome back to the Knowledge Portal video series. And today we will be speaking about the AWS simple storage service. Now, before we go ahead and understand more about AWS's three, let's take a simple use case scenario that will help us understand why AWS's three is required. Now, there is a simple usecase related to storage capacity. So let's look into what a use case is. So, Large Corp is a payment organisation and it has more than 10 servers. Being a payment organization, it is also PCI DSS compliant. And one of the rules of PCIDSS compliance is that the logs related to the payment service should be retained for a minimum of one year. So that is one of the things that organisations must follow. Now, it has been noted that the logs related to the payment servers are around 200GB per day. So every day, around 200GB of logs are generated. And the use case is how to achieve this use case pertaining to the storage capacity in a cost-effective manner. So basically, the use case is that every day there is 200 GP of log which is generated. So what is the best solution that you can design in a very cost-effective manner? Now, since the lock being generated needs to be stored for a minimum of one year, if you calculate 200 GPinto 365, it comes to around 70 terabytes of storage. Now in this case, you know that there is a requirement of 70 terabytes of storage. So how will you go ahead with a solution? So, let's look into the older approach to what organisations generally used to do. So, the first and foremost approach is to buy a huge storage device. We have already calculated that 70 terabytes of storage will be required. So buying a huge storage device is a first-and-foremost task. The next task is to ensure higher availability. So let's assume you have a 170 terabyte storage device. What happens if the storage device fails? So this is a risk. So what you need to do is you need to at least have two storage devices of 70 terabytes each. And that is huge. So that is the second requirement. The third requirement is that, because you have such large storage devices, you may need to hire storage administrators to maintain them. And the fourth point is to ensure that proper security is given to the storage devices. Otherwise, the data, the logs, which might contain sensitive data, if they get compromised, then there will be a lot of client information that will be compromised, which again creates a lot of legal trouble for the organization. So this is one of the older approaches. When we talk about buying huge storage devices,let me actually show you if you go to DellEMC, so EMC is one of the world's best, you can say world leaders in terms of data storage. So if you see over here, they have various devices, storage devices like the 33 terabyte starterconfiguration and if you look into the pricing,the starting price is 42 $0. Now, this is 33 terabytes. So you have pricing for various types of configurations that are available. Now, we already discussed that if an organisation is under 200GB per day, then in a higher availabilityconfiguration of two storage devices, you need 140 terabytes. Now, just assume that you are getting a 140 terabyte storage device. Assume you'll spend $150,000 as a minimum just buying a storage device. So this is something which organisations have to go through in the older approach. So let's talk about a newer approach. In the newer approach, you just have to do two things. First you create an AWS account, and second, you upload all the log files to AWS, and that's it. Now, One of the benefits of the newer approach is that you don't really have to invest the higher amount in buying storage devices. maintaining higher availability. On top of that, that is really a big pain and on top of that.You have to hire storage administrators and you also have to ensure security for the storage service that you have brought, which is really a big pain for most of the organization.And I still remember that I have a lot of friends who are storage administrators, and because of the ease of use of the newer approach, a lot of organisations are now migrating from older approaches to newer approaches. So, most of my storage friends are pursuing the AWS Solutions architect associate level certification because they are concerned that the older approach will be phased out in most larger organisations in the coming years. When I talk about uploading log files toAWS s three again, I don't really want to be platform specific because if you go to theindustry, you need to look into the wider range. So three is one of the good options. But I'm very sure that you might have heard about various other websites like Dropbox or Media Fire. Among these, Media Fire is one of my favorites. So if I just open up the Media Fireover here, this is one of my favourite websites where I keep all of my backups. It has been there for many years. I have been using it for the past, I believe, five years. So if you just go down, let me look into the plans which are available for Media Fire. I am using the professional one. If you look, it is just $3.75 per month and you are getting 1 storage unit. That is really amazing. So, for this price, you get a year of storage as well as a variety of other benefits. Now, when we talk about the business plan over here,you're paying $40 per month, which is nothing for a business organisation and it comes with a lot of additional features, like you have up to 100 terabytes of storage space which is available. So I would say it is a very cheap and very reliable hosting provider which is available on the market. Mediafire is definitely very cheap when you compare this with AWS sthree, definitely media fire is very cheap.When you look into the pricing of 1 GB of storage in MediaFire and S3, then MediaFire wins by a great margin. However, features-wise, if we compare, MediaFire is not as good as S Three. S Three wins there by a big margin. So let's get started with AWS three. So let's look into the first slide and let's get started with AWS S Three. So, in simple terms, AWS S3 is object-based storage which is designed to store and retrieve any amount of data anywhere. So if you want to store 200 terabytes of storage, you can store it. You don't really have to worry about buying the storage devices etc. So those portions are taken care of by AWS. The second important point is that it is designed for 99.9 x 9% durability. So you have 99.9 times 9% and 99.99% availability. Now, we will be talking in great detail about this, so just keep it in the parking lot for now. We will be discussing it in the upcoming sections. Now, the thing that makes AWS S Threeso powerful, which we will discuss below, are the features that come preloaded with Amazon AWS S Three. So when we talk about features, there are great features which are needed for maybe a small startup to an enterprise-based organization. So you have various features like versioning, encryption, logging, you have cross-region replication,you also have static website hosting requestto pay and so many of them. So we will be looking into all of these features as time goes by. But these features bundled with the storage are something that makes AWS S3 a truly powerful service. So, let's get started. There are two important terms that you need to remember as far as AWS x Three is concerned, which are buckets and objects. So, in a very simple term, a bucket is an afolder in terms of windows, and an object is files. So this is a simple screenshot of AWS s. three. So you see in the AWS logs that you'll find, this is a bucket, it also has a bucket symbol, and this is an object. So this is the image file. So this is an object. So this is a bucket and an object. So this is the basic of AWS's three. So let's come out of the PowerPoint presentation and let's start with a practical session. So I'm in my AWS console. I'll go to Services and I'll click on three. So you see, I already have a bucket which is already created. If I click here, you see this is the bucket that we were speaking about and this is the object. An object is basically a file that you can consider. Now, in order to create a bucket, or you can say, in order to create a folder, it is very simple. You just click on "create bucket." You can give the bucket a name. Remember, the bucket name that you give is Share. The bucket namespace is shared across all the users in the AWS account. So if I just try to create a bucket with a name test, it might probably fade. Let's just check. You see, the bucket name already exists. Now this bucket's namespace is shared among all the users. Any AWS user could have created a bucket name test. So you won't be able to create it. So you need to have a unique name. So what I will do is let me put Kplabs in. I hope this bucket name is no one's taken it. The second thing that you have to remember is the region. You can select the region in which the bucket needs to be created. So we'll use Origan as a region and I'll click on Create. I believe the Kplabs have also been thrown in the bucket. Let me just go back to the beginning. Now I'm having trouble coming up with a good bucket name. So let me do one thing. I'll put Kplabs internal for the time being, and let's try and click on Create. If any of you have taken the Kplabs in bucketname, please delete it so that I can use it for my demo purposes anyway. So I'm kidding. You can use it if you want. So we have the Kplabs internal bucket created. Now if I'll just go here, this is an empty bucket. So if you can see, I can create a folder over here and I can even upload objects. As you can see, you uploaded an object. So let me just click on Upload and I'll click on Add File and I'll add a finance TXT file. So this is a text file that contains some finance-related information. I'll just click on "open" and I'll click on "Upload." So the upload will be started. You can see the operations over here. You see one success and you will find various information. If you just click on this particular file,you'll find various instructions related to the size,the storage class, whether the object is encrypted or not, as well as the modification date. So if I just click on Open over here,I think I have to charge my battery anyways. If I just click on Open over here, you can open the text file from the browser itself. So it's not necessary that you download it. You can open it from the browser too. So this is the basic of AWS's three. Remember, the bucket name that you create has to be unique, and you can only create buckets in a specific region. Inside the bucket, you can create a folder. So if I just create a folder, say folder one, I'll click on Save. The folder does not have to be unique. It is just the bucket name that has to be unique. So this is the folder and this is the object, or a file. So this is the basic idea of AWS.

20. S3 - Public Access Settings

Hey everyone, and welcome back. So AWS recently released a feature that makes objects inside a bucket public by default. In fact, this is a very useful feature because in the past, a developer or someone unfamiliar with assist would make some critical or sensitive files public, allowing an attacker or malicious user access. So this feature actually works quite well. So I'll just show you how this feature really works. Let me create a bucket. I'll say kplabs testing. I'll say Hyphen 2019 I'll go ahead and I'll create a bucket. So once the bucket is created, if I quickly search for it, this is the bucket. Now basically, I have administrator access to this AWS account. So let me just quickly upload some sample files within this bucket. All right. So now you see, the file has been successfully uploaded. Now, if you tried to make this public, let's try it out. When I do make it public, let me try it, and you see, it gave an error. It gave an error saying that it failed. The reason why it has failed is because at the bucket level, there is a policy that you need to change so that the files within the bucket can be made public. So let's look into how we can do that. So let me click on "permission." So within the permission, you have a tab called "Public Access Settings." So this is what you need to edit. Now you see, there is an option which says "block new public ACL and upload public objects." So let me just deselect this and remove public access granted through public ACL. Let me also remove this and let me also deselect the third option here. And I'll go ahead and I'll do a save. It will ask me to do the confirmation. I'll go ahead and I'll do the confirmation here. Perfect. So now the public access settings have been updated successfully. So once this is done, you can try to make the bucket public. great. So now you see, it has been successful. So now this object within the bucket has been made public successfully. So this is how you can go ahead and make an object within a bucket public. So I hope this video has been informative for you and I look forward to seeing you in the next video.

21. S3 Storage Classes

Hey everyone, and welcome back to the Knowledge Portal video series. Today we will talk about S three storage classes. So let's go ahead and understand this. Now, S Three primarily offers four major types of storage access. The first is General Purpose, which is also called Standard S three.The second is called infrequent access,which is also called standard IA. IA stands for Infrequent Access. RRS, or reduced redundancy storage, is the third option. And the fourth is Archive, which is also called Glacier. Now, the question is, why is there a need for so many storage facilities? Why can't we just upload the objects and just relax? And the answer to this is pricing. Now, each of these storage classes differs in terms of availability as well as durability. As a result, general purpose or standard S three have greater availability than infrequent access. So, since this standard S3 has higher availability,the pricing of this particular storage class is much higher when compared to Infrequent Access. And similarly, if you are planning to upload your objects, let's assume you want to upload your objects, but you don't really care about very high availability, then maybe you can choose Standard IA and have lower pricing. So, again, it depends upon what your requirements are in terms of durability and availability. And, depending on your needs, you can select either of them, and thus your pricing will vary. So let's talk about AWS S Threestandard, which is the first one. Now, the S Three standards offer high durability, availability, and performance for objects that you store. Now, when you talk about the durability aspect, it is 99 times nine times nine of durability. So, in total, it is eleven nine. So the total is eleven-nine of durability. When you talk about availability, it is 99.99% of availability over a given year. Now, we have already looked into the caveat of one filegetting lost in 10,000 years, or in 10 million years. So again, we know the caveat on this, but this is the example which you will find in various sources. So just understand the caveat aspect as well. So these are the AWS s three standard.Due to this good amount of durability, availability, and performance, the three standards are one of the highest among all the four classes as far as pricing is concerned. Let's go to the second storage class, which is the Standard IA, also called the Standard Infrequent Access. This type of storage class is basically used for data that needs a good amount of durability. But when you talk about availability,it can be compromised a bit. So, while the durability of StandardIA is very similar to that of Standard S3, the availability is 99.90% compared to 99.99% for Standard S3. Due to this, the pricing is much lower than that of Standard S Three. Talking about the third aspect, which is RRS, So basically, RRS also stands for Reduced Redundancy Storage, which enables customers to significantly reduce their costs by storing noncritical, reproducible data. It is very important to understand that reproducible data has lower levels of redundancy than S3 standard storage. So basically, if you want to store your data which is reproducible and you do not care a lot about data getting lost, then RRS is for you. So if you look into the durability aspect, it is 99.99% durable. Again, this is very nice and there is 99.99% availability. So this is specific to RRS. And if you just have a standard comparison between each of these classes, this is the comparison of each of them. Now, there is one more important storage class called Glacier. And Glacier is generally used for long-term backups. So you can consider the glacier. If you put the file inside a glacier, don't expect any availability. If you want to retrieve the file for download, it might take a few hours for the file to be available for you to be downloaded.So, that is Glacier. So it is meant for archiving and storing long-term backups. The second point, again, is very important that it may take several hours for objects to be restored. Now, the durability is very similar to that of standard S Three.However, the availability aspect, if you see it, is not part of this because it might take a few hours for the file to be retrieved. Again, because of this availability, the price is significantly lower than that of a standard S Three. Now, the standard use cases for Glacier are for storing the application locks or your security-related locks that are older than one year. So you can actually store them at a very lower cost. Now, let me go to the AWS S3 console, and if you see over here, the storage class is standard. Now, if I just select a specific file, let me just select a screenshot for the time being. I'll click next. Now, if you see over here, the storageclass is standard, standard IA, and RRS. Now, you will not find Glacier here because you cannot directly upload files to the Glacier-based storage. This is very important to remember. You have to upload to one of them. And once you upload to the standard storage class,then you can move your file to Glacier. So, this is the basic of the storage classes. I hope you got the basic concept of AWSS's three storage classes and why are they beneficial?

22. New S3 Storage Class - Intelligent-Tiering

Hey everyone, and welcome back. Now in today's video we will be discussing the new AWS S three storage classes. AWS has recently updated its offering of storage classes for S Three.So as of now, there are multiple storage classes that are available. Now, if I go to the S Three console, this is a test S Three bucket that I have. Let me click on upload and I'll add a file. So let's click on next. I'll do it again next again.And now under storage classes, you will see that there are multiple storage classes which are currently available and it is important for us to keep updated and have a clear understanding of each of the storage classes. So let's get started. Now, in terms of the new storageclasses which S3 has released, So earlier S three had the standard, the standard infrequent access, the glacier and the RRS, which is reduced redundancy. Now S Three has launched three more, which is the Intelligent Tiering. You have one zone IA and one glacier deep archive. So let's go ahead and understand that in today's video we'll be focusing on the intelligent tiering post which we'll discuss the other ones as well. Now, the S3 intelligent tiering is primarily designed to optimise cost by automatically moving the data to the most cost-effective S3 tier. Now, when you talk about the price difference, because here we were discussing that there were multiple S-three storage classes. So in terms of the older storage classes which SThree used to offer, one among them was the standard one, and the second was the standard Infrequent Access. Now, when you talk about the price difference between both of them, let's say that you are storing one TB of data in standard S3,then the cost would be $22.88. Now, for the same one TB of data, storing standard infrequent access costs twelve point fifty dollars. So the price has been reduced by more than half. So you see, there is a huge price difference between the general purpose standard S3 and Infrequent Access. Now for the enterprises that have been storing petabytes of data, they have hundreds of terabytes of data being stored in S Three.As a result, such a small price difference can save those businesses a significant amount of money. Now the problem is that, let's say you have a backup script which takes a backup of your data and it stores it to standard history. Now you also need to segregate the data. Let's say that you know that 50% of the data is not going to be accessed quite frequently. So you can send 50%of the data to infrequent access. But that is a manual part and it requires a lot of effort there. So it would be great if there was a solution which could automatically move the infrequent data to the infrequent access tier, and that is what the S3 intelligent tiering is all about. Now, the S3 intelligent tiering works by storing data in one of the two access tiers. One is the frequent access tier, which is costly. The second is the infrequent access tier,which is much cheaper. So let's say that you have a frequent access tier here and you have an infrequent access tier. The frequent access tier is costly. Infrequent access steering is much, much cheaper. Now, what you want is, by default, the data to be stored in the general purpose, which you can call the Frequent Access Tier. So all the data would be stored here. So now you want a solution that can observe that data over a period of time and can make a decision. So it is now known that there is a certain amount of data which is never accessed. So now it should automatically move that data to the infrequent Access Tier. So that intelligent system is what is being offered here. So let's take an example. So let's say that you have data in the Frequent Access Tier. Someone has taken a backup of the system and the backup is stored in this frequent access tier. So now with the S Three IntelligentTiering, what you have is something like a smart automation system. So this is something that I have named it.AWS might have a different naming convention, but this architecture diagram will help you understand this in a much quicker way. So you have a smart intelligent system here. Now, it connects to both the frequent access tier and the infrequent access tier, and it monitors all of the data in both the frequent access tier and the infrequent access tier. So now, over the period of time, it is realised that there is a certain amount of data in the frequent access tier which is never accessed at all. So here you see it detected that there was one block of data which was never accessed and it moved that block to the infrequent access tier. Again, it detected that there was a certain blob of data which was never accessed and it moved to the infrequent access tier. So now what is happening is the organisation is saving a good amount of money because there is this automation system which is monitoring all of the data here and it is segregating it into the frequent and infrequent access tiers. So I hope you got the overview of what the S-Third Intelligent Tiering is all about. Now, just to revise, the Amazon S-Three monitors the access patterns of the objects in S-Tiering and moves the ones that have not been accessed for 30 consecutive days to the infrequent access Tier. So any data blob here which is not accessed at all for the next 30 consecutive days will automatically move to the infrequent access tier. Now, if an object in an infrequent access tier is accessed, then the object is automatically moved back to the frequent access tier. So, this is quite simple to understand. Now, certain important pointers here: The first one is that this type of storage class is preferable for long-lived data. Because here, if you see it, for 30 consecutive days. And if you have data which is only stored for six or seven days, then there is no need for S3 intelligent hearing. So this is why this type of storage is preferred for long-lived data access patterns that are unknown or unpredictable. So you never know whether the data will be accessed or not be accessed. So the access pattern is unpredictable. Now, this S Three Intelligent Tiering, like other storage classes in S Three, is isconfigured at the object level. Now, to understand the pricing of S ThreeIntelligent Tiering, we already discussed that one TB of data in standard S Three is 22.88. One TB of data in twelve points of infrequent access The cost of 51 TB of data stored with standard Intelligent is $23. So there is a very minimal amount of additional cost that has been occurring.So you have 22.88 and you have $23. all right? So you have to compare the first one and the third one here. So, coming back to our S Three console, if you look into the Intelligent Tiering over here, you will see the minimum storage duration is 30 days. Now, this is important because if you are storing data for less than 30 days, then there is no need for Intelligent Tiering over here. all right? So now, since we have uploaded one object, you can select that this object should be associated with the Intelligent Tiering. So now, when you do the next,you see the storage class Intelligent Tiering. And you can go ahead and you can upload the object. So now, this specific object is monitored within the storage class, and as you can see, it is Intelligent Tiering. So this is monitored. And after 30 days, if the intelligent tiering detects that this specific object has not been accessed in 30 days, it will move to the Infrequent Access Tier. As a result, you will save a significant amount of money.

ExamSnap's Amazon AWS Certified Cloud Practitioner Practice Test Questions and Exam Dumps, study guide, and video training course are complicated in premium bundle. The Exam Updated are monitored by Industry Leading IT Trainers with over 15 years of experience, Amazon AWS Certified Cloud Practitioner Exam Dumps and Practice Test Questions cover all the Exam Objectives to make sure you pass your exam easily.