In the second AWS Masterclass webinar of 2014 we cover the fundamentals of Amazon EC2 service, a service thjat

1. Masterclass
Elastic Compute Cloud
Ian Massingham – Technical Evangelist
@IanMmmm

2. A technical deep dive beyond the basics
Help educate you on how to get the best from AWS technologies
Show you how things work and how to get things done
Broaden your knowledge in ~45 mins
Masterclass

3. On-demand compute to run application workloads
Easy come easy go – disposable resource
We provide the infrastructure, you decide what you run
Amazon EC2

4. What is EC2?
Elastic capacity Flexible
Complete control
Reliable
Inexpensive
Secure

5. Securely
segregated
Shared
environment
Elastic capacity
Physical Interfaces
Customer 1
Hypervisor
Customer 2 Customer n
…
…
Virtual Interfaces
Firewall
Customer 1
Security
Groups
Customer 2
Security
Groups
Customer n
Security
Groups

6. Securely
segregated
Shared
environment
Elastic capacity
Physical Interfaces
Customer 1
Hypervisor
Customer 2 Customer n
…
…
Virtual Interfaces
Firewall
Customer 1
Security
Groups
Customer 2
Security
Groups
Customer n
Security
Groups

7. AMI
Amazon Machine
Image

8. AMI
Amazon Machine
Image
Instance
Running or
Stopped machine

9. AMI
Amazon Machine
Image
Instance
Running or
Stopped machine
VPC

10. AMI
Amazon Machine
Image
Instance
Running or
Stopped machine
VPC
Availability Zone
Region

11. AMI
Amazon Machine
Image
Instance
Running or
Stopped machine
VPC
Availability Zone Availability Zone
VPC
Region

12. AMI
Amazon Machine
Image
Instance
Running or
Stopped machine
VPC
Availability Zone Availability Zone
EBS EBS EBS
VPC
EBS EBS EBS
Region

13. AMI
Amazon Machine
Image
Instance
Running or
Stopped machine
VPC
Availability Zone Availability Zone
S3
EBS EBS EBS
VPC
EBS EBS EBS
EBS
Snapshots
S3 Buckets
Region

14. Instance

15. Instance Unit of scale
Unit of resilience
Unit of control

16. Instance Unit of scale
Unit of resilience
Unit of control
Your stack

17. Instance
Instance
Instance
Instance
Unit of scale
Unit of resilience
Unit of control
Scaleout

18. Instance
Instance
Instance
Instance
Unit of scale
Unit of resilience
Unit of control

19. Instance
Instance
Instance
Instance
Unit of scale
Unit of resilience
Unit of control

20. Instance
Instance
Instance
Unit of scale
Unit of resilience
Unit of control

21. Instance
Instance
Instance
Unit of scale
Unit of resilience
Unit of control
Instance

22. Instance types
Choose the right unit for your workload

23. EC2 Compute Units
Memory(GB)
0.5
1
2
4
8
16
32
64
128
256
1 2 4 8 16 32 64 128
General Purpose
Compute Optimized
GPU Instances
Memory Optimized
Storage Optimized
t1.micro

24. EC2 Compute Units
Memory(GB)
0.5
1
2
4
8
16
32
64
128
256
1 2 4 8 16 32 64 128
General Purpose
Compute Optimized
GPU Instances
Memory Optimized
Storage Optimized
t1.micro
t1.micro 613 MB
Up to 2 ECUs
(for short bursts)
m1.small 1.7 GB,
1 EC2 Compute Unit
1 virtual core
m1.medium 3.7 GB,
2 EC2 Compute Units
1 virtual core
m1.large 7.5 GB
4 EC2 Compute Units
2 virtual cores
m1.xlarge 15 GB
8 EC2 Compute Units
4 virtual cores
m3.medium 3.7 GB,
3 EC2 Compute Units
1 virtual core
m3.large 7.5 GB
6.5 EC2 Compute Units
2 virtual cores
m3.xlarge 15 GB
13 EC2 Compute Units
4 virtual cores
m3.2xlarge 30 GB
26 EC2 Compute Units
8 virtual cores

