AWS for Developers For Dummies. Mueller John Paul
Читать онлайн книгу.
In addition, most of the tasks you perform with AWS require that you work in your browser.
This book is largely platform independent. However, none of the procedures are tested using small mobile devices, such as a smartphone (and some are almost guaranteed not to work on a small device). Differences in appearance do emerge when using a smaller device; a control that appears as a button on a larger device may appear as a link or other control on a smaller device. You need access to the sort of setup that a developer will use to create and configure online applications, which means a larger tablet, notebook, or, better yet, a full desktop system. The various people who worked on this book used desktop systems running the Windows, Linux, and Mac OS X platforms and using a number of common browsers.
Because this is a book about application development, you also need to have some understanding of the development process. Knowledge of Python would be nice, but it’s not absolutely necessary because of the way the examples work. You may still need to spend some time with a Python tutorial to understand everything that the examples provide. In addition, you need to know how to work at the command prompt or terminal window. Many of the examples require that you manually type commands rather than work with a GUI. In fact, a few of the examples simply won’t work with a GUI because the options are unavailable. (These examples are clearly marked in the book.)
Icons Used in This Book
As you read this book, you encounter icons in the margins that indicate material of special interest (or not, as the case may be!). Here’s what the icons mean:
Beyond the Book
This book isn’t the end of your AWS learning experience – it’s really just the beginning. I provide online content to make this book more flexible and better able to meet your needs. That way, as I receive email from you, I can address questions and tell you how updates to AWS or its associated add-ons affect book content. In fact, you gain access to these cool additions:
❯❯ Cheat sheet: You remember using crib notes in school to make a better mark on a test, don’t you? You do? Well, a cheat sheet is sort of like that. It provides you with some special notes about tasks that you can do with AWS that not every other person knows. To find the cheat sheet for this book, go to www.dummies.com and search for AWS For Developers For Dummies Cheat Sheet. On the page that appears, scroll down the page until your cursor turns the AWS For Developers For Dummies Cheat Sheet link blue; then click it. The cheat sheet contains really neat information such as figuring out which service you want to use.
❯❯ Updates: Sometimes changes happen. For example, I might not have seen an upcoming change when I looked into my crystal ball during the writing of this book. In the past, this possibility simply meant that the book became outdated and less useful, but you can now find updates to the book at www.dummies.com.
In addition to these updates, check out the blog posts with answers to reader questions and demonstrations of useful book-related techniques at http://blog.johnmuellerbooks.com/.
❯❯ Companion files: Hey! Who really wants to type all the code in the book manually? Most readers prefer to spend their time actually working with Python, performing tasks using AWS, and seeing the interesting things they can do, rather than typing. Fortunately for you, the examples used in the book are available for download, so all you need to do is read the book to learn AWS usage techniques. To get the source code, go to www.dummies.com and search AWS For Developers For Dummies. Scroll down to the graphic of the book cover and click it. Click the More About This Book box that appears and then the Download tab to find the files.
Where to Go from Here
It’s time to start your AWS adventure! If you’re completely new to AWS, you should start with Chapter 1 and progress through the book at a pace that allows you to absorb as much of the material as possible. Chapter 2 is especially important because it helps you understand what Amazon means by free-tier services. You should also read Chapter 3, even if you have experience with AWS, because it provides information about the services discussed in the book.
Readers who have some exposure to AWS must still work through the latter half of Chapter 2 because it shows how to obtain your developer key. After that, you can move directly to Chapter 4. You can always go back to earlier chapters as necessary when you have questions. However, you do need to understand how each technique works before moving to the next one. Every technique and procedure has important lessons for you, and you can miss vital content if you start skipping too much information.
Part 1
Discovering the AWS Development Environment
IN THIS PART …
Get started with Amazon Web Services (AWS).
Create a good AWS development environment.
Obtain your developer key.
Understand the AWS free tier.
Consider the security issues.
Chapter 1
Starting Your AWS Adventure
IN THIS CHAPTER
❯❯ Exploring the AWS cloud
❯❯ Considering Infrastructure as a Service (IaaS)
❯❯ Defining when, why, and how to use AWS
❯❯ Ensuring you have a supported platform
There was a time when business development meant creating software for a single machine or for a workgroup. The client-server architecture, with its emphasis on both local and centralized servers, came next. Developers eventually started creating applications for the Internet as well, enabling people to do things like work from home without losing contact with the organization’s database. Browser-based applications actually appear on most desktops today, and you might spend much of your nondevelopment time using one.
As development has moved onward and outward, the tools, techniques, and processes for development have changed as well. Today you deal with the cloud, where the server that holds your application doesn’t even reside on the premises. In many respects, everyone is a remote user today. Of course, organizations have a huge investment in existing hardware and software,