Getting Started with AWS Devops.pdf

© 1998-2020 NetCom Learning www.netcomlearning.com info@netcomlearning.com 1-888-563-8266
|
|
|
|
Master Class – Getting
started with AWS DevOps
NetCom Learning
Brian Wu
© Interested in training? Contact us! | www.netcomlearning.com | (888) 563-8266 | aws@netcomlearning.com
1998-2022 NetCom Learning

|
|
|
|
AGENDA
Introduction to DevOps
Understand the implementation of DevOps culture and techniques in the AWS Cloud
Basic understanding of Infrastructure Automation
Explore AWS CloudFormation template and its structure, parameters, stacks, updates, importing resources,
and drift detection
Q&A session with the speaker

|
|
Introduction to DevOps
DevOps is a combination of cultural philosophies, practices, and tools that combine software
development with information technology operations. These practices enable companies to deliver
new application features and improved services to customers at a higher velocity.
Dev Ops
Test
Security

|
|
Amazon development transformation
In the beginning
Monolithic
Does everything

|
|
Monolithic challenges
• Single, large platform
• Long development cycles
• Complexity with scaling
• Failures affect entire architecture (monolith model)
• Refactoring to fix failures or bugs (increased deployment cycle)
5

|
|
Completely
independent
Comparison of monolithic & microservice architectures
APIs
APIs
Monolith
Does everything
Microservice
Does one thing

|
|
Understand the implementation of
DevOps culture and techniques in the
AWS Cloud

|
|
Factors driving the DevOps transformation
Organizational mindset alignment, engineering enablement, and builder
empowerment
Practices
and
patterns
Tools (and
automation)
Cultural
philosophy

|
|
DevOps culture
DevOps is about removing the barriers
With DevOps, teams work together to optimize both the productivity of developers and the
reliability of operations
People over process over tools

|
|
Two-pizza teams for increased collaboration
Dev team Ops team
Pizza Team 1
Pizza Team 2
Pizza Team 3

|
|
Small-team properties
Full ownership
Full accountability
Adherence to “DevOps” principles
Focused innovation

|
|
DevOps practices and techniques (Process)
Continuous
integration
Continuous
delivery
Monitoring and
logging
Microservices
Infrastructure
as code
Communication and
collaboration

|
|
Monoliths before microservices
Monitor
Release
Test
Build
Developers
Delivery Pipelines
Services

|
|
Optimizing for DevOps: microservices
Microservices are an architectural and organizational approach that is composed of small
independent services optimized for DevOps.
• Small
• Decoupled
• Owned by self-contained teams

|
|
Microservice architecture
• Minimal function services
• Deployed separately, but interact together
• Fit for purpose-based data options
• Organized around business capabilities
• State is externalized
• Choice of technology for each microservice
• Serverless and automated operational model
• Characteristics • Microservice architecture
Completely
independent
APIs
APIs
Process notes

|
|
Microservices
Developers Services
Monitor
Release
Test
Build
Delivery Pipelines
Monitor
Release
Test
Build
Monitor
Release
Test
Build
Monitor
Release
Test
Build
Monitor
Release
Test
Build
Monitor
Release
Test
Build

|
|
Example of Monolithic vs Microservice

|
|
Code Build Test Provision Deploy Monitor
CI/CD
Continuous integration
Continuous delivery
Continuous deployment

|
|
• Integration tests
with other
systems
• Load testing
• UI tests
• Penetration
testing
Release processes major phases
• Check-in source
code
• Peer review new
code
• Compile code
• Unit tests
• Style checkers
• Code metrics
• Create container
images
• Deployment to
production
environments
Source Build Test Deploy Monitor
• Monitor in
production to
quickly detect
unusual activity or
errors

|
|
CI/CD Tools
Prometheus
Amazon CloudWatch
Container Insights

|
|
Explore AWS Cloud Formation Template
& its Structure, Parameters, Stacks,
Updates, Importing Resources, & Drift
Detection

|
|
Why Automate?
• Reduce human error (avoiding deviations from configuration standards)
• Faster releases and response times
• Creation of multiple identical environment
• Versioned and managed just like application source code Maintain
• Compliance with policy as code
• Can be tracked, validated, and reconfigured (all through automation)

|
|
Basic understanding of Infrastructure Automation
Infrastructure as code
AWS Cloud
VPC
User
Amazon Route 53
Amazon CloudFront Internet
gateway
Public subnet
Availability Zone
Public subnet
App Load
Balancer
Auto Scaling
…
Resources:
VPC: …
InternetGateway: …
PublicSubnet: …
AppServer: …
DNSRecord: …
WebServerGroup: …
Type: “AWS::
AutoScaling…”
…

|
|
Structure of AWS CloudFormation template: YAML format
YAML
---
AWSTemplateFormatVersion: "2020-01-09"
Description:
String
Parameters:
set of parameters
Mappings:
set of mappings
Conditions:
set of conditions
Transform:
set of transforms
Resources:
set of resources
Outputs:
set of outputs
Format Version (opt): Corresponding AWS CloudFormation
template version
Description (opt): A text string
Parameters (opt): Inputs into template
Mappings (opt): Static variables; key-value pairs
Conditions (opt): Controls for if and when certain
resources are created or updated
Transform (opt): Specifies the version of AWS SAM to use
Resources (req): AWS assets to create
Outputs (opt): Values of custom resources created by
template (URLs, username, etc.)

|
|
AWS CloudFormation stacks
• Create your stacks through the console or AWS CLI
• Common parameters include:
• ClientRequestToken
• OnFailure
• TimeoutInMinutes
• Import existing resources

|
|
Stacks: Layered architecture approach
A layered architecture
Front end web interface, admin interface, analytics dashboard
Backend
customers, campaigns, products,
marketing collateral, analytics
Shared
databases, common monitoring or alarms,
subnets, security groups
Base
network
VPCs, internet gateways, VPNs,
NAT gateways
Identity IAM users, groups, roles

|
|
Update your stack by using Change sets
• Use change sets to:
• Preview proposed changes to a stack
• Determine how they affect your running resources
• Verify whether your changes delete or replace any
critical resources
• AWS CloudFormation makes changes to your stack only
when you decide to run the change set

|
|
Run
change set
Using change sets to update a stack
Original stack Change set Change set
AWS
CloudFormation
updates stack
Create change
set
View
change set
Create additional
change sets

|
|
Detecting drifts on stacks
Status of the stack's actual configuration compared to its expected configuration:
• DRIFTED
• NOT_CHECKED
• IN_SYNC

|
|
Monitor and logging
• Observe and track large sets of data from applications and infrastructure
• Operational visibility and insight
• Collect metrics
• Improve performance

Getting Started with AWS Devops.pdf

Recommended

Recommended

More Related Content

Similar to Getting Started with AWS Devops.pdf

Similar to Getting Started with AWS Devops.pdf (20)

More from Tuan Yang

More from Tuan Yang (17)

Recently uploaded

Recently uploaded (20)

Getting Started with AWS Devops.pdf