25. EC2 Compute Units
Memory(GB)
0.5
1
2
4
8
16
32
64
128
256
1 2 4 8 16 32 64 128
General Purpose
Compute Optimized
GPU Instances
Memory Optimized
Storage Optimized
t1.micro
m2.xlarge 17.1 GB
6.5 EC2 Compute Units
2 virtual cores
m2.2xlarge 34.2 GB
13 EC2 Compute Units
4 virtual cores
m2.4xlarge 68.4 GB
26 EC2 Compute Units
8 virtual cores
cr1.8xlarge 244 GB
88 EC2 Compute Units
32 virtual cores
c1.medium 1.7 GB
5 EC2 Compute Units
2 virtual cores
c3.large 3.75 GB
7 EC2 Compute Units
2 virtual cores
C3.xlarge 7.5 GB
14 EC2 Compute Units
4 virtual cores
c1.xlarge 7 GB
20 EC2 Compute Units
8 virtual cores
C3.2xlarge 15 GB
28 EC2 Compute Units
8 virtual cores
C3.4xlarge 30GB
55 EC2 Compute Units
16 virtual cores
C3.8xlarge 60GB
108 EC2 Compute Units
32 virtual cores
Cc2.8xlarge 60.5GB
88 EC2 Compute Units
32 virtual cores

26. + Storage Optimised
+ IO Optimised
+ GPU Backed
Find out more at : aws.amazon.com/ec2/instance-types

27. Start small
Easy to up-size

28. AMIs
Your machine images
AMIs you have created from
EC2 instances
Can be kept private or shared
with other accounts
Amazon maintained
Set of Linux and Windows
images
Kept up to date by Amazon in
each region
Community
maintained
Images published by other AWS
users
Managed and maintained by
Marketplace partners

29. WindowsLinux Enterprise Linux
Small instance from
$0.060 per hour
Small instance from
$0.091 per hour
AMIs
Small instance from
$0.120 per hour
Small instance from
$0.090 per hour
Find out more at : aws.amazon.com/ec2/pricing

30. Unix/Linux instances start at
$0.02/hour
Pay as you go for compute power
Low cost and flexibility
Pay only for what you use, no up-front
commitments or long-term contracts
Use Cases:
Applications with short term, spiky, or
unpredictable workloads;
Application development or testing
On-demand instances
Instance types

31. Unix/Linux instances start at
$0.02/hour
Pay as you go for compute power
Low cost and flexibility
Pay only for what you use, no up-front
commitments or long-term contracts
Use Cases:
Applications with short term, spiky, or
unpredictable workloads;
Application development or testing
On-demand instances
1- or 3-year terms
Pay low up-front fee, receive significant hourly
discount
Low Cost / Predictability
Helps ensure compute capacity is available
when needed
Use Cases:
Applications with steady state or predictable
usage
Applications that require reserved capacity,
including disaster recovery
Reserved instances
Instance types

32. Unix/Linux instances start at
$0.02/hour
Pay as you go for compute power
Low cost and flexibility
Pay only for what you use, no up-front
commitments or long-term contracts
Use Cases:
Applications with short term, spiky, or
unpredictable workloads;
Application development or testing
On-demand instances
1- or 3-year terms
Pay low up-front fee, receive significant hourly
discount
Low Cost / Predictability
Helps ensure compute capacity is available
when needed
Use Cases:
Applications with steady state or predictable
usage
Applications that require reserved capacity,
including disaster recovery
Reserved instances
> 80% utilization
Lower costs up to 58%
Use Cases: Databases, Large Scale HPC,
Always-on infrastructure, Baseline
Heavy utilization RIInstance types

33. Unix/Linux instances start at
$0.02/hour
Pay as you go for compute power
Low cost and flexibility
Pay only for what you use, no up-front
commitments or long-term contracts
Use Cases:
Applications with short term, spiky, or
unpredictable workloads;
Application development or testing
On-demand instances
1- or 3-year terms
Pay low up-front fee, receive significant hourly
discount
Low Cost / Predictability
Helps ensure compute capacity is available
when needed
Use Cases:
Applications with steady state or predictable
usage
Applications that require reserved capacity,
including disaster recovery
Reserved instances
> 80% utilization
Lower costs up to 58%
Use Cases: Databases, Large Scale HPC,
Always-on infrastructure, Baseline
Heavy utilization RI
41-79% utilization
Lower costs up to 49%
Use Cases: Web applications, many heavy
processing tasks, running much of the time
Medium utilization RI
Instance types

