Amazon Web Services in Action, Second Edition

Recommendations

Info

14 CHAPTER 1 What is Amazon Web Services?UserInternetDynamicStaticLoad balancerDNSCDNVirtual machinesDatabaseObjectstorageBilled by hours of usageBilled by trafficBilled by storage usageFigure 1.8AWS bills services on minutes or hours of usage, by traffic, or by used storage.the web servers, and the database. Other services, like the amount of storage neededfor static files, didn’t change, so the price stayed the same.Table 1.1How an AWS bill changes if the number of web shop visitors increasesService January usage February usage February charge IncreaseVisits to website 100,000 500,000CDN25 M requests + 25 GBtraffic125 M requests + 125 GBtraffic$135.63 USD $107.50 USDStatic files 50 GB used storage 50 GB used storage $1.15 USD $0.00 USDLoad balancer 748 hours + 50 GB traffic 748 hours + 250 GB traffic $20.70 USD $1.60 USDWeb servers 1 virtual machine = 748hours4 virtual machines = 2,992hours$200.46 USD $150.35 USDDatabase (748hours)Small virtual machine + 20GB storageLarge virtual machine + 20GB storage$133.20 USD $105.47 USDDNS 2 M requests 10 M requests $4.00 USD $3.20 USDTotal cost $495.14 USD $368.12 USD
Comparing alternatives15With AWS, you can achieve a linear relationship between traffic and costs. And otheropportunities await you with this pricing model.1.4.3 Pay-per-use opportunitiesThe AWS pay-per-use pricing model creates new opportunities. For example, the barrierfor starting a new project is lowered, as you no longer need to invest in infrastructureup front. You can start virtual machines on demand and only pay per second ofusage, and you can stop using those virtual machines whenever you like and no longerhave to pay for them. You don’t need to make an upfront commitment regarding howmuch storage you’ll use.Another example: a big server costs exactly as much as two smaller ones with thesame capacity. Thus you can divide your systems into smaller parts, because the cost isthe same. This makes fault tolerance affordable not only for big companies but alsofor smaller budgets.1.5 Comparing alternativesAWS isn’t the only cloud computing provider. Microsoft Azure and Google Cloud Platform(GCP) are major players as well.The three major cloud providers share a lot in common. They all have:• A worldwide infrastructure that provides computing, networking, and storagecapabilities.• An IaaS offering that provides virtual machines on-demand: Amazon EC2,Azure Virtual Machines, Google Compute Engine.• Highly distributed storage systems able to scale storage and I/O capacity withoutlimits: Amazon S3, Azure Blob storage, Google Cloud Storage.• A pay-as-you-go pricing model.But what are the differences between the cloud providers?AWS is the market leader in cloud computing, offering an extensive product portfolio.Even if AWS has expanded into the enterprise sector during recent years, it is stillobvious that AWS started with services to solve internet-scale problems. Overall, AWS isbuilding great services based on innovative, mostly open source, technologies. AWSoffers complicated but rock-solid ways to restrict access to your cloud infrastructure.Microsoft Azure provides Microsoft’s technology stack in the cloud, recentlyexpanding into web-centric and open source technologies as well. It seems like Microsoftis putting a lot of effort into catching up with Amazon’s market share in cloudcomputing.GCP is focused on developers looking to build sophisticated distributed systems.Google combines their worldwide infrastructure to offer scalable and fault-tolerantservices (such as Google Cloud Load Balancing). The GCP seems more focused oncloud-native applications than on migrating your locally hosted applications to thecloud, in our opinion.
Page 1 and 2: SECOND EDITIONMichael WittigAndreas
Page 3: Praise for the First EditionFantast
Page 6 and 7: For online information and ordering
Page 8 and 9: viBRIEF CONTENTS10 ■ Sharing data
Page 10 and 11: viiiCONTENTS21.4 How much does it c
Page 12 and 13: xCONTENTS67Securing your system: IA
Page 14 and 15: xiiCONTENTS111210.3 Mounting the EF
Page 16 and 17: xivCONTENTS13.7 Removing data 37313
Page 19 and 20: forewordThroughout the late 1990s a
Page 21 and 22: prefaceWhen we started our career a
Page 23 and 24: acknowledgmentsWriting a book is ti
Page 25 and 26: about this bookOur book guides you
Page 27 and 28: ABOUT THIS BOOKxxvChapter 13 introd
Page 29 and 30: about the authorsAndreas Wittig and
Page 31 and 32: Part 1Getting startedHave you watch
Page 33 and 34: What isAmazon Web Services?This cha
Page 35 and 36: What can you do with AWS?5Clouds ar
Page 37 and 38: What can you do with AWS?7John is h
Page 39 and 40: What can you do with AWS?9So far, A
Page 41 and 42: How you can benefit from using AWS1
Page 43: How much does it cost?13pricing for
Page 47 and 48: Exploring AWS services17Administrat
Page 49 and 50: Interacting with AWS191.7 Interacti
Page 51 and 52: Interacting with AWS21Figure 1.14Th
Page 53 and 54: Creating an AWS account23USING AN O
Page 55 and 56: Creating an AWS account25Figure 1.1
Page 57 and 58: Creating an AWS account27Figure 1.2
Page 59 and 60: Creating an AWS account29The most i
Page 61 and 62: Creating an AWS account31CBFigure 1
Page 63 and 64: Create a billing alarm to keep trac
Page 65 and 66: Summary35Check your inbox and click
Page 67 and 68: Creating your infrastructure37Aroun
Page 69 and 70: Creating your infrastructure393 Cre
Page 71 and 72: Creating your infrastructure41Step
Page 73 and 74: Creating your infrastructure43Reloa
Page 75 and 76: Exploring your infrastructure45Choo
Page 77 and 78: Exploring your infrastructure47Sele
Page 79 and 80: Exploring your infrastructure492.2.
Page 81 and 82: Exploring your infrastructure51EFS
Page 83 and 84: How much does it cost?53Unfortunate
Page 85: Summary55Summary• Creating a blog
Page 88 and 89: Chapter 3 covers working with virtu
Page 90 and 91: 60 CHAPTER 3 Using virtual machines
Page 92 and 93: 62 CHAPTER 3 Using virtual machines
Page 94 and 95:
64 CHAPTER 3 Using virtual machines
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
100 CHAPTER 3 Using virtual machine
Page 132 and 133:
Programmingyour infrastructure:The
Page 134 and 135:
104 CHAPTER 4 Programming your infr
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
136 CHAPTER 5 Automating deployment
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
166 CHAPTER 6 Securing your system:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
200 CHAPTER 7 Automating operationa
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Overview of data storage servicesSe
Page 266 and 267:
236 CHAPTER 8 Storing your objects:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Storing data on hard drives:EBS and
Page 290 and 291:
260 CHAPTER 9 Storing data on hard
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Sharing data volumesbetween machine
Page 306 and 307:
276 CHAPTER 10 Sharing data volumes
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
Page 322 and 323:
Page 324 and 325:
Using a relationaldatabase service:
Page 326 and 327:
296 CHAPTER 11 Using a relational d
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
322 CHAPTER 12 Caching data in memo
Page 354 and 355:
Page 356 and 357:
Page 358 and 359:
Page 360 and 361:
Page 362 and 363:
Page 364 and 365:
Page 366 and 367:
Page 368 and 369:
Page 370 and 371:
Page 372 and 373:
Page 374 and 375:
Page 376 and 377:
Page 378 and 379:
Page 380 and 381:
350 CHAPTER 13 Programming for the
Page 382 and 383:
Page 384 and 385:
Page 386 and 387:
Page 388 and 389:
Page 390 and 391:
Page 392 and 393:
Page 394 and 395:
Page 396 and 397:
Page 398 and 399:
Page 400 and 401:
Page 402 and 403:
Page 404 and 405:
Page 406 and 407:
Page 408 and 409:
Page 411 and 412:
Part 4Architecting on AWSWerner Vog
Page 413 and 414:
Achieving highavailability: availab
Page 415 and 416:
Recovering from EC2 instance failur
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Recovering from a data center outag
Page 425 and 426:
Page 427 and 428:
Page 429 and 430:
Page 431 and 432:
Page 433 and 434:
Page 435 and 436:
Page 437 and 438:
Page 439 and 440:
Page 441 and 442:
Analyzing disaster-recovery require
Page 443 and 444:
Decoupling your infrastructure:Elas
Page 445 and 446:
Synchronous decoupling with load ba
Page 447 and 448:
Page 449 and 450:
Page 451 and 452:
Asynchronous decoupling with messag
Page 453 and 454:
Page 455 and 456:
Page 457 and 458:
Page 459 and 460:
Page 461 and 462:
Designingfor fault toleranceThis ch
Page 463 and 464:
433The following services are fault
Page 465 and 466:
Using redundant EC2 instances to in
Page 467 and 468:
Considerations for making your code
Page 469 and 470:
Considerations for making your code
Page 471 and 472:
Building a fault-tolerant web appli
Page 473 and 474:
Page 475 and 476:
Page 477 and 478:
Page 479 and 480:
Page 481 and 482:
Page 483 and 484:
Page 485 and 486:
Page 487 and 488:
Page 489 and 490:
Page 491 and 492:
Page 493 and 494:
Scaling up and down:auto-scaling an
Page 495 and 496:
Managing a dynamic EC2 instance poo
Page 497 and 498:
Managing a dynamic EC2 instance poo
Page 499 and 500:
Using metrics or schedules to trigg
Page 501 and 502:
Page 503 and 504:
Page 505 and 506:
Decouple your dynamic EC2 instance
Page 507 and 508:
Page 509 and 510:
Page 511 and 512:
Page 513 and 514:
Page 515:
Summary485• To distribute load am
Page 518 and 519:
488INDEXautomating operational task
Page 520 and 521:
490INDEXDdata centerslocations 4, 1
Page 522 and 523:
492INDEXGlacier serviceadding lifec
Page 524 and 525:
494INDEXobject stores (continued)mo
Page 526 and 527:
496INDEXstatelessness 465static web
Page 528 and 529:
RELATED MANNING TITLESLearn Amazon
Page 530:
CLOUD/AWSAmazon Web Services IN ACT
show all

Amazon Web Services in Action, Second Edition

Create successful ePaper yourself

Delete template?

Save as template?