Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

Best Practices for Application Management in AWS

1.
APPLICATION MANAGEMENT IN
AWS
BEST PRACTICES

2.
INTRODUCTION
BRAD ADAIR
▸ Director of Infrastructure Services at IQ Innovations, LLC.
▸ Have been working in IT for 12+ years in various areas ranging
from desktop support to system administration to management.
▸ AWS Certiﬁed Solutions Architect
▸ Have been working heavily in AWS for about 2.5 years.
▸ Email: brad@adair.tech
▸ Twitter: @bpadair

3.
INTRODUCTION
APPLICATION MANAGEMENT IN AWS
▸ Public cloud in general, and AWS in particular are
changing the way that we think about infrastructure and
the way we manage the applications that run on that
infrastructure.
▸ Less permanence, more ephemeral and temporary.
▸ More purpose built and dedicated resources.
▸ Less “make it ﬁt”

10.
SECURITY
HAVEN’T WE BEEN DOING THIS FOREVER?
▸ Yes, and a lot of existing knowledge still applies.
▸ You still need smart policies.
▸ Your application still needs to protect against common attack vectors.
▸ Some things to change with a move to AWS, however.
▸ You are no longer responsible for physical security.
▸ You are no longer responsible for hypervisor security or patching.
▸ Depending on the service you may not even be responsible for OS
security and patching.

13.
RELIABILITY
EASIER AND HARDER SIMULTANEOUSLY
▸ A lot of the work for reliability is done for you.
▸ It is a mistake to put too much trust in this.
▸ The tools are there, but you have to choose to use them.
▸ Architecture matters.

14.
RELIABILITY
CRITICAL THINGS TO UNDERSTAND
▸ Availability zones
▸ Regions
▸ Difference between AZs and Regions and how they should
be used together.
▸ Replication of different services.
▸ Availability SLAs.
▸ S3 storage classes/levels

15.
RELIABILITY
CASE STUDY: CONFIDENTIAL COMPANY
▸ Pre-AWS:
▸ Only in one data center due to cost.
▸ Had clients nationwide, but all resources were
centralized.
▸ Had to have 4 or more hours of downtime for
deployments
▸ Many SPoF including storage and network. Redundancy
was attempted but not done well.

16.
RELIABILITY
CASE STUDY: CONFIDENTIAL COMPANY
▸ AWS Setup:
▸ Multiple VPCs spread across multiple regions to provide redundancy
and be close to customers.
▸ VPC peering to reduce single points of failure.
▸ MAZ RDS instances for databases.
▸ EFS for network based storage.
▸ Replication of databases across regions.
▸ IaC templates for VPCs to allow for rapid reproduction in other regions.

17.
SCALABILITY
WHAT IS SCALABILITY
▸ Scalability is about more than simply adding more
resources in response to increased demand.
▸ Scalability needs to include both scaling up and scaling
down.
▸ Goal is to maximize user experience while minimizing cost.