34. Unix/Linux instances start at
$0.02/hour
Pay as you go for compute power
Low cost and flexibility
Pay only for what you use, no up-front
commitments or long-term contracts
Use Cases:
Applications with short term, spiky, or
unpredictable workloads;
Application development or testing
On-demand instances
1- or 3-year terms
Pay low up-front fee, receive significant hourly
discount
Low Cost / Predictability
Helps ensure compute capacity is available
when needed
Use Cases:
Applications with steady state or predictable
usage
Applications that require reserved capacity,
including disaster recovery
Reserved instances
> 80% utilization
Lower costs up to 58%
Use Cases: Databases, Large Scale HPC,
Always-on infrastructure, Baseline
Heavy utilization RI
41-79% utilization
Lower costs up to 49%
Use Cases: Web applications, many heavy
processing tasks, running much of the time
Medium utilization RI
15-40% utilization
Lower costs up to 34%
Use Cases: Disaster Recovery, Weekly /
Monthly reporting, Elastic Map Reduce
Light utilization RI
Instance types

35. Unix/Linux instances start at
$0.02/hour
Pay as you go for compute power
Low cost and flexibility
Pay only for what you use, no up-front
commitments or long-term contracts
Use Cases:
Applications with short term, spiky, or
unpredictable workloads;
Application development or testing
On-demand instances
1- or 3-year terms
Pay low up-front fee, receive significant hourly
discount
Low Cost / Predictability
Helps ensure compute capacity is available
when needed
Use Cases:
Applications with steady state or predictable
usage
Applications that require reserved capacity,
including disaster recovery
Reserved instances
Bid on unused EC2 capacity
Spot Price based on supply/demand,
determined automatically
Cost / Large Scale, dynamic workload handling
Use Cases:
Applications with flexible start and end times
Applications only feasible at very low compute
prices
Spot instances
Instance types

36. Launch an instance
Commands, keypairs & security groups

38. Region
Instance size
AMI
Key pair
Security group

39. key pairs
secure access

40. Public Key
Inserted by Amazon into
each EC2 instance that you
launch
Private Key
Downloaded and stored by
you
EC2
Instance
Comms secured
with private key

41. x.509Keypairs Credentials
Used to authenticate
when accessing and
instance
Used to authenticate
against some APIs
Keypairs & Secrets
Access key and secret
key used to authenticate
against APIs

42. security groups
instance firewalling

43. Security
Group
instance
Port 80
(HTTP)
Port 22
(SSH)
Name
Description
Protocol
Port range
IP Address, range, or
another security group

44. PS C:> New-EC2Instances
-ImageId ami-269dbb63
-KeyName mykey
-SecurityGroupId sg-9cf9e5d9
-InstanceType t1.micro

45. aws ec2 run-instances
--image-id ami-54cf5c3d
--count 2
--security-groups webservers
--key-name mykey
--instance-type m1.small
$>

46. >>> import boto.ec2
>>> conn = boto.ec2.connect_to_region("us-east-1")
>>> conn.run_instances(
'ami-54cf5c3d',
key_name='mykey',
instance_type='m1.small',
security_groups=['webservers'])

47. Wait a minute
I want to use those tools too…

48. IAM Roles and EC2 tools
1. Start an EC2 Linux instance
2. Assign an IAM role at launch time:
3. Sets up all the tools you need & manages
API access credentials
1. Up and running with CLI tools in a couple
of minutes – just SSH on and use
2. Terminate/stop instance when you are
done
{
"Statement": [
{
"Effect": "Allow",
"NotAction": "iam:*",
"Resource": "*"
}
]
}

49. Now you have tools
Try this…

50. $> aws ec2 run-instances
--image-id ami-54cf5c3d
--count 2

51. $>
What about all this?
aws ec2 run-instances
--image-id ami-54cf5c3d
--count 2
--security-groups webservers
--key-name mykey
--instance-type m1.small

52. $> aws ec2 run-instances
--image-id ami-54cf5c3d
--count 2
--security-groups Default
--key-name NONE
--instance-type default (m1.small)
Defaults

53. $> aws ec2 run-instances
--image-id ami-54cf5c3d
--count 2
--security-groups Default
--key-name NONE
--instance-type default (m1.small)

54. Instances don’t need
keypairs
But how do you configure it if you can’t
log onto it?

55. Bake an AMI
Start an instance
Configure the instance
Create an AMI from your
instance
Start new ones from the
AMI
Bootstrapping

56. Bake an AMI Configure dynamically
Start an instance
Configure the instance
Create an AMI from your
instance
Start new ones from the
AMI
Bootstrapping
Launch an instance
Use metadata service
and cloud-init to perform
actions on instance
when it launches
vs

