Amazon Web Services in Action, Third Edition Version 3

Amazon Web Services in Action, Third Edition MEAP V03
Copyright
Welcome
Brief contents
Chapter 1: What is Amazon Web Services?
	1.1 What is Amazon Web Services (AWS)?
	1.2 What can you do with AWS?
		1.2.1 Hosting a web shop
		1.2.2 Running a Java EE application in your private network
		1.2.3 Implementing a highly available system
		1.2.4 Profiting from low costs for batch processing infrastructure
	1.3 How you can benefit from using AWS
		1.3.1 Innovative and fast-growing platform
		1.3.2 Services solve common problems
		1.3.3 Enabling automation
		1.3.4 Flexible capacity (scalability)
		1.3.5 Built for failure (reliability)
		1.3.6 Reducing time to market
		1.3.7 Benefiting from economies of scale
		1.3.8 Global infrastructure
		1.3.9 Professional partner
	1.4 How much does it cost?
		1.4.1 Free Tier
		1.4.2 Billing example
		1.4.3 Pay-per-use opportunities
	1.5 Comparing alternatives
	1.6 Exploring AWS services
	1.7 Interacting with AWS
		1.7.1 Management Console
		1.7.2 Command-line interface
		1.7.3 SDKs
		1.7.4 Blueprints
	1.8 Creating an AWS account
		1.8.1 Signing up
		1.8.2 Signing In
	1.9 Create a budget alert to keep track of your AWS bill
	1.10 Summary
Chapter 2: A simple example: WordPress in fifteen minutes
	2.1 Creating your infrastructure
	2.2 Exploring your infrastructure
		2.2.1 Virtual machines
		2.2.2 Load balancer
		2.2.3 MySQL database
		2.2.4 Network filesystem
	2.3 How much does it cost?
	2.4 Deleting your infrastructure
	2.5 Summary
Chapter 14: Achieving high availability: Availability zones, auto-scaling, and CloudWatch
	14.1 Recovering from EC2 instance failure with CloudWatch
		14.1.1 How does a CloudWatch alarm recover an EC2 instance?
	14.2 Recovering from a data center outage with Auto Scaling Group
		14.2.1 Availability zones: groups of isolated data centers
		14.2.2 Recovering a failed virtual machine to another availability zone with the help of auto-scaling
		14.2.3 Pitfall: recovering network-attached storage
		14.2.4 Pitfall: network interface recovery
		14.2.5 Insights into availability zones
	14.3 Architecting for high availability
		14.3.1 RTO and RPO comparison for a single EC2 instance
		14.3.2 AWS services come with different high availability guarantees
	14.4 Summary
Chapter 15: Decoupling your infrastructure: Elastic load balancing and simple queue service
	15.1 Synchronous decoupling with load balancers
		15.1.1 Setting up a load balancer with virtual machines
	15.2 Asynchronous decoupling with message queues
		15.2.1 Turning a synchronous process into an asynchronous one
		15.2.2 Architecture of the URL2PNG application
		15.2.3 Setting up a message queue
		15.2.4 Producing messages programmatically
		15.2.5 Consuming messages programmatically
		15.2.6 Limitations of messaging with SQS
	15.3 Summary
Chapter 16: Designing for fault tolerance
	16.1 Using redundant EC2 instances to increase availability
		16.1.1 Redundancy can remove a single point of failure
		16.1.2 Redundancy requires decoupling
	16.2 Considerations for making your code fault-tolerant
		16.2.1 Let it crash, but also retry
		16.2.2 Idempotent retry makes fault tolerance possible
	16.3 Building a fault-tolerant web application: Imagery
		16.3.1 The idempotent state machine
		16.3.2 Implementing a fault-tolerant web service
		16.3.3 Implementing a fault-tolerant worker to consume SQS messages
		16.3.4 Deploying the application
	16.4 Summary
Chapter 17: Scaling up and down: auto-scaling and CloudWatch
	17.1 Managing a dynamic EC2 instance pool
	17.2 Using metrics or schedules to trigger scaling
		17.2.1 Scaling based on a schedule
		17.2.2 Scaling based on CloudWatch metrics
	17.3 Decouple your dynamic EC2 instance pool
		17.3.1 Scaling a dynamic EC2 instance pool synchronously decoupled by a load balancer
		17.3.2 Scaling a dynamic EC2 instances pool asynchronously decoupled by a queue
	17.4 Summary
Chapter 18: Building modern architectures for the cloud: ECS and Fargate
	18.1 Why should you consider containers instead of virtual machines?
	18.2 Comparing different options to run containers on AWS
	18.3 The ECS basics: cluster, service, task, and task definition
	18.4 AWS Fargate: running containers without managing a cluster of virtual machines
	18.5 Walking through a cloud-native architecture: ECS, Fargate, and S3
	18.6 Summary
Notes