Читать книгу AWS For Admins For Dummies - Mueller John Paul - Страница 5

Part 1
Getting Started with AWS
Chapter 2
Obtaining Free Amazon Services

Оглавление

IN THIS CHAPTER

❯❯ Considering the free service offerings

❯❯ Ensuring that you have the right hardware

❯❯ Ensuring that you have the right networking setup

❯❯ Getting your free account

❯❯ Using your free account for the first time

One of the purposes of this book is to help you discover a lot more about Amazon Web Services (AWS) through experimentation. Of course, Amazon would just love to have you buy these services, but a free option, which is the focus of this chapter, is also available. The issue is one of figuring out just what Amazon means by free. This chapter’s first section clears up the questions you might have about what free means, because some services are always free and others are free for a limited time. In addition, you must consider the limits of free. If you use some of these services too much, you end up paying for them. Therefore, you need to know the rules in order to get the services free.

The next two sections of the chapter consider hardware and network requirements. Note that Amazon likes you to have both Linux and Windows knowledge when you take your certification exams (see the “Understanding the AWS Certifications” section of Chapter 1), and such knowledge is helpful even if you don’t want to obtain a certification. This chapter doesn’t delve too deeply into platform specifics, but it does help you understand what you need to do to get a basic setup running.

Now that you have some idea of what you’re getting and what you need in order to get it, it’s time to get your free account. The rest of the book assumes that you have a free account to use. Going through the various procedures is the best way to build an understanding of AWS. Yes, some people can get a feeling for how things work just by reading, but doing things hands on really is better.

The chapter ends by having you perform a simple task using AWS, just to get a feel for how it works. Don’t worry: You really can’t mess up the account. If you do make an unfortunate choice, starting over is easy enough. Nothing will get damaged by the exercise in this chapter – it’s totally safe. Make sure you have some fun doing it! After all, cloud computing should be an easier and more efficient way to perform administrative tasks, and you’ll find that it truly is as the book progresses.

Discovering the Limits of Free Services

Amazon does provide the means for using many of its cloud services for free. In fact, you can see some of these services at http://aws.amazon.com/free/. However, as you look through the list of services, you see that the some expire, others don’t. In addition, some have limits and others don’t. Those that do have limits don’t have the same limits, so you need to watch usage carefully. It’s really quite confusing. The following sections help clarify what Amazon actually means by saying some services are free.

Expiring services versus nonexpiring services

Many of the AWS services you obtain through the free tier have expiration dates, and you need to consider this limitation when evaluating and possibly using the service to perform useful work. Figure 2-1 shows an example of a service with an expiration date. Notice that you must begin paying for the service 12 months after you begin using it.


FIGURE 2-1: Some services have an expiration date when you must begin paying for them.


In some cases, the product itself doesn’t have an expiration date, but the service on which it runs does. For example, when viewing the terms for using the free software, the software itself is indeed free. However, in order to run the software, you must have the required service, which does come with an expiration date (see Figure 2-2).


FIGURE 2-2: Software may be free, but the service on which it runs might not be.


You also have access to some products that are both free and have no expiration date. These nonexpiring offers still have limitations, but you don’t have to worry about using those products within the limits for however long you want (or until Amazon changes the terms). Figure 2-3 shows examples of these kinds of services.


FIGURE 2-3: A few services don’t come with expiration dates.


Knowing the terms under which you use a service is essential. The free period for services with an expiration date goes all too quickly, and you may suddenly find yourself paying for something that you thought remained free for a longer time frame. Given that Amazon can change the terms of usage at any time, you need to keep checking the terms of service for the services that you use. A service that lacks an expiration date today may have an expiration date tomorrow.

ABOUT THE GRAPHICS IN THE BOOK

The material in this book works on several different platforms, including Windows, Linux, and Mac OS X. However, presenting screenshots of every platform you can use with AWS isn’t practical because the book would end up filled with pictures rather than content. For this reason, the screenshots you see in the book are from a Windows 7 system using the Firefox browser, where appropriate. Depending on the operating system, browser, and other software you use, you may not see precisely the same screenshots on your system. In looking at the graphics, you should compare content rather than precise appearance. Any differences in appearance are normal, and you don’t need to worry about them.

Considering the usage limits

Look again at Figures 2-1 through 2-3. Note that all these products have some sort of usage limit attached to them – even the free software – because of the software’s reliance on an underlying service. (Some software relies on more than one service, so you must also consider this need.) For example, you can use Amazon Elastic Compute Cloud (EC2) for 750 hours per month as either a Linux or Windows setup. A 31-day month contains 744 hours, so you really don’t have much leeway if you want to use the EC2 service continuously.