57. Bake an AMI Configure dynamically
Build your base images
and setup custom
initialisation scripts
Maintain your ‘golden’
base
Bootstrapping
Use bootstrapping to
pass custom information
in and perform post
launch tasks like pulling
code from SVN
+

58. Bake an AMI Configure dynamically
Bootstrapping
Time consuming
configuration (startup time)
Static configurations (less
change management)

59. Bake an AMI Configure dynamically
Bootstrapping
Continuous deployment
(latest code)
Environment specific (dev-
test-prod)

60. Goal is bring an instance up in a
useful state
The balance will vary depending upon your
application

61. Instance
request
User
data

62. Instance
request
User
data
Meta-data
service

63. Instance
request
User
data
Instance
Meta-data
service

64. #!/bin/sh
yum -y install httpd php mysql php-mysql
chkconfig httpd on
/etc/init.d/httpd start
Shell script in user-data will be executed on launch:

65. 65
Amazon Windows EC2Config Service executes user-data on
launch:
<script>dir > c:test.log</script>
<powershell>any command that you can run</powershell>
<powershell>
Read-S3Object -BucketName myS3Bucket
-Key myFolder/myFile.zip
-File c:destinationFile.zip
</powershell>
AWS Powershell Tools (use IAM roles as before…)

66. Why do this?
Automation
Less fingers, less mistakes
Availability
Drive higher
availability with self-
healing
Security
Instances locked
down by default
Flexible
Shell, Powershell,
CloudFormation,C
hef, Puppet,
OpsWorks Scale
Manage large scale
deployments and drive
autoscaling
Efficiency
Audit and manage
your estate with less
time & effort

67. Do
Some does and don’ts
Use IAM roles
Go keyless if you can
Strike a balance between
AMI and dynamic
bootstrapping

68. Do Don’t
Some does and don’ts
Use IAM roles
Go keyless if you can
Strike a balance between
AMI and dynamic
bootstrapping
Put your API access keys
into code (and then publish
to GIT) or bake into AMIs
(and share)


69. Block storage
Understanding instance storage vs EBS

70. Instance Storage
Local ‘on host’ disk
volumes
Data dependent upon
instance lifecycle

71. Elastic Block StorageInstance Storage VS
Local ‘on host’ disk
volumes
Data dependent upon
instance lifecycle
Network attached optimised
block storage
Data independent of instance
lifecycle

72. Instance Storage
Local ‘on host’ disk
volumes
Data dependent upon
instance lifecycle
Host 1
eph0 eph1 eph2 eph3
Instance Store
Instance A
Instance B
Instance C
Host 2
eph0 eph1 eph2 eph3
Instance Store
Instance D
Instance E
Instance F

73. Instance Storage
Local ‘on host’ disk
volumes
Data dependent upon
instance lifecycle
If an instance reboots (intentionally or
unintentionally), data in the instance store
persists
Data on instance store volumes is lost under the
following circumstances:
• Failure of an underlying drive
• Stopping an Amazon EBS-backed instance
• Terminating an instance

74. Options
Differing types of
instance storage
General purpose m3.medium 1 x 4 SSD*6
Compute optimized c1.xlarge 4 x 420
General purpose m3.large 1 x 32 SSD*6
Compute optimized cc2.8xlarge 4 x 840
General purpose m3.xlarge 2 x 40 SSD*6
GPU instances g2.2xlarge 1 x 60 SSD
General purpose m3.2xlarge 2 x 80 SSD*6
GPU instances cg1.4xlarge 2 x 840
General purpose m1.small 1 x 160 Memory optimized m2.xlarge 1 x 420
General purpose m1.medium 1 x 410 Memory optimized m2.2xlarge 1 x 850
General purpose m1.large 2 x 420 Memory optimized m2.4xlarge 2 x 840
General purpose m1.xlarge 4 x 420 Memory optimized cr1.8xlarge 2 x 120 SSD
Compute optimized c3.large 2 x 16 SSD Storage optimized i2.xlarge 1 x 800 SSD
Compute optimized c3.xlarge 2 x 40 SSD Storage optimized i2.2xlarge 2 x 800 SSD
Compute optimized c3.2xlarge 2 x 80 SSD Storage optimized i2.4xlarge 4 x 800 SSD
Compute optimized c3.4xlarge 2 x 160 SSD Storage optimized i2.8xlarge 8 x 800 SSD
Compute optimized c3.8xlarge 2 x 320 SSD Storage optimized hs1.8xlarge 24 x 2,048*3
Compute optimized c1.medium 1 x 350 Storage optimized hi1.4xlarge 2 x 1,024 SSD
Instance Storage

75. Elastic Block Storage
Network attached optimised
block storage
Data independent of instance
lifecycle
EBSEC2
Workspace
Hypervisor
S3
EBS
snapshot
Network
One or more ephemeral
(temporary) drives
(instance storage)
One or more EBS
(persistent) drives
EBS snapshots
(backup images)

76. Elastic Block Storage
Network attached optimised
block storage
Data independent of instance
lifecycle
EBSEC2
Hypervisor
S3
EBS
snapshot
Boot cycle

77. Elastic Block Storage
Network attached optimised
block storage
Data independent of instance
lifecycle
EBSEC2
Workspace
Hypervisor
S3
EBS
snapshot
Boot cycle

78. Elastic Block Storage
Network attached optimised
block storage
Data independent of instance
lifecycle
EBSEC2
Workspace
Hypervisor
S3
EBS
snapshot
Boot cycle

79. Elastic Block Storage
Network attached optimised
block storage
Data independent of instance
lifecycle
EBSEC2
Workspace
Hypervisor
S3
Boot cycle
Network

80. EBS Persistence
EBS volume is off-instance storage
You pay for the volume usage as long as the data
persists
1. By default, EBS volumes that are attached to a running instance
automatically detach from the instance with their data intact when that
instance is terminated
2. By default, EBS volumes that are created and attached to an instance
at launch are deleted when that instance is terminated. You can modify
this behavior by changing the value of the flag DeleteOnTermination to
false when you launch the instance.

81. Elastic Load Balancer
Spreading the load and fronting EC2

82. A regional service
Load balance across availability zones

83. Availability Zone Availability Zone
Region
Availability Zone
Instance Instance Instance Instance Instance Instance
Elastic Load Balancer

84. Offload
SSL processing on ELB
Remove load from EC2
instances
Spread
Go small and wide
Balance resources across
AZs
Health check
Choose the right healthcheck
point
Check whole layers
Elastic Load Balancing

85. 1. Persistent HTTP connections – enable them and ELB to
Server will be optimized
2. Never address underlying IP – always DNS name
• There’s a set behind an ELB and real clients spread
across them
• They will change as the ELB scales to keep ahead of
demand
3. If you span ELB across AZs have an instance in all Azs
4. De-register instances from an ELB before terminating

87. AutoScaling
Automate EC2 commissioning and
decommisioning