The description then provides you with an example of usage. Amazon bases the usage terms on instances. Consequently, you have access to a single Linux or single Windows setup. If you wanted to work with both Linux and Windows, you would need two instances and could use them for only 15 days and 15 hours each month. In short, you need to exercise care in how you set up and configure the services to ensure that you don’t exceed the usage limits.

The free, nonexpiring services also have limits. For example, when working with Amazon DynamoDB, you have access to 25GB of storage, 25 units of read capacity, and 25 units of write capacity. Theoretically, this is enough capacity to handle 200 million requests each month. However, whether you can actually use all that capacity depends on the size of the requests and how you interact with the service. You could easily run out of storage capacity long before you run out of request capacity when working with larger files, such as graphics. Again, you need to watch all the limits carefully or you could find yourself paying for a service that you thought was free.

Considering the Hardware Requirements

No matter how many services AWS offers, you still require some amount of hardware to use the services. The amount of hardware you require when working with services in the cloud is minimal because the AWS hardware does all the heavy lifting. When working with services locally, you need additional hardware because AWS is no longer doing the heavy lifting for you. Therefore, you should consider different hardware requirements depending on where you host the AWS service. The following sections help you obtain additional information about working with both cloud and local services.

Hosting the services in the cloud

Hidden in the AWS documentation is all sorts of useful information about various services. For example, AWS Storage Gateway (http://aws.amazon.com/documentation/storage-gateway/) will connect an on-premises software appliance (an application combined with just enough operating system capability to run on hardware or on a virtual machine) with cloud-based storage. In other words, you use the gateway to connect your application to the data storage it requires. It might seem as if running the gateway in the cloud would be a good idea because you wouldn’t need to invest in additional hardware. However, when you look at the requirements shown in Figure 2-4, you see that using an EC2 instance allows you to run only gateway-cached volumes and gateway-VTLs (you can’t run gateway-stored volumes). You don’t need to know what these terms mean, but you do need to understand that the cloud present limits that you must consider during any planning stage.


FIGURE 2-4: Using cloud-based services can come with limitations.


After you make certain that you can run your intended configuration, you can begin to consider the advantages and disadvantages of working in the cloud. For example, when hosting the service in the cloud, you get automatic scaling as needed, and Amazon performs many of the administrative tasks for you. Chapter 1 discusses many of the advantages of the cloud for you. However, for a realistic perspective, you must offset these advantages with disadvantages, such as:

❯❯ Potential for lower application speed

❯❯ Need to maintain a reliable Internet connection

❯❯ Loss of flexibility

❯❯ Vendors going out of business

Even though basic hardware needs become less expensive, you do need to consider additional expenses in the form of redundancies. Most organizations find that the hardware costs of moving to the cloud are substantially less than maintaining a full IT department, which is why they make the move. However, you must make the move with the understanding that you have other matters to consider when you do.

Hosting the services locally

When hosting services locally, you need to provide all the required infrastructure, which can get expensive. AWS does provide guidance on the minimum requirements for hosting a service locally. For example, Figure 2-5 shows the requirements for the AWS Storage Gateway.


FIGURE 2-5: Make sure that you can actually host the service locally.


A good rule of thumb when hosting services locally is to view any vendor-supplied requirements as minimums. If you don’t plan to load the service heavily, these minimums usually work. However, when you click the Optimizing Gateway Performance link, the first suggestion you see is adding resources to your gateway, as shown in Figure 2-6. Planning for too much capacity is better than for not enough, but getting the configuration as close as possible to what you need will always help financially.

FIGURE 2-6: Plan ahead for sufficient resources.


Not all the services will work locally, but you may be surprised to find that many do. The issue is one of defining precisely how you plan to use a given service and the trade-offs that you’re willing to make. For example, when hosting a service locally, you may find it hard to provide the same level of connectivity that you could provide to third parties when hosting the same service in the cloud.

Considering the Network Requirements

To use the AWS services, you need a network connection. In some cases, you need more than one. You not only need an Internet connection for the AWS user interface, but the services may require dedicated connections as well and these connections can become part of your business network. Because of this close relationship, creating the network configuration carefully is essential. Otherwise, you may find that the AWS network connection conflicts with the configuration used for your business (a problem that occurs more often than you might think).


Конец ознакомительного фрагмента. Купить книгу
AWS For Admins For Dummies

Подняться наверх