88. Describes what Auto Scaling
will create when adding
Instances
AMI
Instance Type
Security Group
Instance Key Pair
Only one active launch configuration
at a time
Auto Scaling will terminate instances
with old launch configuration first
rolling update
Auto Scaling managed grouping
of EC2 instances
Automatic health check to maintain
pool size
Automatically scale the number of
instances by policy – Min, Max,
Desired
Automatic Integration with ELB
Automatic distribution & balancing
across AZs
Parameters for performing an
Auto Scaling action
Scale Up/Down and by how much
ChangeInCapacity (+/- #)
ExactCapacity (#)
ChangeInPercent (+/- %)
Cool Down (seconds)
Policy can be triggered by
CloudWatch events
Launch Configuration Auto-Scaling Group Auto-Scaling Policy

89. aws autoscaling create-launch-configuration
--image-id ami-54cf5c3d
--instance-type m1.small
--key-name mykey
--security-groups webservers
--launch-configuration-name 101-launch-config
Create a launch configuration:

90. Create a launch configuration:
The usual
suspects
aws autoscaling create-launch-configuration
--image-id ami-54cf5c3d
--instance-type m1.small
--key-name mykey
--security-groups webservers
--launch-configuration-name 101-launch-config

91. aws autoscaling create-auto-scaling-group
--auto-scaling-group-name 101-as-group
--availability-zones us-east-1a us-east-1b us-east-1c
--launch-configuration-name 101-launch-config
--load-balancer-names myELB
--max-size 5
--min-size 1
Create an auto scaling group:

92. Create an auto scaling group:
What’s going to launch
aws autoscaling create-auto-scaling-group
--auto-scaling-group-name 101-as-group
--availability-zones us-east-1a us-east-1b us-east-1c
--launch-configuration-name 101-launch-config
--load-balancer-names myELB
--max-size 5
--min-size 1

93. Create an auto scaling group:
Integrate with an ELB?
aws autoscaling create-auto-scaling-group
--auto-scaling-group-name 101-as-group
--availability-zones us-east-1a us-east-1b us-east-1c
--launch-configuration-name 101-launch-config
--load-balancer-names myELB
--max-size 5
--min-size 1

94. aws autoscaling put-scaling-policy
--policy-name 101ScaleUpPolicy
--auto-scaling-group-name 101-as-group
--scaling-adjustment 1
--adjustment-type ChangeInCapacity
--cooldown 300
Create an auto-scaling policy (scale up):

95. Create an auto-scaling policy (scale up):
Period before another action will take place
(Damper)
aws autoscaling put-scaling-policy
--policy-name 101ScaleUpPolicy
--auto-scaling-group-name 101-as-group
--scaling-adjustment 1
--adjustment-type ChangeInCapacity
--cooldown 300

96. Create an auto-scaling policy (scale down):
aws autoscaling put-scaling-policy
--policy-name 101ScaleDownPolicy
--auto-scaling-group-name 101-as-group
“--scaling-adjustment=-1”
--adjustment-type ChangeInCapacity
--cooldown 300

98. CloudWatch
Know what is going on

101. CPU >= 50% for 5 mins
Takes action:Cloud Watch Alarm:
Scale up policy
CPU < 30% for 10 mins Scale down policy

102. CPU >= 50% for 5 mins
Takes action:Cloud Watch Alarm:
Scale up policy

104. CPU >= 50% for 5 mins
Takes action:Cloud Watch Alarm:
SNS Topic
CPU < 30% for 10 mins
Send Email
Post to endpoint
Deliver message to Q

105. CloudWatch
Comprehensive
Billing, technical, aggregate &
custom metrics
Alarms
Set custom alarms
and thresholds
SNS
Integration
Push alarms to
SNS topics
HTTP
Poke HTTP
endpoints for
custom alarm
actions
Custom Metrics
Write your own metrics in
via SDKs
Email
integration
Send alarm
notifications to
emails

106. Other topics to look at:

107. Route 53
Front EC2 and ELBs with
Route 53 for control over
DNS
Resource tagging
Tag resources like EC2
and have it appear on
billing reports
Rolling deployments
Use Route 53 and ELBs to do
rolling deployments, A/B
testing
Other topics…

108. OpsWorks
Manage stacks as layers
and implement Chef recipes
to automate EC2
configuration
Beanstalk
Manage an entire
autoscaling stack for
popular containers such
as ruby, python etc
CloudFormation
Template everything from
configuration of CloudWatch
alarms, SNS topics, EC2
instances
Other topics…

109. Summary

110. Stop doing these:
Provisioning and fixing servers
Treating compute as physical things
Thinking of compute as a finite commitment

111. and start doing these
Security
Build systems secure by
default
Elasticity
Stateless autoscaling
applications
Replace not fix
Build from scratch, don’t fix
something Unconstrained
Say goodbye to traditional
capacity planning
Be cost aware
Tag resources, play with
instance types
Automation
Create instances when
you need them, drop
them when not

112. aws.amazon.com

113. Join us and learn about the AWS platform,
new services and how to get started.
Register for a Summit near you.
aws.amazon.com/aws-summit-2014/
San Francisco | March 26
Register now
Sydney | April 9
Register now
London | April 30
Register now
Auckland | May 7
Paris | May 13
Berlin | May 15
Register now
Stockholm | May 22
Sao Paulo | May 27
Amsterdam | June 10
New York | July 10
Tokyo | July 17-18
Beijing | TBD
Seoul | September 3
Tel Aviv | September 17

114. Ian Massingham – Technical Evangelist
@IanMmmm
@AWS_UKI for local AWS events & news
@AWScloud for Global AWS News and Announcements
©Amazon.com, Inc. and its affiliates. All rights reserved.

115. AWS Training & Certification
Certification
aws.amazon.com/certification
Demonstrate your skills,
knowledge, and expertise
with the AWS platform
Self-Paced Labs
aws.amazon.com/training/
self-paced-labs
Try products, gain new
skills, and get hands-on
practice working with
AWS technologies
aws.amazon.com/training
Training
Skill up and gain
confidence to design,
develop, deploy and
manage your applications
on AWS

116. We typically see customers start by trying our
services
Get started now at : aws.amazon.com/getting-started

117. Design your application for the AWS Cloud
More details on the AWS Architecture Center at : aws.amazon.com/architecture