Aws General

Amazon Web Services
General Reference
Version 1.0
Amazon Web Services General Reference
Amazon Web Services: General Reference

Copyright © 2018 Amazon Web Services, Inc. and/or its affiliates. All rights reserved.
Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner
that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not
owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by
Amazon.
Table of Contents
AWS General Reference ...................................................................................................................... 1
AWS Regions and Endpoints ................................................................................................................ 2
Alexa for Business ...................................................................................................................... 5
Amazon API Gateway ................................................................................................................. 5
Application Auto Scaling ............................................................................................................. 6
Amazon AppStream 2.0 .............................................................................................................. 8
AWS AppSync ............................................................................................................................ 8
AWS AppSync Control Plane ................................................................................................ 8
AWS AppSync Data Plane .................................................................................................... 9
Athena ...................................................................................................................................... 9
Amazon Aurora ........................................................................................................................ 10
Amazon Aurora with MySQL compatibility ........................................................................... 10
Amazon Aurora with PostgreSQL compatibility .................................................................... 11
AWS Auto Scaling .................................................................................................................... 11
Amazon EC2 Auto Scaling ......................................................................................................... 12
AWS Batch .............................................................................................................................. 13
AWS Billing and Cost Management ............................................................................................. 14
AWS Cost Explorer ............................................................................................................ 14
AWS Budgets ................................................................................................................... 14
AWS Price List Service ....................................................................................................... 14
AWS Certificate Manager ........................................................................................................... 15
AWS Cloud9 ............................................................................................................................ 16
Amazon Cloud Directory ........................................................................................................... 16
AWS CloudFormation ................................................................................................................ 16
Amazon CloudFront .................................................................................................................. 18
AWS CloudHSM ........................................................................................................................ 18
AWS CloudHSM Classic ............................................................................................................. 19
Amazon CloudSearch ................................................................................................................ 19
AWS CloudTrail ........................................................................................................................ 20
Amazon CloudWatch ................................................................................................................. 21
Amazon CloudWatch Events ...................................................................................................... 22
Amazon CloudWatch Logs ......................................................................................................... 24
AWS CodeBuild ........................................................................................................................ 25
AWS CodeCommit .................................................................................................................... 26
AWS CodeDeploy ...................................................................................................................... 27
AWS CodePipeline .................................................................................................................... 28
AWS CodeStar .......................................................................................................................... 29
Amazon Cognito Identity ........................................................................................................... 29
Amazon Cognito Your User Pools ....................................................................................... 30
Amazon Cognito Federated Identities .................................................................................. 30
Amazon Cognito Sync ............................................................................................................... 31
Amazon Comprehend ............................................................................................................... 32
AWS Config ............................................................................................................................. 32
...................................................................................................................................... 33
AWS Config Rules ..................................................................................................................... 33
Amazon Connect ...................................................................................................................... 34
AWS Data Pipeline .................................................................................................................... 35
AWS Database Migration Service ................................................................................................ 35
AWS Device Farm ..................................................................................................................... 36
Amazon DevPay ....................................................................................................................... 36
AWS Direct Connect ................................................................................................................. 36
AWS Directory Service .............................................................................................................. 37
Amazon DynamoDB .................................................................................................................. 39
DynamoDB Accelerator (DAX) ..................................................................................................... 41
Version 1.0
iii
Amazon DynamoDB Streams ..................................................................................................... 41

AWS Elastic Beanstalk ............................................................................................................... 42
AWS Elastic Beanstalk Health Service .......................................................................................... 43
Amazon Elastic Compute Cloud (Amazon EC2) ............................................................................. 44
Amazon Elastic Container Registry .............................................................................................. 46
Amazon Elastic Container Service ............................................................................................... 47
Amazon Elastic File System ....................................................................................................... 48
Elastic Load Balancing .............................................................................................................. 48
Amazon Elastic Transcoder ........................................................................................................ 50
Amazon ElastiCache .................................................................................................................. 50
Amazon Elasticsearch Service ..................................................................................................... 51
Amazon EMR ........................................................................................................................... 52
Amazon GameLift ..................................................................................................................... 54
Amazon Glacier ........................................................................................................................ 55
AWS Glue ................................................................................................................................ 56
AWS Greengrass ....................................................................................................................... 56
Amazon GuardDuty .................................................................................................................. 57
AWS Health ............................................................................................................................. 58
AWS Identity and Access Management (IAM) ................................................................................ 58
AWS Import/Export .................................................................................................................. 59
AWS Import/Export Disk ................................................................................................... 59
Amazon Inspector .................................................................................................................... 60
AWS IoT .................................................................................................................................. 60
AWS Key Management Service ................................................................................................... 62
Amazon Kinesis Data Analytics ................................................................................................... 63
Amazon Kinesis Data Firehose .................................................................................................... 63
Amazon Kinesis Data Streams .................................................................................................... 64
Amazon Kinesis Video Streams .................................................................................................. 65
AWS Lambda ........................................................................................................................... 66
Amazon Lex ............................................................................................................................. 67
Amazon Lightsail ...................................................................................................................... 67
Amazon Machine Learning ......................................................................................................... 68
AWS Elemental MediaConvert .................................................................................................... 68
AWS Elemental MediaLive ......................................................................................................... 68
AWS Elemental MediaPackage ................................................................................................... 69
AWS Elemental MediaStore ....................................................................................................... 69
AWS Elemental MediaTailor ....................................................................................................... 70
Amazon Mechanical Turk ........................................................................................................... 70
AWS Migration Hub .................................................................................................................. 70
Amazon Mobile Analytics .......................................................................................................... 71
Amazon MQ ............................................................................................................................ 71
AWS OpsWorks ........................................................................................................................ 71
AWS OpsWorks CM ........................................................................................................... 71
AWS OpsWorks Stacks ...................................................................................................... 72
AWS Organizations ................................................................................................................... 73
Amazon Pinpoint ...................................................................................................................... 74
Amazon Polly ........................................................................................................................... 74
Amazon QuickSight .................................................................................................................. 75
Amazon Redshift ...................................................................................................................... 75
Amazon Rekognition ................................................................................................................. 77
Amazon Relational Database Service (Amazon RDS) ...................................................................... 77
AWS Resource Groups ............................................................................................................... 78
Amazon Route 53 ..................................................................................................................... 79
AWS Server Migration Service .................................................................................................... 80
Amazon SageMaker .................................................................................................................. 81
AWS Security Token Service (AWS STS) ....................................................................................... 81
AWS Serverless Application Repository ....................................................................................... 83
Version 1.0
iv
AWS Service Catalog ................................................................................................................. 83

AWS Shield Advanced ............................................................................................................... 84
Amazon Simple Email Service (Amazon SES) ................................................................................ 84
Amazon Simple Notification Service (Amazon SNS) ....................................................................... 85
Amazon Simple Queue Service (Amazon SQS) .............................................................................. 86
Amazon SQS Legacy Endpoints .......................................................................................... 87
Amazon Simple Storage Service (Amazon S3) .............................................................................. 89
Amazon Simple Storage Service Website Endpoints .............................................................. 92
Amazon Simple Workflow Service (Amazon SWF) ......................................................................... 93
Amazon SimpleDB .................................................................................................................... 95
AWS Snowball ......................................................................................................................... 95
AWS Step Functions ................................................................................................................. 97
AWS Storage Gateway .............................................................................................................. 98
AWS Support ........................................................................................................................... 99
AWS Systems Manager .............................................................................................................. 99
Amazon Transcribe ................................................................................................................. 100
Amazon Translate ................................................................................................................... 100
Amazon VPC .......................................................................................................................... 100
AWS WAF .............................................................................................................................. 101
Amazon WorkDocs .................................................................................................................. 102
Amazon WorkMail .................................................................................................................. 102
Amazon WorkSpaces ............................................................................................................... 104
AWS X-Ray ............................................................................................................................ 104
AWS Security Credentials ................................................................................................................. 106
AWS Account Root User Credentials vs. IAM User Credentials ....................................................... 106
AWS Tasks That Require AWS Account Root User ................................................................ 107
Understanding and Getting Your Security Credentials .................................................................. 107
Email and Password (Root User) ....................................................................................... 108
IAM User Name and Password .......................................................................................... 108
Multi-Factor Authentication (MFA) .................................................................................... 108
Access Keys (Access Key ID and Secret Access Key) .............................................................. 109
Key Pairs ....................................................................................................................... 109
AWS Account Identifiers .......................................................................................................... 110
Finding Your AWS Account ID .......................................................................................... 110
Finding Your Account Canonical User ID ............................................................................ 111
Best Practices for Managing AWS Access Keys ............................................................................ 112
Remove (or Don't Generate) Account Access Key ................................................................. 112
Use Temporary Security Credentials (IAM Roles) Instead of Long-Term Access Keys .................. 112
Manage IAM User Access Keys Properly ............................................................................. 113
More Resources .............................................................................................................. 114
Managing Access Keys for Your AWS Account ............................................................................. 114
Creating, Disabling, and Deleting Access Keys for Your AWS Account ..................................... 115
AWS Security Audit Guidelines ................................................................................................. 115
When Should You Perform a Security Audit? ...................................................................... 116
General Guidelines for Auditing ........................................................................................ 116
Review Your AWS Account Credentials ............................................................................... 116
Review Your IAM Users .................................................................................................... 116
Review Your IAM Groups ................................................................................................. 117
Review Your IAM Roles .................................................................................................... 117
Review Your IAM Providers for SAML and OpenID Connect (OIDC) ......................................... 117
Review Your Mobile Apps ................................................................................................ 118
Review Your Amazon EC2 Security Configuration ................................................................ 118
Review AWS Policies in Other Services .............................................................................. 118
Monitor Activity in Your AWS Account ............................................................................... 119
Tips for Reviewing IAM Policies ........................................................................................ 119
More Information ........................................................................................................... 120
Amazon Resource Names (ARNs) and AWS Service Namespaces ............................................................ 121
Version 1.0
v
ARN Format ........................................................................................................................... 121

Example ARNs ........................................................................................................................ 122
Alexa for Business .......................................................................................................... 124
Amazon API Gateway ...................................................................................................... 124
AWS AppSync ................................................................................................................ 124
AWS Artifact .................................................................................................................. 124
Amazon EC2 Auto Scaling ............................................................................................... 125
AWS Certificate Manager ................................................................................................. 125
AWS Cloud9 ................................................................................................................... 125
Amazon Cloud Directory .................................................................................................. 125
AWS CloudFormation ...................................................................................................... 126
Amazon CloudFront ........................................................................................................ 126
Amazon CloudSearch ...................................................................................................... 126
AWS CloudTrail .............................................................................................................. 126
Amazon CloudWatch ....................................................................................................... 126
Amazon CloudWatch Events ............................................................................................. 127
Amazon CloudWatch Logs ............................................................................................... 127
AWS CodeBuild .............................................................................................................. 127
AWS CodeCommit .......................................................................................................... 128
AWS CodeDeploy ............................................................................................................ 128
Amazon Cognito Your User Pools ..................................................................................... 128
Amazon Cognito Federated Identities ................................................................................ 128
Amazon Cognito Sync ..................................................................................................... 128
AWS Config ................................................................................................................... 129
AWS CodePipeline .......................................................................................................... 129
AWS CodeStar ................................................................................................................ 129
AWS Direct Connect ........................................................................................................ 129
AWS Directory Service ..................................................................................................... 130
Amazon DynamoDB ........................................................................................................ 130
AWS Elastic Beanstalk ..................................................................................................... 130
Amazon Elastic Compute Cloud (Amazon EC2) ................................................................... 130
Amazon Elastic Container Registry (Amazon ECR) ............................................................... 131
Amazon Elastic Container Service (Amazon ECS) ................................................................. 131
Amazon Elastic File System .............................................................................................. 132
Elastic Load Balancing (Application Load Balancer) ............................................................. 132
Elastic Load Balancing (Network Load Balancer) ................................................................. 132
Elastic Load Balancing (Classic Load Balancer) .................................................................... 133
Amazon Elastic Transcoder .............................................................................................. 133
Amazon ElastiCache ........................................................................................................ 133
Amazon Elasticsearch Service ........................................................................................... 133
Amazon Glacier .............................................................................................................. 133
Amazon GuardDuty ......................................................................................................... 134
AWS Health / Personal Health Dashboard .......................................................................... 134
AWS Identity and Access Management (IAM) ...................................................................... 134
AWS IoT ........................................................................................................................ 135
AWS Key Management Service (AWS KMS) ......................................................................... 135
Amazon Kinesis Data Firehose (Kinesis Data Firehose) .......................................................... 135
Amazon Kinesis Data Streams (Kinesis Data Streams) .......................................................... 136
Amazon Kinesis Data Analytics (Kinesis Data Analytics) ........................................................ 136
Amazon Kinesis Video Streams (Kinesis Video Streams) ....................................................... 136
AWS Lambda (Lambda) ................................................................................................... 136
Amazon Machine Learning (Amazon ML) ........................................................................... 137
AWS Elemental MediaConvert .......................................................................................... 137
AWS Elemental MediaLive ............................................................................................... 137
AWS Elemental MediaPackage .......................................................................................... 137
AWS Elemental MediaStore .............................................................................................. 138
AWS Elemental MediaTailor ............................................................................................. 138
Version 1.0
vi
AWS Mobile Hub ............................................................................................................ 138

Amazon MQ ................................................................................................................... 138
AWS Organizations ......................................................................................................... 139
Amazon Pinpoint ............................................................................................................ 139
Amazon Polly ................................................................................................................. 139
Amazon Redshift ............................................................................................................ 139
Amazon Relational Database Service (Amazon RDS) ............................................................ 140
Amazon Route 53 ........................................................................................................... 140
AWS Serverless Application Repository .............................................................................. 141
Amazon Simple Email Service (Amazon SES) ...................................................................... 141
Amazon Simple Notification Service (Amazon SNS) ............................................................. 141
Amazon Simple Queue Service (Amazon SQS) .................................................................... 141
Amazon Simple Storage Service (Amazon S3) ..................................................................... 142
Amazon Simple Workflow Service (Amazon SWF) ............................................................... 142
AWS Step Functions ........................................................................................................ 142
AWS Storage Gateway ..................................................................................................... 143
AWS Systems Manager .................................................................................................... 143
AWS Trusted Advisor ....................................................................................................... 143
AWS WAF ...................................................................................................................... 144
Paths in ARNs ........................................................................................................................ 144
AWS Service Namespaces ........................................................................................................ 145
Signing AWS API Requests ............................................................................................................... 150
When Do You Need to Sign Requests? ...................................................................................... 150
Why Requests Are Signed ........................................................................................................ 150
Signing Requests .................................................................................................................... 151
Signature Versions .................................................................................................................. 151
Signature Version 4 Signing Process .......................................................................................... 152
Changes in Signature Version 4 ........................................................................................ 152
Signing AWS Requests .................................................................................................... 153
Handling Dates .............................................................................................................. 165
Examples of How to Derive a Signing Key .......................................................................... 165
Signing Examples (Python) .............................................................................................. 168
Test Suite ...................................................................................................................... 175
Troubleshooting ............................................................................................................. 177
Service-Specific Reference ............................................................................................... 180
Signature Version 2 Signing Process .......................................................................................... 180
Supported Regions and Services ....................................................................................... 180
Components of a Query Request for Signature Version 2 ..................................................... 181
How to Generate a Signature Version 2 for a Query Request ................................................ 182
AWS Service Limits ......................................................................................................................... 188
Amazon API Gateway Limits .................................................................................................... 190
Application Auto Scaling Limits ................................................................................................ 191
AWS Application Discovery Service Limits .................................................................................. 191
Amazon AppStream 2.0 Limits ................................................................................................. 191
AWS AppSync Limits ............................................................................................................... 192
Amazon Athena Limits ............................................................................................................ 192
AWS Auto Scaling Limits ......................................................................................................... 192
Auto Scaling Limits ................................................................................................................. 193
AWS Batch Limits ................................................................................................................... 193
AWS Certificate Manager (ACM) Limits ...................................................................................... 193
AWS Cloud9 Limits ................................................................................................................. 194
AWS CloudFormation Limits ..................................................................................................... 194
Amazon CloudFront Limits ....................................................................................................... 194
AWS CloudHSM Limits ............................................................................................................ 195
AWS CloudHSM Classic Limits .................................................................................................. 196
Amazon CloudSearch Limits ..................................................................................................... 196
AWS CloudTrail Limits ............................................................................................................. 196
Version 1.0
vii
Amazon CloudWatch Limits ..................................................................................................... 196

Amazon CloudWatch Events Limits ........................................................................................... 197
Amazon CloudWatch Logs Limits .............................................................................................. 198
AWS CodeBuild Limits ............................................................................................................. 199
AWS CodeCommit Limits ......................................................................................................... 199
AWS CodeDeploy Limits .......................................................................................................... 199
AWS CodePipeline Limits ......................................................................................................... 200
Amazon Cognito User Pools Limits ........................................................................................... 201
Amazon Cognito Federated Identities Limits .............................................................................. 201
Amazon Cognito Sync Limits .................................................................................................... 201
Amazon Comprehend Limits .................................................................................................... 202
AWS Config Limits .................................................................................................................. 202
Amazon Connect Limits ........................................................................................................... 202
AWS Data Pipeline Limits ........................................................................................................ 203
AWS Database Migration Service Limits ..................................................................................... 204
AWS Device Farm Limits .......................................................................................................... 204
AWS Direct Connect Limits ...................................................................................................... 204
AWS Directory Service Limits ................................................................................................... 205
Amazon DynamoDB Limits ....................................................................................................... 205
AWS Elastic Beanstalk Limits .................................................................................................... 205
Amazon Elastic Block Store (Amazon EBS) Limits ........................................................................ 206
Amazon Elastic Compute Cloud (Amazon EC2) Limits .................................................................. 206
Amazon Elastic Container Registry (Amazon ECR) Limits .............................................................. 207
Amazon Elastic Container Service (Amazon ECS) Limits ............................................................... 208
Amazon Elastic File System Limits ............................................................................................ 208
Elastic Load Balancing Limits ................................................................................................... 208
Amazon Elastic Transcoder Limits ............................................................................................. 210
Amazon ElastiCache Limits ...................................................................................................... 210
Amazon Elasticsearch Service Limits ......................................................................................... 211
Amazon GameLift Limits ......................................................................................................... 211
Amazon Glacier Limits ............................................................................................................. 212
AWS Glue Limits ..................................................................................................................... 212
AWS Greengrass Limits ............................................................................................................ 213
AWS Greengrass Cloud API Limits ..................................................................................... 213
AWS Greengrass core Limits ............................................................................................. 213
Amazon GuardDuty Limits ....................................................................................................... 214
AWS Identity and Access Management (IAM) Limits ..................................................................... 215
AWS Import/Export Limits ....................................................................................................... 215
AWS Snowball (Snowball) ................................................................................................ 215
Amazon Inspector Limits ......................................................................................................... 215
AWS IoT Limits ....................................................................................................................... 216
Thing Limits ................................................................................................................... 216
Message Broker Limits ..................................................................................................... 216
Protocol Limits ............................................................................................................... 219
Device Shadow Limits ..................................................................................................... 220
Security and Identity Limits ............................................................................................. 221
Throttling Limits ............................................................................................................ 222
AWS IoT Rules Engine Limits ............................................................................................ 223
AWS IoT Job Limits ......................................................................................................... 223
AWS IoT Bulk Thing Registration Limits ............................................................................. 225
AWS Key Management Service (AWS KMS) Limits ....................................................................... 225
Amazon Kinesis Data Firehose Limits ........................................................................................ 226
Amazon Kinesis Data Streams Limits ......................................................................................... 226
Amazon Kinesis Data Analytics Limits ....................................................................................... 226
Amazon Kinesis Video Streams Limits ....................................................................................... 227
Control Plane API limits .................................................................................................. 227
Data Plane API limits ...................................................................................................... 227
Version 1.0
viii
AWS Lambda Limits ................................................................................................................ 229

Amazon Lightsail Limits .......................................................................................................... 230
Amazon Machine Learning (Amazon ML) Limits .......................................................................... 230
AWS Elemental MediaConvert Limits ......................................................................................... 231
AWS Elemental MediaLive Limits .............................................................................................. 231
AWS Elemental MediaPackage Limits ........................................................................................ 231
AWS Elemental MediaStore Limits ............................................................................................ 232
AWS Elemental MediaTailor Limits ............................................................................................ 232
Amazon MQ Limits ................................................................................................................. 232
Amazon Neptune Limits .......................................................................................................... 232
AWS OpsWorks for Chef Automate and AWS OpsWorks for Puppet Enterprise Limits ....................... 233
AWS OpsWorks Stacks Limits ................................................................................................... 233
AWS Organizations Limits ........................................................................................................ 233
Amazon Pinpoint Limits .......................................................................................................... 233
Amazon Polly Limits ............................................................................................................... 234
Amazon Redshift Limits ........................................................................................................... 235
Amazon Rekognition Limits ..................................................................................................... 235
Amazon Relational Database Service (Amazon RDS) Limits ........................................................... 235
AWS Resource Groups Limits .................................................................................................... 236
Amazon Route 53 Limits .......................................................................................................... 236
Amazon SageMaker Limits ....................................................................................................... 237
AWS Server Migration Service Limits ......................................................................................... 238
AWS Serverless Application Repository Limits ............................................................................ 239
AWS Service Catalog Limits ..................................................................................................... 239
AWS Shield Advanced Limits .................................................................................................... 239
Amazon Simple Email Service (Amazon SES) Limits ..................................................................... 239
Amazon Simple Notification Service (Amazon SNS) Limits ............................................................ 240
Amazon SNS API Throttling Limits .................................................................................... 240
Amazon Simple Queue Service (Amazon SQS) ............................................................................ 241
Amazon Simple Storage Service (Amazon S3) Limits ................................................................... 241
Amazon Simple Workflow Service (Amazon SWF) Limits .............................................................. 241
Amazon SimpleDB Limits ......................................................................................................... 241
AWS Step Functions Limits ...................................................................................................... 241
AWS Storage Gateway Limits ................................................................................................... 241
AWS Systems Manager Limits .................................................................................................. 242
Amazon Virtual Private Cloud (Amazon VPC) Limits .................................................................... 244
Amazon VPC DNS Limits ......................................................................................................... 247
AWS WAF Limits ..................................................................................................................... 247
Amazon WorkMail Limits ......................................................................................................... 248
Amazon WorkSpaces Limits ..................................................................................................... 248
AWS X-Ray Limits ................................................................................................................... 248
AWS IP Address Ranges ................................................................................................................... 249
Download .............................................................................................................................. 249
Syntax ................................................................................................................................... 249
Filtering the JSON File ............................................................................................................ 251
Windows ....................................................................................................................... 251
Linux ............................................................................................................................. 251
Implementing Egress Control ................................................................................................... 252
AWS IP Address Ranges Notifications ........................................................................................ 252
API Retries ..................................................................................................................................... 254
AWS SDK Support for Amazon S3 Client-Side Encryption .................................................................... 256
AWS SDK Features for Amazon S3 Client-Side Encryption ............................................................ 256
Amazon S3 Encryption Client Cryptographic Algorithms .............................................................. 257
Markdown in AWS .......................................................................................................................... 259
Paragraphs, Line Spacing, and Horizontal Lines .......................................................................... 259
Headings ............................................................................................................................... 259
Text Formatting ..................................................................................................................... 260
Version 1.0
ix
Links ..................................................................................................................................... 260

Lists ...................................................................................................................................... 260
Tables and Buttons (CloudWatch Dashboards) ............................................................................ 261
Document Conventions ................................................................................................................... 262
AWS Glossary ................................................................................................................................. 264
Version 1.0
x
AWS General Reference

This is the Amazon Web Services General Reference.
Contents
• AWS Regions and Endpoints (p. 2)

• AWS Security Credentials (p. 106)
• Amazon Resource Names (ARNs) and AWS Service Namespaces (p. 121)
• Signing AWS API Requests (p. 150)
• AWS Service Limits (p. 188)
• AWS IP Address Ranges (p. 249)
• Error Retries and Exponential Backoff in AWS (p. 254)
• AWS SDK Support for Amazon S3 Client-Side Encryption (p. 256)
• AWS Tasks That Require AWS Account Root User (p. 107)
• AWS Glossary (p. 264)
Version 1.0
1
AWS Regions and Endpoints

To reduce data latency in your applications, most Amazon Web Services offer a regional endpoint
to make your requests. An endpoint is a URL that is the entry point for a web service. For example,
https://dynamodb.us-west-2.amazonaws.com is an entry point for the Amazon DynamoDB
service.
Some services, such as IAM, do not support regions; therefore, their endpoints do not include a region.
Some services, such as Amazon EC2, let you specify an endpoint that does not include a specific region,
for example, https://ec2.amazonaws.com. In that case, AWS routes the endpoint to us-east-1.
If a service supports regions, the resources in each region are independent. For example, if you create an
Amazon EC2 instance or an Amazon SQS queue in one region, the instance or queue is independent from
instances or queues in another region.
You can find region and endpoint information from the following sources:
• To see the supported services per region in a tabbed format, see the Region Table. This page does not
include endpoint information.
• For information about the AWS services and endpoints available in the China (Beijing) Region, see
China (Beijing) Region Endpoints.
• For information about the AWS services and endpoints available in the AWS GovCloud (US) Region, see
AWS GovCloud (US) Endpoints.
• For information about which regions and endpoints are supported for each service, see the following
tables.
Services
• Alexa for Business (p. 5)
• Amazon API Gateway (p. 5)
• Application Auto Scaling (p. 6)
• Amazon AppStream 2.0 (p. 8)
• AWS AppSync (p. 8)
• Athena (p. 9)
• Amazon Aurora (p. 10)
• AWS Auto Scaling (p. 11)
• Amazon EC2 Auto Scaling (p. 12)
• AWS Batch (p. 13)
• AWS Billing and Cost Management (p. 14)
• AWS Certificate Manager (p. 15)
• AWS Cloud9 (p. 16)
• Amazon Cloud Directory (p. 16)
• AWS CloudFormation (p. 16)
• Amazon CloudFront (p. 18)
• AWS CloudHSM (p. 18)
• AWS CloudHSM Classic (p. 19)
• Amazon CloudSearch (p. 19)
• AWS CloudTrail (p. 20)
Version 1.0
2
• Amazon CloudWatch (p. 21)

• Amazon CloudWatch Events (p. 22)
• Amazon CloudWatch Logs (p. 24)
• AWS CodeBuild (p. 25)
• AWS CodeCommit (p. 26)
• AWS CodeDeploy (p. 27)
• AWS CodePipeline (p. 28)
• AWS CodeStar (p. 29)
• Amazon Cognito Identity (p. 29)
• Amazon Cognito Sync (p. 31)
• Amazon Comprehend (p. 32)
• AWS Config (p. 32)
• AWS Config Rules (p. 33)
• Amazon Connect (p. 34)
• AWS Data Pipeline (p. 35)
• AWS Database Migration Service (p. 35)
• AWS Device Farm (p. 36)
• Amazon DevPay (p. 36)
• AWS Direct Connect (p. 36)
• AWS Directory Service (p. 37)
• Amazon DynamoDB (p. 39)
• DynamoDB Accelerator (DAX) (p. 41)
• Amazon DynamoDB Streams (p. 41)
• AWS Elastic Beanstalk (p. 42)
• AWS Elastic Beanstalk Health Service (p. 43)
• Amazon Elastic Compute Cloud (Amazon EC2) (p. 44)
• Amazon Elastic Container Registry (p. 46)
• Amazon Elastic Container Service (p. 47)
• Amazon Elastic File System (p. 48)
• Elastic Load Balancing (p. 48)
• Amazon Elastic Transcoder (p. 50)
• Amazon ElastiCache (p. 50)
• Amazon Elasticsearch Service (p. 51)
• Amazon EMR (p. 52)
• Amazon GameLift (p. 54)
• Amazon Glacier (p. 55)
• AWS Glue (p. 56)
• AWS Greengrass (p. 56)
• Amazon GuardDuty (p. 57)
• AWS Health (p. 58)
• AWS Identity and Access Management (IAM) (p. 58)
• AWS Import/Export (p. 59)
• Amazon Inspector (p. 60)
• AWS IoT (p. 60)
• AWS Key Management Service (p. 62)
• Amazon Kinesis Data Analytics (p. 63)
Version 1.0
3
• Amazon Kinesis Data Firehose (p. 63)

• Amazon Kinesis Data Streams (p. 64)
• Amazon Kinesis Video Streams (p. 65)
• AWS Lambda (p. 66)
• Amazon Lex (p. 67)
• Amazon Lightsail (p. 67)
• Amazon Machine Learning (p. 68)
• AWS Elemental MediaConvert (p. 68)
• AWS Elemental MediaLive (p. 68)
• AWS Elemental MediaPackage (p. 69)
• AWS Elemental MediaStore (p. 69)
• AWS Elemental MediaTailor (p. 70)
• Amazon Mechanical Turk (p. 70)
• AWS Migration Hub (p. 70)
• Amazon Mobile Analytics (p. 71)
• Amazon MQ (p. 71)
• AWS OpsWorks (p. 71)
• AWS Organizations (p. 73)
• Amazon Pinpoint (p. 74)
• Amazon Polly (p. 74)
• Amazon QuickSight (p. 75)
• Amazon Redshift (p. 75)
• Amazon Rekognition (p. 77)
• Amazon Relational Database Service (Amazon RDS) (p. 77)
• AWS Resource Groups (p. 78)
• Amazon Route 53 (p. 79)
• AWS Server Migration Service (p. 80)
• Amazon SageMaker (p. 81)
• AWS Security Token Service (AWS STS) (p. 81)
• AWS Serverless Application Repository (p. 83)
• AWS Service Catalog (p. 83)
• AWS Shield Advanced (p. 84)
• Amazon Simple Email Service (Amazon SES) (p. 84)
• Amazon Simple Notification Service (Amazon SNS) (p. 85)
• Amazon Simple Queue Service (Amazon SQS) (p. 86)
• Amazon Simple Storage Service (Amazon S3) (p. 89)
• Amazon Simple Workflow Service (Amazon SWF) (p. 93)
• Amazon SimpleDB (p. 95)
• AWS Snowball (p. 95)
• AWS Step Functions (p. 97)
• AWS Storage Gateway (p. 98)
• AWS Support (p. 99)
• AWS Systems Manager (p. 99)
• Amazon Transcribe (p. 100)
• Amazon Translate (p. 100)
Version 1.0
4
Alexa for Business
• Amazon VPC (p. 100)

• AWS WAF (p. 101)
• Amazon WorkDocs (p. 102)
• Amazon WorkMail (p. 102)
• Amazon WorkSpaces (p. 104)
• AWS X-Ray (p. 104)
Alexa for Business

Region Region Endpoint Protocol
Name
US East (N. us-east-1 a4b.us-east-1.amazonaws.com HTTPS

Virginia)
Amazon API Gateway

Region Region Endpoint Protocol Amazon
Name Route 53
Hosted
Zone ID*
US East us-east-2 apigateway.us-east-2.amazonaws.com HTTPS ZOJJZC49E0EPZ

(Ohio)
US East (N. us-east-1 apigateway.us-east-1.amazonaws.com HTTPS Z1UJRXOUMOOFQ8

Virginia)
US us-west-1 apigateway.us-west-1.amazonaws.com HTTPS Z2MUQ32089INYE

West (N.
California)
US West us-west-2 apigateway.us-west-2.amazonaws.com HTTPS Z2OJLYMUO9EFXC

(Oregon)
Asia ap- apigateway.ap-south-1.amazonaws.com HTTPS Z3VO1THU9YC4UR

Pacific south-1
(Mumbai)
Asia ap- apigateway.ap-northeast-2.amazonaws.com HTTPS Z20JF4UZKIW1U8

Pacific northeast-2
(Seoul)
Asia ap- apigateway.ap-northeast-3.amazonaws.com HTTPS Z2YQB5RD63NC85

(Osaka-
Local)
Asia ap- apigateway.ap-southeast-1.amazonaws.com HTTPS ZL327KTPIQFUL

Pacific southeast-1
(Singapore)
Version 1.0
5
Application Auto Scaling
Region Region Endpoint Protocol Amazon

Name Route 53
Hosted
Zone ID*
Asia ap- apigateway.ap-southeast-2.amazonaws.com HTTPS Z2RPCDW04V8134

Pacific southeast-2
(Sydney)
Asia ap- apigateway.ap-northeast-1.amazonaws.com HTTPS Z1YSHQZHG15GKL

(Tokyo)
Canada ca- apigateway.ca-central-1.amazonaws.com HTTPS Z19DQILCV0OWEC

(Central) central-1
China cn-north-1 apigateway.cn-north-1.amazonaws.com.cn HTTPS None

(Beijing)
EU eu- apigateway.eu-central-1.amazonaws.com HTTPS Z1U9ULNL0V5AJ3

(Frankfurt) central-1
EU eu-west-1 apigateway.eu-west-1.amazonaws.com HTTPS ZLY8HYME6SFDD

(Ireland)
EU eu-west-2 apigateway.eu-west-2.amazonaws.com HTTPS ZJ5UAJN8Y3Z2Q

(London)
EU (Paris) eu-west-3 apigateway.eu-west-3.amazonaws.com HTTPS Z3KY65QIEKYHQQ
South sa-east-1 apigateway.sa-east-1.amazonaws.com HTTPS ZCMLWB8V5SYIT

America
(São
Paulo)
* The Route 53 Hosted Zone ID column shows the Route 53 Hosted Zone IDs for the API Gateway
regional endpoints. For edge-optimized endpoints, the Route 53 Hosted Zone ID is Z2FDTNDATAQYW2
for all the regions.

Name
US East us-east-2 autoscaling.us-east-2.amazonaws.com HTTP and

(Ohio) HTTPS
US East (N. us-east-1 autoscaling.us-east-1.amazonaws.com HTTP and

Virginia) HTTPS
US West (N. us-west-1 autoscaling.us-west-1.amazonaws.com HTTP and

California) HTTPS
US West us-west-2 autoscaling.us-west-2.amazonaws.com HTTP and

(Oregon) HTTPS
Version 1.0
6

Name
Asia Pacific ap- autoscaling.ap-northeast-1.amazonaws.com HTTP and

(Tokyo) northeast-1 HTTPS

(Seoul) northeast-2 HTTPS

(Osaka- northeast-3 HTTPS
Local)
Asia Pacific ap-south-1 autoscaling.ap-south-1.amazonaws.com HTTP and

(Mumbai) HTTPS
Asia Pacific ap- autoscaling.ap-southeast-1.amazonaws.com HTTP and

(Singapore) southeast-1 HTTPS

(Sydney) southeast-2 HTTPS
Canada ca-central-1 autoscaling.ca-central-1.amazonaws.com HTTP and

(Central) HTTPS
China cn-north-1 autoscaling.cn-north-1.amazonaws.com.cn HTTP and

(Beijing) HTTPS
China cn- autoscaling.cn-northwest-1.amazonaws.com.cn HTTP and

(Ningxia) northwest-1 HTTPS
EU eu-central-1 autoscaling.eu-central-1.amazonaws.com HTTP and

(Frankfurt) HTTPS
EU (Ireland) eu-west-1 autoscaling.eu-west-1.amazonaws.com HTTP and

HTTPS
EU (London) eu-west-2 autoscaling.eu-west-2.amazonaws.com HTTP and

HTTPS
EU (Paris) eu-west-3 autoscaling.eu-west-3.amazonaws.com HTTP and

HTTPS
South sa-east-1 autoscaling.sa-east-1.amazonaws.com HTTP and

America HTTPS
(Sao Paulo)
For information about using Application Auto Scaling in the China (Beijing) Region, see China (Beijing)
Region Endpoints.
Version 1.0
7
Amazon AppStream 2.0
Amazon AppStream 2.0

Name
US East (N. us-east-1 appstream2.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 appstream2.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- appstream2.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Asia Pacific ap- appstream2.ap-southeast-1.amazonaws.com HTTPS

(Singapore) southeast-1
Asia Pacific ap- appstream2.ap-southeast-2.amazonaws.com HTTPS

(Sydney) southeast-2
EU (Ireland) eu-west-1 appstream2.eu-west-1.amazonaws.com HTTPS
AWS AppSync
AWS AppSync Control Plane

Name
US East us-east-2 appsync.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 appsync.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 appsync.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- appsync.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- appsync.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU (Ireland) eu-west-1 appsync.eu-west-1.amazonaws.com HTTPS
Version 1.0
8
AWS AppSync Data Plane
AWS AppSync Data Plane

Name
US East us-east-2 <unique-id>.appsync.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 <unique-id>.appsync.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 <unique-id>.appsync.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- <unique-id>.appsync.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- <unique-id>.appsync.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU (Ireland) eu-west-1 <unique-id>.appsync.eu-west-1.amazonaws.com HTTPS
Athena
Region Name Region Endpoint Protocol
US East (Ohio) us-east-2 athena.us-east-2.amazonaws.com HTTPS
US East (N. us-east-1 athena.us-east-1.amazonaws.com HTTPS

Virginia)
US West (Oregon) us-west-2 athena.us-west-2.amazonaws.com HTTPS
Asia Pacific ap-south-1 athena.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific (Seoul) ap-northeast-2 athena.ap-northeast-2.amazonaws.com HTTPS
Asia Pacific ap-southeast-1 athena.ap-southeast-1.amazonaws.com HTTPS

(Singapore)
Asia Pacific ap-southeast-2 athena.ap-southeast-2.amazonaws.com HTTPS

(Sydney)
Asia Pacific ap-northeast-1 athena.ap-northeast-1.amazonaws.com HTTPS

(Tokyo)
EU (Frankfurt) eu-central-1 athena.eu-central-1.amazonaws.com HTTPS
EU (Ireland) eu-west-1 athena.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 athena.eu-west-2.amazonaws.com HTTPS
Note
To connect to the service via the JDBC (Java Database Connectivity) driver, use the URL
connection string formats in the Connect with JDBC.
Version 1.0
9
Amazon Aurora
To connect to the service via the ODBC (Open Database Connectivity) driver, use the URL
connection string formats in the Athena ODBC Driver Installation and Configuration Guide.
Amazon Aurora
Amazon Aurora with MySQL compatibility

Name
US East (N. us-east-1 rds.us-east-1.amazonaws.com HTTPS

Virginia)
US East us-east-2 rds.us-east-2.amazonaws.com HTTPS

(Ohio)
US West (N. us-west-1 rds.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 rds.us-west-2.amazonaws.com HTTPS

(Oregon)
Canada ca-central-1 rds.ca-central-1.amazonaws.com HTTPS

(Central)
Asia Pacific ap-south-1 rds.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- rds.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1

(Seoul) northeast-2
Asia Pacific ap- rds.ap-southeast-1.amazonaws.com HTTPS


EU eu-central-1 rds.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 rds.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 rds.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 rds.eu-west-3.amazonaws.com HTTPS
Version 1.0
10
Amazon Aurora with PostgreSQL compatibility
Amazon Aurora with PostgreSQL compatibility

Name

Virginia)

(Ohio)

(Oregon)

(Central)

(Mumbai)

(Tokyo) northeast-1



(Frankfurt)
AWS Auto Scaling

Name

(Ohio) HTTPS

Virginia) HTTPS

(Oregon) HTTPS

Version 1.0
11
Amazon EC2 Auto Scaling

Name

HTTPS

Name

(Ohio) HTTPS

Virginia) HTTPS
US West (N. us-west-1 autoscaling.us-west-1.amazonaws.com HTTP and

California) HTTPS

(Oregon) HTTPS



Local)
Asia Pacific ap-south-1 autoscaling.ap-south-1.amazonaws.com HTTP and

(Mumbai) HTTPS


Canada ca-central-1 autoscaling.ca-central-1.amazonaws.com HTTP and

(Central) HTTPS
China cn-north-1 autoscaling.cn-north-1.amazonaws.com.cn HTTP and

(Beijing) HTTPS
China cn- autoscaling.cn-northwest-1.amazonaws.com.cn HTTP and

EU eu-central-1 autoscaling.eu-central-1.amazonaws.com HTTP and

(Frankfurt) HTTPS

HTTPS
Version 1.0
12
AWS Batch

Name
EU (London) eu-west-2 autoscaling.eu-west-2.amazonaws.com HTTP and

HTTPS
EU (Paris) eu-west-3 autoscaling.eu-west-3.amazonaws.com HTTP and

HTTPS
South sa-east-1 autoscaling.sa-east-1.amazonaws.com HTTP and

America HTTPS
(Sao Paulo)
AWS us-gov- autoscaling.us-gov-west-1.amazonaws.com HTTP and

GovCloud west-1 HTTPS
(US)
If you just specify the general endpoint (autoscaling.amazonaws.com), Amazon EC2 Auto Scaling directs
your request to the us-east-1 endpoint.
For information about using Amazon EC2 Auto Scaling in the AWS GovCloud (US) Region, see AWS
GovCloud (US) Endpoints.
For information about using Amazon EC2 Auto Scaling in the China (Beijing) Region, see China (Beijing)
Region Endpoints.
AWS Batch
Name
US West us-west-2 batch.us-west-2.amazonaws.com HTTPS

(Oregon)
US West (N. us-west-1 batch.us-west-1.amazonaws.com HTTPS

California)
US East us-east-2 batch.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 batch.us-east-1.amazonaws.com HTTPS

Virginia)
Canada ca-central-1 batch.ca-central-1.amazonaws.com HTTPS

(Central)
EU (London) eu-west-2 batch.eu-west-2.amazonaws.com HTTPS
EU (Ireland) eu-west-1 batch.eu-west-1.amazonaws.com HTTPS
EU eu-central-1 batch.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
Asia Pacific ap- batch.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Version 1.0
13
AWS Billing and Cost Management

Name
Asia Pacific ap- batch.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap- batch.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- batch.ap-southeast-1.amazonaws.com HTTPS

AWS Billing and Cost Management

AWS Billing and Cost Management includes the AWS Cost Explorer API, the AWS Budgets API, and the
AWS Price List API.
AWS Cost Explorer

Name
US East (N. us-east-1 https://ce.us-east-1.amazonaws.com HTTPS

Virginia)
AWS Budgets

Name
US East (N. us-east-1 https://budgets.us-east-1.amazonaws.com HTTPS

Virginia)
AWS Price List Service

Name
US East (N. us-east-1 https://api.pricing.us-east-1.amazonaws.com HTTPS

Virginia)
Asia Pacific ap-south-1 https://api.pricing.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Version 1.0
14
AWS Certificate Manager

Name
US East us-east-2 acm.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 acm.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 acm.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 acm.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- acm.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1

(Seoul) northeast-2

(Osaka- northeast-3
Local)
Asia Pacific ap-south-1 acm.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- acm.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- acm.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 acm.ca-central-1.amazonaws.com HTTPS

(Central)
EU eu-central-1 acm.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 acm.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 acm.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 acm.eu-west-3.amazonaws.com HTTPS
South sa-east-1 acm.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS us-gov- acm.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US)
For information about using AWS Certificate Manager in the AWS GovCloud (US) Region, see AWS
Version 1.0
15
AWS Cloud9
AWS Cloud9
Name
US East us-east-2 cloud9.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 cloud9.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 cloud9.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- cloud9.ap-southeast-1.amazonaws.com HTTPS

EU (Ireland) eu-west-1 cloud9.eu-west-1.amazonaws.com HTTPS
Amazon Cloud Directory

Name
US East us-east-2 clouddirectory.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 clouddirectory.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 clouddirectory.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- clouddirectory.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- clouddirectory.ap-southeast-2.amazonaws.com HTTPS

EU eu-central-1 clouddirectory.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 clouddirectory.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 clouddirectory.eu-west-2.amazonaws.com HTTPS
AWS CloudFormation
Name
US East us-east-2 cloudformation.us-east-2.amazonaws.com HTTPS

(Ohio)
Version 1.0
16
AWS CloudFormation

Name
US East (N. us-east-1 cloudformation.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 cloudformation.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 cloudformation.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- cloudformation.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1

(Seoul) northeast-2

(Osaka- northeast-3
Local)
Asia Pacific ap-south-1 cloudformation.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- cloudformation.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- cloudformation.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 cloudformation.ca-central-1.amazonaws.com HTTPS

(Central)
China cn-north-1 cloudformation.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
China cn- cloudformation.cn-northwest-1.amazonaws.com.cn HTTPS

(Ningxia) northwest-1
EU eu-central-1 cloudformation.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 cloudformation.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 cloudformation.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 cloudformation.eu-west-3.amazonaws.com HTTPS
South sa-east-1 cloudformation.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS us-gov- cloudformation.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US)
For information about using AWS CloudFormation in the AWS GovCloud (US) Region, see AWS GovCloud
(US) Endpoints.
Version 1.0
17
Amazon CloudFront
For information about using AWS CloudFormation in the China (Beijing) Region, see China (Beijing)
Region Endpoints.
Amazon CloudFront
Amazon CloudFront distributions have a single endpoint: cloudfront.amazonaws.com and only supports
HTTPS requests. When you submit requests to CloudFront programmatically, specify us-east-1 for the US
East (N. Virginia) Region.
The CloudFront hosted zone ID value is Z2FDTNDATAQYW2.
AWS CloudHSM
US East (Ohio) us-east-2 cloudhsmv2.us- HTTPS

east-2.amazonaws.com
US East (N. Virginia) us-east-1 cloudhsmv2.us- HTTPS

US West (N. California) us-west-1 cloudhsmv2.us- HTTPS

west-1.amazonaws.com
US West (Oregon) us-west-2 cloudhsmv2.us- HTTPS

Asia Pacific (Mumbai) ap-south-1 cloudhsmv2.ap- HTTPS

south-1.amazonaws.com
Asia Pacific (Singapore) ap-southeast-1 cloudhsmv2.ap- HTTPS

southeast-1.amazonaws.com
Asia Pacific (Sydney) ap-southeast-2 cloudhsmv2.ap- HTTPS

Asia Pacific (Tokyo) ap-northeast-1 cloudhsmv2.ap- HTTPS

northeast-1.amazonaws.com
Canada (Central) ca-central-1 cloudhsmv2.ca- HTTPS

central-1.amazonaws.com
EU (Frankfurt) eu-central-1 cloudhsmv2.eu- HTTPS

EU (Ireland) eu-west-1 cloudhsmv2.eu- HTTPS

Version 1.0
18
AWS CloudHSM Classic
AWS CloudHSM Classic

US East (Ohio) us-east-2 cloudhsm.us- HTTPS

US East (N. Virginia) us-east-1 cloudhsm.us- HTTPS

US West (N. California) us-west-1 cloudhsm.us- HTTPS

US West (Oregon) us-west-2 cloudhsm.us- HTTPS

Asia Pacific (Singapore) ap-southeast-1 cloudhsm.ap- HTTPS

Asia Pacific (Sydney) ap-southeast-2 cloudhsm.ap- HTTPS

Asia Pacific (Tokyo) ap-northeast-1 cloudhsm.ap- HTTPS

Canada (Central) ca-central-1 cloudhsm.ca- HTTPS

EU (Frankfurt) eu-central-1 cloudhsm.eu- HTTPS

EU (Ireland) eu-west-1 cloudhsm.eu- HTTPS

For information about using AWS CloudHSM Classic in the AWS GovCloud (US) Region, see AWS
Amazon CloudSearch
Name
US East (N. us-east-1 cloudsearch.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 cloudsearch.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 cloudsearch.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- cloudsearch.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Version 1.0
19
AWS CloudTrail

Name
Asia Pacific ap- cloudsearch.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- cloudsearch.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- cloudsearch.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU eu-central-1 cloudsearch.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 cloudsearch.eu-west-1.amazonaws.com HTTPS
South sa-east-1 cloudsearch.sa-east-1.amazonaws.com HTTPS

America
(São Paulo)
AWS CloudTrail
Name
US East us-east-2 cloudtrail.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 cloudtrail.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 cloudtrail.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 cloudtrail.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- cloudtrail.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1

(Seoul) northeast-2

(Osaka- northeast-3
Local)
Asia Pacific ap-south-1 cloudtrail.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- cloudtrail.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- cloudtrail.ap-southeast-2.amazonaws.com HTTPS

Version 1.0
20
Amazon CloudWatch

Name
Canada ca-central-1 cloudtrail.ca-central-1.amazonaws.com HTTPS

(Central)
China cn-north-1 cloudtrail.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
China cn- cloudtrail.cn-northwest-1.amazonaws.com.cn HTTPS

EU eu-central-1 cloudtrail.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 cloudtrail.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 cloudtrail.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 cloudtrail.eu-west-3.amazonaws.com HTTPS
South sa-east-1 cloudtrail.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS us-gov- cloudtrail.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US)
For information about using AWS CloudTrail in the AWS GovCloud (US) Region, see AWS GovCloud (US)
Endpoints.
For information about using AWS CloudTrail in the China (Beijing) Region, see China (Beijing) Region
Endpoints.
Amazon CloudWatch
Name
US East us-east-2 monitoring.us-east-2.amazonaws.com HTTP and

(Ohio) HTTPS
US East (N. us-east-1 monitoring.us-east-1.amazonaws.com HTTP and

Virginia) HTTPS
US West (N. us-west-1 monitoring.us-west-1.amazonaws.com HTTP and

California) HTTPS
US West us-west-2 monitoring.us-west-2.amazonaws.com HTTP and

(Oregon) HTTPS
Asia Pacific ap- monitoring.ap-northeast-1.amazonaws.com HTTP and


Version 1.0
21
Amazon CloudWatch Events

Name

Local)
Asia Pacific ap-south-1 monitoring.ap-south-1.amazonaws.com HTTP and

(Mumbai) HTTPS
Asia Pacific ap- monitoring.ap-southeast-1.amazonaws.com HTTP and

Asia Pacific ap- monitoring.ap-southeast-2.amazonaws.com HTTP and

Canada ca-central-1 monitoring.ca-central-1.amazonaws.com HTTP and

(Central) HTTPS
China cn-north-1 monitoring.cn-north-1.amazonaws.com.cn HTTP and

(Beijing) HTTPS
China cn- monitoring.cn-northwest-1.amazonaws.com.cn HTTP and

EU eu-central-1 monitoring.eu-central-1.amazonaws.com HTTP and

(Frankfurt) HTTPS
EU (Ireland) eu-west-1 monitoring.eu-west-1.amazonaws.com HTTP and

HTTPS
EU (London) eu-west-2 monitoring.eu-west-2.amazonaws.com HTTP and

HTTPS
EU (Paris) eu-west-3 monitoring.eu-west-3.amazonaws.com HTTP and

HTTPS
South sa-east-1 monitoring.sa-east-1.amazonaws.com HTTP and

America HTTPS
(Sao Paulo)
AWS us-gov- monitoring.us-gov-west-1.amazonaws.com HTTP and

(US)

Name
US East us-east-2 events.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 events.us-east-1.amazonaws.com HTTPS

Virginia)
Version 1.0
22

Name
US West (N. us-west-1 events.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 events.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- events.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1

(Seoul) northeast-2

(Osaka- northeast-3
Local)
Asia Pacific ap-south-1 events.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- events.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- events.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 events.ca-central-1.amazonaws.com HTTPS

(Central)
China cn-north-1 events.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
China cn- events.cn-northwest-1.amazonaws.com.cn HTTPS

EU eu-central-1 events.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 events.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 events.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 events.eu-west-3.amazonaws.com HTTPS
South sa-east-1 events.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS us-gov- events.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US)
For information about using Amazon CloudWatch Events in the AWS GovCloud (US) Region, see AWS
Version 1.0
23
Amazon CloudWatch Logs

Name
US East us-east-2 logs.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 logs.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 logs.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 logs.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- logs.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1

(Seoul) northeast-2

(Osaka- northeast-3
Local)
Asia Pacific ap-south-1 logs.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- logs.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- logs.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 logs.ca-central-1.amazonaws.com HTTPS

(Central)
China cn-north-1 logs.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
China cn- logs.cn-northwest-1.amazonaws.com.cn HTTPS

EU eu-central-1 logs.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 logs.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 logs.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 logs.eu-west-3.amazonaws.com HTTPS
South sa-east-1 logs.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
Version 1.0
24
AWS CodeBuild

Name
AWS us-gov- logs.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US)
For information about using Amazon CloudWatch Logs in the AWS GovCloud (US) Region, see AWS
For information about using Amazon CloudWatch Logs in the China (Beijing) Region, see China (Beijing)
Region Endpoints.
AWS CodeBuild
Name
US East us-east-2 codebuild.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 codebuild.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 codebuild.us-west-2.amazonaws.com HTTPS

(Oregon)
EU (Ireland) eu-west-1 codebuild.eu-west-1.amazonaws.com HTTPS
Asia Pacific ap- codebuild.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Asia Pacific ap- codebuild.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap- codebuild.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- codebuild.ap-southeast-2.amazonaws.com HTTPS

EU eu-central-1 codebuild.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
US West (N. us-west-1 codebuild.us-west-1.amazonaws.com HTTPS

California)
EU (London) eu-west-2 codebuild.eu-west-2.amazonaws.com HTTPS
Canada ca-central-1 codebuild.ca-central-1.amazonaws.com HTTPS

(Central)
Version 1.0
25
AWS CodeCommit
AWS CodeCommit
Name
US East us-east-2 codecommit.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 codecommit.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 codecommit.us-west-2.amazonaws.com HTTPS

(Oregon)
EU (Ireland) eu-west-1 codecommit.eu-west-1.amazonaws.com HTTPS
Asia Pacific ap- codecommit.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Asia Pacific ap- codecommit.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- codecommit.ap-southeast-2.amazonaws.com HTTPS

EU eu-central-1 codecommit.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
Asia Pacific ap- codecommit.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
South sa-east-1 codecommit.sa-east-1.amazonaws.com HTTPS

America
(São Paulo)
US West (N. us-west-1 codecommit.us-west-1.amazonaws.com HTTPS

California)
EU (London) eu-west-2 codecommit.eu-west-2.amazonaws.com HTTPS
Asia Pacific ap-south-1 codecommit.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Canada ca-central-1 codecommit.ca-central-1.amazonaws.com HTTPS

(Central)
For information about Git connection endpoints, including SSH and HTTPS information, see Regions and
Git Connection Endpoints for AWS CodeCommit.
Version 1.0
26
AWS CodeDeploy
AWS CodeDeploy
Name
US East us-east-2 codedeploy.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 codedeploy.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 codedeploy.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 codedeploy.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- codedeploy.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1

(Seoul) northeast-2

(Osaka- northeast-3
Local)
Asia Pacific ap-south-1 codedeploy.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- codedeploy.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- codedeploy.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 codedeploy.ca-central-1.amazonaws.com HTTPS

(Central)
China cn-north-1 codedeploy.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
China cn- codedeploy.cn-northwest-1.amazonaws.com.cn HTTPS

EU eu-central-1 codedeploy.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 codedeploy.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 codedeploy.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 codedeploy.eu-west-3.amazonaws.com HTTPS
South sa-east-1 codedeploy.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
Version 1.0
27
AWS CodePipeline

Name
AWS us-gov- codedeploy.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US)
For information about using AWS CodeDeploy in the AWS GovCloud (US) Region, see AWS GovCloud (US)
Endpoints.
For information about using AWS CodeDeploy in the China (Beijing) Region, see China (Beijing) Region
Endpoints.
AWS CodePipeline
Name
US East us-east-2 codepipeline.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 codepipeline.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 codepipeline.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 codepipeline.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- codepipeline.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Asia Pacific ap- codepipeline.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap-south-1 codepipeline.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- codepipeline.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- codepipeline.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 codepipeline.ca-central-1.amazonaws.com HTTPS

(Central)
EU eu-central-1 codepipeline.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 codepipeline.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 codepipeline.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 codepipeline.eu-west-3.amazonaws.com HTTPS
Version 1.0
28
AWS CodeStar

Name
South sa-east-1 codepipeline.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS CodeStar
Name
US East us-east-2 codestar.us-east-2.amazonaws.com

(Ohio)
US East (N. us-east-1 codestar.us-east-1.amazonaws.com

Virginia)
US West (N. us-west-1 codestar.us-west-1.amazonaws.com

California)
US West us-west-2 codestar.us-west-2.amazonaws.com

(Oregon)
Asia Pacific ap- codestar.ap-northeast-1.amazonaws.com

(Tokyo) northeast-1
Asia Pacific ap- codestar.ap-northeast-2.amazonaws.com

(Seoul) northeast-2
Asia Pacific ap- codestar.ap-southeast-1.amazonaws.com

Asia Pacific ap- codestar.ap-southeast-2.amazonaws.com

Canada ca-central-1 codestar.ca-central-1.amazonaws.com

(Central)
EU eu-central-1 codestar.eu-central-1.amazonaws.com
(Frankfurt)
EU (Ireland) eu-west-1 codestar.eu-west-1.amazonaws.com
EU (London) eu-west-2 codestar.eu-west-2.amazonaws.com
Amazon Cognito Identity

Amazon Cognito Identity includes Amazon Cognito Your User Pools and Amazon Cognito Federated
Identities.
Version 1.0
29
Amazon Cognito Your User Pools

Name
US East us-east-2 cognito-idp.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 cognito-idp.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 cognito-idp.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap-south-1 cognito-idp.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- cognito-idp.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap- cognito-idp.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- cognito-idp.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- cognito-idp.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU eu-central-1 cognito-idp.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 cognito-idp.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 cognito-idp.eu-west-2.amazonaws.com HTTPS
Amazon Cognito Federated Identities

Name
US East us-east-2 cognito-identity.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 cognito-identity.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 cognito-identity.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap-south-1 cognito-identity.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- cognito-identity.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Version 1.0
30
Amazon Cognito Sync

Name
Asia Pacific ap- cognito-identity.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- cognito-identity.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- cognito-identity.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU eu-central-1 cognito-identity.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 cognito-identity.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 cognito-identity.eu-west-2.amazonaws.com HTTPS
Amazon Cognito Sync

Name
US East us-east-2 cognito-sync.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 cognito-sync.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 cognito-sync.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap-south-1 cognito-sync.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- cognito-sync.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap- cognito-sync.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- cognito-sync.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- cognito-sync.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU eu-central-1 cognito-sync.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 cognito-sync.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 cognito-sync.eu-west-2.amazonaws.com HTTPS
Version 1.0
31
Amazon Comprehend
Amazon Comprehend
Name
US East us-east-2 https://comprehend.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 https://comprehend.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 https://comprehend.us-west-2.amazonaws.com HTTPS

(Oregon)
EU (Ireland) eu-west-1 https://comprehend.eu-west-1.amazonaws.com HTTPS
AWS Config
Name
US East us-east-2 config.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 config.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 config.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 config.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- config.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Asia Pacific ap- config.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap-south-1 config.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- config.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- config.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 config.ca-central-1.amazonaws.com HTTPS

(Central)
China cn-north-1 config.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
China cn- config.cn-northwest-1.amazonaws.com.cn HTTPS

Version 1.0
32
AWS Config Rules

Name
EU eu-central-1 config.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 config.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 config.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 config.eu-west-3.amazonaws.com HTTPS
South sa-east-1 config.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS us-gov- config.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US)
For information about using AWS Config in the AWS GovCloud (US) Region, see AWS GovCloud (US)
Endpoints.
For information about using AWS Config in the China (Beijing) Region, see China (Beijing) Region
Endpoints.
AWS Config Rules

You can use AWS Config Rules to evaluate your AWS resource configurations in the following regions.

Name
US East us-east-2 configrules.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 configrules.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 configrules.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 configrules.us-west-2.amazonaws.com HTTPS

(Oregon)
Canada ca-central-1 configrules.ca-central-1.amazonaws.com HTTPS

(Central)
Asia Pacific ap-south-1 configrules.ap-south-1.amazonaws.com HTTPS

(Mumbai)
China cn-north-1 configrules.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
Asia Pacific ap- configrules.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Version 1.0
33
Amazon Connect

Name
Asia Pacific ap- configrules.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- configrules.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- configrules.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU eu-central-1 configrules.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 configrules.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 configrules.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 configrules.eu-west-3.amazonaws.com HTTPS
South sa-east-1 configrules.sa-east-1.amazonaws.com HTTPS

America
(São Paulo)
For information about using AWS Config Rules in the AWS GovCloud (US) Region, see AWS GovCloud
(US) Endpoints.
For information about using AWS Config Rules in the China (Beijing) Region, see China (Beijing) Region
Endpoints.
Amazon Connect
US East (N. Virginia) us-east-1 connect.us- HTTPS

US West (Oregon) us-west-2 connect.us- HTTPS

Asia Pacific (Sydney) ap-southeast-2 connect.ap- HTTPS

EU (Frankfurt) eu-central-1 connect.eu- HTTPS

Version 1.0
34
AWS Data Pipeline
AWS Data Pipeline

Name
US East (N. us-east-1 datapipeline.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 datapipeline.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- datapipeline.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- datapipeline.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU (Ireland) eu-west-1 datapipeline.eu-west-1.amazonaws.com HTTPS
AWS Database Migration Service

Name
US East us-east-2 dms.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 dms.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 dms.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 dms.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap-south-1 dms.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- dms.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap- dms.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- dms.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- dms.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Canada ca-central-1 dms.ca-central-1.amazonaws.com HTTPS

(Central)
EU eu-central-1 dms.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
Version 1.0
35
AWS Device Farm

Name
EU (Ireland) eu-west-1 dms.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 dms.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 dms.eu-west-3.amazonaws.com HTTPS
South sa-east-1 dms.sa-east-1.amazonaws.com HTTPS

America
(São Paulo)
AWS Device Farm

Name
US West us-west-2 devicefarm.us-west-2.amazonaws.com HTTPS

(Oregon)
Amazon DevPay
n/a n/a ls.amazonaws.com HTTPS
AWS Direct Connect

Name
US East us-east-2 directconnect.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 directconnect.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 directconnect.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 directconnect.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- directconnect.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Asia Pacific ap- directconnect.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Version 1.0
36
AWS Directory Service

Name
Asia Pacific ap-south-1 directconnect.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- directconnect.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- directconnect.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 directconnect.ca-central-1.amazonaws.com HTTPS

(Central)
China cn-north-1 directconnect.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
China cn- directconnect.cn-northwest-1.amazonaws.com.cn HTTPS

EU eu-central-1 directconnect.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 directconnect.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 directconnect.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 directconnect.eu-west-3.amazonaws.com HTTPS
South sa-east-1 directconnect.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS us-gov- directconnect.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US)
For information about using AWS Direct Connect in the AWS GovCloud (US) Region, see AWS GovCloud
(US) Endpoints.
For information about using AWS Direct Connect in the China (Beijing) Region, see China (Beijing) Region
Endpoints.

The following tables provide a list of region specific endpoints for the various AWS Directory Service
directory types.
AWS Directory Service for Microsoft Active Directory

Name
US East us-east-2 ds.us-east-2.amazonaws.com HTTPS

(Ohio)
Version 1.0
37

Name
US East (N. us-east-1 ds.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 ds.us-west-2.amazonaws.com HTTPS

(Oregon)
US West (N. us-west-1 ds.us-west-1.amazonaws.com HTTPS

California)
Canada ca-central-1 ds.ca-central-1.amazonaws.com HTTPS

(Central)
Asia Pacific ap-south-1 ds.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- ds.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap- ds.ap-southeast-1.amazonaws.com HTTPS



(Tokyo) northeast-1
EU eu-central-1 ds.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 ds.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 ds.eu-west-2.amazonaws.com HTTPS
South sa-east-1 ds.sa-east-1.amazonaws.com HTTPS

America
(São Paulo)
AD Connector

Name

Virginia)

(Oregon)


Version 1.0
38
Amazon DynamoDB

Name

(Tokyo) northeast-1
EU eu-central-1 ds.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (London) eu-west-2 ds.eu-west-2.amazonaws.com HTTPS
South sa-east-1 ds.sa-east-1.amazonaws.com HTTPS

America
(São Paulo)
Simple AD

Name

Virginia)

(Oregon)



(Tokyo) northeast-1
Amazon DynamoDB
Name
US East us-east-2 dynamodb.us-east-2.amazonaws.com HTTP and

(Ohio) HTTPS
US East (N. us-east-1 dynamodb.us-east-1.amazonaws.com HTTP and

Virginia) HTTPS
US West (N. us-west-1 dynamodb.us-west-1.amazonaws.com HTTP and

California) HTTPS
US West us-west-2 dynamodb.us-west-2.amazonaws.com HTTP and

(Oregon) HTTPS
Version 1.0
39
Amazon DynamoDB

Name
Asia Pacific ap- dynamodb.ap-northeast-1.amazonaws.com HTTP and



Local)
Asia Pacific ap-south-1 dynamodb.ap-south-1.amazonaws.com HTTP and

(Mumbai) HTTPS
Asia Pacific ap- dynamodb.ap-southeast-1.amazonaws.com HTTP and

Asia Pacific ap- dynamodb.ap-southeast-2.amazonaws.com HTTP and

Canada ca-central-1 dynamodb.ca-central-1.amazonaws.com HTTP and

(Central) HTTPS
China cn-north-1 dynamodb.cn-north-1.amazonaws.com.cn HTTP and

(Beijing) HTTPS
China cn- dynamodb.cn-northwest-1.amazonaws.com.cn HTTP and

EU eu-central-1 dynamodb.eu-central-1.amazonaws.com HTTP and

(Frankfurt) HTTPS
EU (Ireland) eu-west-1 dynamodb.eu-west-1.amazonaws.com HTTP and

HTTPS
EU (London) eu-west-2 dynamodb.eu-west-2.amazonaws.com HTTP and

HTTPS
EU (Paris) eu-west-3 dynamodb.eu-west-3.amazonaws.com HTTP and

HTTPS
South sa-east-1 dynamodb.sa-east-1.amazonaws.com HTTP and

America HTTPS
(Sao Paulo)
AWS us-gov- dynamodb.us-gov-west-1.amazonaws.com HTTP and

(US)
For information about using Amazon DynamoDB in the AWS GovCloud (US) Region, see AWS GovCloud
(US) Endpoints.
For information about using Amazon DynamoDB in the China (Beijing) Region, see China (Beijing) Region
Endpoints.
Version 1.0
40
DynamoDB Accelerator (DAX)
DynamoDB Accelerator (DAX)

Name
US East (N. us-east-1 dax.us-east-1.amazonaws.com HTTP and

Virginia) HTTPS
US West (N. us-west-1 dax.us-west-1.amazonaws.com HTTP and

California) HTTPS
US West us-west-2 dax.us-west-2.amazonaws.com HTTP and

(Oregon) HTTPS
Asia Pacific ap- dax.ap-northeast-1.amazonaws.com HTTP and

Asia Pacific ap-south-1 dax.ap-south-1.amazonaws.com HTTP and

(Mumbai) HTTPS
Asia Pacific ap- dax.ap-southeast-1.amazonaws.com HTTP and

Asia Pacific ap- dax.ap-southeast-2.amazonaws.com HTTP and

EU (Ireland) eu-west-1 dax.eu-west-1.amazonaws.com HTTP and

HTTPS
South sa-east-1 dax.sa-east-1.amazonaws.com HTTP and

America HTTPS
(Sao Paulo)
Amazon DynamoDB Streams

Name
US East us-east-2 streams.dynamodb.us-east-2.amazonaws.com HTTP and

(Ohio) HTTPS
US East (N. us-east-1 streams.dynamodb.us-east-1.amazonaws.com HTTP and

Virginia) HTTPS
US West (N. us-west-1 streams.dynamodb.us-west-1.amazonaws.com HTTP and

California) HTTPS
US West us-west-2 streams.dynamodb.us-west-2.amazonaws.com HTTP and

(Oregon) HTTPS
Asia Pacific ap-south-1 streams.dynamodb.ap-south-1.amazonaws.com HTTP and

(Mumbai) HTTPS
Asia Pacific ap- streams.dynamodb.ap-northeast-2.amazonaws.com HTTP and

Version 1.0
41
AWS Elastic Beanstalk

Name
Asia Pacific ap- streams.dynamodb.ap-southeast-1.amazonaws.com HTTP and

Asia Pacific ap- streams.dynamodb.ap-southeast-2.amazonaws.com HTTP and

Asia Pacific ap- streams.dynamodb.ap-northeast-1.amazonaws.com HTTP and

Canada ca-central-1 streams.dynamodb.ca-central-1.amazonaws.com HTTP and

(Central) HTTPS
EU eu-central-1 streams.dynamodb.eu-central-1.amazonaws.com HTTP and

(Frankfurt) HTTPS
EU (Ireland) eu-west-1 streams.dynamodb.eu-west-1.amazonaws.com HTTP and

HTTPS
EU (London) eu-west-2 streams.dynamodb.eu-west-2.amazonaws.com HTTP and

HTTPS
South sa-east-1 streams.dynamodb.sa-east-1.amazonaws.com HTTP and

America HTTPS
(São Paulo)
For information about using Amazon DynamoDB Streams in the AWS GovCloud (US) Region, see AWS
For information about using Amazon DynamoDB Streams in the China (Beijing) Region, see China
(Beijing) Region Endpoints.

Region Region Endpoint Protocol Route 53 Hosted
Name Zone ID
US East us-east-2 elasticbeanstalk.us- HTTPS Z14LCN19Q5QHIC

(Ohio) east-2.amazonaws.com
US East (N. us-east-1 elasticbeanstalk.us- HTTPS Z117KPS5GTRQ2G

Virginia) east-1.amazonaws.com
US West (N. us-west-1 elasticbeanstalk.us- HTTPS Z1LQECGX5PH1X

California) west-1.amazonaws.com
US West us-west-2 elasticbeanstalk.us- HTTPS Z38NKT9BP95V3O

(Oregon) west-2.amazonaws.com
Canada ca-central-1 elasticbeanstalk.ca- HTTPS ZJFCZL7SSZB5I

(Central) central-1.amazonaws.com
Asia Pacific ap-south-1 elasticbeanstalk.ap- HTTPS Z18NTBI3Y7N9TZ

(Mumbai) south-1.amazonaws.com
Version 1.0
42
AWS Elastic Beanstalk Health Service
Region Region Endpoint Protocol Route 53 Hosted

Name Zone ID
Asia Pacific ap- elasticbeanstalk.ap- HTTPS Z3JE5OI70TWKCP

(Seoul) northeast-2 northeast-2.amazonaws.com
Asia Pacific ap- elasticbeanstalk.ap- HTTPS ZNE5GEY1TIAGY

(Osaka- northeast-3 northeast-3.amazonaws.com
Local)
Asia Pacific ap- elasticbeanstalk.ap- HTTPS Z16FZ9L249IFLT

(Singapore) southeast-1 southeast-1.amazonaws.com
Asia Pacific ap- elasticbeanstalk.ap- HTTPS Z2PCDNR3VC2G1N

(Sydney) southeast-2 southeast-2.amazonaws.com
Asia Pacific ap- elasticbeanstalk.ap- HTTPS Z1R25G3KIG2GBW

(Tokyo) northeast-1 northeast-1.amazonaws.com
China cn- elasticbeanstalk.cn- HTTPS None

(Ningxia) northwest-1 northwest-1.amazonaws.com.cn
EU eu-central-1 elasticbeanstalk.eu- HTTPS Z1FRNW7UH4DEZJ

(Frankfurt) central-1.amazonaws.com
EU (Ireland) eu-west-1 elasticbeanstalk.eu- HTTPS Z2NYPWQ7DFZAZH

EU (London) eu-west-2 elasticbeanstalk.eu- HTTPS Z1GKAAAUGATPF1

EU (Paris) eu-west-3 elasticbeanstalk.eu- HTTPS Z5WN6GAYWG5OB

South sa-east-1 elasticbeanstalk.sa- HTTPS Z10X7K2B4QSOFV

America east-1.amazonaws.com
(São Paulo)
For information about using AWS Elastic Beanstalk in the China (Beijing) Region, see China (Beijing)
Region Endpoints.
AWS Elastic Beanstalk Health Service

Name
US East us-east-2 elasticbeanstalk-health.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 elasticbeanstalk-health.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 elasticbeanstalk-health.us-west-1.amazonaws.com HTTPS

California)
Version 1.0
43
Amazon Elastic Compute Cloud (Amazon EC2)

Name
US West us-west-2 elasticbeanstalk-health.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap-south-1 elasticbeanstalk-health.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- elasticbeanstalk-health.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2

(Osaka- northeast-3
Local)
Asia Pacific ap- elasticbeanstalk-health.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- elasticbeanstalk-health.ap-southeast-2.amazonaws.com HTTPS


(Tokyo) northeast-1
Canada ca-central-1 elasticbeanstalk-health.ca-central-1.amazonaws.com HTTPS

(Central)
EU eu-central-1 elasticbeanstalk-health.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 elasticbeanstalk-health.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 elasticbeanstalk-health.eu-west-2.amazonaws.com HTTPS
South sa-east-1 elasticbeanstalk-health.sa-east-1.amazonaws.com HTTPS

America
(São Paulo)

Name
US East us-east-2 ec2.us-east-2.amazonaws.com HTTP and

(Ohio) HTTPS
US East (N. us-east-1 ec2.us-east-1.amazonaws.com HTTP and

Virginia) HTTPS
US West (N. us-west-1 ec2.us-west-1.amazonaws.com HTTP and

California) HTTPS
US West us-west-2 ec2.us-west-2.amazonaws.com HTTP and

(Oregon) HTTPS
Version 1.0
44

Name
Asia Pacific ap- ec2.ap-northeast-1.amazonaws.com HTTP and



Local)
Asia Pacific ap-south-1 ec2.ap-south-1.amazonaws.com HTTP and

(Mumbai) HTTPS
Asia Pacific ap- ec2.ap-southeast-1.amazonaws.com HTTP and

Asia Pacific ap- ec2.ap-southeast-2.amazonaws.com HTTP and

Canada ca-central-1 ec2.ca-central-1.amazonaws.com HTTP and

(Central) HTTPS
China cn-north-1 ec2.cn-north-1.amazonaws.com.cn HTTP and

(Beijing) HTTPS
China cn- ec2.cn-northwest-1.amazonaws.com.cn HTTP and

EU eu-central-1 ec2.eu-central-1.amazonaws.com HTTP and

(Frankfurt) HTTPS
EU (Ireland) eu-west-1 ec2.eu-west-1.amazonaws.com HTTP and

HTTPS
EU (London) eu-west-2 ec2.eu-west-2.amazonaws.com HTTP and

HTTPS
EU (Paris) eu-west-3 ec2.eu-west-3.amazonaws.com HTTP and

HTTPS
South sa-east-1 ec2.sa-east-1.amazonaws.com HTTP and

America HTTPS
(Sao Paulo)
AWS us-gov- ec2.us-gov-west-1.amazonaws.com HTTP and

(US)
For information about using Amazon EC2 in the AWS GovCloud (US) Region, see AWS GovCloud (US)
Endpoints.
For information about using Amazon EC2 in the China (Beijing) Region, see China (Beijing) Region
Endpoints.
Version 1.0
45
Amazon Elastic Container Registry
Amazon Elastic Container Registry

Name
US East us-east-2 ecr.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 ecr.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 ecr.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 ecr.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- ecr.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Asia Pacific ap- ecr.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap-south-1 ecr.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- ecr.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- ecr.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 ecr.ca-central-1.amazonaws.com HTTPS

(Central)
China cn-north-1 ecr.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
EU eu-central-1 ecr.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 ecr.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 ecr.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 ecr.eu-west-3.amazonaws.com HTTPS
South sa-east-1 ecr.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS us-gov- ecr.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US)
For information about using Amazon Elastic Container Registry in the China (Beijing) Region, see China
Version 1.0
46
Amazon Elastic Container Service
Amazon Elastic Container Service

Name
US East us-east-2 ecs.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 ecs.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 ecs.us-west-2.amazonaws.com HTTPS

(Oregon)
US West (N. us-west-1 ecs.us-west-1.amazonaws.com HTTPS

California)
Canada ca-central-1 ecs.ca-central-1.amazonaws.com HTTPS

(Central)
EU eu-central-1 ecs.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 ecs.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 ecs.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 ecs.eu-west-3.amazonaws.com HTTPS
Asia Pacific ap- ecs.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap- ecs.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Asia Pacific ap- ecs.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- ecs.ap-southeast-1.amazonaws.com HTTPS

South sa-east-1 ecs.sa-east-1.amazonaws.com HTTPS

America
(São Paulo)
Asia Pacific ap-south-1 ecs.ap-south-1.amazonaws.com HTTPS

(Mumbai)
For information about using Amazon Elastic Container Service in the China (Beijing) Region, see China
Version 1.0
47
Amazon Elastic File System

Name
US East us-east-2 elasticfilesystem.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 elasticfilesystem.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 elasticfilesystem.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 elasticfilesystem.us-west-2.amazonaws.com HTTPS

(Oregon)
EU eu-central-1 elasticfilesystem.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 elasticfilesystem.eu-west-1.amazonaws.com HTTPS
Asia Pacific ap- elasticfilesystem.ap-southeast-2.amazonaws.com HTTPS

Elastic Load Balancing

Region Region Endpoint Protocol Route 53 Route 53
Name Hosted Zone Hosted Zone ID
ID (Application (Network Load
Load Balancers, Balancers)
Classic Load
Balancers)
US East us-east-2 elasticloadbalancing.us- HTTPS Z3AADJGX6KTTL2ZLMOA37VPKANP

(Ohio) east-2.amazonaws.com
US us-east-1 elasticloadbalancing.us- HTTPS Z35SXDOTRQ7X7KZ26RNL4JYFTOTI

East (N. east-1.amazonaws.com
Virginia)
US us-west-1 elasticloadbalancing.us- HTTPS Z368ELLRRE2KJ0 Z24FKFUX50B4VW

West (N. west-1.amazonaws.com
California)
US West us-west-2 elasticloadbalancing.us- HTTPS Z1H1FL5HABSF5 Z18D5FSROUN65G

(Oregon) west-2.amazonaws.com
Canada ca- elasticloadbalancing.ca- HTTPS ZQSVJUPU6J1EY Z2EPGBW3API2WT

(Central) central-1 central-1.amazonaws.com
Asia ap- elasticloadbalancing.ap- HTTPS ZP97RAFLXTNZK ZVDDRBQ08TROA

Pacific south-1 south-1.amazonaws.com
(Mumbai)
Version 1.0
48
Elastic Load Balancing
Region Region Endpoint Protocol Route 53 Route 53

Name Hosted Zone Hosted Zone ID
ID (Application (Network Load
Load Balancers, Balancers)
Classic Load
Balancers)
Asia ap- elasticloadbalancing.ap- HTTPS ZWKZPGTI48KDX ZIBE1TIR4HY56

Pacific northeast-2 northeast-2.amazonaws.com
(Seoul)
Asia ap- elasticloadbalancing.ap- HTTPS Z5LXEXXYW11ES None

(Osaka-
Local)
Asia ap- elasticloadbalancing.ap- HTTPS Z1LMS91P8CMLE5ZKVM4W9LS7TM

Pacific southeast-1 southeast-1.amazonaws.com
(Singapore)
Asia ap- elasticloadbalancing.ap- HTTPS Z1GM3OXH4ZPM65

ZCT6FZBF4DROD
Pacific southeast-2 southeast-2.amazonaws.com
(Sydney)
Asia ap- elasticloadbalancing.ap- HTTPS Z14GRHDCWA56QT

Z31USIVHYNEOWT
(Tokyo)
China cn- elasticloadbalancing.cn- HTTPS None None

(Beijing) north-1 north-1.amazonaws.com.cn
China cn- elasticloadbalancing.cn- HTTPS None None

(Ningxia) northwest-1northwest-1.amazonaws.com.cn
EU eu- elasticloadbalancing.eu- HTTPS Z215JYRZR1TBD5 Z3F0SRJ5LGBH90

(Frankfurt) central-1 central-1.amazonaws.com
EU eu-west-1 elasticloadbalancing.eu- HTTPS Z32O12XQLNTSW2

Z2IFOLAFXWLO4F
(Ireland) west-1.amazonaws.com
EU eu-west-2 elasticloadbalancing.eu- HTTPS ZHURV8PSTC4K8 ZD4D7Y8KGAS4G

(London) west-2.amazonaws.com
EU (Paris) eu-west-3 elasticloadbalancing.eu- HTTPS Z3Q77PNBQS71R4Z1CMS0P5QUZ6D5

South sa-east-1 elasticloadbalancing.sa- HTTPS Z2P70J7HTTTPLU ZTK26PT1VY4CU

America east-1.amazonaws.com
(São
Paulo)
If you just specify the general endpoint (elasticloadbalancing.amazonaws.com), Elastic Load Balancing
directs your request to the us-east-1 endpoint.
For information about using Elastic Load Balancing in the AWS GovCloud (US) Region, see AWS GovCloud
(US) Endpoints.
For information about using Elastic Load Balancing in the China (Beijing) Region, see China (Beijing)
Region Endpoints.
Version 1.0
49
Amazon Elastic Transcoder

Name
US East (N. us-east-1 elastictranscoder.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 elastictranscoder.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 elastictranscoder.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap-south-1 elastictranscoder.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- elastictranscoder.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- elastictranscoder.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- elastictranscoder.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU (Ireland) eu-west-1 elastictranscoder.eu-west-1.amazonaws.com HTTPS
Amazon ElastiCache
Name
US East us-east-2 elasticache.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 elasticache.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 elasticache.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 elasticache.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- elasticache.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1

(Seoul) northeast-2

(Osaka- northeast-3
Local)
Version 1.0
50
Amazon Elasticsearch Service

Name
Asia Pacific ap-south-1 elasticache.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- elasticache.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- elasticache.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 elasticache.ca-central-1.amazonaws.com HTTPS

(Central)
China cn-north-1 elasticache.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
China cn- elasticache.cn-northwest-1.amazonaws.com.cn HTTPS

EU eu-central-1 elasticache.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 elasticache.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 elasticache.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 elasticache.eu-west-3.amazonaws.com HTTPS
South sa-east-1 elasticache.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS us-gov- elasticache.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US)
Additional Information:
The Asia Pacific (Osaka-Local) Region is a local region that is available to select AWS customers who
request access. Customers wishing to use the Asia Pacific (Osaka-Local) Region should speak with their
sales representative. The Asia Pacific (Osaka-Local) Region supports a single availavility zone.
For information about using Amazon ElastiCache in the AWS GovCloud (US) Region, see AWS GovCloud
(US) Endpoints.

Name
US East us-east-2 es.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 es.us-east-1.amazonaws.com HTTPS

Virginia)
Version 1.0
51
Amazon EMR

Name
US West (N. us-west-1 es.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 es.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- es.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Asia Pacific ap- es.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap-south-1 es.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- es.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- es.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 es.ca-central-1.amazonaws.com HTTPS

(Central)
China cn- es.cn-northwest-1.amazonaws.com.cn HTTPS

EU eu-central-1 es.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 es.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 es.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 es.eu-west-3.amazonaws.com HTTPS
South sa-east-1 es.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS us-gov- es.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US)
Amazon EMR
Name
US East us-east-2 elasticmapreduce.us-east-2.amazonaws.com HTTP and

(Ohio) HTTPS
US East (N. us-east-1 elasticmapreduce.us-east-1.amazonaws.com HTTP and

Virginia) HTTPS
Version 1.0
52
Amazon EMR

Name
US West (N. us-west-1 elasticmapreduce.us-west-1.amazonaws.com HTTP and

California) HTTPS
US West us-west-2 elasticmapreduce.us-west-2.amazonaws.com HTTP and

(Oregon) HTTPS
Asia Pacific ap- elasticmapreduce.ap-northeast-1.amazonaws.com HTTP and



Local)
Asia Pacific ap-south-1 elasticmapreduce.ap-south-1.amazonaws.com HTTP and

(Mumbai) HTTPS
Asia Pacific ap- elasticmapreduce.ap-southeast-1.amazonaws.com HTTP and

Asia Pacific ap- elasticmapreduce.ap-southeast-2.amazonaws.com HTTP and

Canada ca-central-1 elasticmapreduce.ca-central-1.amazonaws.com HTTP and

(Central) HTTPS
China cn-north-1 elasticmapreduce.cn-north-1.amazonaws.com.cn HTTP and

(Beijing) HTTPS
China cn- elasticmapreduce.cn-northwest-1.amazonaws.com.cn HTTP and

EU eu-central-1 elasticmapreduce.eu-central-1.amazonaws.com HTTP and

(Frankfurt) HTTPS
EU (Ireland) eu-west-1 elasticmapreduce.eu-west-1.amazonaws.com HTTP and

HTTPS
EU (London) eu-west-2 elasticmapreduce.eu-west-2.amazonaws.com HTTP and

HTTPS
EU (Paris) eu-west-3 elasticmapreduce.eu-west-3.amazonaws.com HTTP and

HTTPS
South sa-east-1 elasticmapreduce.sa-east-1.amazonaws.com HTTP and

America HTTPS
(Sao Paulo)
AWS us-gov- elasticmapreduce.us-gov-west-1.amazonaws.com HTTP and

(US)
Version 1.0
53
Amazon GameLift
If you specify the general endpoint (elasticmapreduce.amazonaws.com), Amazon EMR directs your
request to an endpoint in the default region. For accounts created on or after March 8, 2013, the default
region is us-west-2; for older accounts, the default region is us-east-1.
For information about using Amazon EMR in the AWS GovCloud (US) Region, see AWS GovCloud (US)
Endpoints.
For information about using Amazon EMR in the China (Beijing) Region, see China (Beijing) Region
Endpoints.
Amazon GameLift
Name
US East us-east-2 gamelift.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 gamelift.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 gamelift.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 gamelift.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap-south-1 gamelift.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- gamelift.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap- gamelift.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- gamelift.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- gamelift.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Canada ca-central-1 gamelift.ca-central-1.amazonaws.com HTTPS

(Central)
EU eu-central-1 gamelift.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 gamelift.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 gamelift.eu-west-2.amazonaws.com HTTPS
South sa-east-1 gamelift.sa-east-1.amazonaws.com HTTPS

America
(São Paulo)
Version 1.0
54
Amazon Glacier
Amazon Glacier
Name
US East us-east-2 glacier.us-east-2.amazonaws.com HTTP and

(Ohio) HTTPS
US East (N. us-east-1 glacier.us-east-1.amazonaws.com HTTP and

Virginia) HTTPS
US West (N. us-west-1 glacier.us-west-1.amazonaws.com HTTP and

California) HTTPS
US West us-west-2 glacier.us-west-2.amazonaws.com HTTP and

(Oregon) HTTPS
Asia Pacific ap- glacier.ap-northeast-1.amazonaws.com HTTP and



Local)
Asia Pacific ap-south-1 glacier.ap-south-1.amazonaws.com HTTP and

(Mumbai) HTTPS
Asia Pacific ap- glacier.ap-southeast-1.amazonaws.com HTTP and

Asia Pacific ap- glacier.ap-southeast-2.amazonaws.com HTTP and

Canada ca-central-1 glacier.ca-central-1.amazonaws.com HTTP and

(Central) HTTPS
China cn-north-1 glacier.cn-north-1.amazonaws.com.cn HTTP and

(Beijing) HTTPS
China cn- glacier.cn-northwest-1.amazonaws.com.cn HTTP and

EU eu-central-1 glacier.eu-central-1.amazonaws.com HTTP and

(Frankfurt) HTTPS
EU (Ireland) eu-west-1 glacier.eu-west-1.amazonaws.com HTTP and

HTTPS
EU (London) eu-west-2 glacier.eu-west-2.amazonaws.com HTTP and

HTTPS
EU (Paris) eu-west-3 glacier.eu-west-3.amazonaws.com HTTP and

HTTPS
Version 1.0
55
AWS Glue

Name
AWS us-gov- glacier.us-gov-west-1.amazonaws.com HTTP and

(US)
For information about using Amazon Glacier in the AWS GovCloud (US) Region, see AWS GovCloud (US)
Endpoints.
For information about using Amazon Glacier in the China (Beijing) Region, see China (Beijing) Region
Endpoints.
AWS Glue
Name
US East us-east-2 glue.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 glue.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 glue.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- glue.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU (Ireland) eu-west-1 glue.eu-west-1.amazonaws.com HTTPS
AWS Greengrass
The following table provides a list of region-specific endpoints that AWS Greengrass supports for
working with group management.
US East (N. us-east-1 greengrass.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 greengrass.us-west-2.amazonaws.com HTTPS

(Oregon)
EU (Frankfurt) eu-central-1 greengrass.eu-central-1.amazonaws.com HTTPS
Asia Pacific ap-southeast-2 greengrass.ap-southeast-2.amazonaws.com HTTPS

(Sydney)
Asia Pacific ap-northeast-1 greengrass.ap-northeast-1.amazonaws.com HTTPS

(Tokyo)
Version 1.0
56
Amazon GuardDuty
The following table provides a list of region-specific endpoints that AWS Greengrass utilizes for working
with AWS IoT operations. To look up your account-specific prefix, use the describe-endpoint command.
US East (N. us-east-1 prefix.iot.us-east-1.amazonaws.com HTTPS, MQTT

Virginia)
US West us-west-2 prefix.iot.us-west-2.amazonaws.com HTTPS, MQTT

(Oregon)
EU (Frankfurt) eu-central-1 prefix.iot.eu-central-1.amazonaws.com HTTPS, MQTT
Asia Pacific ap-southeast-2 prefix.iot.ap-southeast-2.amazonaws.com HTTPS, MQTT

(Sydney)
Asia Pacific ap-northeast-1 prefix.iot.ap-northeast-1.amazonaws.com HTTPS, MQTT

(Tokyo)
The following table provides a list of region-specific endpoints that AWS Greengrass supports for
working with AWS Greengrass specific runtime operations, such as AWS Greengrass Device Discovery
feature.
US East (N. us-east-1 greengrass.iot.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 greengrass.iot.us-west-2.amazonaws.com HTTPS

(Oregon)
EU (Frankfurt) eu-central-1 greengrass.iot.eu-central-1.amazonaws.com HTTPS
Asia Pacific ap-southeast-2 greengrass.iot.ap-southeast-2.amazonaws.com HTTPS

(Sydney)
Asia Pacific ap-northeast-1 greengrass.iot.ap-northeast-1.amazonaws.com HTTPS

(Tokyo)
Amazon GuardDuty
Name
Asia Pacific ap-south-1 guardduty.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- guardduty.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap- guardduty.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- guardduty.ap-southeast-2.amazonaws.com HTTPS

Version 1.0
57
AWS Health

Name
Asia Pacific ap- guardduty.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Canada ca-central-1 guardduty.ca-central-1.amazonaws.com HTTPS

(Central)
EU eu-central-1 guardduty.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 guardduty.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 guardduty.eu-west-2.amazonaws.com HTTPS
US East (N. us-east-1 guardduty.us-east-1.amazonaws.com HTTPS

Virginia)
US East us-east-2 guardduty.us-east-2.amazonaws.com HTTPS

(Ohio)
US West (N. us-west-1 guardduty.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 guardduty.us-west-2.amazonaws.com HTTPS

(Oregon)
South sa-east-1 guardduty.sa-east-1.amazonaws.com HTTPS

America
(São Paulo)
AWS Health
AWS Health has a single endpoint: health.us-east-1.amazonaws.com (HTTPS).
AWS Identity and Access Management (IAM)

Name
US East us-east-2 iam.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 iam.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 iam.amazonaws.com HTTPS

California)
US West us-west-2 iam.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- iam.amazonaws.com HTTPS

(Tokyo) northeast-1
Version 1.0
58
AWS Import/Export

Name

(Seoul) northeast-2

(Osaka- northeast-3
Local)
Asia Pacific ap-south-1 iam.amazonaws.com HTTPS

(Mumbai)


Canada ca-central-1 iam.amazonaws.com HTTPS

(Central)
China cn-north-1 iam.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
China cn- iam.cn-north-1.amazonaws.com.cn HTTPS

EU eu-central-1 iam.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 iam.amazonaws.com HTTPS
EU (London) eu-west-2 iam.amazonaws.com HTTPS
EU (Paris) eu-west-3 iam.amazonaws.com HTTPS
South sa-east-1 iam.amazonaws.com HTTPS

America
(Sao Paulo)
AWS us-gov- iam.us-gov.amazonaws.com HTTPS

GovCloud west-1
(US)
AWS Import/Export
AWS Snowball is a standalone service now. For region information on that service, see AWS
Snowball (p. 95).
AWS Import/Export Disk

AWS Import/Export Disk has a single endpoint for all regions.
Endpoint Protocol
importexport.amazonaws.com HTTPS
Version 1.0
59
Amazon Inspector
Amazon Inspector
Name
US East (N. us-east-1 inspector.us-east-1.amazonaws.com HTTPS

Virginia)
US East us-east-2 inspector.us-east-2.amazonaws.com HTTPS

(Ohio)
US West (N. us-west-1 inspector.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 inspector.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap-south-1 inspector.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- inspector.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap- inspector.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- inspector.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU (Ireland) eu-west-1 inspector.eu-west-1.amazonaws.com HTTPS
EU eu-central-1 inspector.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
AWS IoT
The following table provides a list of region-specific endpoints that AWS IoT supports for working with
rules, certificates, and policies.
US East (Ohio) us-east-2 iot.us-east-2.amazonaws.com HTTPS
US East (N. us-east-1 iot.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 iot.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap-southeast-1 iot.ap-southeast-1.amazonaws.com HTTPS

(Singapore)
Asia Pacific ap-southeast-2 iot.ap-southeast-2.amazonaws.com HTTPS

(Sydney)
Version 1.0
60
AWS IoT
Asia Pacific ap-northeast-1 iot.ap-northeast-1.amazonaws.com HTTPS

(Tokyo)
Asia Pacific ap-northeast-2 iot.ap-northeast-2.amazonaws.com HTTPS

(Seoul)
EU (Frankfurt) eu-central-1 iot.eu-central-1.amazonaws.com HTTPS
EU (Ireland) eu-west-1 iot.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 iot.eu-west-2.amazonaws.com HTTPS
China (Beijing) cn-north-1 iot.cn-north-1.amazonaws.com.cn HTTPS
The following table provides a list of region-specific endpoints that AWS IoT supports for working with
thing shadows. To look up your account-specific prefix, use the describe-endpoint command.
US East (Ohio) us-east-2 prefix.iot.us-east-2.amazonaws.com HTTPS, MQTT
US East (N. us-east-1 prefix.iot.us-east-1.amazonaws.com HTTPS, MQTT

Virginia)
US West us-west-2 prefix.iot.us-west-2.amazonaws.com HTTPS, MQTT

(Oregon)

(Singapore)

(Sydney)

(Tokyo)

(Seoul)
EU (Frankfurt) eu-central-1 prefix.iot.eu-central-1.amazonaws.com HTTPS, MQTT
EU (Ireland) eu-west-1 prefix.iot.eu-west-1.amazonaws.com HTTPS, MQTT
EU (London) eu-west-2 prefix.iot.eu-west-2.amazonaws.com HTTPS, MQTT
China (Beijing) cn-north-1 prefix.iot.cn-north-1.amazonaws.com.cn HTTPS, MQTT
AWS IoT supports multiple protocols for accessing the message broker and the Thing Shadows service.
The following table lists the ports to use for each protocol.
Port Protocol Authentication Mechanism
443 HTTPS Signature Version 4
Version 1.0
61
AWS Key Management Service
Port Protocol Authentication Mechanism
443 MQTT over Signature Version 4

WebSocket
8443 HTTPS TLS client authentication, with certificates
8883 MQTT TLS client authentication, with certificates
AWS Key Management Service

Region Region Endpoints Protocol
Name
US East (N. us-east-1 kms.us-east-1.amazonaws.com HTTPS

Virginia)
kms-fips.us-east-1.amazonaws.com
US East us-east-2 kms.us-east-2.amazonaws.com HTTPS

(Ohio)
kms-fips.us-east-2.amazonaws.com
US West (N. us-west-1 kms.us-west-1.amazonaws.com HTTPS

California)
kms-fips.us-west-1.amazonaws.com
US West us-west-2 kms.us-west-2.amazonaws.com HTTPS

(Oregon)
kms-fips.us-west-2.amazonaws.com
Asia Pacific ap- kms.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
kms-fips.ap-northeast-1.amazonaws.com

(Seoul) northeast-2
kms-fips.ap-northeast-2.amazonaws.com

(Osaka- northeast-3
Local) kms-fips.ap-northeast-3.amazonaws.com
Asia Pacific ap-south-1 kms.ap-south-1.amazonaws.com HTTPS

(Mumbai)
kms-fips.ap-south-1.amazonaws.com
Asia Pacific ap- kms.ap-southeast-1.amazonaws.com HTTPS

kms-fips.ap-southeast-1.amazonaws.com
Asia Pacific ap- kms.ap-southeast-2.amazonaws.com HTTPS

kms-fips.ap-southeast-2.amazonaws.com
Canada ca-central-1 kms.ca-central-1.amazonaws.com HTTPS

(Central)
kms-fips.ca-central-1.amazonaws.com
Version 1.0
62
Amazon Kinesis Data Analytics
Region Region Endpoints Protocol

Name
EU eu-central-1 kms.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
kms-fips.eu-central-1.amazonaws.com
EU (Ireland) eu-west-1 kms.eu-west-1.amazonaws.com HTTPS
kms-fips.eu-west-1.amazonaws.com
EU (London) eu-west-2 kms.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 kms.eu-west-3.amazonaws.com HTTPS
South sa-east-1 kms.sa-east-1.amazonaws.com HTTPS

America
(São Paulo) kms-fips.sa-east-1.amazonaws.com
AWS us-gov- kms.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US) kms-fips.us-gov-west-1.amazonaws.com
For information about using AWS Key Management Service in the AWS GovCloud (US) Region, see AWS
Amazon Kinesis Data Analytics

Name
US East (N. us-east-1 kinesisanalytics.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 kinesisanalytics.us-west-2.amazonaws.com HTTPS

(Oregon)
EU (Ireland) eu-west-1 kinesisanalytics.eu-west-1.amazonaws.com HTTPS
Amazon Kinesis Data Firehose

Name
US East (N. us-east-1 firehose.us-east-1.amazonaws.com HTTPS

Virginia)
US East us-east-2 firehose.us-east-2.amazonaws.com HTTPS

(Ohio)
Version 1.0
63
Amazon Kinesis Data Streams

Name
US West (N. us-west-1 firehose.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 firehose.us-west-2.amazonaws.com HTTPS

(Oregon)
EU (Ireland) eu-west-1 firehose.eu-west-1.amazonaws.com HTTPS
EU eu-central-1 firehose.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
Asia Pacific ap- firehose.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Asia Pacific ap- firehose.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- firehose.ap-southeast-2.amazonaws.com HTTPS

Amazon Kinesis Data Streams

Name
US East us-east-2 kinesis.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 kinesis.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 kinesis.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 kinesis.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- kinesis.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1

(Seoul) northeast-2

(Osaka- northeast-3
Local)
Asia Pacific ap-south-1 kinesis.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- kinesis.ap-southeast-1.amazonaws.com HTTPS

Version 1.0
64
Amazon Kinesis Video Streams

Name
Asia Pacific ap- kinesis.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 kinesis.ca-central-1.amazonaws.com HTTPS

(Central)
China cn-north-1 kinesis.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
China cn- kinesis.cn-northwest-1.amazonaws.com.cn HTTPS

EU eu-central-1 kinesis.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 kinesis.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 kinesis.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 kinesis.eu-west-3.amazonaws.com HTTPS
South sa-east-1 kinesis.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS us-gov- kinesis.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US)
For information about using Amazon Kinesis Data Streams in the AWS GovCloud (US) Region, see AWS
For information about using Amazon Kinesis Data Streams in the China (Beijing) Region, see China
Amazon Kinesis Video Streams

Name
US East (N. us-east-1 kinesisvideo.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 kinesisvideo.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- kinesisvideo.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU eu-central-1 kinesisvideo.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 kinesisvideo.eu-west-1.amazonaws.com HTTPS
Version 1.0
65
AWS Lambda
AWS Lambda
Name
US East us-east-2 lambda.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 lambda.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 lambda.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 lambda.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- lambda.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Asia Pacific ap- lambda.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap-south-1 lambda.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- lambda.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- lambda.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 lambda.ca-central-1.amazonaws.com HTTPS

(Central)
China cn-north-1 lambda.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
EU eu-central-1 lambda.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 lambda.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 lambda.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 lambda.eu-west-3.amazonaws.com HTTPS
South sa-east-1 lambda.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS us-gov- lambda.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US)
For information about using AWS Lambda in the AWS GovCloud (US) Region, see AWS GovCloud (US)
Endpoints.
Version 1.0
66
Amazon Lex
Amazon Lex
Name
US East (N. us-east-1 models.lex.us-east-1.amazonaws.com HTTPS

Virginia)
EU (Ireland) eu-west-1 models.lex.eu-west-1.amazonaws.com HTTPS
US East (N. us-east-1 runtime.lex.us-east-1.amazonaws.com HTTPS

Virginia)
EU (Ireland) eu-west-1 runtime.lex.eu-west-1.amazonaws.com HTTPS
Amazon Lightsail
Name
US East us-east-2 lightsail.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 lightsail.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 lightsail.us-west-2.amazonaws.com HTTPS

(Oregon)
EU eu-central-1 lightsail.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 lightsail.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 lightsail.eu-west-2.amazonaws.com HTTPS
Asia Pacific ap-south-1 lightsail.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- lightsail.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- lightsail.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- lightsail.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Version 1.0
67
Amazon Machine Learning
Amazon Machine Learning

Name
US East (N. us-east-1 machinelearning.us-east-1.amazonaws.com HTTPS

Virginia)
EU (Ireland) eu-west-1 machinelearning.eu-west-1.amazonaws.com HTTPS
AWS Elemental MediaConvert

Name
US East (N. us-east-1 mediaconvert.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 mediaconvert.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 mediaconvert.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap-south-1 mediaconvert.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- mediaconvert.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- mediaconvert.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- mediaconvert.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU eu-central-1 mediaconvert.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 mediaconvert.eu-west-1.amazonaws.com HTTPS
AWS Elemental MediaLive

Name
US East (N. us-east-1 medialive.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 medialive.us-west-2.amazonaws.com HTTPS

(Oregon)
Version 1.0
68
AWS Elemental MediaPackage

Name
Asia Pacific ap- medialive.ap-southeast-1.amazonaws.com HTTPS

EU (Ireland) eu-west-1 medialive.eu-west-1.amazonaws.com HTTPS

Name
US East (N. us-east-1 mediapackage.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 mediapackage.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- mediapackage.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- mediapackage.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- mediapackage.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU eu-central-1 mediapackage.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 mediapackage.eu-west-1.amazonaws.com HTTPS
EU (Paris) eu-west-3 mediapackage.eu-west-3.amazonaws.com HTTPS
AWS Elemental MediaStore

Name
US East (N. us-east-1 mediastore.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 mediastore.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- mediastore.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- mediastore.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU eu-central-1 mediastore.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
Version 1.0
69
AWS Elemental MediaTailor

Name
EU (Ireland) eu-west-1 mediastore.eu-west-1.amazonaws.com HTTPS

Name
US East (N. us-east-1 mediatailor.us-east-1.amazonaws.com HTTPS

Virginia)
Asia Pacific ap- mediatailor.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- mediatailor.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- mediatailor.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU (Ireland) eu-west-1 mediatailor.eu-west-1.amazonaws.com HTTPS
Amazon Mechanical Turk

Region Endpoint Protocol
Sandbox endpoint mturk-requester-sandbox.us-east-1.amazonaws.com HTTPS

for Amazon
Mechanical Turk
actions.
Production mturk-requester.us-east-1.amazonaws.com HTTPS

endpoint for
Amazon Mechanical
Turk actions.
AWS Migration Hub

AWS Migration Hub helps you monitor the status of your migrations in all AWS public regions, provided
your migration tools are available in that region. The migration tools that integrate with Migration Hub
send migration status to the Migration Hub in US West (Oregon). There, the status is aggregated and
visible in a single location.

Name
US West us-west-2 mgh.us-west-2.amazonaws.com HTTPS

(Oregon)
Version 1.0
70
Amazon Mobile Analytics
Amazon Mobile Analytics

Name
US East (N. us-east-1 mobileanalytics.us-east-1.amazonaws.com HTTPS

Virginia)
Amazon MQ
Name
US East us-east-2 mq.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 mq.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 mq.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- mq.ap-southeast-2.amazonaws.com HTTPS

EU eu-central-1 mq.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 mq.eu-west-1.amazonaws.com HTTPS
AWS OpsWorks
AWS OpsWorks uses the following regional endpoints.
AWS OpsWorks CM
You can create and manage AWS OpsWorks for Chef Automate and AWS OpsWorks for Puppet
Enterprise servers in the following regions. Resources can be managed only in the region in which they
are created. Resources that are created in one regional endpoint are not available, nor can they be cloned
to, another regional endpoint.

Name
US East (N. us-east-1 opsworks-cm.us-east-1.amazonaws.com HTTPS

Virginia)
Region
US East us-east-2 opsworks-cm.us-east-2.amazonaws.com HTTPS

(Ohio)
Region
Version 1.0
71
AWS OpsWorks Stacks

Name
US West (N. us-west-1 opsworks-cm.us-west-1.amazonaws.com HTTPS

California)
Region
US West us-west-2 opsworks-cm.us-west-2.amazonaws.com HTTPS

(Oregon)
Region
Asia Pacific ap- opsworks-cm.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Region
Asia Pacific ap- opsworks-cm.ap-southeast-1.amazonaws.com HTTPS

Region
Asia Pacific ap- opsworks-cm.ap-southeast-2.amazonaws.com HTTPS

Region
EU eu-central-1 opsworks-cm.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
Region
EU (Ireland) eu-west-1 opsworks-cm.eu-west-1.amazonaws.com HTTPS

Region
AWS OpsWorks Stacks

You can create and manage AWS OpsWorks resources in all regions except AWS GovCloud (US) and
the China (Beijing) Region. The Canada (Central) Region region is API-only; you cannot create stacks in
Canada (Central) Region by using the AWS Management Console. Resources can be managed only in the
region in which they are created. Resources that are created in one regional endpoint are not available,
nor can they be cloned to, another regional endpoint.

Name
US East us-east-2 opsworks.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 opsworks.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 opsworks.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 opsworks.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- opsworks.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Version 1.0
72
AWS Organizations

Name
Asia Pacific ap- opsworks.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap-south-1 opsworks.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- opsworks.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- opsworks.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 opsworks.ca-central-1.amazonaws.com HTTPS

(Central)
EU eu-central-1 opsworks.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 opsworks.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 opsworks.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 opsworks.eu-west-3.amazonaws.com HTTPS
South sa-east-1 opsworks.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS Organizations
Name
US East us-east-2 organizations.us-east-1.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 organizations.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 organizations.us-east-1.amazonaws.com HTTPS

California)
US West us-west-2 organizations.us-east-1.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- organizations.us-east-1.amazonaws.com HTTPS

(Tokyo) northeast-1

(Seoul) northeast-2
Asia Pacific ap-south-1 organizations.us-east-1.amazonaws.com HTTPS

(Mumbai)
Version 1.0
73
Amazon Pinpoint

Name


Canada ca-central-1 organizations.us-east-1.amazonaws.com HTTPS

(Central)
EU eu-central-1 organizations.us-east-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 organizations.us-east-1.amazonaws.com HTTPS
EU (London) eu-west-2 organizations.us-east-1.amazonaws.com HTTPS
South sa-east-1 organizations.us-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
Amazon Pinpoint
Name
US East (N. us-east-1 pinpoint.us-east-1.amazonaws.com HTTPS

Virginia)
Amazon Polly
Name
US East (N. us-east-1 polly.us-east-1.amazonaws.com HTTPS

Virginia)
US East us-east-2 polly.us-east-2.amazonaws.com HTTPS

(Ohio)
US West (N. us-west-1 polly.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 polly.us-west-2.amazonaws.com HTTPS

(Oregon)
Canada ca-central-1 polly.ca-central-1.amazonaws.com HTTPS

(Central)
EU (Ireland) eu-west-1 polly.eu-west-1.amazonaws.com HTTPS
Version 1.0
74
Amazon QuickSight

Name
EU eu-central-1 polly.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (London) eu-west-2 polly.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 polly.eu-west-3.amazonaws.com HTTPS
Asia Pacific ap- polly.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- polly.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- polly.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap- polly.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Asia Pacific ap-south-1 polly.ap-south-1.amazonaws.com HTTPS

(Mumbai)
South sa-east-1 polly.sa-east-1.amazonaws.com HTTPS

America
(São Paulo)
Amazon QuickSight
Name
US East us-east-2 us-east-2.quicksight.aws.amazon.com HTTPS

(Ohio)
US East (N. us-east-1 us-east-1.quicksight.aws.amazon.com HTTPS

Virginia)
US West us-west-2 us-west-2.quicksight.aws.amazon.com HTTPS

(Oregon)
EU (Ireland) eu-west-1 eu-west-1.quicksight.aws.amazon.com HTTPS
Amazon Redshift
Name
US East us-east-2 redshift.us-east-2.amazonaws.com HTTPS

(Ohio)
Version 1.0
75
Amazon Redshift

Name
US East (N. us-east-1 redshift.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 redshift.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 redshift.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- redshift.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1

(Seoul) northeast-2

(Osaka- northeast-3
Local)
Asia Pacific ap-south-1 redshift.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- redshift.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- redshift.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 redshift.ca-central-1.amazonaws.com HTTPS

(Central)
China cn-north-1 redshift.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
China cn- redshift.cn-northwest-1.amazonaws.com.cn HTTPS

EU eu-central-1 redshift.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 redshift.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 redshift.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 redshift.eu-west-3.amazonaws.com HTTPS
South sa-east-1 redshift.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS us-gov- redshift.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US)
For information about using Amazon Redshift in the AWS GovCloud (US) Region, see AWS GovCloud (US)
Endpoints.
Version 1.0
76
Amazon Rekognition
For information about using Amazon Redshift in the China (Beijing) Region, see China (Beijing) Region
Endpoints.
Amazon Rekognition
The Amazon Rekognition Video streaming API is not available in the US East (Ohio) region.

Name
US East us-east-2 rekognition.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 rekognition.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 rekognition.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- rekognition.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- rekognition.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU (Ireland) eu-west-1 rekognition.eu-west-1.amazonaws.com HTTPS
For information about using Amazon Rekognition in the AWS GovCloud (US) Region, see AWS GovCloud
(US) Endpoints.
Amazon Relational Database Service (Amazon

RDS)
Name

(Ohio)

Virginia)
US West (N. us-west-1 rds.us-west-1.amazonaws.com HTTPS

California)

(Oregon)

(Tokyo) northeast-1

(Seoul) northeast-2
Version 1.0
77
AWS Resource Groups

Name

(Osaka- northeast-3
Local)

(Mumbai)



(Central)
China cn-north-1 rds.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
China cn- rds.cn-northwest-1.amazonaws.com.cn HTTPS


(Frankfurt)
South sa-east-1 rds.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS us-gov- rds.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US)
For information about using Amazon Relational Database Service in the AWS GovCloud (US) Region, see
For information about using Amazon Relational Database Service in the China (Beijing) Region, see China
AWS Resource Groups

AWS Resource Groups is available in all commercial AWS regions.

Name
US East us-east-2 resource-groups.us-east-2.amazonaws.com HTTPS

(Ohio)
Version 1.0
78
Amazon Route 53

Name
US East (N. us-east-1 resource-groups.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 resource-groups.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 resource-groups.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap-south-1 resource-groups.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- resource-groups.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap- resource-groups.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- resource-groups.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- resource-groups.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Canada ca-central-1 resource-groups.ca-central-1.amazonaws.com HTTPS

(Central)
EU eu-central-1 resource-groups.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 resource-groups.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 resource-groups.eu-west-2.amazonaws.com HTTPS
South sa-east-1 resource-groups.sa-east-1.amazonaws.com HTTPS

America
(São Paulo)
Amazon Route 53
The endpoint that you use depends on the operation that you want to perform.
Requests for hosted zones, resource record sets, health checks, and cost allocation tags use the following
endpoint:
US East (N. us-east-1 route53.amazonaws.com HTTPS

Virginia)
Requests for domain registration use the following endpoint:
Version 1.0
79
AWS Server Migration Service
US East (N. us-east-1 route53domains.us-east-1.amazonaws.com HTTPS

Virginia)
Requests for auto naming use the following endpoints:
EU (Ireland) eu-west-1 servicediscovery.eu-west-1.amazonaws.com HTTPS
US East (N. us-east-1 servicediscovery.us-east-1.amazonaws.com HTTPS

Virginia)
US East (Ohio) us-east-2 servicediscovery.us-east-2.amazonaws.com HTTPS
US West us-west-2 servicediscovery.us-west-2.amazonaws.com HTTPS

(Oregon)
AWS Server Migration Service

Name
US East us-east-2 sms.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 sms.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 sms.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 sms.us-west-2.amazonaws.com HTTPS

(Oregon)
Canada ca-central-1 sms.ca-central-1.amazonaws.com HTTPS

(Central)
Asia Pacific ap-south-1 sms.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- sms.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap- sms.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- sms.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU eu-central-1 sms.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
Version 1.0
80
Amazon SageMaker

Name
EU (Ireland) eu-west-1 sms.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 sms.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 sms.eu-west-3.amazonaws.com HTTPS
Amazon SageMaker
The following table provides a list of region-specific endpoints that Amazon SageMaker supports for
training and deploying models. This include creating and managing notebook instances, training jobs,
model, endpoint configurations, and endpoints.
US East (N. Virginia) us-east-1 sagemaker.us- HTTPS

US East (Ohio) us-east-2 sagemaker.us- HTTPS

US West (Oregon) us-west-2 sagemaker.us- HTTPS

EU (Ireland) eu-west-1 sagemaker.eu- HTTPS

The following table provides a list of region-specific endpoints that Amazon SageMaker supports for
making inference requests against models hosted in Amazon SageMaker.

Name
US East (N. us-east-1 runtime.sagemaker.us-east-1.amazonaws.com HTTPS

Virginia)
US East us-east-2 runtime.sagemaker.us-east-2.amazonaws.com HTTPS

(Ohio)
US West us-west-2 runtime.sagemaker.us-west-2.amazonaws.com HTTPS

(Oregon)
EU (Ireland) eu-west-1 runtime.sagemaker.eu-west-1.amazonaws.com HTTPS
AWS Security Token Service (AWS STS)

The default endpoint for AWS Security Token Service is https://sts.amazonaws.com, which serves all
global requests. You can also make calls to other regional endpoints that are activated for your AWS
account. All regions are activated by default, but you can deactivate regions that you do not intend to
Version 1.0
81
AWS Security Token Service (AWS STS)
use. If you deactivate a region, you must reactivate it for your account in the AWS Management Console
before you can use that region’s endpoint.
For more information, see Activating and Deactivating AWS STS in an AWS Region in the IAM User Guide.

Name
--Global-- --Global-- sts.amazonaws.com HTTPS
US East us-east-2 sts.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 sts.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 sts.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 sts.us-west-2.amazonaws.com HTTPS

(Oregon)
Canada ca-central-1 sts.ca-central-1.amazonaws.com HTTPS

(Central)
Asia Pacific ap-south-1 sts.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- sts.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap- sts.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- sts.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- sts.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU eu-central-1 sts.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 sts.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 sts.eu-west-2.amazonaws.com HTTPS
South sa-east-1 sts.sa-east-1.amazonaws.com HTTPS

America
(São Paulo)
For information about using AWS Security Token Service in the AWS GovCloud (US) Region, see AWS
For information about using AWS Security Token Service in the China (Beijing) Region, see China (Beijing)
Region Endpoints.
Version 1.0
82
AWS Serverless Application Repository

Name
US East us-east-2 serverlessrepo.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 serverlessrepo.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 serverlessrepo.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 serverlessrepo.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- serverlessrepo.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Asia Pacific ap- serverlessrepo.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap-south-1 serverlessrepo.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- serverlessrepo.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- serverlessrepo.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 serverlessrepo.ca-central-1.amazonaws.com HTTPS

(Central)
EU eu-central-1 serverlessrepo.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 serverlessrepo.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 serverlessrepo.eu-west-2.amazonaws.com HTTPS
South sa-east-1 serverlessrepo.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS Service Catalog

US East us-east-2 servicecatalog.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 servicecatalog.us-east-1.amazonaws.com HTTPS

Virginia)
Version 1.0
83
AWS Shield Advanced
US West (N. us-west-1 servicecatalog.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 servicecatalog.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap-south-1 servicecatalog.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- servicecatalog.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap- servicecatalog.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- servicecatalog.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- servicecatalog.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Canada ca-central-1 servicecatalog.ca-central-1.amazonaws.com HTTPS

(Central)
EU eu-central-1 servicecatalog.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 servicecatalog.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 servicecatalog.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 servicecatalog.eu-west-3.amazonaws.com HTTPS
South sa-east-1 servicecatalog.sa-east-1.amazonaws.com HTTPS

America (São
Paulo)
AWS Shield Advanced

AWS Shield Advanced has a single endpoint: shield.us-east-1.amazonaws.com. It supports HTTPS
requests only.
Amazon Simple Email Service (Amazon SES)

Region Name Region API (HTTPS) SMTP Endpoint Email Sending or
Endpoint Receiving
US East (N. us-east-1 email.us- email-smtp.us- Email sending

US West (Oregon) us-west-2 email.us- email-smtp.us- Email sending

Version 1.0
84
Amazon Simple Notification Service (Amazon SNS)
Region Name Region API (HTTPS) SMTP Endpoint Email Sending or

Endpoint Receiving
EU (Ireland) eu-west-1 email.eu- email-smtp.eu- Email sending

US East (N. us-east-1 N/A inbound-smtp.us- Email receiving

US West (Oregon) us-west-2 N/A inbound-smtp.us- Email receiving

EU (Ireland) eu-west-1 N/A inbound-smtp.eu- Email receiving


Name
US East us-east-2 sns.us-east-2.amazonaws.com HTTP and

(Ohio) HTTPS
US East (N. us-east-1 sns.us-east-1.amazonaws.com HTTP and

Virginia) HTTPS
US West (N. us-west-1 sns.us-west-1.amazonaws.com HTTP and

California) HTTPS
US West us-west-2 sns.us-west-2.amazonaws.com HTTP and

(Oregon) HTTPS
Asia Pacific ap- sns.ap-northeast-1.amazonaws.com HTTP and



Local)
Asia Pacific ap-south-1 sns.ap-south-1.amazonaws.com HTTP and

(Mumbai) HTTPS
Asia Pacific ap- sns.ap-southeast-1.amazonaws.com HTTP and

Asia Pacific ap- sns.ap-southeast-2.amazonaws.com HTTP and

Canada ca-central-1 sns.ca-central-1.amazonaws.com HTTP and

(Central) HTTPS
China cn-north-1 sns.cn-north-1.amazonaws.com.cn HTTP and

(Beijing) HTTPS
Version 1.0
85
Amazon Simple Queue Service (Amazon SQS)

Name
China cn- sns.cn-northwest-1.amazonaws.com.cn HTTP and

EU eu-central-1 sns.eu-central-1.amazonaws.com HTTP and

(Frankfurt) HTTPS
EU (Ireland) eu-west-1 sns.eu-west-1.amazonaws.com HTTP and

HTTPS
EU (London) eu-west-2 sns.eu-west-2.amazonaws.com HTTP and

HTTPS
EU (Paris) eu-west-3 sns.eu-west-3.amazonaws.com HTTP and

HTTPS
South sa-east-1 sns.sa-east-1.amazonaws.com HTTP and

America HTTPS
(Sao Paulo)
AWS us-gov- sns.us-gov-west-1.amazonaws.com HTTP and

(US)
For information about using Amazon Simple Notification Service in the AWS GovCloud (US) Region, see
For information about using Amazon Simple Notification Service in the China (Beijing) Region, see China

Name
US East us-east-2 sqs.us-east-2.amazonaws.com HTTP and

(Ohio) HTTPS
US East (N. us-east-1 sqs.us-east-1.amazonaws.com HTTP and

Virginia) HTTPS
US West (N. us-west-1 sqs.us-west-1.amazonaws.com HTTP and

California) HTTPS
US West us-west-2 sqs.us-west-2.amazonaws.com HTTP and

(Oregon) HTTPS
Asia Pacific ap- sqs.ap-northeast-1.amazonaws.com HTTP and


Version 1.0
86
Amazon SQS Legacy Endpoints

Name

Local)
Asia Pacific ap-south-1 sqs.ap-south-1.amazonaws.com HTTP and

(Mumbai) HTTPS
Asia Pacific ap- sqs.ap-southeast-1.amazonaws.com HTTP and

Asia Pacific ap- sqs.ap-southeast-2.amazonaws.com HTTP and

Canada ca-central-1 sqs.ca-central-1.amazonaws.com HTTP and

(Central) HTTPS
China cn-north-1 sqs.cn-north-1.amazonaws.com.cn HTTP and

(Beijing) HTTPS
China cn- sqs.cn-northwest-1.amazonaws.com.cn HTTP and

EU eu-central-1 sqs.eu-central-1.amazonaws.com HTTP and

(Frankfurt) HTTPS
EU (Ireland) eu-west-1 sqs.eu-west-1.amazonaws.com HTTP and

HTTPS
EU (London) eu-west-2 sqs.eu-west-2.amazonaws.com HTTP and

HTTPS
EU (Paris) eu-west-3 sqs.eu-west-3.amazonaws.com HTTP and

HTTPS
South sa-east-1 sqs.sa-east-1.amazonaws.com HTTP and

America HTTPS
(Sao Paulo)
AWS us-gov- sqs.us-gov-west-1.amazonaws.com HTTP and

(US)
For information about using Amazon Simple Queue Service in the AWS GovCloud (US) Region, see AWS
For information about using Amazon Simple Queue Service in the China (Beijing) Region, see China

If you use the AWS CLI or SDK for Python, you can use the following legacy endpoints.
Version 1.0
87
US East (Ohio) us-east-2 us- HTTP and HTTPS

east-2.queue.amazonaws.com
US East (N. Virginia) us-east-1 queue.amazonaws.com HTTP and HTTPS
US West (N. California) us-west-1 us- HTTP and HTTPS

west-1.queue.amazonaws.com
US West (Oregon) us-west-2 us- HTTP and HTTPS

Asia Pacific (Tokyo) ap-northeast-1 ap- HTTP and HTTPS

northeast-1.queue.amazonaws.com
Asia Pacific (Seoul) ap-northeast-2 ap- HTTP and HTTPS

northeast-2.queue.amazonaws.com
Asia Pacific (Osaka- ap-northeast-3 ap- HTTP and HTTPS

Local) northeast-3.queue.amazonaws.com
Asia Pacific (Mumbai) ap-south-1 ap- HTTP and HTTPS

south-1.queue.amazonaws.com
Asia Pacific (Singapore) ap-southeast-1 ap- HTTP and HTTPS

southeast-1.queue.amazonaws.com
Asia Pacific (Sydney) ap-southeast-2 ap- HTTP and HTTPS

southeast-2.queue.amazonaws.com
Canada (Central) ca-central-1 ca- HTTP and HTTPS

central-1.queue.amazonaws.com
China (Beijing) cn-north-1 cn- HTTP and HTTPS

north-1.queue.amazonaws.com
China (Ningxia) cn-northwest-1 cn- HTTP and HTTPS

northwest-1.queue.amazonaws.com
EU (Frankfurt) eu-central-1 eu- HTTP and HTTPS

central-1.queue.amazonaws.com
EU (Ireland) eu-west-1 eu- HTTP and HTTPS

EU (London) eu-west-2 eu- HTTP and HTTPS

EU (Paris) eu-west-3 eu- HTTP and HTTPS

South America (São sa-east-1 sa- HTTP and HTTPS

Paulo) east-1.queue.amazonaws.com
Version 1.0
88
Amazon Simple Storage Service (Amazon S3)

When sending requests to these endpoints using the REST API, you can use the virtual-hosted style and
path-style methods. For more information, see Virtual Hosting of Buckets.
Region Region Endpoint Location Protocol Signature

Name Constraint Version(s)
Support
US East us-east-2 Valid endpoint names for this us-east-2 HTTP and Versions 4
(Ohio) region: HTTPS only
• s3.us-east-2.amazonaws.com
• s3-us-east-2.amazonaws.com
• s3.dualstack.us-
US East (N. us-east-1 Valid endpoint names for this (none HTTP and Versions 2
Virginia) region: required) HTTPS and 4
• s3.amazonaws.com
• s3.us-east-1.amazonaws.com
• s3-external-1.amazonaws.com
east-1.amazonaws.com**
US West (N. us-west-1 Valid endpoint names for this us-west-1 HTTP and Versions 2
California) region: HTTPS and 4
• s3.us-west-1.amazonaws.com
• s3-us-west-1.amazonaws.com
west-1.amazonaws.com**
US West us-west-2 Valid endpoint names for this us-west-2 HTTP and Versions 2
(Oregon) region: HTTPS and 4
• s3.us-west-2.amazonaws.com
• s3-us-west-2.amazonaws.com
Canada ca- Valid endpoint names for this ca- HTTP and Version 4
(Central) central-1 region: central-1 HTTPS only
• s3.ca-
• s3-ca-
• s3.dualstack.ca-
central-1.amazonaws.com**
Asia Pacific ap-south-1 Valid endpoint names for this ap-south-1 HTTP and Version 4
(Mumbai) region: HTTPS only
Version 1.0
89

Support
• s3.ap-
• s3-ap-
• s3.dualstack.ap-
south-1.amazonaws.com**
Asia Pacific ap- Valid endpoint names for this ap- HTTP and Version 4
(Seoul) northeast-2 region: northeast-2 HTTPS only
• s3.ap-
• s3-ap-
northeast-2.amazonaws.com**
Asia Pacific ap- Valid endpoint names for this ap- HTTP and Version 4
(Osaka- northeast-3 region: northeast-3 HTTPS only
Local) ***
• s3.ap-
• s3-ap-
Asia Pacific ap- Valid endpoint names for this ap- HTTP and Versions 2
(Singapore) southeast-1 region: southeast-1 HTTPS and 4
• s3.ap-
• s3-ap-
southeast-1.amazonaws.com**
(Sydney) southeast-2 region: southeast-2 HTTPS and 4
• s3.ap-
• s3-ap-
southeast-2.amazonaws.com**
Version 1.0
90

Support
(Tokyo) northeast-1 region: northeast-1 HTTPS and 4
• s3.ap-
• s3-ap-
China cn-north-1 Valid endpoint name for this cn-north-1 HTTP and Version 4
(Beijing) region: HTTPS only
• s3.cn-
north-1.amazonaws.com.cn
China cn- Valid endpoint name for this cn- HTTP and Version 4
(Ningxia) northwest-1 region: northwest-1 HTTPS only
• s3.cn-
northwest-1.amazonaws.com.cn
EU eu- Valid endpoint names for this eu- HTTP and Version 4
(Frankfurt) central-1 region: central-1 HTTPS only
• s3.eu-
• s3-eu-
• s3.dualstack.eu-
central-1.amazonaws.com**
EU (Ireland) eu-west-1 Valid endpoint names for this EU or eu- HTTP and Versions 2
region: west-1 HTTPS and 4
• s3.eu-west-1.amazonaws.com
• s3-eu-west-1.amazonaws.com
EU eu-west-2 Valid endpoint names for this eu-west-2 HTTP and Version 4
(London) region: HTTPS only
Version 1.0
91
Amazon Simple Storage Service Website Endpoints

Support
EU (Paris) eu-west-3 Valid endpoint names for this eu-west-3 HTTP and Version 4
region: HTTPS only
South sa-east-1 Valid endpoint names for this sa-east-1 HTTP and Versions 2
America region: HTTPS and 4
(São Paulo)
• s3.sa-east-1.amazonaws.com
• s3-sa-east-1.amazonaws.com
• s3.dualstack.sa-
east-1.amazonaws.com**
**Amazon S3 dual-stack endpoints support requests to S3 buckets over IPv6 and IPv4. For more
information, see Using Dual-Stack Endpoints.
***You can use the Asia Pacific (Osaka-Local) Region only in conjunction with the Asia Pacific (Tokyo)
Region. To request access to the Asia Pacific (Osaka-Local) Region, contact your sales representative.
When using the preceding endpoints the following additional considerations apply:
• Amazon S3 renamed the US Standard Region to the US East (N. Virginia) Region to be consistent with
AWS regional naming conventions. There is no change to the endpoint and you do not need to make
any changes to your application.
• If you use a region other than the US East (N. Virginia) endpoint to create a bucket, you must set the
LocationConstraint bucket parameter to the same region. Both the AWS SDK for Java and AWS SDK
for .NET use an enumeration for setting location constraints (Region for Java, S3Region for .NET). For
more information, see PUT Bucket in the Amazon Simple Storage Service API Reference.
Amazon Simple Storage Service Website Endpoints

When you configure your bucket as a website, the website is available using the following region-specific
website endpoints. Note that the website endpoints are different than the REST API endpoints listed in
the preceding table. For more information about hosting websites on Amazon S3, see Hosting Websites
on Amazon S3 in the Amazon Simple Storage Service Developer Guide. You need the hosted zone IDs
when using the Amazon Route 53 API to add an alias record to your hosted zone.
Note
The website endpoints do not support https.
Region Name Website Endpoint Route 53 Hosted

Zone ID
US East (Ohio) s3-website.us-east-2.amazonaws.com Z2O1EMRO9K5GLX
US East (N. s3-website-us-east-1.amazonaws.com Z3AQBSTGFYJSTF

Virginia)
Version 1.0
92
Amazon Simple Workflow Service (Amazon SWF)
Region Name Website Endpoint Route 53 Hosted

Zone ID
US West (N. s3-website-us-west-1.amazonaws.com Z2F56UZL2M1ACD

California)
US West s3-website-us-west-2.amazonaws.com Z3BJ6K6RIION7M

(Oregon)
Canada (Central) s3-website.ca-central-1.amazonaws.com Z1QDHH18159H29
Asia Pacific s3-website.ap-south-1.amazonaws.com Z11RGJOFQNVJUP

(Mumbai)
Asia Pacific s3-website.ap-northeast-2.amazonaws.com Z3W03O7B5YMIYP

(Seoul)
Asia Pacific s3-website.ap-northeast-3.amazonaws.com Z2YQB5RD63NC85

(Osaka-Local)
Asia Pacific s3-website-ap-southeast-1.amazonaws.com Z3O0J2DXBE1FTB

(Singapore)
Asia Pacific s3-website-ap-southeast-2.amazonaws.com Z1WCIGYICN2BYD

(Sydney)
Asia Pacific s3-website-ap-northeast-1.amazonaws.com Z2M4EHUR26P7ZW

(Tokyo)
China (Ningxia) s3-website.cn-northwest-1.amazonaws.com.cn Not supported
EU (Frankfurt) s3-website.eu-central-1.amazonaws.com Z21DNDUVLTQW6Q
EU (Ireland) s3-website-eu-west-1.amazonaws.com Z1BKCTXD74EZPE
EU (London) s3-website.eu-west-2.amazonaws.com Z3GKZC51ZF0DB4
EU (Paris) s3-website.eu-west-3.amazonaws.com Z3R1K369G5AVDG
South America s3-website-sa-east-1.amazonaws.com Z7KQH4QJS55SO

(São Paulo)
For information about using Amazon Simple Storage Service in the AWS GovCloud (US) Region, see AWS
For information about using Amazon Simple Storage Service in the China (Beijing) Region, see China

Name
US East us-east-2 swf.us-east-2.amazonaws.com HTTPS

(Ohio)
Version 1.0
93

Name
US East (N. us-east-1 swf.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 swf.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 swf.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- swf.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1

(Seoul) northeast-2

(Osaka- northeast-3
Local)
Asia Pacific ap-south-1 swf.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- swf.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- swf.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 swf.ca-central-1.amazonaws.com HTTPS

(Central)
China cn-north-1 swf.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
China cn- swf.cn-northwest-1.amazonaws.com.cn HTTPS

EU eu-central-1 swf.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 swf.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 swf.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 swf.eu-west-3.amazonaws.com HTTPS
South sa-east-1 swf.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS us-gov- swf.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US)
For information about using Amazon Simple Workflow Service in the AWS GovCloud (US) Region, see
Version 1.0
94
Amazon SimpleDB
For information about using Amazon Simple Workflow Service in the China (Beijing) Region, see China
Amazon SimpleDB
Name
US East (N. us-east-1 sdb.amazonaws.com HTTP and

Virginia) HTTPS
US West (N. us-west-1 sdb.us-west-1.amazonaws.com HTTP and

California) HTTPS
US West us-west-2 sdb.us-west-2.amazonaws.com HTTP and

(Oregon) HTTPS
Asia Pacific ap- sdb.ap-southeast-1.amazonaws.com HTTP and

Asia Pacific ap- sdb.ap-southeast-2.amazonaws.com HTTP and

Asia Pacific ap- sdb.ap-northeast-1.amazonaws.com HTTP and

EU (Ireland) eu-west-1 sdb.eu-west-1.amazonaws.com HTTP and

HTTPS
South sa-east-1 sdb.sa-east-1.amazonaws.com HTTP and

America HTTPS
(São Paulo)
AWS Snowball
AWS Snowball, used with a standard Snowball appliance, is available in the following regions and
includes these endpoints.
US East (Ohio) us-east-2 snowball.us- HTTPS

US East (N. Virginia) us-east-1 snowball.us- HTTPS

US West (N. California) us-west-1 snowball.us- HTTPS

US West (Oregon) us-west-2 snowball.us- HTTPS

Canada (Central) ca-central-1 snowball.ca- HTTPS

Version 1.0
95
AWS Snowball
Asia Pacific (Mumbai) ap-south-1 snowball.ap- HTTPS

Asia Pacific (Singapore) ap-southeast-1 snowball.ap- HTTPS

Asia Pacific (Sydney) ap-southeast-2 snowball.ap- HTTPS

Asia Pacific (Tokyo) ap-northeast-1 snowball.ap- HTTPS

EU (Frankfurt) eu-central-1 snowball.eu- HTTPS

EU (Ireland) eu-west-1 snowball.eu- HTTPS

EU (London) eu-west-2 snowball.eu- HTTPS

EU (Paris) eu-west-3 snowball.eu- HTTPS

South America (São sa-east-1 snowball.sa- HTTPS

Paulo) east-1.amazonaws.com
AWS Snowball, used with an AWS Snowball Edge appliance, is available in the following regions and
includes these endpoints.
US East (Ohio) us-east-2 snowball.us- HTTPS

US East (N. Virginia) us-east-1 snowball.us- HTTPS

US West (N. California) us-west-1 snowball.us- HTTPS

US West (Oregon) us-west-2 snowball.us- HTTPS

Canada (Central) ca-central-1 snowball.ca- HTTPS

Asia Pacific (Sydney) ap-southeast-2 snowball.ap- HTTPS

Asia Pacific (Tokyo) ap-northeast-1 snowball.ap- HTTPS

EU (Frankfurt) eu-central-1 snowball.eu- HTTPS

Version 1.0
96
AWS Step Functions
EU (Ireland) eu-west-1 snowball.eu- HTTPS

EU (London) eu-west-2 snowball.eu- HTTPS

EU (Paris) eu-west-3 snowball.eu- HTTPS

South America (São sa-east-1 snowball.sa- HTTPS

Paulo) east-1.amazonaws.com
For information about using AWS Snowball in the AWS GovCloud (US) Region, see AWS GovCloud (US)
Endpoints.
AWS Step Functions

Name
US East us-east-2 states.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 states.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 states.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- states.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Asia Pacific ap- states.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- states.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 states.ca-central-1.amazonaws.com HTTPS

(Central)
EU eu-central-1 states.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 states.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 states.eu-west-2.amazonaws.com HTTPS
Version 1.0
97
AWS Storage Gateway
AWS Storage Gateway

Name
US East us-east-2 storagegateway.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 storagegateway.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 storagegateway.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 storagegateway.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- storagegateway.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Asia Pacific ap- storagegateway.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
Asia Pacific ap-south-1 storagegateway.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- storagegateway.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- storagegateway.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 storagegateway.ca-central-1.amazonaws.com HTTPS

(Central)
China cn-north-1 storagegateway.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
EU eu-central-1 storagegateway.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 storagegateway.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 storagegateway.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 storagegateway.eu-west-3.amazonaws.com HTTPS
South sa-east-1 storagegateway.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
For information about using AWS Storage Gateway in the China (Beijing) Region, see China (Beijing)
Region Endpoints.
Version 1.0
98
AWS Support
AWS Support
AWS Support has a single endpoint: support.us-east-1.amazonaws.com (HTTPS).
AWS Systems Manager

Name
US East us-east-2 ssm.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 ssm.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 ssm.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 ssm.us-west-2.amazonaws.com HTTPS

(Oregon)
Canada ca-central-1 ssm.ca-central-1.amazonaws.com HTTPS

(Central)
Asia Pacific ap-south-1 ssm.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- ssm.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- ssm.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- ssm.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Asia Pacific ap- ssm.ap-northeast-2.amazonaws.com HTTPS

(Seoul) northeast-2
China cn-north-1 ssm.cn-north-1.amazonaws.com.cn HTTPS

(Beijing)
China cn- ssm.cn-northwest-1.amazonaws.com.cn HTTPS

EU eu-central-1 ssm.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 ssm.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 ssm.eu-west-2.amazonaws.com HTTPS
South sa-east-1 ssm.sa-east-1.amazonaws.com HTTPS

America
(São Paulo)
Version 1.0
99
Amazon Transcribe
For information about using AWS Systems Manager in the AWS GovCloud (US) Region, see AWS
For information about using AWS Systems Manager in the China (Beijing) Region, see China (Beijing)
Region Endpoints.
For information about using Amazon EC2 Systems Manager in the AWS GovCloud (US) Region, see AWS
For information about using Amazon EC2 Systems Manager in the China (Beijing) Region, see China
Amazon Transcribe
Name
US East (N. us-east-1 transcribe.us-east-1.amazonaws.com HTTPS

Virginia)
Amazon Translate
Name
US East us-east-2 https://translate.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 https://translate.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 https://translate.us-west-2.amazonaws.com HTTPS

(Oregon)
Amazon VPC
Name
US East us-east-2 ec2.us-east-2.amazonaws.com HTTPS

(Ohio)
US East (N. us-east-1 ec2.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 ec2.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 ec2.us-west-2.amazonaws.com HTTPS

(Oregon)
Version 1.0
100
AWS WAF

Name
Asia Pacific ap- ec2.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1

(Seoul) northeast-2

(Osaka- northeast-3
Local)
Asia Pacific ap-south-1 ec2.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap- ec2.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- ec2.ap-southeast-2.amazonaws.com HTTPS

Canada ca-central-1 ec2.ca-central-1.amazonaws.com HTTPS

(Central)
EU eu-central-1 ec2.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 ec2.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 ec2.eu-west-2.amazonaws.com HTTPS
EU (Paris) eu-west-3 ec2.eu-west-3.amazonaws.com HTTPS
South sa-east-1 ec2.sa-east-1.amazonaws.com HTTPS

America
(Sao Paulo)
AWS us-gov- ec2.us-gov-west-1.amazonaws.com HTTPS

GovCloud west-1
(US)
If you specify the general endpoint (ec2.amazonaws.com), Amazon VPC directs your request to the us-
east-1 endpoint.
For information about using Amazon VPC in the AWS GovCloud (US) Region, see AWS GovCloud (US)
Endpoints.
For information about using Amazon VPC in the China (Beijing) Region, see China (Beijing) Region
Endpoints.
AWS WAF
AWS WAF for CloudFront distributions has a single endpoint: waf.amazonaws.com. It supports HTTPS
requests only.
AWS WAF for Application Load Balancers has the following endpoints:
Version 1.0
101
Amazon WorkDocs

Name
US East (N. us-east-1 waf-regional.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 waf-regional.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 waf-regional.us-west-2.amazonaws.com HTTPS

(Oregon)
EU eu-central-1 waf-regional.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 waf-regional.eu-west-1.amazonaws.com HTTPS
Asia Pacific ap- waf-regional.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
Asia Pacific ap- waf-regional.ap-southeast-2.amazonaws.com HTTPS

Amazon WorkDocs
Name
US East (N. us-east-1 workdocs.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 workdocs.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- workdocs.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- workdocs.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- workdocs.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU (Ireland) eu-west-1 workdocs.eu-west-1.amazonaws.com HTTPS
Amazon WorkMail
Region Name Region Service Endpoint
US East (N. Virginia) us-east-1 Amazon WorkMail https://workmail.us-

SDK east-1.amazonaws.com
US East (N. Virginia) us-east-1 Autodiscover autodiscover-service.mail.us-

east-1.awsapps.com
Version 1.0
102
Amazon WorkMail
Region Name Region Service Endpoint
US East (N. Virginia) us-east-1 Exchange Web ews.mail.us-east-1.awsapps.com

Service
US East (N. Virginia) us-east-1 Exchange Active mobile.mail.us-east-1.awsapps.com

Sync
US East (N. Virginia) us-east-1 MAPI Proxy outlook.mail.us-east-1.awsapps.com
US East (N. Virginia) us-east-1 IMAPS imap.mail.us-east-1.awsapps.com
US East (N. Virginia) us-east-1 SMTP via TLS (port smtp.mail.us-east-1.awsapps.com

465)
US West (Oregon) us-west-2 Amazon WorkMail https://workmail.us-

SDK west-2.amazonaws.com
US West (Oregon) us-west-2 Autodiscover autodiscover-service.mail.us-

west-2.awsapps.com
US West (Oregon) us-west-2 Exchange Web ews.mail.us-west-2.awsapps.com

Service
US West (Oregon) us-west-2 Exchange Active mobile.mail.us-west-2.awsapps.com

Sync
US West (Oregon) us-west-2 MAPI Proxy outlook.mail.us-west-2.awsapps.com
US West (Oregon) us-west-2 IMAPS imap.mail.us-west-2.awsapps.com
US West (Oregon) us-west-2 SMTP via TLS (port smtp.mail.us-west-2.awsapps.com

465)
EU (Ireland) eu-west-1 Amazon WorkMail https://workmail.eu-

SDK west-1.amazonaws.com
EU (Ireland) eu-west-1 Autodiscover autodiscover-service.mail.eu-

west-1.awsapps.com
EU (Ireland) eu-west-1 Exchange Web ews.mail.eu-west-1.awsapps.com

Service
EU (Ireland) eu-west-1 Exchange Active mobile.mail.eu-west-1.awsapps.com

Sync
EU (Ireland) eu-west-1 MAPI Proxy outlook.mail.eu-west-1.awsapps.com
EU (Ireland) eu-west-1 IMAPS imap.mail.eu-west-1.awsapps.com
EU (Ireland) eu-west-1 SMTP via TLS (port smtp.mail.eu-west-1.awsapps.com

465)
Version 1.0
103
Amazon WorkSpaces
Amazon WorkSpaces
Name
US East (N. us-east-1 workspaces.us-east-1.amazonaws.com HTTPS

Virginia)
US West us-west-2 workspaces.us-west-2.amazonaws.com HTTPS

(Oregon)
Asia Pacific ap- workspaces.ap-southeast-1.amazonaws.com HTTPS

Asia Pacific ap- workspaces.ap-southeast-2.amazonaws.com HTTPS

Asia Pacific ap- workspaces.ap-northeast-1.amazonaws.com HTTPS

(Tokyo) northeast-1
EU eu-central-1 workspaces.eu-central-1.amazonaws.com HTTPS

(Frankfurt)
EU (Ireland) eu-west-1 workspaces.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 workspaces.eu-west-2.amazonaws.com HTTPS
South sa-east-1 workspaces.sa-east-1.amazonaws.com HTTPS

America
(São Paulo)
AWS X-Ray
US East (Ohio) us-east-2 xray.us-east-2.amazonaws.com HTTPS
US East (N. us-east-1 xray.us-east-1.amazonaws.com HTTPS

Virginia)
US West (N. us-west-1 xray.us-west-1.amazonaws.com HTTPS

California)
US West us-west-2 xray.us-west-2.amazonaws.com HTTPS

(Oregon)
Canada (Central) ca-central-1 xray.ca-central-1.amazonaws.com HTTPS
Asia Pacific ap-south-1 xray.ap-south-1.amazonaws.com HTTPS

(Mumbai)
Asia Pacific ap-northeast-2 xray.ap-northeast-2.amazonaws.com HTTPS

(Seoul)
Asia Pacific ap-southeast-1 xray.ap-southeast-1.amazonaws.com HTTPS

(Singapore)
Version 1.0
104
AWS X-Ray
Asia Pacific ap-southeast-2 xray.ap-southeast-2.amazonaws.com HTTPS

(Sydney)
Asia Pacific ap-northeast-1 xray.ap-northeast-1.amazonaws.com HTTPS

(Tokyo)
EU (Frankfurt) eu-central-1 xray.eu-central-1.amazonaws.com HTTPS
EU (Ireland) eu-west-1 xray.eu-west-1.amazonaws.com HTTPS
EU (London) eu-west-2 xray.eu-west-2.amazonaws.com HTTPS
South America sa-east-1 xray.sa-east-1.amazonaws.com HTTPS

(São Paulo)
Version 1.0
105
AWS Account Root User Credentials
vs. IAM User Credentials
AWS Security Credentials

When you interact with AWS, you specify your AWS security credentials to verify who you are and
whether you have permission to access the resources that you are requesting. AWS uses the security
credentials to authenticate and authorize your requests.
For example, if you want to download a specific file from an Amazon Simple Storage Service (Amazon
S3) bucket, your credentials must allow that access. If your credentials aren't authorized to download the
file, AWS denies your request.
Note
In some cases, you can make calls to AWS without security credentials, such as downloading a
file that is publicly shared in an Amazon S3 bucket.
Topics
• AWS Account Root User Credentials vs. IAM User Credentials (p. 106)
• Understanding and Getting Your Security Credentials (p. 107)
• AWS Account Identifiers (p. 110)
• Best Practices for Managing AWS Access Keys (p. 112)
• Managing Access Keys for Your AWS Account (p. 114)
• AWS Security Audit Guidelines (p. 115)
AWS Account Root User Credentials vs. IAM User

Credentials
All AWS accounts have root user credentials (that is, the credentials of the account owner). These
credentials allow full access to all resources in the account. Because you can't restrict permissions for
root user credentials, we recommend that you delete your root user access keys. Then create AWS
Identity and Access Management (IAM) user credentials for everyday interaction with AWS. For more
information, see Lock away your AWS account (root) access keys in the IAM User Guide.
Note
You may need AWS account root user access for specific tasks, such as changing an AWS support
plan or closing your account. In these cases, sign in to the AWS Management Console with your
email and password. See Email and Password (Root User) (p. 108).
For a list of tasks that require root user access, see AWS Tasks That Require AWS Account Root
User (p. 107).
With IAM, you can securely control access to AWS services and resources for users in your AWS account.
For example, if you require administrator-level permissions, you can create an IAM user, grant that user
full access, and then use those credentials to interact with AWS. If you need to modify or revoke your
permissions, you can delete or modify the policies that are associated with that IAM user.
If you have multiple users that require access to your AWS account, you can create unique credentials
for each user and define who has access to which resources. You don't need to share credentials. For
example, you can create IAM users with read-only access to resources in your AWS account and distribute
those credentials to your users.
Version 1.0
106
AWS Tasks That Require AWS Account Root User
Note
Any activity or costs that are associated with the IAM user are billed to the AWS account owner.
AWS Tasks That Require AWS Account Root User

The tasks listed below require you to sign in as the AWS account root user. We normally recommend that
you use a standard IAM user with appropriate permissions to perform all normal user or administrative
tasks. However, you can perform the tasks listed below only when you sign in as the root user of an
account.
• Modify root user details (p. 108). This includes changing the root user's password.
• Change your AWS support plan.
• Change or delete your payment options - an IAM user can perform this after you enable billing access
for IAM users. For more information, see Activating Access to the Billing and Cost Management
Console.
• View your account's billing information - an IAM user can perform this after you enable billing access
for IAM users. For more information, see Activating Access to the Billing and Cost Management
Console
• Close an AWS account.
• Sign up for GovCloud.
• Submit a Reverse DNS for Amazon EC2 request. The "this form" link on that page to submit a request
works only if you sign in with root user credentials.
• Create a CloudFront key pair.
• Create an AWS-created X.509 signing certificate. (You can still make self-created certificates for IAM
users.)
• Transfer an Route 53 domain to another AWS account.
• Change the Amazon EC2 setting for longer resource IDs. Changing this setting as the root user affects
all users and roles in the account. Changing it as an IAM user or IAM role affects only that user or role.
• Submit a request to perform penetration testing on your AWS infrastructure using the web form.
Alternatively, you can submit your request via email without needing root user access.
• Request removal of the port 25 email throttle on your EC2 instance.
• Find your AWS account canonical user ID (p. 111). You can view your canonical user ID from the AWS
Management Console only while signed in as the AWS account root user. You can view your canonical
user ID as an IAM user with the AWS API or AWS CLI.
• Reassigning permissions in a resource-based policy (such as an S3 bucket policy) that were revoked by
explicitly denying IAM users access. Root users are not blocked by an explicit deny like IAM users can
be.
Understanding and Getting Your Security

Credentials
You use different types of security credentials depending on how you interact with AWS. For example,
you use a user name and password to sign in to the AWS Management Console. You use access keys to
make programmatic calls to AWS API operations.
If you forget or lose your credentials, you can't recover them. For security reasons, AWS doesn't allow you
to retrieve your passwords or secret access keys and does not store the private keys that are part of a key
pair. However, you can create new credentials and then disable or delete the old credentials.
Version 1.0
107
Email and Password (Root User)
Note
Security credentials are account specific. If you have access to multiple AWS accounts, use the
credentials that are associated with the account that you want to access.
Getting AWS account root user credentials is different than getting IAM user credentials. For root user
credentials, you get credentials, such as access keys or key pairs, from the Security Credentials page in
the AWS Management Console. For IAM user credentials, you get credentials from the IAM console.
The following list describes the types of AWS security credentials, when you might use them, and how to
get each type of credential for the AWS account root user or for an IAM user.
Topics
• Email and Password (Root User) (p. 108)
• IAM User Name and Password (p. 108)
• Multi-Factor Authentication (MFA) (p. 108)
• Access Keys (Access Key ID and Secret Access Key) (p. 109)
• Key Pairs (p. 109)
Email and Password (Root User)

When you sign up for AWS, you provide an email address and password that is associated with your
AWS account. You use these AWS account root user credentials to sign in to AWS webpages such as
the AWS Management Console, AWS discussion forums, or AWS Support center. The account email
address and password are root-level credentials, and anyone who uses these credentials has full access
to all resources in the account. We recommend that you can use an IAM user name and password to
sign in to AWS webpages. For more information, see AWS Account Root User Credentials vs. IAM User
Credentials (p. 106).
You can change the email address and password on the Security Credentials page. You can also choose
Forgot password? on the AWS sign-in page to reset your password.
IAM User Name and Password

When multiple individuals or applications require access to your AWS account, AWS Identity and Access
Management (IAM) lets you create unique IAM user identities. Users can use their own user names and
passwords to sign in to the AWS Management Console, AWS discussion forums, or AWS Support center.
In some cases, an IAM user name and password are required to use a service, such as sending email with
SMTP by using Amazon Simple Email Service (Amazon SES).
For more information about IAM users, see Identities (Users, Groups, and Roles) in the IAM User Guide.
You specify user names when you create them. After you create users, you can create passwords for each
user. For more information, see Managing Passwords for IAM Users in the IAM User Guide.
Note
IAM users can manage their own password but only if they have been given permission. For
more information, see Permitting IAM Users to Change Their Own Password in the IAM User
Guide.
Multi-Factor Authentication (MFA)

Multi-factor authentication (MFA) provides an extra level of security that you can apply to your AWS
account. For additional security, we recommend that you require MFA on the AWS account root user
credentials and highly privileged IAM users. For more information, see Using Multi-Factor Authentication
(MFA) in AWS in the IAM User Guide.
Version 1.0
108
Access Keys (Access Key ID and Secret Access Key)
With MFA enabled, when you sign in to the AWS website, you are prompted for your user name and
password, and an authentication code from an MFA device. Together, they provide increased security for
your AWS account settings and resources.
By default, MFA (multi-factor authentication) is not enabled. You can enable and manage MFA devices
for the AWS account root user by going to the Security Credentials page or the IAM dashboard in the
AWS Management Console. For more information about enabling MFA for IAM users, see Enabling MFA
Devices in the IAM User Guide.
Access Keys (Access Key ID and Secret Access Key)

Access keys consist of an access key ID (for example, AKIAIOSFODNN7EXAMPLE) and a secret access
key (for example, wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY). You use access keys to sign
programmatic requests that you make to AWS if you use the AWS SDKs, REST, or Query API operations.
The AWS SDKs use your access keys to sign requests for you, so that you don't have to handle the
signing process. You can also sign requests manually. For more information, see Signing AWS API
Requests (p. 150).
Important
Do not provide your access keys to a third party, even to help find your canonical user
ID (p. 111). By doing this, you might give someone full access to your account.
Access keys are also used with command line interfaces (CLIs). When you use a CLI, the commands that
you issue are signed by your access keys. You can pass access keys either with the command or store as
configuration settings on your computer.
You can also create and use temporary access keys, known as temporary security credentials. In addition
to the access key ID and secret access key, temporary security credentials include a security token that
you must send to AWS when you use temporary security credentials. The advantage of temporary
security credentials is that they are short term. After they expire, they're no longer valid. You can use
temporary access keys in less secure environments or distribute them to grant users temporary access
to resources in your AWS account. For example, you can grant entities from other AWS accounts access
to resources in your AWS account (cross-account access). You can also grant users who don't have AWS
security credentials access to resources in your AWS account (federation). For more information, see
Temporary Security Credentials in the IAM User Guide.
You can have a maximum of two access keys (active or inactive) at a time. For your AWS (root) account,
see Managing Access Keys for Your AWS Account (p. 114). For IAM users, you can create IAM access keys
with the IAM console. For more information, see Creating, Modifying, and Viewing Access Keys (AWS
Management Console) in the IAM User Guide.
Important
If you or your IAM users forget or lose the secret access key, you can create a new access key.
Key Pairs
Key pairs consist of a public key and a private key. You use the private key to create a digital signature,
and then AWS uses the corresponding public key to validate the signature. Key pairs are used only for
Amazon EC2 and Amazon CloudFront.
For Amazon EC2, you use key pairs to access Amazon EC2 instances, such as when you use SSH to log in
to a Linux instance. For more information, see Connect to Your Linux Instances in the Amazon EC2 User
Guide for Linux Instances.
For Amazon CloudFront, you use key pairs to create signed URLs for private content, such as when you
want to distribute restricted content that someone paid for. For more information, see Serving Private
Content through CloudFront in the Amazon CloudFront Developer Guide.
Version 1.0
109
AWS Account Identifiers
AWS does not provide key pairs for your account; you must create them. You can create Amazon EC2 key
pairs from the Amazon EC2 console, CLI, or API. For more information, see Amazon EC2 Key Pairs in the
Amazon EC2 User Guide for Linux Instances.
You create Amazon CloudFront key pairs from the Security Credentials page. Only the AWS account root
user (not IAM users) can create CloudFront key pairs. For more information, see Serving Private Content
through CloudFront in the Amazon CloudFront Developer Guide.
AWS Account Identifiers

AWS assigns two unique IDs to each AWS account:
• An AWS account ID
• A canonical user ID
The AWS account ID is a 12-digit number, such as 123456789012, that you use to construct Amazon
Resource Names (ARNs). When you refer to resources, such as an IAM user or an Amazon Glacier vault,
the account ID distinguishes your resources from resources in other AWS accounts.
The canonical user ID is a long string, such as

79a59df900b949e55d96a1e698fbacedfd6e09d98eacf8f8d5218e7cd47ef2be.
You can use canonical user IDs in an Amazon S3 bucket policy for cross-account access, which means
an AWS account can access resources in another AWS account. For example, to grant another AWS
account access to your bucket, you specify the account's canonical user ID in the bucket's policy. For more
information, see Bucket Policy Examples in the Amazon Simple Storage Service Developer Guide.
Finding Your AWS Account ID

You can find the AWS account ID from AWS Management Console. The method that you use to find the
account ID depends on how you are logged in to the console.
To view your AWS account ID when signed in as an AWS account root user
1. Use your AWS account email address and password to sign in to the AWS Management Console as
the root user.
Important
If you are signed in to the AWS Management Console with IAM user credentials, you must
sign out and then sign in as the root user. If you see the account-specific IAM user sign-in
page, choose Sign-in using root account credentials near the bottom of the page to return
to the main sign-in page. From there, you can type your AWS account email address and
password to sign in as the root user.
2. In the top right of the console, choose your account name or number. Then choose My Security
Credentials.
3. If necessary, in the dialog box, choose Continue to Security Credentials. You can choose the box
next to Don’t show me this message again to stop the dialog box from appearing in the future.
4. Expand the Account Identifiers section to view your AWS account ID.
To view your AWS account ID when signed in as a federated user or an IAM user
1. Sign in to the AWS Management Console as a federated user.
Version 1.0
110
Finding Your Account Canonical User ID
2. Choose Support in the upper-right corner of the console and choose Support Center. If necessary,
in the dialog box, choose Continue to Security Credentials. You can select the box next to Don’t
show me this message again to stop the dialog box from appearing in the future.
3. Your AWS account ID appears in the upper right. The account ID for an AWS account is the same for
the AWS account root user and its IAM users. For more information, see Your AWS Account ID and Its
Alias.
Finding Your Account Canonical User ID

You can view your canonical user ID from the AWS Management Console while signed in as the AWS
account root user, or using the AWS API or AWS CLI while signed in as an IAM user. To learn about the
differences between root user credentials and IAM user credentials, see the section called “AWS Account
Root User Credentials vs. IAM User Credentials” (p. 106).
To use the the AWS API or AWS CLI, the IAM user must have permissions to perform the
s3:ListAllMyBuckets action. For more information about permissions, see Permissions Related to
Buckets and Managing Access Permissions to Your Amazon S3 Resources ( ) in the Amazon Simple Storage
Service Developer Guide.
Important
Do not provide your Access Keys (Access Key ID and Secret Access Key) (p. 109) to a third
party to help find your canonical user ID. By doing this, you might give them full access to your
account.
To view your canonical user ID when signed in as an AWS account root user (console)
1. Sign in as the root user using your AWS account email address and password.
Important
If you are signed in to the AWS Management Console with IAM user credentials, then you
must sign out and then sign in as the root user. If you see the account-specific IAM user
sign-in page, choose Sign-in using root account credentials near the bottom of the page
to return to the main sign-in page. From there, you can type your AWS account email
address and password to sign in as the root user.
2. In the top right of the console, choose your account name or number. Then choose My Security
Credentials.
3. If necessary, in the dialog box, choose Continue to Security Credentials. You can choose the box
next to Don’t show me this message again to stop the dialog box from appearing in the future.
4. Expand the Account Identifiers section to view your canonical user ID.
Note
If you do not see the Account Identifiers section, then you are not signed in as the root
user. Return to Step 1 above. If you do not have access to the root user credentials, contact
your AWS account administrator and ask them to retrieve the canonical user ID.
To view your canonical user ID as an IAM user (API)
• You can use the Amazon S3 ListBuckets API with your IAM user credentials to return the AWS
account owner ID, which is the canonical user ID. For more information, see GET Service Response
Elements in the Amazon Simple Storage Service API Reference.
To view your canonical user ID as an IAM user (CLI)
• You can use the list-buckets command with your IAM user credentials to return the AWS account
owner ID, which is the canonical user ID. For more information, see s3api list-buckets in the AWS CLI
Command Reference.
Version 1.0
111
Best Practices for Managing AWS Access Keys
Best Practices for Managing AWS Access Keys

When you access AWS programmatically, you use an access key to verify your identity and the identity of
your applications. An access key consists of an access key ID (something like AKIAIOSFODNN7EXAMPLE)
and a secret access key (something like wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY).
Anyone who has your access key has the same level of access to your AWS resources that you do.
Consequently, AWS goes to significant lengths to protect your access keys, and, in keeping with our
shared-responsibility model, you should as well.
The steps that follow can help you protect access keys. For general background, see AWS Security
Credentials (p. 106).
Note
Your organization may have different security requirements and policies than those described in
this topic. The suggestions provided here are intended to be general guidelines.
Remove (or Don't Generate) Account Access Key

An access key is required in order to sign requests that you make using the AWS Command Line Tools,
the AWS SDKs, or direct API calls. Anyone who has the access key for your AWS account root user has
unrestricted access to all the resources in your account, including billing information. You cannot restrict
the permissions for your AWS account root user.
One of the best ways to protect your account is to not have an access key for your AWS account root
user. Unless you must have a root user access key (which is very rare), it is best not to generate one.
Instead, the recommended best practice is to create one or more AWS Identity and Access Management
(IAM) users, give them the necessary permissions, and use IAM users for everyday interaction with AWS.
If you already have an access key for your account, we recommend the following: Find places in your
applications where you are currently using that key (if any), replace the root user access key with an
IAM user access key, and then disable and remove the root user access key. For details about how to
substitute one access key for another, see the post How to Rotate Access Keys for IAM Users on the AWS
Security Blog.
By default, AWS does not generate an access key for new accounts.
For information about how to create an IAM user with administrative permissions, see Creating Your First
IAM Admin User and Group in the IAM User Guide.
Use Temporary Security Credentials (IAM Roles)

Instead of Long-Term Access Keys
In many scenarios, you don't need a long-term access key that never expires (as you have with an IAM
user). Instead, you can create IAM roles and generate temporary security credentials. Temporary security
credentials consist of an access key ID and a secret access key, but they also include a security token that
indicates when the credentials expire.
Long-term access keys, such as those associated with IAM users and AWS account root users, remain valid
until you manually revoke them. However, temporary security credentials obtained through IAM roles
and other features of the AWS Security Token Service expire after a short period of time. Use temporary
security credentials to help reduce your risk in case credentials are accidentally exposed.
Use an IAM role and temporary security credentials in these scenarios:
• You have an application or AWS CLI scripts running on an Amazon EC2 instance. Do not pass an
access key to the application, embed it in the application, or have the application read a key from a
source such as an Amazon S3 bucket (even if the bucket is encrypted). Instead, define an IAM role that
Version 1.0
112
Manage IAM User Access Keys Properly
has appropriate permissions for your application and launch the Amazon EC2 instance with roles for
EC2. This associates an IAM role with the Amazon EC2 instance and lets the application get temporary
security credentials that it can in turn use to make AWS calls. The AWS SDKs and the AWS CLI can get
temporary credentials from the role automatically.
• You need to grant cross-account access. Use an IAM role to establish trust between accounts,
and then grant users in one account limited permissions to access the trusted account. For more
information, see Tutorial: Delegate Access Across AWS Accounts Using IAM Roles in the IAM User Guide.
• You have a mobile app. Do not embed an access key with the app, even in encrypted storage. Instead,
use Amazon Cognito to manage user identity in your app. This service lets you authenticate users using
Login with Amazon, Facebook, Google, or any OpenID Connect (OIDC)–compatible identity provider.
You can then use the Amazon Cognito credentials provider to manage credentials that your app uses
to make requests to AWS. For more information, see Using the Amazon Cognito Credentials Provider
on the AWS Mobile Blog.
• You want to federate into AWS and your organization supports SAML 2.0. If you work for an
organization that has an identity provider that supports SAML 2.0, configure the provider to use
SAML to exchange authentication information with AWS and get back a set of temporary security
credentials. For more information, see About SAML 2.0-based Federation in the IAM User Guide.
• You want to federate into AWS and your organization has an on-premises identity store. If users
can authenticate inside your organization, you can write an application that can issue them temporary
security credentials for access to AWS resources. For more information, see Creating a URL that
Enables Federated Users to Access the AWS Management Console (Custom Federation Broker) in the
IAM User Guide.
Manage IAM User Access Keys Properly

If you do need to create access keys for programmatic access to AWS, create an IAM user and grant that
user only the permissions he or she needs. Then generate an access key for that user. For details, see
Managing Access Keys for IAM Users in the IAM User Guide.
Note
Remember that if you are running an application on an Amazon EC2 instance and the
application needs access to AWS resources, you should use IAM roles for EC2, as described in the
previous section.
Observe these precautions when using access keys:
• Don't embed access keys directly into code. The AWS SDKs and the AWS Command Line Tools allow
you to put access keys in known locations so that you do not have to keep them in code.
Put access keys in one of the following locations:

• The AWS credentials file. The AWS SDKs and AWS CLI automatically use the credentials that you
store in the AWS credentials file.
For information about using the AWS credentials file, see the documentation for your SDK. Examples
include Set up AWS Credentials and Region for Development in the AWS SDK for Java Developer
Guide and Configuration and Credential Files in the AWS Command Line Interface User Guide.
Note
To store credentials for the AWS SDK for .NET and the AWS Tools for Windows PowerShell,
we recommend that you use the SDK Store. For more information, see Using the SDK Store
in the AWS SDK for .NET Developer Guide.
• Environment variables. On a multitenant system, choose user environment variables, not system
environment variables.
For more information about using environment variables to store credentials, see Environment
Variables in the AWS Command Line Interface User Guide.
Version 1.0
113
More Resources
• Use different access keys for different applications. Do this so that you can isolate the permissions
and revoke the access keys for individual applications if an access key is exposed. Having separate
access keys for different applications also generates distinct entries in AWS CloudTrail log files, which
makes it easier for you to determine which application performed specific actions.
• Rotate access keys periodically. Change access keys on a regular basis. For details, see Rotating Access
Keys (AWS CLI, Tools for Windows PowerShell, and AWS API) in the IAM User Guide and How to Rotate
Access Keys for IAM Users on the AWS Security Blog.
• Remove unused access keys. If a user leaves your organization, remove the corresponding IAM user so
that the user's access to your resources is removed. To find out when an access key was last used, use
the GetAccessKeyLastUsed API (AWS CLI command: aws iam get-access-key-last-used).
• Configure multi-factor authentication for your most sensitive operations. For details, see Using
Multi-Factor Authentication (MFA) in AWS in the IAM User Guide.
More Resources
For more information about best practices for keeping your AWS account secure, see the following
resources:
• IAM Best Practices. This topic presents a list of suggestions for using the AWS Identity and Access
Management (IAM) service to help secure your AWS resources.
• The following pages provide guidance for setting up the AWS SDKs and the AWS CLI to use access
keys.
• Set up AWS Credentials and Region for Development in the AWS SDK for Java Developer Guide.
• Using the SDK Store in the AWS SDK for .NET Developer Guide.
• Providing Credentials to the SDK in the AWS SDK for PHP Developer Guide.
• Configuration in the Boto 3 (AWS SDK for Python) documentation.
• Using AWS Credentials in the AWS Tools for Windows PowerShell guide.
• Configuration and Credential Files in the AWS Command Line Interface User Guide.
• Granting Access Using an IAM Role. This walkthrough discusses how programs written using the .NET
SDK can automatically get temporary security credentials when running on an Amazon EC2 instance. A
similar topic is available for the AWS SDK for Java.
Managing Access Keys for Your AWS Account

You can create, rotate, disable, or delete access keys (access key IDs and secret access keys) for your AWS
account root user. Anyone who has an access key for your AWS account has unrestricted access to all the
resources in your account, including billing information.
We recommend that you don't create access keys for your AWS account and delete any that exist.
Instead, create a user in AWS Identity and Access Management (IAM) and choose Programmatic access
to create an access key for the user. For more information, see Lock away your AWS account root user
access keys in the IAM User Guide.
When you create an access key, AWS gives you an opportunity to view and download the secret access
key only once. If you don't download it or if you lose it, you can delete the access key and then create a
new one.
A newly created access key has the status of active, which means that you can use the access key for API
calls. You can have up to two access keys for your AWS account, which is useful when you want to rotate
the access keys (p. 113). When you disable an access key, you can't use it for API calls.
You can create or delete an access key any time. However, when you delete an access key, it's gone
forever and can't be retrieved.
Version 1.0
114
Creating, Disabling, and Deleting
Access Keys for Your AWS Account
Creating, Disabling, and Deleting Access Keys for Your

AWS Account
Follow these steps to manage access keys for your AWS account. For information about managing access
keys for IAM users, see Managing Access Keys for IAM Users in the IAM User Guide.
To create, disable, or delete an access key for your AWS account root user
1. Use your AWS account email address and password to sign in to the AWS Management Console as
the AWS account root user.
Note
If you previously signed in to the console with IAM user credentials, your browser might
remember this preference and open your account-specific sign-in page. You cannot use the
IAM user sign-in page to sign in with your AWS account root user credentials. If you see the
IAM user sign-in page, choose Sign-in using root user credentials near the bottom of the
page to return to the main sign-in page. From there, you can type your AWS account email
address and password.
2. On the IAM Dashboard page, choose your account name in the navigation bar, and then choose My
Security Credentials.
3. If you see a warning about accessing the security credentials for your AWS account, choose Continue
to Security Credentials.
4. Expand the Access keys (access key ID and secret access key) section.
5. Choose your preferred action:
To create an access key
Choose Create New Access Key. Then choose Download Key File to save the access key ID and
secret access key to a file on your computer. After you close the dialog box, you can't retrieve
this secret access key again.
To disable an existing access key
Choose Make Inactive next to the access key that you are disabling. To reenable an inactive
access key, choose Make Active.
To delete an existing access key
Before you delete an access key, make sure it's no longer in use. For more information, see
Finding unused access keys in the IAM User Guide. You can't recover an access key after deleting
it. To delete your access key, choose Delete next to the access key that you you want to delete.
AWS Security Audit Guidelines

You should periodically audit your security configuration to make sure it meets your current business
needs. An audit gives you an opportunity to remove unneeded IAM users, roles, groups, and policies, and
to make sure that your users and software have only the permissions that are required.
Following are guidelines for systematically reviewing and monitoring your AWS resources for security
best practices.
Topics
• When Should You Perform a Security Audit? (p. 116)
• General Guidelines for Auditing (p. 116)
• Review Your AWS Account Credentials (p. 116)
Version 1.0
115
When Should You Perform a Security Audit?
• Review Your IAM Users (p. 116)

• Review Your IAM Groups (p. 117)
• Review Your IAM Roles (p. 117)
• Review Your IAM Providers for SAML and OpenID Connect (OIDC) (p. 117)
• Review Your Mobile Apps (p. 118)
• Review Your Amazon EC2 Security Configuration (p. 118)
• Review AWS Policies in Other Services (p. 118)
• Monitor Activity in Your AWS Account (p. 119)
• Tips for Reviewing IAM Policies (p. 119)
• More Information (p. 120)
When Should You Perform a Security Audit?

You should audit your security configuration in the following situations:
• On a periodic basis. You should perform the steps described in this document at regular intervals as a
best practice for security.
• If there are changes in your organization, such as people leaving.
• If you have stopped using one or more individual AWS services. This is important for removing
permissions that users in your account no longer need.
• If you've added or removed software in your accounts, such as applications on Amazon EC2 instances,
AWS OpsWorks stacks, AWS CloudFormation templates, etc.
• If you ever suspect that an unauthorized person might have accessed your account.
General Guidelines for Auditing

As you review your account's security configuration, follow these guidelines:
• Be thorough. Look at all aspects of your security configuration, including those you might not use
regularly.
• Don't assume. If you are unfamiliar with some aspect of your security configuration (for example, the
reasoning behind a particular policy or the existence of a role), investigate the business need until you
are satisfied.
• Keep things simple. To make auditing (and management) easier, use IAM groups, consistent naming
schemes, and straightforward policies.
Review Your AWS Account Credentials

Take these steps when you audit your AWS account credentials:
1. If you're not using the root access keys for your account, remove them. We strongly recommend that
you do not use root access keys for everyday work with AWS, and that instead you create IAM users.
2. If you do need to keep the access keys for your account, rotate them regularly.
Review Your IAM Users

Take these steps when you audit your existing IAM users:
Version 1.0
116
Review Your IAM Groups
1. Delete users that are not active.

2. Remove users from groups that they don't need to be a part of.
3. Review the policies attached to the groups the user is in. See Tips for Reviewing IAM Policies (p. 119).
4. Delete security credentials that the user doesn't need or that might have been exposed. For example,
an IAM user that is used for an application does not need a password (which is necessary only to sign
in to AWS websites). Similarly, if a user does not use access keys, there's no reason for the user to have
one. For more information, see Managing Passwords for IAM Users and Managing Access Keys for IAM
Users in the IAM User Guide.
You can generate and download a credential report that lists all IAM users in your account and the
status of their various credentials, including passwords, access keys, and MFA devices. For passwords
and access keys, the credential report shows how recently the password or access key has been
used. Credentials that have not been used recently might be good candidates for removal. For more
information, see Getting Credential Reports for your AWS Account in the IAM User Guide.
5. Rotate (change) user security credentials periodically, or immediately if you ever share them with an
unauthorized person. For more information, see Managing Passwords for IAM Users and Managing
Access Keys for IAM Users in the IAM User Guide.
Review Your IAM Groups

Take these steps when you audit your IAM groups:
1. Delete unused groups.

2. Review users in each group and remove users who don't belong. See Review Your IAM Users (p. 116)
earlier.
3. Review the policies attached to the group. See Tips for Reviewing IAM Policies (p. 119).
Review Your IAM Roles

Take these steps when you audit your IAM roles:
1. Delete roles that are not in use.

2. Review the role's trust policy. Make sure that you know who the principal is and that you understand
why that account or user needs to be able to assume the role.
3. Review the access policy for the role to be sure that it grants suitable permissions to whoever assumes
the role—see Tips for Reviewing IAM Policies (p. 119).
Review Your IAM Providers for SAML and OpenID

Connect (OIDC)
If you have created an IAM entity for establishing trust with a SAML or OIDC identity provider, take these
steps:
1. Delete unused providers.

2. Download and review the AWS metadata documents for each SAML provider and make sure the
documents reflect your current business needs. Alternatively, get the latest metadata documents from
the SAML IdPs that you want to establish trust with and update the provider in IAM.
Version 1.0
117
Review Your Mobile Apps
Review Your Mobile Apps

If you have created a mobile app that makes requests to AWS, take these steps:
1. Make sure that the mobile app does not contain embedded access keys, even if they are in encrypted
storage.
2. Get temporary credentials for the app by using APIs that are designed for that purpose. We
recommend that you use Amazon Cognito to manage user identity in your app. This service lets you
authenticate users using Login with Amazon, Facebook, Google, or any OpenID Connect (OIDC)–
compatible identity provider. You can then use the Amazon Cognito credentials provider to manage
credentials that your app uses to make requests to AWS.
If your mobile app doesn't support authentication using Login with Amazon, Facebook, Google, or any
other OIDC-compatible identity provider, you can create a proxy server that can dispense temporary
credentials to your app.
Review Your Amazon EC2 Security Configuration

Take the following steps for each AWS region:
1. Delete Amazon EC2 key pairs that are unused or that might be known to people outside your
organization.
2. Review your Amazon EC2 security groups:
• Remove security groups that no longer meet your needs.
• Remove rules from security groups that no longer meet your needs. Make sure you know why the
ports, protocols, and IP address ranges they permit have been allowed.
3. Terminate instances that aren't serving a business need or that might have been started by someone
outside your organization for unapproved purposes. Remember that if an instance is started with a
role, applications that run on that instance can access AWS resources using the permissions that are
granted by that role.
4. Cancel spot instance requests that aren't serving a business need or that might have been made by
someone outside your organization.
5. Review your Auto Scaling groups and configurations. Shut down any that no longer meet your needs
or that might have been configured by someone outside your organization.
Review AWS Policies in Other Services

Review the permissions for services that use resource-based policies or that support other security
mechanisms. In each case, make sure that only users and roles with a current business need have access
to the service's resources, and that the permissions granted on the resources are the fewest necessary to
meet your business needs.
• Review your Amazon S3 bucket policies and ACLs.

• Review your Amazon SQS queue policies.
• Review your Amazon SNS topic policies.
• Review your AWS OpsWorks permissions.
• Review your AWS KMS key policies.
Version 1.0
118
Monitor Activity in Your AWS Account
Monitor Activity in Your AWS Account

Follow these guidelines for monitoring AWS activity:
• Turn on AWS CloudTrail in each account and use it in each supported region.
• Periodically examine CloudTrail log files. (CloudTrail has a number of partners who provide tools for
reading and analyzing log files.)
• Enable Amazon S3 bucket logging to monitor requests made to each bucket.
• If you believe there has been unauthorized use of your account, pay particular attention to temporary
credentials that have been issued. If temporary credentials have been issued that you don't recognize,
disable their permissions.
• Enable billing alerts in each account and set a cost threshold that lets you know if your charges exceed
your normal usage.
Tips for Reviewing IAM Policies

Policies are powerful and subtle, so it's important to study and understand the permissions that are
granted by each policy. Use the following guidelines when reviewing policies:
• As a best practice, attach policies to groups instead of to individual users. If an individual user has a
policy, make sure you understand why that user needs the policy.
• Make sure that IAM users, groups, and roles have only the permissions that they need.
• Use the IAM Policy Simulator to test policies that are attached to users or groups.
• Remember that a user's permissions are the result of all applicable policies—user policies, group
policies, and resource-based policies (on Amazon S3 buckets, Amazon SQS queues, Amazon SNS
topics, and AWS KMS keys). It's important to examine all the policies that apply to a user and to
understand the complete set of permissions granted to an individual user.
• Be aware that allowing a user to create an IAM user, group, role, or policy and attach a policy to the
principal entity is effectively granting that user all permissions to all resources in your account. That is,
users who are allowed to create policies and attach them to a user, group, or role can grant themselves
any permissions. In general, do not grant IAM permissions to users or roles whom you do not trust
with full access to the resources in your account. The following list contains IAM permissions that you
should review closely:
• iam:PutGroupPolicy
• iam:PutRolePolicy
• iam:PutUserPolicy
• iam:CreatePolicy
• iam:CreatePolicyVersion
• iam:AttachGroupPolicy
• iam:AttachRolePolicy
• iam:AttachUserPolicy
• Make sure policies don't grant permissions for services that you don't use. For example, if you use
AWS managed policies, make sure the AWS managed policies that are in use in your account are for
services that you actually use. To find out which AWS managed policies are in use in your account, use
the IAM GetAccountAuthorizationDetails API (AWS CLI command: aws iam get-account-
authorization-details).
• If the policy grants a user permission to launch an Amazon EC2 instance, it might also allow the
iam:PassRole action, but if so it should explicitly list the roles that the user is allowed to pass to the
Amazon EC2 instance.
Version 1.0
119
More Information
• Closely examine any values for the Action or Resource element that include *. It's a best practice
to grant Allow access to only the individual actions and resources that users need. However, the
following are reasons that it might be suitable to use * in a policy:
• The policy is designed to grant administrative-level privileges.
• The wildcard character is used for a set of similar actions (for example, Describe*) as a
convenience, and you are comfortable with the complete list of actions that are referenced in this
way.
• The wildcard character is used to indicate a class of resources or a resource path (e.g.,
arn:aws:iam::account-id:users/division_abc/*), and you are comfortable granting access
to all of the resources in that class or path.
• A service action does not support resource-level permissions, and the only choice for a resource is *.
• Examine policy names to make sure they reflect the policy's function. For example, although a
policy might have a name that includes "read only," the policy might actually grant write or change
permissions.
More Information
For information about managing IAM resources, see the following:
• IAM Users and Groups in the IAM User Guide.

• Permissions and Policies in the IAM User Guide.
• IAM Roles (Delegation and Federation) in the IAM User Guide.
• IAM Policy Simulator in the Using IAM Policy Simulator guide.
For more information about Amazon EC2 security, see the following:
• Network and Security in the Amazon EC2 User Guide for Linux Instances.
• Demystifying EC2 Resource-Level Permissions on the AWS Security Blog.
For more information about monitoring an AWS account, see the re:Invent 2013 presentation "Intrusion
Detection in the Cloud" (video, PDF of slide presentation). You can also download a sample Python
program that shows how to automate security auditing functions.
Version 1.0
120
ARN Format
Amazon Resource Names (ARNs) and

AWS Service Namespaces
Amazon Resource Names (ARNs) uniquely identify AWS resources. We require an ARN when you need to
specify a resource unambiguously across all of AWS, such as in IAM policies, Amazon Relational Database
Service (Amazon RDS) tags, and API calls.
Contents
• ARN Format (p. 121)
• Example ARNs (p. 122)
• Paths in ARNs (p. 144)
• AWS Service Namespaces (p. 145)
ARN Format
Here are some example ARNs:


arn:aws:elasticbeanstalk:us-east-1:123456789012:environment/My App/MyEnvironment


arn:aws:iam::123456789012:user/David


arn:aws:rds:eu-west-1:123456789012:db:mysql-db


arn:aws:s3:::my_corporate_bucket/exampleobject.png
The following are the general formats for ARNs; the specific components and values used depend on the
AWS service.
arn:partition:service:region:account-id:resource
arn:partition:service:region:account-id:resourcetype/resource
arn:partition:service:region:account-id:resourcetype:resource
partition
The partition that the resource is in. For standard AWS regions, the partition is aws. If you have
resources in other partitions, the partition is aws-partitionname. For example, the partition for
resources in the China (Beijing) region is aws-cn.
service
The service namespace that identifies the AWS product (for example, Amazon S3, IAM, or Amazon
RDS). For a list of namespaces, see AWS Service Namespaces (p. 145).
region
The region the resource resides in. Note that the ARNs for some resources do not require a region, so
this component might be omitted.
Version 1.0
121
Example ARNs
account
The ID (p. 110) of the AWS account that owns the resource, without the hyphens. For example,
123456789012. Note that the ARNs for some resources don't require an account number, so this
component might be omitted.
resource, resourcetype:resource, or resourcetype/resource
The content of this part of the ARN varies by service. It often includes an indicator of the type of
resource—for example, an IAM user or Amazon RDS database —followed by a slash (/) or a colon (:),
followed by the resource name itself. Some services allow paths for resource names, as described in
Paths in ARNs (p. 144).
Example ARNs
The following sections provide syntax and examples of the ARNs for different services. For more
information about using ARNs in a specific AWS service, see the documentation for that service.
Some services support IAM resource-level permissions. For more information, see AWS Services That
Work with IAM.
Services
• Alexa for Business (p. 124)
• Amazon API Gateway (p. 124)
• AWS AppSync (p. 124)
• AWS Artifact (p. 124)
• Amazon EC2 Auto Scaling (p. 125)
• AWS Certificate Manager (p. 125)
• AWS Cloud9 (p. 125)
• Amazon Cloud Directory (p. 125)
• AWS CloudFormation (p. 126)
• Amazon CloudFront (p. 126)
• Amazon CloudSearch (p. 126)
• AWS CloudTrail (p. 126)
• Amazon CloudWatch (p. 126)
• Amazon CloudWatch Events (p. 127)
• Amazon CloudWatch Logs (p. 127)
• AWS CodeBuild (p. 127)
• AWS CodeCommit (p. 128)
• AWS CodeDeploy (p. 128)
• Amazon Cognito Your User Pools (p. 128)
• Amazon Cognito Federated Identities (p. 128)
• Amazon Cognito Sync (p. 128)
• AWS Config (p. 129)
• AWS CodePipeline (p. 129)
• AWS CodeStar (p. 129)
• AWS Direct Connect (p. 129)
• AWS Directory Service (p. 130)
• Amazon DynamoDB (p. 130)
Version 1.0
122
Example ARNs
• AWS Elastic Beanstalk (p. 130)

• Amazon Elastic Compute Cloud (Amazon EC2) (p. 130)
• Amazon Elastic Container Registry (Amazon ECR) (p. 131)
• Amazon Elastic Container Service (Amazon ECS) (p. 131)
• Amazon Elastic File System (p. 132)
• Elastic Load Balancing (Application Load Balancer) (p. 132)
• Elastic Load Balancing (Network Load Balancer) (p. 132)
• Elastic Load Balancing (Classic Load Balancer) (p. 133)
• Amazon Elastic Transcoder (p. 133)
• Amazon ElastiCache (p. 133)
• Amazon Elasticsearch Service (p. 133)
• Amazon Glacier (p. 133)
• Amazon GuardDuty (p. 134)
• AWS Health / Personal Health Dashboard (p. 134)
• AWS Identity and Access Management (IAM) (p. 134)
• AWS IoT (p. 135)
• AWS Key Management Service (AWS KMS) (p. 135)
• Amazon Kinesis Data Firehose (Kinesis Data Firehose) (p. 135)
• Amazon Kinesis Data Streams (Kinesis Data Streams) (p. 136)
• Amazon Kinesis Data Analytics (Kinesis Data Analytics) (p. 136)
• Amazon Kinesis Video Streams (Kinesis Video Streams) (p. 136)
• AWS Lambda (Lambda) (p. 136)
• Amazon Machine Learning (Amazon ML) (p. 137)
• AWS Elemental MediaConvert (p. 137)
• AWS Elemental MediaLive (p. 137)
• AWS Elemental MediaPackage (p. 137)
• AWS Elemental MediaStore (p. 138)
• AWS Elemental MediaTailor (p. 138)
• AWS Mobile Hub (p. 138)
• Amazon MQ (p. 138)
• AWS Organizations (p. 139)
• Amazon Pinpoint (p. 139)
• Amazon Polly (p. 139)
• Amazon Redshift (p. 139)
• Amazon Relational Database Service (Amazon RDS) (p. 140)
• Amazon Route 53 (p. 140)
• AWS Serverless Application Repository (p. 141)
• Amazon Simple Email Service (Amazon SES) (p. 141)
• Amazon Simple Notification Service (Amazon SNS) (p. 141)
• Amazon Simple Storage Service (Amazon S3) (p. 142)
• Amazon Simple Workflow Service (Amazon SWF) (p. 142)
• AWS Step Functions (p. 142)
• AWS Storage Gateway (p. 143)
• AWS Systems Manager (p. 143)
• AWS Trusted Advisor (p. 143)
Version 1.0
123
Alexa for Business
• AWS WAF (p. 144)
Alexa for Business

Syntax:
arn:aws:a4b:region:accountid:resourcetype/resource
Example:
arn:aws:a4b:us-
east-1:123456789012:room/7315ffdf0eeb874dc4ab8a546e8b70ec/5f90e5d608b6baa9c88db56654aef158
Amazon API Gateway

Syntax:
arn:aws:apigateway:region::resource-path
arn:aws:execute-api:region:account-id:api-id/stage-name/HTTP-VERB/resource-path
Examples:
arn:aws:apigateway:us-east-1::/restapis/a123456789012bc3de45678901f23a45/*
arn:aws:apigateway:us-east-1::a123456789012bc3de45678901f23a45:/test/mydemoresource/*
arn:aws:apigateway:*::a123456789012bc3de45678901f23a45:/*/petstorewalkthrough/pets
arn:aws:execute-api:us-east-1:123456789012:qsxrty/test/GET/mydemoresource/*
AWS AppSync
Syntax:
arn:aws:appsync:your-region:account-id:apis/AppSyncEndpointName/types/Query/fields/field-
name
arn:aws:appsync:your-region:account-id:apis/AppSyncEndpointName/types/Mutation/
fields/field-name
arn:aws:appsync:your-region:account-id:apis/AppSyncEndpointName/types/Subscription/
fields/field-name
Examples:
arn:aws:appsync:us-west-2:123456789012:apis/AppSyncEndpointName/types/Query/fields/posts
arn:aws:appsync:us-west-2:123456789012:apis/AppSyncEndpointName/types/Mutation/fields/
addPost
arn:aws:appsync:us-west-2:123456789012:apis/AppSyncEndpointName/types/Query/fields/my-
subscription
AWS Artifact
Syntax:
arn:aws:artifact:::report-package/document-type/report-type
Version 1.0
124
Examples:
arn:aws:artifact:::report-package/Certifications and Attestations/SOC/*

arn:aws:artifact:::report-package/Certifications and Attestations/ISO/*
arn:aws:artifact:::report-package/Certifications and Attestations/PCI/*

Syntax:
arn:aws:autoscaling:region:account-
id:scalingPolicy:policyid:autoScalingGroupName/groupfriendlyname:policyname/
policyfriendlyname
arn:aws:autoscaling:region:account-
id:autoScalingGroup:groupid:autoScalingGroupName/groupfriendlyname
Example:
arn:aws:autoscaling:us-east-1:123456789012:scalingPolicy:c7a27f55-d35e-4153-
b044-8ca9155fc467:autoScalingGroupName/my-test-asg1:policyName/my-scaleout-policy

Syntax:
arn:aws:acm:region:account-id:certificate/certificate-id
Example:
arn:aws:acm:us-east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012
AWS Cloud9
Syntax:
arn:aws:cloud9:region:account-id:environment:environment-id
Example:
arn:aws:cloud9:us-west-2:123456789012:environment:81e900317347585a0601e04c8d52eaEX
Amazon Cloud Directory

Syntax:
arn:aws:clouddirectory:region:account-id:directory/directoryID
Example:
arn:aws:clouddirectory:us-west-2:123456789012:directory/ARIqk1HD-UjdtmcIrJHEvPI
Version 1.0
125
AWS CloudFormation
AWS CloudFormation
Syntax:
arn:aws:cloudformation:region:account-id:stack/stackname/additionalidentifier
arn:aws:cloudformation:region:account-id:changeSet/changesetname/additionalidentifier
Examples:
arn:aws:cloudformation:us-east-1:123456789012:stack/MyProductionStack/abc9dbf0-43c2-11e3-
a6e8-50fa526be49c
arn:aws:cloudformation:us-east-1:123456789012:changeSet/MyProductionChangeSet/
abc9dbf0-43c2-11e3-a6e8-50fa526be49c
Amazon CloudFront
Syntax:
arn:aws:cloudfront::account-id:*
Example:
arn:aws:cloudfront::123456789012:*
Amazon CloudSearch
Syntax:
arn:aws:cloudsearch:region:account-id:domain/domainname
Example:
arn:aws:cloudsearch:us-east-1:123456789012:domain/imdb-movies
AWS CloudTrail
Syntax:
arn:aws:cloudtrail:region:account-id:trail/trailname
Example:
arn:aws:cloudtrail:us-east-1:123456789012:trail/mytrailname
Amazon CloudWatch
Syntax:
Version 1.0
126
arn:aws:cloudwatch:region:account-id:alarm:alarm-name
arn:aws:cloudwatch::account-id:dashboard/dashboard-name
Examples:
arn:aws:cloudwatch:us-east-1:123456789012:alarm:*
arn:aws:cloudwatch:us-east-1:123456789012:alarm:MyAlarmName
arn:aws:cloudwatch::123456789012:dashboard/MyDashboardName

Syntax:
arn:aws:events:region:*:*
Examples:
arn:aws:events:us-east-1:*:*
arn:aws:events:us-east-1:123456789012:*
arn:aws:events:us-east-1:123456789012:rule/my-rule

Syntax:
arn:aws:logs:region:*:*
Examples:
arn:aws:logs:us-east-1:*:*
arn:aws:logs:us-east-1:123456789012:*
arn:aws:logs:us-east-1:123456789012:log-group:my-log-group
arn:aws:logs:us-east-1:123456789012:log-group:my-log-group:*
arn:aws:logs:us-east-1:123456789012:log-group:my-log-group*
arn:aws:logs:us-east-1:123456789012:log-group:my-log-group:log-stream:my-log-stream
arn:aws:logs:us-east-1:123456789012:log-group:my-log-group:log-stream:my-log-stream*
arn:aws:logs:us-east-1:123456789012:log-group:my-log-group*:log-stream:my-log-stream*
AWS CodeBuild
Syntax:
arn:aws:codebuild:region:account-id:resourcetype/resource
Examples:
arn:aws:codebuild:us-east-1:123456789012:project/my-demo-project
arn:aws:codebuild:us-east-1:123456789012:build/my-demo-
project:7b7416ae-89b4-46cc-8236-61129df660ad
Version 1.0
127
AWS CodeCommit
AWS CodeCommit
Syntax:
arn:aws:codecommit:region:account-id:resource-specifier
Example:
arn:aws:codecommit:us-east-1:123456789012:MyDemoRepo
AWS CodeDeploy
Syntax:
arn:aws:codedeploy:region:account-id:resource-type:resource-specifier
arn:aws:codedeploy:region:account-id:resource-type/resource-specifier
Example:
arn:aws:codedeploy:us-east-1:123456789012:application:WordPress_App
arn:aws:codedeploy:us-east-1:123456789012:instance/AssetTag*

Syntax:
arn:aws:cognito-idp:region:account-id:userpool/user-pool-id
Example:
arn:aws:cognito-idp:us-east-1:123456789012:userpool/us-east-1:1a1a1a1a-
ffff-1111-9999-12345678
Amazon Cognito Federated Identities

Syntax:
arn:aws:cognito-identity:region:account-id:identitypool/identity-pool-id
Example:
arn:aws:cognito-identity:us-east-1:123456789012:/identitypool/us-east-1:1a1a1a1a-
ffff-1111-9999-12345678
Amazon Cognito Sync

Syntax:
arn:aws:cognito-sync:region:account-id:identitypool/identity-pool-id
Version 1.0
128
AWS Config
arn:aws:cognito-sync:region:account-id:identitypool/identity-pool-id/identity/identity-id
arn:aws:cognito-sync:region:account-id:identitypool/identity-pool-id/identity/identity-id/
dataset/dataset-name
Example:
arn:aws:cognito-sync:us-east-1:123456789012:identitypool/us-east-1:1a1a1a1a-
ffff-1111-9999-12345678
AWS Config
Syntax:
arn:aws:config:region:account-id:config-rule/config-rule-id
Example:
arn:aws:config:us-east-1:123456789012:config-rule/config-rule-8fngan
AWS CodePipeline
Syntax:
arn:aws:codepipeline:region:account-id:resource-specifier
Example:
arn:aws:codepipeline:us-east-1:123456789012:MyDemoPipeline
AWS CodeStar
Syntax:
arn:aws:codestar:region:account-id:resource-specifier
Example:
arn:aws:codestar:us-east-1:123456789012:my-first-project
AWS Direct Connect

Syntax:
arn:aws:directconnect:region:account-id:dxcon/connection-id
arn:aws:directconnect:region:account-id:dxlag/lag-id
arn:aws:directconnect:region:account-id:dxvif/virtual-interface-id
Examples:
Version 1.0
129
arn:aws:directconnect:us-east-1:123456789012:dxcon/dxcon-fgase048
arn:aws:directconnect:us-east-1:123456789012:dxlag/dxlag-ffy7zraq
arn:aws:directconnect:us-east-1:123456789012:dxvif/dxvif-fgrb110x

Syntax:
arn:aws:ds:region:account-id:directory/directoryId
Example:
arn:aws:ds:us-west-2:123456789012:directory/ARIqk1HD-UjdtmcIrJHEvPI
Amazon DynamoDB
Syntax:
arn:aws:dynamodb:region:account-id:table/tablename
arn:aws:dynamodb:region:account-id:table/tablename/stream/label
Example:
arn:aws:dynamodb:us-east-1:123456789012:table/books_table
arn:aws:dynamodb:us-east-1:123456789012:table/books_table/stream/2015-05-11T21:21:33.291

Syntax:
arn:aws:elasticbeanstalk:region:account-id:application/applicationname
arn:aws:elasticbeanstalk:region:account-id:applicationversion/applicationname/versionlabel
arn:aws:elasticbeanstalk:region:account-id:environment/applicationname/environmentname
arn:aws:elasticbeanstalk:region::solutionstack/solutionstackname
arn:aws:elasticbeanstalk:region:account-
id:configurationtemplate/applicationname/templatename
Examples:
arn:aws:elasticbeanstalk:us-east-1:123456789012:application/My App
arn:aws:elasticbeanstalk:us-east-1:123456789012:applicationversion/My App/My Version
arn:aws:elasticbeanstalk:us-east-1:123456789012:environment/My App/MyEnvironment
arn:aws:elasticbeanstalk:us-east-1::solutionstack/32bit Amazon Linux running Tomcat 7
arn:aws:elasticbeanstalk:us-east-1:123456789012:configurationtemplate/My App/My Template

Syntax:
arn:aws:ec2:region:account-id:customer-gateway/cgw-id
arn:aws:ec2:region:account-id:dedicated-host/host_id
arn:aws:ec2:region:account-id:dhcp-options/dhcp-options-id
arn:aws:ec2:region:account-id:egress-only-internet-gateway/eigw-id
Version 1.0
130
Amazon Elastic Container Registry (Amazon ECR)
arn:aws:ec2:region:account-id:elastic-gpu/elastic-gpu-id
arn:aws:ec2:region::image/image-id
arn:aws:ec2:region:account-id:instance/instance-id
arn:aws:iam::account:instance-profile/instance-profile-name
arn:aws:ec2:region:account-id:internet-gateway/igw-id
arn:aws:ec2:region:account-id:key-pair/key-pair-name
arn:aws:ec2:region:account-id:launch-template/launch-template-id
arn:aws:ec2:region:account-id:natgateway/natgateway-id
arn:aws:ec2:region:account-id:network-acl/nacl-id
arn:aws:ec2:region:account-id:network-interface/eni-id
arn:aws:ec2:region:account-id:placement-group/placement-group-name
arn:aws:ec2:region:account-id:reserved-instances/reservation-id
arn:aws:ec2:region:account-id:route-table/route-table-id
arn:aws:ec2:region:account-id:security-group/security-group-id
arn:aws:ec2:region::snapshot/snapshot-id
arn:aws:ec2:region:account-id:spot-instances-request/spot-instance-request-id
arn:aws:ec2:region:account-id:subnet/subnet-id
arn:aws:ec2:region:account-id:volume/volume-id
arn:aws:ec2:region:account-id:vpc/vpc-id
arn:aws:ec2:region:account-id:vpc-peering-connection/vpc-peering-connection-id
arn:aws:ec2:region:account-id:vpn-connection/vpn-id
arn:aws:ec2:region:account-id:vpn-gateway/vgw-id
Examples:
arn:aws:ec2:us-east-1:123456789012:dedicated-host/h-12345678
arn:aws:ec2:us-east-1::image/ami-1a2b3c4d
arn:aws:ec2:us-east-1:123456789012:instance/*
arn:aws:ec2:us-east-1:123456789012:volume/*
arn:aws:ec2:us-east-1:123456789012:volume/vol-1a2b3c4d

Syntax:
arn:aws:ecr:region:account-id:repository/repository-name
Example:
arn:aws:ecr:us-east-1:123456789012:repository/my-repository
Amazon Elastic Container Service (Amazon ECS)

Syntax:
arn:aws:ecs:region:account-id:cluster/cluster-name
arn:aws:ecs:region:account-id:container-instance/container-instance-id
arn:aws:ecs:region:account-id:task-definition/task-definition-family-name:task-definition-
revision-number
arn:aws:ecs:region:account-id:service/service-name
arn:aws:ecs:region:account-id:task/task-id
arn:aws:ecs:region:account-id:container/container-id
Examples:
arn:aws:ecs:us-east-1:123456789012:cluster/my-cluster
arn:aws:ecs:us-east-1:123456789012:container-instance/403125b0-555c-4473-86b5-65982db28a6d
arn:aws:ecs:us-east-1:123456789012:task-definition/hello_world:8
Version 1.0
131
arn:aws:ecs:us-east-1:123456789012:service/sample-webapp
arn:aws:ecs:us-east-1:123456789012:task/1abf0f6d-a411-4033-b8eb-a4eed3ad252a
arn:aws:ecs:us-east-1:123456789012:container/476e7c41-17f2-4c17-9d14-412566202c8a

Syntax:
arn:aws:elasticfilesystem:region:account-id:file-system/file-system-id
Example:
arn:aws:elasticfilesystem:us-east-1:123456789012:file-system-id/fs12345678
Elastic Load Balancing (Application Load Balancer)

Syntax:
arn:aws:elasticloadbalancing:region:account-id:loadbalancer/app/load-balancer-name/load-
balancer-id
arn:aws:elasticloadbalancing:region:account-id:listener/app/load-balancer-name/load-
balancer-id/listener-id
arn:aws:elasticloadbalancing:region:account-id:listener-rule/app/load-balancer-name/load-
balancer-id/listener-id/rule-id
arn:aws:elasticloadbalancing:region:account-id:targetgroup/target-group-name/target-group-
id
Examples:
arn:aws:elasticloadbalancing:us-east-1:123456789012:loadbalancer/app/my-load-
balancer/50dc6c495c0c9188
arn:aws:elasticloadbalancing:us-east-1:123456789012:listener/app/my-load-
balancer/50dc6c495c0c9188/f2f7dc8efc522ab2
arn:aws:elasticloadbalancing:us-east-1:123456789012:listener-rule/app/my-load-
balancer/50dc6c495c0c9188/f2f7dc8efc522ab2/9683b2d02a6cabee
arn:aws:elasticloadbalancing:us-east-1:123456789012:targetgroup/my-targets/73e2d6bc24d8a067
Elastic Load Balancing (Network Load Balancer)

Syntax:
arn:aws:elasticloadbalancing:region:account-id:loadbalancer/net/load-balancer-name/load-
balancer-id
arn:aws:elasticloadbalancing:region:account-id:listener/net/load-balancer-name/load-
balancer-id/listener-id
arn:aws:elasticloadbalancing:region:account-id:listener-rule/net/load-balancer-name/load-
balancer-id/listener-id/rule-id
arn:aws:elasticloadbalancing:region:account-id:targetgroup/target-group-name/target-group-
id
Examples:
arn:aws:elasticloadbalancing:us-east-1:123456789012:loadbalancer/net/my-load-
balancer/50dc6c495c0c9188
arn:aws:elasticloadbalancing:us-east-1:123456789012:listener/net/my-load-
balancer/50dc6c495c0c9188/f2f7dc8efc522ab2
Version 1.0
132
Elastic Load Balancing (Classic Load Balancer)
arn:aws:elasticloadbalancing:us-east-1:123456789012:listener-rule/net/my-load-
balancer/50dc6c495c0c9188/f2f7dc8efc522ab2/9683b2d02a6cabee
arn:aws:elasticloadbalancing:us-east-1:123456789012:targetgroup/my-targets/73e2d6bc24d8a067
Elastic Load Balancing (Classic Load Balancer)

Syntax:
arn:aws:elasticloadbalancing:region:account-id:loadbalancer/name
Example:
arn:aws:elasticloadbalancing:us-east-1:123456789012:loadbalancer/my-load-balancer

Syntax:
arn:aws:elastictranscoder:region:account-id:resource/id
Example:
arn:aws:elastictranscoder:us-east-1:123456789012:preset/*
Amazon ElastiCache
Syntax:
arn:aws:elasticache:region:account-id:resourcetype:resourcename
Examples:
arn:aws:elasticache:us-east-2:123456789012:cluster:myCluster
arn:aws:elasticache:us-east-2:123456789012:snapshot:mySnapshot

Syntax:
arn:aws:es:region:account-id:domain/domain-name
Example:
arn:aws:es:us-east-1:123456789012:domain/streaming-logs
Amazon Glacier
Syntax:
arn:aws:glacier:region:account-id:vaults/vaultname
Version 1.0
133
Amazon GuardDuty
Examples:
arn:aws:glacier:us-east-1:123456789012:vaults/examplevault
arn:aws:glacier:us-east-1:123456789012:vaults/example*
arn:aws:glacier:us-east-1:123456789012:vaults/*
Amazon GuardDuty
Syntax:
arn:aws:guardduty:region:account-id:detector/detector-id
arn:aws:guardduty:region:account-id:ipset/ipset-id
arn:aws:guardduty:region:account-id:threatintelset/threatintelset-id
Examples:
arn:aws:guardduty:us-east-1:123456789012:detector/12abc34d567e8fa901bc2d34e56789f0
arn:aws:guardduty:us-east-1:123456789012:ipset/0cb0141ab9fbde177613ab9436212e90
arn:aws:guardduty:us-east-1:123456789012:threatintelset/12a34567890bc1de2345f67ab8901234
AWS Health / Personal Health Dashboard

Syntax:
arn:aws:health:region::event/event-id
arn:aws:health:region:account-id:entity/entity-id
Examples:
arn:aws:health:us-east-1::event/AWS_EC2_EXAMPLE_ID
arn:aws:health:us-east-1:123456789012:entity/AVh5GGT7ul1arKr1sE1K
AWS Identity and Access Management (IAM)

Syntax:
arn:aws:iam::account-id:root
arn:aws:iam::account-id:user/user-name
arn:aws:iam::account-id:group/group-name
arn:aws:iam::account-id:role/role-name
arn:aws:iam::account-id:policy/policy-name
arn:aws:iam::account-id:instance-profile/instance-profile-name
arn:aws:sts::account-id:federated-user/user-name
arn:aws:sts::account-id:assumed-role/role-name/role-session-name
arn:aws:iam::account-id:mfa/virtual-device-name
arn:aws:iam::account-id:server-certificate/certificate-name
arn:aws:iam::account-id:saml-provider/provider-name
arn:aws:iam::account-id:oidc-provider/provider-name
Version 1.0
134
AWS IoT
Examples:
arn:aws:iam::123456789012:root
arn:aws:iam::123456789012:user/Bob
arn:aws:iam::123456789012:user/division_abc/subdivision_xyz/Bob
arn:aws:iam::123456789012:group/Developers
arn:aws:iam::123456789012:group/division_abc/subdivision_xyz/product_A/Developers
arn:aws:iam::123456789012:role/S3Access
arn:aws:iam::123456789012:role/application_abc/component_xyz/S3Access
arn:aws:iam::123456789012:policy/UsersManageOwnCredentials
arn:aws:iam::123456789012:policy/division_abc/subdivision_xyz/UsersManageOwnCredentials
arn:aws:iam::123456789012:instance-profile/Webserver
arn:aws:sts::123456789012:federated-user/Bob
arn:aws:sts::123456789012:assumed-role/Accounting-Role/Mary
arn:aws:iam::123456789012:mfa/BobJonesMFA
arn:aws:iam::123456789012:server-certificate/ProdServerCert
arn:aws:iam::123456789012:server-certificate/division_abc/subdivision_xyz/ProdServerCert
arn:aws:iam::123456789012:saml-provider/ADFSProvider
arn:aws:iam::123456789012:oidc-provider/GoogleProvider
For more information about IAM ARNs, see IAM ARNs in IAM User Guide.
AWS IoT
Syntax:
arn:aws:iot:your-region:account-id:cert/cert-ID
arn:aws:iot:your-region:account-id:policy/policy-name
arn:aws:iot:your-region:account-id:rule/rule-name
arn:aws:iot:your-region:account-id:client/client-id/rule-name
Examples:
arn:aws:iot:your-
region:123456789012:cert/123a456b789c123d456e789f123a456b789c123d456e789f123a456b789c123c456d7
arn:aws:iot:your-region:123456789012:policy/MyIoTPolicy
arn:aws:iot:your-region:123456789012:rule/MyIoTRule
arn:aws:iot:your-region:123456789012:client/client101
AWS Key Management Service (AWS KMS)

Syntax:
arn:aws:kms:region:account-id:key/key-id
arn:aws:kms:region:account-id:alias/alias
Examples:
arn:aws:kms:us-east-1:123456789012:key/12345678-1234-1234-1234-123456789012
arn:aws:kms:us-east-1:123456789012:alias/example-alias
Amazon Kinesis Data Firehose (Kinesis Data Firehose)

Syntax:
arn:aws:firehose:region:account-id:deliverystream/delivery-stream-name
Version 1.0
135
Amazon Kinesis Data Streams (Kinesis Data Streams)
Example:
arn:aws:firehose:us-east-1:123456789012:deliverystream/example-stream-name
Amazon Kinesis Data Streams (Kinesis Data Streams)

Syntax:
arn:aws:kinesis:region:account-id:stream/stream-name
Example:
arn:aws:kinesis:us-east-1:123456789012:stream/example-stream-name
Amazon Kinesis Data Analytics (Kinesis Data

Analytics)
Syntax:
arn:aws:kinesisanalytics:region:account-id:application/application-name
Example:
arn:aws:kinesisanalytics:us-east-1:123456789012:application/example-application-name
Amazon Kinesis Video Streams (Kinesis Video

Streams)
Syntax:
arn:aws:kinesisvideo:region:account-id:application/stream-name/code
Example:
arn:aws:kinesisvideo:us-east-1:123456789012:stream/example-stream-name/0123456789012
AWS Lambda (Lambda)

Syntax:
arn:aws:lambda:region:account-id:function:function-name
arn:aws:lambda:region:account-id:function:function-name:alias-name
arn:aws:lambda:region:account-id:function:function-name:version
arn:aws:lambda:region:account-id:event-source-mappings:event-source-mapping-id
Examples:
arn:aws:lambda:us-east-1:123456789012:function:ProcessKinesisRecords
arn:aws:lambda:us-east-1:123456789012:function:ProcessKinesisRecords:your alias
Version 1.0
136
Amazon Machine Learning (Amazon ML)
arn:aws:lambda:us-east-1:123456789012:function:ProcessKinesisRecords:1.0
arn:aws:lambda:us-east-1:123456789012:event-source-mappings:kinesis-stream-arn
Amazon Machine Learning (Amazon ML)

Syntax:
arn:aws:machinelearning:region:account-id:datasource/datasourceID
arn:aws:machinelearning:region:account-id:mlmodel/mlmodelID
arn:aws:machinelearning:region:account-id:batchprediction/batchpredictionlID
arn:aws:machinelearning:region:account-id:evaluation/evaluationID
Examples:
arn:aws:machinelearning:us-east-1:123456789012:datasource/my-datasource-1
arn:aws:machinelearning:us-east-1:123456789012:mlmodel/my-mlmodel
arn:aws:machinelearning:us-east-1:123456789012:batchprediction/my-batchprediction
arn:aws:machinelearning:us-east-1:123456789012:evaluation/my-evaluation
AWS Elemental MediaConvert

Syntax:
arn:aws:mediaconvert:region:account-id:jobs/jobID
arn:aws:mediaconvert:region:account-id:jobTemplates/jobTemplateID
arn:aws:mediaconvert:region:account-id:presets/presetID
arn:aws:mediaconvert:region:account-id:queues/queueID
Examples:
arn:aws:mediaconvert:us-east-1:111111111111:jobs/0123456789012-abc123
arn:aws:mediaconvert:us-east-1:111111111111:jobTemplates/2345678
arn:aws:mediaconvert:us-east-1:111111111111:presets/System-169_WIFI_1080p
arn:aws:mediaconvert:us-east-1:111111111111:queues/default
AWS Elemental MediaLive

Syntax:
arn:aws:medialive:region:account-id:inputSecurityGroup:inputSecurityGroupID
arn:aws:medialive:region:account-id:input:inputID
arn:aws:medialive:region:account-id:channel:channelID
Examples:
arn:aws:medialive:us-east-1:111111111111:inputSecurityGroup:1234567
arn:aws:medialive:us-east-1:111111111111:input:2345678
arn:aws:medialive:us-east-1:111111111111:channel:3456789

Syntax:
arn:aws:mediapackage:region:account-id:channels/channelID
Version 1.0
137
arn:aws:mediapackage:region:account-id:origin_endpoints/originEndpointID
Examples:
arn:aws:mediapackage:eu-west-1:111122223333:channels/0a1234bc567890d12efghi3j456k789m
arn:aws:mediapackage:eu-
west-1:111122223333:origin_endpoints/1b2345cd678901e34fghij4k567m890n

Syntax:
arn:aws:mediastore:region:account-id:resourceType/resourceID
Examples:
arn:aws:mediastore:us-east-1:111111111111:container/ExampleName/example-folder/folder-
segment.ts

Syntax:
arn:aws:mediatailor:region:account-id:configurations/configurationID
Examples:
arn:aws:mediatailor:us-east-1:111111111111:configurations/2c3456de789012f34ghijk5m678n901o
AWS Mobile Hub

Syntax:
arn:aws:mobilehub:region:account-id:project/projectID
Examples:
arn:aws:mobilehub:us-east-1:123456789012:project/a01234567-b012345678-123c-d013456789abc
Amazon MQ
Syntax:
arn:aws:mq:region:account-id:broker:broker-name:broker-id
arn:aws:mq:region:account-id:configuration:configuration-name:configuration-id
Examples:
arn:aws:mq:us-east-1:123456789012:broker:MyBroker:b-1234a5b6-78cd-901e-2fgh-3i45j6k178l9
arn:aws:mq:us-
east-1:123456789012:configuration:MyConfiguration:c-1234a5b6-78cd-901e-2fgh-3i45j6k178l9
Version 1.0
138
AWS Organizations
AWS Organizations
Syntax:
arn:aws:organizations::master-account-id:organization/o-organization-id
arn:aws:organizations::master-account-id:root/o-organization-id/r-root-id
arn:aws:organizations::master-account-id:account/o-organization-id/account-id
arn:aws:organizations::master-account-id:ou/o-organization-id/ou-organizational-unit-id
arn:aws:organizations::master-account-id:policy/o-organization-id/policy-type/p-policy-id
arn:aws:organizations::master-account-id:handshake/o-organization-id/handshake-type/
h-handshake-id
Example:
arn:aws:organizations::123456789012:organization/o-a1b2c3d4e5example
arn:aws:organizations::123456789012:root/o-a1b2c3d4e5/r-f6g7h8i9j0example
arn:aws:organizations::123456789012:account/o-a1b2c3d4e5/123456789012
arn:aws:organizations::123456789012:ou/o-a1b2c3d4e5/ou-1a2b3c-k9l8m7n6o5example
arn:aws:organizations::123456789012:policy/o-a1b2c3d4e5/service_control_policy/p-
p4q3r2s1t0example
arn:aws:organizations::123456789012:handshake/o-a1b2c3d4e5/h-u2v4w5x8y0example
Amazon Pinpoint
Syntax:
arn:aws:mobiletargeting:us-east-1:account-id:apps/appId
arn:aws:mobiletargeting:us-east-1:account-id:apps/appId/campaigns/campaignId
arn:aws:mobiletargeting:us-east-1:account-id:apps/appId/segments/segmentId
Examples:
arn:aws:mobiletargeting:us-east-1:123456789012:apps/0d72ff0905e7f8b2b879fe7744d4952a9b
arn:aws:mobiletargeting:us-east-1:123456789012:apps/0d72ff0905e7f8b2b879fe7744d4952a9b/
campaigns/8c95f63b24089f85819443be7c92d7
arn:aws:mobiletargeting:us-east-1:123456789012:apps/0d72ff0905e7f8b2b879fe7744d4952a9b/
segments/6cdc025ba495672bb0aea4983afebf
Amazon Polly
Syntax:
arn:aws:polly:region:account-id:lexicon/LexiconName
Example:
arn:aws:polly:us-east-1:123456789012:lexicon/myLexicon
Amazon Redshift
Syntax:
arn:aws:redshift:region:account-id:cluster:cluster-name
arn:aws:redshift:region:account-id:dbname:cluster-name/database-name
Version 1.0
139
Amazon Relational Database Service (Amazon RDS)
arn:aws:redshift:region:account-id:dbuser:cluster-name/database-user-name
arn:aws:redshift:region:account-id:dbgroup:cluster-name/database-group-name
arn:aws:redshift:region:account-id:parametergroup:parameter-group-name
arn:aws:redshift:region:account-id:securitygroup:security-group-name
arn:aws:redshift:region:account-id:snapshot:cluster-name/snapshot-name
arn:aws:redshift:region:account-id:subnetgroup:subnet-group-name
Examples:
arn:aws:redshift:us-east-1:123456789012:cluster:my-cluster
arn:aws:redshift:us-east-1:123456789012:dbname:my-cluster/my-database
arn:aws:redshift:us-east-1:123456789012:dbuser:my-cluster/my-database-user
arn:aws:redshift:us-east-1:123456789012:dbgroup:my-cluster/my-database-group
arn:aws:redshift:us-east-1:123456789012:parametergroup:my-parameter-group
arn:aws:redshift:us-east-1:123456789012:securitygroup:my-public-group
arn:aws:redshift:us-east-1:123456789012:snapshot:my-cluster/my-snapshot20130807
arn:aws:redshift:us-east-1:123456789012:subnetgroup:my-subnet-10
Amazon Relational Database Service (Amazon RDS)

ARNs are used in Amazon RDS only with tags for DB instances. For more information, see Tagging a DB
Instance in the Amazon Relational Database Service User Guide.
Syntax:
arn:aws:rds:region:account-id:db:db-instance-name
arn:aws:rds:region:account-id:snapshot:snapshot-name
arn:aws:rds:region:account-id:cluster:db-cluster-name
arn:aws:rds:region:account-id:cluster-snapshot:cluster-snapshot-name
arn:aws:rds:region:account-id:og:option-group-name
arn:aws:rds:region:account-id:pg:parameter-group-name
arn:aws:rds:region:account-id:cluster-pg:cluster-parameter-group-name
arn:aws:rds:region:account-id:secgrp:security-group-name
arn:aws:rds:region:account-id:subgrp:subnet-group-name
arn:aws:rds:region:account-id:es:subscription-name
Examples:
arn:aws:rds:us-east-1:123456789012:db:mysql-db-instance1
arn:aws:rds:us-east-1:123456789012:snapshot:my-snapshot2
arn:aws:rds:us-east-1:123456789012:cluster:my-cluster1
arn:aws:rds:us-east-1:123456789012:cluster-snapshot:cluster1-snapshot7
arn:aws:rds:us-east-1:123456789012:og:mysql-option-group1
arn:aws:rds:us-east-1:123456789012:pg:mysql-repl-pg1
arn:aws:rds:us-east-1:123456789012:cluster-pg:aurora-pg3
arn:aws:rds:us-east-1:123456789012:secgrp:dev-secgrp2
arn:aws:rds:us-east-1:123456789012:subgrp:prod-subgrp1
arn:aws:rds:us-east-1:123456789012:es:monitor-events2
Amazon Route 53
Syntax:
arn:aws:route53:::hostedzone/zoneid
arn:aws:route53:::change/change-id
arn:aws:route53::account-id:domain/domain-name
arn:aws:servicediscovery:region:account-id:namespace/namespace-id
arn:aws:servicediscovery:region:account-id:service/service-id
Version 1.0
140
Amazon Route 53 does not require an account number or region in ARNs.
Examples:
arn:aws:route53:::hostedzone/Z148QEXAMPLE8V
arn:aws:route53:::change/C2RDJ5EXAMPLE2
arn:aws:route53:::change/*
arn:aws:route53::123456789012:domain:example.com

Syntax:
arn:aws:serverlessrepo:region:account-id:applications/application-name
arn:aws:serverlessrepo:region:account-id:applications/application-name/versions/symantic-
version
Examples:
arn:aws:serverlessrepo:us-east-1:123456789012:applications/myApp
arn:aws:serverlessrepo:us-east-1:123456789012:applications/myApp/versions/1.0.0
Amazon Simple Email Service (Amazon SES)

In Amazon SES, ARNs are most commonly used to set up Sending Authorization. For more information,
see Using Sending Authorization with Amazon SES in the Amazon Simple Email Service Developer Guide.
Syntax:
arn:aws:ses:region:account-id:identity/identity
Examples:
arn:aws:ses:us-east-1:123456789012:identity/example.com
arn:aws:ses:us-east-1:123456789012:identity/[email protected]

Syntax:
arn:aws:sns:region:account-id:topicname
arn:aws:sns:region:account-id:topicname:subscriptionid
Examples:
arn:aws:sns:*:123456789012:my_corporate_topic
arn:aws:sns:us-east-1:123456789012:my_corporate_topic:02034b43-fefa-4e07-a5eb-3be56f8c54ce

Syntax:
Version 1.0
141
arn:aws:sqs:region:account-id:queuename
Example:
arn:aws:sqs:us-east-1:123456789012:queue1

Syntax:
arn:aws:s3:::bucket_name
arn:aws:s3:::bucket_name/key_name
Note
Amazon S3 does not require an account number or region in ARNs. If you specify an ARN for a
policy, you can also use a wildcard "*" character in the relative-ID part of the ARN.
Examples:
arn:aws:s3:::my_corporate_bucket
arn:aws:s3:::my_corporate_bucket/exampleobject.png
arn:aws:s3:::my_corporate_bucket/*
arn:aws:s3:::my_corporate_bucket/Development/*
For more information, see Specifying Resources in a Policy in the Amazon Simple Storage Service
Developer Guide.

Syntax:
arn:aws:swf:region:account-id:/domain/domain_name
Examples:
arn:aws:swf:us-east-1:123456789012:/domain/department1
arn:aws:swf:*:123456789012:/domain/*
AWS Step Functions

Syntax:
arn:aws:states:region:account-id:activity:activityName
arn:aws:states:region:account-id:stateMachine:stateMachineName
arn:aws:states:region:account-id:execution:stateMachineName:executionName
Examples:
arn:aws:states:us-east-1:123456789012:activity:HelloActivity
arn:aws:states:us-east-1:123456789012:stateMachine:HelloStateMachine
arn:aws:states:us-
east-1:123456789012:execution:HelloStateMachine:HelloStateMachineExecution
Version 1.0
142
AWS Storage Gateway
AWS Storage Gateway

Syntax:
arn:aws:storagegateway:region:account-id:gateway/gateway-id
arn:aws:storagegateway:region:account-id:share/share-id
arn:aws:storagegateway:region:account-id:gateway/gateway-id/volume/volume-id
arn:aws:storagegateway:region:account-id:tape/tapebarcode
arn:aws:storagegateway:region:account-id:gateway/gateway-id/target/iSCSItarget
arn:aws:storagegateway:region:account-id:gateway/gateway-id/device/vtldevice
Examples:
arn:aws:storagegateway:us-east-1:123456789012:gateway/sgw-12A3456B
arn:aws:storagegateway:us-east-1:123456789012:share/share-17A34572
arn:aws:storagegateway:us-east-1:123456789012:gateway/sgw-12A3456B/volume/vol-1122AABB
arn:aws:storagegateway:us-east-1:123456789012:tape/AMZNC8A26D
arn:aws:storagegateway:us-east-1:123456789012:gateway/sgw-12A3456B/target/
iqn.1997-05.com.amazon:vol-1122AABB
arn:aws:storagegateway:us-east-1:123456789012:gateway/sgw-12A3456B/device/AMZN_SGW-
FF22CCDD_TAPEDRIVE_00010
Note
For each AWS Storage Gateway resource, you can specify a wild card (*).
AWS Systems Manager

Syntax:
arn:aws:ssm:region:account-id:document/document_name
arn:aws:ssm:region:account-id:parameter/parameter_name
arn:aws:ssm:region:account-id:patchbaseline/baseline_id
arn:aws:ssm:region:account-id:maintenancewindow/window_id
arn:aws:ssm:region:account-id:automation-execution/execution_id
arn:aws:ssm:region:account-id:automation-Activity/activity_name
arn:aws:ssm:region:account-id:automation-definition/definitionName:version
arn:aws:ssm:region:account-id:managed-instance/instance_id
arn:aws:ssm:region:account-id:managed-instance-inventory/instance_id
Examples:
arn:aws:ssm:us-east-1:123456789012:document/highAvailabilityServerSetup
arn:aws:ssm:us-east-1:123456789012:parameter/myParameterName
arn:aws:ssm:us-east-1:123456789012:patchbaseline/pb-12345678901234567
arn:aws:ssm:us-east-1:123456789012:maintenancewindow/mw-12345678901234567
arn:aws:ssm:us-east-1:123456789012:automation-execution/123456-6789-1a2b3-c4d5-e1a2b3c4d
arn:aws:ssm:us-east-1:123456789012:automation-activity/myActivityName
arn:aws:ssm:us-east-1:123456789012:automation-definition/myDefinitionName:1
arn:aws:ssm:us-east-1:123456789012:managed-instance/mi-12345678901234567
arn:aws:ssm:us-east-1:123456789012:managed-instance-inventory/i-12345661
AWS Trusted Advisor

Syntax:
arn:aws:trustedadvisor:*:account-id:checks/categorycode/checkid
Version 1.0
143
AWS WAF
Example:
arn:aws:trustedadvisor:*:123456789012:checks/fault_tolerance/BueAdJ7NrP
AWS WAF
Syntax, WAF Global (Used for CloudFront):
arn:aws:waf::account-id:resource-type/resource-id
Syntax, WAF Regional (Used for Application Load Balancers):
arn:aws:waf-regional::account-id:resource-type/resource-id
Examples:
arn:aws:waf::123456789012:rule/41b5b052-1e4a-426b-8149-3595be6342c2
arn:aws:waf-regional:us-east-1:123456789012:rule/41b5b052-1e4a-426b-8149-3595be6342c2
arn:aws:waf::123456789012:webacl/3bffd3ed-fa2e-445e-869f-a6a7cf153fd3
arn:aws:waf-regional:us-east-1:123456789012:webacl/3bffd3ed-fa2e-445e-869f-a6a7cf153fd3
arn:aws:waf::123456789012:ipset/3f74bd8c-f046-4970-a1a7-41aa52e05480
arn:aws:waf-regional:us-east-1:123456789012:ipset/3f74bd8c-f046-4970-a1a7-41aa52e05480
arn:aws:waf::123456789012:bytematchset/d131bc0b-57be-4536-af1d-4894fd28acc4
arn:aws:waf-regional:us-east-1:123456789012:bytematchset/d131bc0b-57be-4536-
af1d-4894fd28acc4
Paths in ARNs
Some services let you specify a path for the resource name. For example, in Amazon S3, the resource
identifier is an object name that can include slashes (/) to form a path. Similarly, IAM user names and
group names can include paths.
In some circumstances, paths can include a wildcard character, namely an asterisk (*). For example, if you
are writing an IAM policy and in the Resource element you want to specify all IAM users that have the
path product_1234, you can use a wildcard like this:
arn:aws:iam::123456789012:user/Development/product_1234/*
Similarly, in the Resource element of an IAM policy, at the end of the ARN you can specify user/* to
mean all users or group/* to mean all groups, as in the following examples:
"Resource":"arn:aws:iam::123456789012:user/*"
"Resource":"arn:aws:iam::123456789012:group/*"
You cannot use a wildcard to specify all users in the Principal element in a resource-based policy or a
role trust policy. Groups are not supported as principals in any policy.
The following example shows ARNs for an Amazon S3 bucket in which the resource name includes a
path:
arn:aws:s3:::my_corporate_bucket/*
Version 1.0
144
arn:aws:s3:::my_corporate_bucket/Development/*
You cannot use a wildcard in the portion of the ARN that specifies the resource type, such as the term
user in an IAM ARN.
The following is not allowed:
arn:aws:iam::123456789012:u*

When you create IAM policies or work with Amazon Resource Names (ARNs), you identify an AWS service
using a namespace. For example, the namespace for Amazon S3 is s3, and the namespace for Amazon
EC2 is ec2. You use namespaces when identifying actions and resources.
The following example shows an IAM policy where the value of the Action elements and the values in
the Resource and Condition elements use namespaces to identify the services for the actions and
resources.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "ec2:*",
"Resource": [
"arn:aws:ec2:us-west-2:123456789012:customer-gateway/*",
"arn:aws:ec2:us-west-2:123456789012:dhcp-options/*",
"arn:aws:ec2:us-west-2::image/*",
"arn:aws:ec2:us-west-2:123456789012:instance/*",
"arn:aws:iam::123456789012:instance-profile/*",
"arn:aws:ec2:us-west-2:123456789012:internet-gateway/*",
"arn:aws:ec2:us-west-2:123456789012:key-pair/*",
"arn:aws:ec2:us-west-2:123456789012:network-acl/*",
"arn:aws:ec2:us-west-2:123456789012:network-interface/*",
"arn:aws:ec2:us-west-2:123456789012:placement-group/*",
"arn:aws:ec2:us-west-2:123456789012:route-table/*",
"arn:aws:ec2:us-west-2:123456789012:security-group/*",
"arn:aws:ec2:us-west-2::snapshot/*",
"arn:aws:ec2:us-west-2:123456789012:subnet/*",
"arn:aws:ec2:us-west-2:123456789012:volume/*",
"arn:aws:ec2:us-west-2:123456789012:vpc/*",
"arn:aws:ec2:us-west-2:123456789012:vpc-peering-connection/*"
]
},
{
"Effect": "Allow",
"Action": "s3:*",
"Resource": "arn:aws:s3:::example_bucket/marketing/*"
},
{
"Effect": "Allow",
"Action": "s3:ListBucket*",
"Resource": "arn:aws:s3:::example_bucket",
"Condition": {"StringLike": {"s3:prefix": "marketing/*"}}
}
]
}
Version 1.0
145
The following table contains the namespace for each AWS service.
Service Namespace
API Gateway apigateway
Amazon AppStream appstream
AWS AppSync appsync
AWS Artifact artifact
Amazon EC2 Auto Scaling autoscaling
AWS Billing and Cost Management aws-portal
AWS Certificate Manager (ACM) acm
AWS Cloud9 cloud9
Amazon Cloud Directory clouddirectory
AWS CloudFormation cloudformation
Amazon CloudFront cloudfront
AWS CloudHSM cloudhsm
Amazon CloudSearch cloudsearch
AWS CloudTrail cloudtrail
Amazon CloudWatch cloudwatch
Amazon CloudWatch Events events
Amazon CloudWatch Logs logs
AWS CodeBuild codebuild
AWS CodeCommit codecommit
AWS CodeDeploy codedeploy
AWS CodePipeline codepipeline
AWS CodeStar codestar
Amazon Cognito Your User Pools cognito-idp
Amazon Cognito Federated Identities cognito-identity
Amazon Cognito Sync cognito-sync
AWS Config config
AWS Data Pipeline datapipeline
AWS Database Migration Service (AWS DMS) dms
AWS Device Farm devicefarm
AWS Direct Connect directconnect
Version 1.0
146
Service Namespace
AWS Directory Service ds
Amazon DynamoDB dynamodb
Amazon Elastic Compute Cloud (Amazon EC2) ec2
Amazon Elastic Container Registry (Amazon ECR) ecr
Amazon Elastic Container Service (Amazon ECS) ecs
Amazon EC2 Systems Manager (SSM) ssm
AWS Elastic Beanstalk elasticbeanstalk
Amazon Elastic File System (Amazon EFS) elasticfilesystem
Elastic Load Balancing elasticloadbalancing
Amazon EMR elasticmapreduce
Amazon Elastic Transcoder elastictranscoder
Amazon ElastiCache elasticache
Amazon Elasticsearch Service (Amazon ES) es
Amazon GameLift gamelift
Amazon Glacier glacier
AWS Glue glue
Amazon GuardDuty guardduty
AWS Health / Personal Health Dashboard health
AWS Identity and Access Management (IAM) iam
AWS Import/Export importexport
Amazon Inspector inspector
AWS IoT iot
AWS Key Management Service (AWS KMS) kms
Amazon Kinesis Data Analytics kinesisanalytics
Amazon Kinesis Data Firehose firehose
Amazon Kinesis Data Streams kinesis
AWS Lambda lambda
Amazon Lightsail lightsail
Amazon Machine Learning machinelearning
AWS Marketplace aws-marketplace
AWS Marketplace Management Portal aws-marketplace-management
Version 1.0
147
Service Namespace
AWS Elemental MediaConvert mediaconvert
AWS Elemental MediaLive medialive
AWS Elemental MediaPackage mediapackage
AWS Elemental MediaStore mediastore
AWS Elemental MediaTailor mediatailor
Amazon Mobile Analytics mobileanalytics
AWS Mobile Hub mobilehub
Amazon MQ Service (Amazon MQ) mq
AWS OpsWorks opsworks
AWS OpsWorks for Chef Automate opsworks-cm
AWS Organizations organizations
Amazon Pinpoint mobiletargeting
Amazon Polly polly
Amazon Redshift redshift
Amazon Relational Database Service (Amazon rds

RDS)
Amazon Route 53 route53
Amazon Route 53 Auto Naming servicediscovery
Amazon Route 53 Domains route53domains
AWS Security Token Service (AWS STS) sts
AWS Serverless Application Repository serverlessrepo
AWS Service Catalog servicecatalog
AWS Shield Advanced DDoSProtection
Amazon Simple Email Service (Amazon SES) ses
Amazon Simple Notification Service (Amazon sns

SNS)
Amazon Simple Queue Service (Amazon SQS) sqs
Amazon Simple Storage Service (Amazon S3) s3
Amazon Simple Workflow Service (Amazon SWF) swf
Amazon SimpleDB sdb
AWS Step Functions states
AWS Storage Gateway storagegateway
Version 1.0
148
Service Namespace
AWS Support support
AWS Trusted Advisor trustedadvisor
Amazon Virtual Private Cloud (Amazon VPC) ec2
AWS WAF waf
Amazon WorkDocs workdocs
Amazon WorkMail workmail
Amazon WorkSpaces workspaces
Version 1.0
149
When Do You Need to Sign Requests?
Signing AWS API Requests

When you send HTTP requests to AWS, you sign the requests so that AWS can identify who sent them.
You sign requests with your AWS access key, which consists of an access key ID and secret access key.
Some requests do not need to be signed, such as anonymous requests to Amazon Simple Storage
Service (Amazon S3) and some API operations in AWS Security Token Service (AWS STS) such as
AssumeRoleWithWebIdentity.
Note
You need to learn how to sign HTTP requests only when you manually create them. When you
use the AWS Command Line Interface (AWS CLI) or one of the AWS SDKs to make requests to
AWS, these tools automatically sign the requests for you with the access key that you specify
when you configure the tools. When you use these tools, you don't need to learn how to sign
requests yourself.
When Do You Need to Sign Requests?

When you write custom code to send HTTP requests to AWS, you need to include code to sign the
requests. You might do this for the following reasons:
• You are working with a programming language for which there is no AWS SDK.
• You want complete control over how a request is sent to AWS.
You don't need to sign a request when you use the AWS Command Line Interface (AWS CLI) or one of the
AWS SDKs. These tools manage the connection details, such as calculating signatures, handling request
retries, and error handling. In most cases, they also contain sample code, tutorials, and other resources to
help you get started writing applications that interact with AWS.
Why Requests Are Signed

The signing process helps secure requests in the following ways:
• Verify the identity of the requester
Signing makes sure that the request has been sent by someone with a valid access key. For more
information, see Understanding and Getting Your Security Credentials (p. 107).
• Protect data in transit
To prevent tampering with a request while it's in transit, some of the request elements are used to
calculate a hash (digest) of the request, and the resulting hash value is included as part of the request.
When an AWS service receives the request, it uses the same information to calculate a hash and
matches it against the hash value in your request. If the values don't match, AWS denies the request.
• Protect against potential replay attacks
In most cases, a request must reach AWS within five minutes of the time stamp in the request.
Otherwise, AWS denies the request.
Version 1.0
150
Signing Requests
Signing Requests
To sign a request, you first calculate a hash (digest) of the request. Then you use the hash value, some
other information from the request, and your secret access key to calculate another hash known as the
signature. Then you add the signature to the request in one of the following ways:
• Using the HTTP Authorization header.

• Adding a query string value to the request. Because the signature is part of the URL in this case, this
type of URL is called a presigned URL.
Signature Versions
AWS supports two signature versions: Signature Version 4 and Signature Version 2. You should use
Signature Version 4. All AWS services support Signature Version 4, except Amazon SimpleDB which
requires Signature Version 2. For AWS services that support both versions, we recommend that you use
Signature Version 4.
All AWS regions support Signature Version 4.
Version 1.0
151
Signature Version 4 Signing Process

Signature Version 4 is the process to add authentication information to AWS requests. For security, most
requests to AWS must be signed with an access key, which consists of an access key ID and secret access
key.
Important
When you use the AWS Command Line Interface (AWS CLI) or one of the AWS SDKs to make
requests to AWS, these tools automatically sign the requests for you with the access key that
you specify when you configure the tools. When you use these tools, you don't need to learn
how to sign requests yourself. However, when you manually create HTTP requests to AWS, you
must sign the requests yourself.
How Signature Version 4 works
1. You create a canonical request.

2. You use the canonical request and some other information to create a string to sign.
3. You use your AWS secret access key to derive a signing key, and then use that signing key and the
string to sign to create a signature.
4. You add the resulting signature to the HTTP request in a header or as a query string parameter.
When AWS receives the request, it performs the same steps that you did to calculate the signature. AWS
then compares the calculated signature to the one you sent with the request. If the signatures match, the
request is processed. If the signatures don't match, the request is denied.
For more information, see the following resources:
• To get started with the signing process, see Signing AWS Requests with Signature Version 4 (p. 153).
• For sample signed requests, see Examples of the Complete Version 4 Signing Process
(Python) (p. 168).
• If you have questions about Signature Version 4, post your question in the AWS Identity and Access
Management forum.
Changes in Signature Version 4

Signature Version 4 is the current AWS signing protocol. It includes several changes from the previous
Signature Version 2:
• To sign your message, you use a signing key that is derived from your secret access key rather than
using the secret access key itself. For more information about deriving keys, see Task 3: Calculate the
Signature for AWS Signature Version 4 (p. 161).
• You derive your signing key from the credential scope, which means that you don't need to include the
key itself in the request. Credential scope is represented by a slash-separated string of dimensions in
the following order:
1. Date information as an eight-digit string representing the year (YYYY), month (MM), and day (DD)
of the request (for example, 20150830). For more information about handling dates, see Handling
Dates in Signature Version 4 (p. 165).
2. Region information as a lowercase alphanumeric string. Use the region name that is part of the
service's endpoint. For services with a globally unique endpoint such as IAM, use us-east-1.
3. Service name information as a lowercase alphanumeric string (for example, iam). Use the
service name that is part of the service's endpoint. For example, the IAM endpoint is https://
iam.amazonaws.com, so you use the string iam as part of the Credential parameter.
4. A special termination string: aws4_request.
Version 1.0
152
Signing AWS Requests
• You use the credential scope in each signing task:

• If you add signing information to the query string, include the credential scope as part of the X-
Amz-Credential parameter when you create the canonical request in Task 1: Create a Canonical
Request for Signature Version 4 (p. 155).
• You must include the credential scope as part of your string to sign in Task 2: Create a String to Sign
for Signature Version 4 (p. 160).
• Finally, you use the date, region, and service name components of the credential scope to derive
your signing key in Task 3: Calculate the Signature for AWS Signature Version 4 (p. 161).
Signing AWS Requests with Signature Version 4

This section explains how to create a signature and add it to a request.
Topics
• What Signing Looks Like in a Request (p. 153)
• GET and POST Requests in the Query API (p. 154)
• Summary of Signing Steps (p. 154)
• Task 1: Create a Canonical Request for Signature Version 4 (p. 155)
• Task 2: Create a String to Sign for Signature Version 4 (p. 160)
• Task 3: Calculate the Signature for AWS Signature Version 4 (p. 161)
• Task 4: Add the Signing Information to the Request (p. 163)
What Signing Looks Like in a Request

The following example shows what an HTTPS request might look like as it is sent from your client to
AWS, without any signing information.
GET https://iam.amazonaws.com/?Action=ListUsers&Version=2010-05-08 HTTP/1.1

Content-Type: application/x-www-form-urlencoded; charset=utf-8
Host: iam.amazonaws.com
X-Amz-Date: 20150830T123600Z
After you complete the signing tasks, you add the authentication information to the request. You can
add the authentication information in two ways:
Authorization header
You can add the authentication information to the request with an Authorization header. Although
the HTTP header is named Authorization, the signing information is actually used for authentication
to establish who the request came from.
The Authorization header includes the following information:
• Algorithm you used for signing (AWS4-HMAC-SHA256)

• Credential scope (with your access key ID)
• List of signed headers
• Calculated signature. The signature is based on your request information, and you use your AWS secret
access key to produce the signature. The signature confirms your identity to AWS.
The following example shows what the preceding request might look like after you've created the
signing information and added it to the request in the Authorization header.
Version 1.0
153
Note that in the actual request, the Authorization header would appear as a continuous line of text.
The version below has been formatted for readability.

Authorization: AWS4-HMAC-SHA256
Credential=AKIDEXAMPLE/20150830/us-east-1/iam/aws4_request,
SignedHeaders=content-type;host;x-amz-date,
Signature=5d672d79c15b13162d9279b0855cfba6789a8edb4c82c400e06b5924a6f2b5d7
content-type: application/x-www-form-urlencoded; charset=utf-8
host: iam.amazonaws.com
x-amz-date: 20150830T123600Z
Query string
As an alternative to adding authentication information with an HTTP request header, you can include it
in the query string. The query string contains everything that is part of the request, including the name
and parameters for the action, the date, and the authentication information.
The following example shows how you might construct a GET request with the action and authentication
information in the query string.
(In the actual request, the query string would appear as a continuous line of text. The version below has
been formatted with line breaks for readability.)
GET https://iam.amazonaws.com?Action=ListUsers&Version=2010-05-08
&X-Amz-Algorithm=AWS4-HMAC-SHA256
&X-Amz-Credential=AKIDEXAMPLE%2F20150830%2Fus-east-1%2Fiam%2Faws4_request
&X-Amz-Date=20150830T123600Z
&X-Amz-Expires=60
&X-Amz-SignedHeaders=content-type%3Bhost
&X-Amz-Signature=37ac2f4fde00b0ac9bd9eadeb459b1bbee224158d66e7ae5fcadb70b2d181d02 HTTP/1.1
content-type: application/x-www-form-urlencoded; charset=utf-8
host: iam.amazonaws.com
GET and POST Requests in the Query API

The query API that many AWS services support lets you make requests using either HTTP GET or POST.
(In the query API, you can use GET even if you're making requests that change state; that is, the query
API is not inherently RESTful.) Because GET requests pass parameters on the query string, they are
limited to the maximum length of a URL. If a request includes a large payload (for example, you might
upload a large IAM policy or send many parameters in JSON format for a DynamoDB request), you
generally use a POST request.
The signing process is the same for both types of requests.
Summary of Signing Steps

To create a signed request, complete the following:
• Task 1: Create a Canonical Request for Signature Version 4 (p. 155)
Arrange the contents of your request (host, action, headers, etc.) into a standard (canonical) format.
The canonical request is one of the inputs used to create a string to sign.
• Task 2: Create a String to Sign for Signature Version 4 (p. 160)
Create a string to sign with the canonical request and extra information such as the algorithm, request
date, credential scope, and the digest (hash) of the canonical request.
• Task 3: Calculate the Signature for AWS Signature Version 4 (p. 161)
Version 1.0
154
Derive a signing key by performing a succession of keyed hash operations (HMAC operations) on the
request date, region, and service, with your AWS secret access key as the key for the initial hashing
operation. After you derive the signing key, you then calculate the signature by performing a keyed
hash operation on the string to sign. Use the derived signing key as the hash key for this operation.
• Task 4: Add the Signing Information to the Request (p. 163)
After you calculate the signature, add it to an HTTP header or to the query string of the request.
Note
The AWS SDKs handle the signature calculation process for you, so you do not have to manually
complete the signing process. For more information, see Tools for Amazon Web Services.
The following additional resources illustrate aspects of the signing process:
• Examples of How to Derive a Signing Key for Signature Version 4 (p. 165). This page shows how to
derive a signing key using Java, C#, Python, Ruby, and JavaScript.
• Examples of the Complete Version 4 Signing Process (Python) (p. 168). This set of programs in
Python provide complete examples of the signing process. The examples show signing with a POST
request, with a GET request that has signing information in a request header, and with a GET request
that has signing information in the query string.
• Signature Version 4 Test Suite (p. 175). This downloadable package contains a collection of examples
that include signature information for various steps in the signing process. You can use these examples
to verify that your signing code is producing the correct results at each step of the process.
Task 1: Create a Canonical Request for Signature Version 4

To begin the signing process, create a string that includes information from your request in a
standardized (canonical) format. This ensures that when AWS receives the request, it can calculate the
same signature that you calculated.
Follow the steps here to create a canonical version of the request. Otherwise, your version and the
version calculated by AWS won't match, and the request will be denied.
The following example shows the pseudocode to create a canonical request.
Example canonical request pseudocode
CanonicalRequest =
HTTPRequestMethod + '\n' +
CanonicalURI + '\n' +
CanonicalQueryString + '\n' +
CanonicalHeaders + '\n' +
SignedHeaders + '\n' +
HexEncode(Hash(RequestPayload))
In this pseudocode, Hash represents a function that produces a message digest, typically SHA-256. (Later
in the process, you specify which hashing algorithm you're using.) HexEncode represents a function
that returns the base-16 encoding of the digest in lowercase characters. For example, HexEncode("m")
returns the value 6d rather than 6D. Each input byte must be represented as exactly two hexadecimal
characters.
Signature Version 4 does not require that you use a particular character encoding to encode the
canonical request. However, some AWS services might require a specific encoding. For more information,
consult the documentation for that service.
Version 1.0
155
The following examples show how to construct the canonical form of a request to IAM. The original
request might look like this as it is sent from the client to AWS, except that this example does not include
the signing information yet.
Example request

X-Amz-Date: 20150830T123600Z
The preceding example request is a GET request (method) that makes a ListUsers API (action) call to
AWS Identity and Access Management (host). This action takes the Version parameter.
To create a canonical request, concatenate the following components from each step into a
single string:
1. Start with the HTTP request method (GET, PUT, POST, etc.), followed by a newline character.
Example request method
GET
2. Add the canonical URI parameter, followed by a newline character. The canonical URI is the URI-
encoded version of the absolute path component of the URI, which is everything in the URI from the
HTTP host to the question mark character ("?") that begins the query string parameters (if any).
Normalize URI paths according to RFC 3986. Remove redundant and relative path components. Each
path segment must be URI-encoded.
Example canonical URI with encoding
/documents%20and%20settings/
Note
In exception to this, you do not normalize URI paths for requests to Amazon S3.
For example, if you have a bucket with an object named my-object//example//
photo.user, use that path. Normalizing the path to my-object/example/photo.user
will cause the request to fail. For more information, see Task 1: Create a Canonical Request
in the Amazon Simple Storage Service API Reference.
If the absolute path is empty, use a forward slash (/). In the example IAM request, nothing follows
the host in the URI, so the absolute path is empty.
Example canonical URI
3. Add the canonical query string, followed by a newline character. If the request does not include a
query string, use an empty string (essentially, a blank line). The example request has the following
query string.
Example canonical query string
Action=ListUsers&Version=2010-05-08
Version 1.0
156
To construct the canonical query string, complete the following steps:
a. Sort the parameter names by character code point in ascending order. For example, a parameter
name that begins with the uppercase letter F precedes a parameter name that begins with a
lowercase letter b.
b. URI-encode each parameter name and value according to the following rules:
• Do not URI-encode any of the unreserved characters that RFC 3986 defines: A-Z, a-z, 0-9,
hyphen ( - ), underscore ( _ ), period ( . ), and tilde ( ~ ).
• Percent-encode all other characters with %XY, where X and Y are hexadecimal characters (0-9
and uppercase A-F). For example, the space character must be encoded as %20 (not using '+',
as some encoding schemes do) and extended UTF-8 characters must be in the form %XY%ZA
%BC.
c. Build the canonical query string by starting with the first parameter name in the sorted list.
d. For each parameter, append the URI-encoded parameter name, followed by the equals
sign character (=), followed by the URI-encoded parameter value. Use an empty string for
parameters that have no value.
e. Append the ampersand character (&) after each parameter value, except for the last value in the
list.
One option for the query API is to put all request parameters in the query string. For example, you
can do this for Amazon S3 to create a presigned URL. In that case, the canonical query string must
include not only parameters for the request, but also the parameters used as part of the signing
process—the hashing algorithm, credential scope, date, and signed headers parameters.
The following example shows a query string that includes authentication information. The example
is formatted with line breaks for readability, but the canonical query string must be one continuous
line of text in your code.
Example authentication parameters in a query string
Action=ListUsers&
Version=2010-05-08&
X-Amz-Algorithm=AWS4-HMAC-SHA256&
X-Amz-Credential=AKIDEXAMPLE%2F20150830%2Fus-east-1%2Fiam%2Faws4_request&
X-Amz-Date=20150830T123600Z&
X-Amz-SignedHeaders=content-type%3Bhost%3Bx-amz-date
For more information about authentication parameters, see Task 2: Create a String to Sign for
Signature Version 4 (p. 160).
Note
You can use temporary security credentials provided by the AWS Security Token Service
(AWS STS) to sign a request. The process is the same as using long-term credentials, but
when you add signing information to the query string you must add an additional query
parameter for the security token. The parameter name is X-Amz-Security-Token, and
the parameter's value is the URI-encoded session token (the string you received from AWS
STS when you obtained temporary security credentials).
For some services, you must include the X-Amz-Security-Token query parameter in the
canonical (signed) query string. For other services, you add the X-Amz-Security-Token
parameter at the end, after you calculate the signature. For details, see the API reference
documentation for that service.
4. Add the canonical headers, followed by a newline character. The canonical headers consist of a list of
all the HTTP headers that you are including with the signed request.
Version 1.0
157
At a minimum, you must include the host header. Standard headers like content-type are
optional. Different services might require other headers.
Example canonical headers
content-type:application/x-www-form-urlencoded; charset=utf-8\n
host:iam.amazonaws.com\n
x-amz-date:20150830T123600Z\n
To create the canonical headers list, convert all header names to lowercase and remove leading
spaces and trailing spaces. Convert sequential spaces in the header value to a single space.
The following pseudocode describes how to construct the canonical list of headers:
CanonicalHeaders =
CanonicalHeadersEntry0 + CanonicalHeadersEntry1 + ... + CanonicalHeadersEntryN
CanonicalHeadersEntry =
Lowercase(HeaderName) + ':' + Trimall(HeaderValue) + '\n'
Lowercase represents a function that converts all characters to lowercase. The Trimall function
removes excess white space before and after values, and converts sequential spaces to a single
space.
Build the canonical headers list by sorting the (lowercase) headers by character code and then
iterating through the header names. Construct each header according to the following rules:
• Append the lowercase header name followed by a colon.

• Append a comma-separated list of values for that header. Do not sort the values in headers that
have multiple values.
• Append a new line ('\n').
The following examples compare a more complex set of headers with their canonical form:
Example original headers
Host:iam.amazonaws.com\n
Content-Type:application/x-www-form-urlencoded; charset=utf-8\n
My-header1: a b c \n
X-Amz-Date:20150830T123600Z\n
My-Header2: "a b c" \n
Example canonical form
content-type:application/x-www-form-urlencoded; charset=utf-8\n
host:iam.amazonaws.com\n
my-header1:a b c\n
my-header2:"a b c"\n
x-amz-date:20150830T123600Z\n
Note
Each header is followed by a newline character, meaning the complete list ends with a
newline character.
In the canonical form, the following changes were made:

Version 1.0
158
• The header names were converted to lowercase characters.

• The headers were sorted by character code.
• Leading and trailing spaces were removed from the my-header1 and my-header2 values.
• Sequential spaces in a b c were converted to a single space for the my-header1 and my-
header2 values.
Note
You can use temporary security credentials provided by the AWS Security Token Service
(AWS STS) to sign a request. The process is the same as using long-term credentials, but
when you include signing information in the Authorization header you must add an
additional HTTP header for the security token. The header name is X-Amz-Security-
Token, and the header's value is the session token (the string you received from AWS STS
when you obtained temporary security credentials).
5. Add the signed headers, followed by a newline character. This value is the list of headers that you
included in the canonical headers. By adding this list of headers, you tell AWS which headers in the
request are part of the signing process and which ones AWS can ignore (for example, any additional
headers added by a proxy) for purposes of validating the request.
The host header must be included as a signed header. If you include a date or x-amz-date header,
you must also include that header in the list of signed headers.
To create the signed headers list, convert all header names to lowercase, sort them by character
code, and use a semicolon to separate the header names. The following pseudocode describes how
to construct a list of signed headers. Lowercase represents a function that converts all characters
to lowercase.
SignedHeaders =
Lowercase(HeaderName0) + ';' + Lowercase(HeaderName1) + ";" + ... +
Lowercase(HeaderNameN)
Build the signed headers list by iterating through the collection of header names, sorted by
lowercase character code. For each header name except the last, append a semicolon (';') to the
header name to separate it from the following header name.
Example signed headers
content-type;host;x-amz-date\n
6. Use a hash (digest) function like SHA256 to create a hashed value from the payload in the body of
the HTTP or HTTPS request. Signature Version 4 does not require that you use a particular character
encoding to encode text in the payload. However, some AWS services might require a specific
encoding. For more information, consult the documentation for that service.
Example structure of payload
HashedPayload = Lowercase(HexEncode(Hash(requestPayload)))
When you create the string to sign, you specify the signing algorithm that you used to hash the
payload. For example, if you used SHA256, you will specify AWS4-HMAC-SHA256 as the signing
algorithm. The hashed payload must be represented as a lowercase hexadecimal string.
If the payload is empty, use an empty string as the input to the hash function. In the IAM example,
the payload is empty.
Version 1.0
159
Example hashed payload (empty string)
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
7. To construct the finished canonical request, combine all the components from each step as a single
string. As noted, each component ends with a newline character. If you follow the canonical request
pseudocode explained earlier, the resulting canonical request is shown in the following example.
Example canonical request
GET
/
Action=ListUsers&Version=2010-05-08
content-type:application/x-www-form-urlencoded; charset=utf-8
host:iam.amazonaws.com
x-amz-date:20150830T123600Z
content-type;host;x-amz-date
8. Create a digest (hash) of the canonical request with the same algorithm that you used to hash the
payload.
Note
Signature Version 4 does not require that you use a particular character encoding to encode
the canonical request before calculating the digest. However, some AWS services might
require a specific encoding. For more information, consult the documentation for that
service.
The hashed canonical request must be represented as a string of lowercase hexademical characters.
The following example shows the result of using SHA-256 to hash the example canonical request.
Example hashed canonical request
f536975d06c0309214f805bb90ccff089219ecd68b2577efef23edd43b7e1a59
You include the hashed canonical request as part of the string to sign in Task 2: Create a String to
Sign for Signature Version 4 (p. 160).
Task 2: Create a String to Sign for Signature Version 4

The string to sign includes meta information about your request and about the canonical request that
you created in Task 1: Create a Canonical Request for Signature Version 4 (p. 155). You will use the
string to sign and a derived signing key that you create later as inputs to calculate the request signature
in Task 3: Calculate the Signature for AWS Signature Version 4 (p. 161).
To create the string to sign, concatenate the algorithm, date and time, credential scope, and digest of the
canonical request, as shown in the following pseudocode:
Structure of string to sign
StringToSign =
Algorithm + \n +
RequestDateTime + \n +
CredentialScope + \n +
HashedCanonicalRequest
Version 1.0
160
The following example shows how to construct the string to sign with the same request from Task 1:
Create A Canonical Request (p. 155).
Example HTTPS request

X-Amz-Date: 20150830T123600Z
To create the string to sign
1. Start with the algorithm designation, followed by a newline character. This value is the hashing
algorithm that you use to calculate the digests in the canonical request. For SHA256, AWS4-HMAC-
SHA256 is the algorithm.
AWS4-HMAC-SHA256\n
2. Append the request date value, followed by a newline character. The date is specified with ISO8601
basic format in the x-amz-date header in the format YYYYMMDD'T'HHMMSS'Z'. This value must
match the value you used in any previous steps.
20150830T123600Z\n
3. Append the credential scope value, followed by a newline character. This value is a string that
includes the date, the region you are targeting, the service you are requesting, and a termination
string ("aws4_request") in lowercase characters. The region and service name strings must be
UTF-8 encoded.
20150830/us-east-1/iam/aws4_request\n
• The date must be in the YYYYMMDD format. Note that the date does not include a time value.
• Verify that the region you specify is the region that you are sending the request to. See AWS
Regions and Endpoints (p. 2).
4. Append the hash of the canonical request that you created in Task 1: Create a Canonical Request
for Signature Version 4 (p. 155). This value is not followed by a newline character. The hashed
canonical request must be lowercase base-16 encoded, as defined by Section 8 of RFC 4648.
The following string to sign is a request to IAM on August 30, 2015.
Example string to sign
AWS4-HMAC-SHA256
20150830T123600Z
20150830/us-east-1/iam/aws4_request
Task 3: Calculate the Signature for AWS Signature Version 4

Before you calculate a signature, you derive a signing key from your AWS secret access key. Because the
derived signing key is specific to the date, service, and region, it offers a greater degree of protection.
You don't just use your secret access key to sign the request. You then use the signing key and the string
Version 1.0
161
to sign that you created in Task 2: Create a String to Sign for Signature Version 4 (p. 160) as the inputs
to a keyed hash function. The hex-encoded result from the keyed hash function is the signature.
Signature Version 4 does not require that you use a particular character encoding to encode the string to
sign. However, some AWS services might require a specific encoding. For more information, consult the
To calculate a signature
1. Derive your signing key. To do this, use your secret access key to create a series of hash-based
message authentication codes (HMACs). This is shown in the following pseudocode, where
HMAC(key, data) represents an HMAC-SHA256 function that returns output in binary format. The
result of each hash function becomes input for the next one.
Pseudocode for deriving a signing key
kSecret = your secret access key

kDate = HMAC("AWS4" + kSecret, Date)
kRegion = HMAC(kDate, Region)
kService = HMAC(kRegion, Service)
kSigning = HMAC(kService, "aws4_request")
Note that the date used in the hashing process is in the format YYYYMMDD (for example, 20150830),
and does not include the time.
Make sure you specify the HMAC parameters in the correct order for the programming language you
are using. This example shows the key as the first parameter and the data (message) as the second
parameter, but the function that you use might specify the key and data in a different order.
Use the digest (binary format) for the key derivation. Most languages have functions to compute
either a binary format hash, commonly called a digest, or a hex-encoded hash, called a hexdigest.
The key derivation requires that you use a binary-formatted digest.
The following example show the inputs to derive a signing key and the resulting output, where
kSecret = wJalrXUtnFEMI/K7MDENG+bPxRfiCYEXAMPLEKEY.
The example uses the same parameters from the request in Task 1 and Task 2 (a request to IAM in
the us-east-1 region on August 30, 2015).
Example inputs
HMAC(HMAC(HMAC(HMAC("AWS4" + kSecret,"20150830"),"us-east-1"),"iam"),"aws4_request")
The following example shows the derived signing key that results from this sequence of HMAC hash
operations. This shows the hexadecimal representation of each byte in the binary signing key.
Example signing key
c4afb1cc5771d871763a393e44b703571b55cc28424d1a5e86da6ed3c154a4b9
For more information about how to derive a signing key in different programming languages, see
Examples of How to Derive a Signing Key for Signature Version 4 (p. 165).
2. Calculate the signature. To do this, use the signing key that you derived and the string to sign as
inputs to the keyed hash function. After you calculate the signature, convert the binary value to a
hexadecimal representation.
The following pseudocode shows howVersion

to calculate
1.0 the signature.
162
signature = HexEncode(HMAC(derived signing key, string to sign))
Note
Make sure you specify the HMAC parameters in the correct order for the programming
language you are using. This example shows the key as the first parameter and the data
(message) as the second parameter, but the function that you use might specify the key and
data in a different order.
The following example shows the resulting signature if you use the same signing key and the string
to sign from Task 2:
Example signature
5d672d79c15b13162d9279b0855cfba6789a8edb4c82c400e06b5924a6f2b5d7
Task 4: Add the Signing Information to the Request

After you calculate the signature, you add it to the request. You can add the signing information to a
request in one of two ways:
• An HTTP header named Authorization

• The query string
You cannot pass signing information in both the Authorization header and the query string.
Note
You can use temporary security credentials provided by the AWS Security Token Service (AWS
STS) to sign a request. The process is the same as using long-term credentials, but requires
an additional HTTP header or query string parameter for the security token. The name of
the header or query string parameter is X-Amz-Security-Token, and the value is the
session token (the string you received from AWS STS when you obtained temporary security
credentials).
When you add the X-Amz-Security-Token parameter to the query string, some services
require that you include this parameter in the canonical (signed) request. For other services,
you add this parameter at the end, after you calculate the signature. For details, see the API
reference documentation for that service.
Adding Signing Information to the Authorization Header

You can include signing information by adding it to an HTTP header named Authorization. The
contents of the header are created after you calculate the signature as described in the preceding steps,
so the Authorization header is not included in the list of signed headers. Although the header is
named Authorization, the signing information is actually used for authentication.
The following pseudocode shows the construction of the Authorization header.
Authorization: algorithm Credential=access key ID/credential scope,

SignedHeaders=SignedHeaders, Signature=signature
The following example shows a finished Authorization header.
Note that in the actual request, the authorization header would appear as a continuous line of text. The
version below has been formatted for readability.
Version 1.0
163
Authorization: AWS4-HMAC-SHA256
Credential=AKIDEXAMPLE/20150830/us-east-1/iam/aws4_request,
SignedHeaders=content-type;host;x-amz-date,
Signature=5d672d79c15b13162d9279b0855cfba6789a8edb4c82c400e06b5924a6f2b5d7
Note the following:
• There is no comma between the algorithm and Credential. However, the SignedHeaders and
Signature are separated from the preceding values with a comma.
• The Credential value starts with the access key ID, which is followed by a forward slash (/), which
is followed by the credential scope that you calculated in Task 2: Create a String to Sign for Signature
Version 4 (p. 160). The secret access key is used to derive the signing key for the signature, but is not
included in the signing information sent in the request.
Adding Signing Information to the Query String

You can make requests and pass all request values in the query string, including signing information. This
is sometimes referred to as a presigned URL, because it produces a single URL with everything required
in order to make a successful call to AWS. It's commonly used in Amazon S3. For more information, see
Authenticating Requests by Using Query Parameters (AWS Signature Version 4) in the Amazon Simple
Storage Service API Reference.
Important
If you make a request in which all parameters are included in the query string, the resulting URL
represents an AWS action that is already authenticated. Therefore, treat the resulting URL with
as much caution as you would treat your actual credentials. We recommend you specify a short
expiration time for the request with the X-Amz-Expires parameter.
When you use this approach, all the query string values (except the signature) are included in the
canonical query string that is part of the canonical query that you construct in the first part of the
signing process (p. 155).
The following pseudocode shows the construction of a query string that contains all request parameters.
querystring = Action=action
querystring += &X-Amz-Algorithm=algorithm
querystring += &X-Amz-Credential= urlencode(access_key_ID + '/' + credential_scope)
querystring += &X-Amz-Date=date
querystring += &X-Amz-Expires=timeout interval
querystring += &X-Amz-SignedHeaders=signed_headers
After the signature is calculated (which uses the other query string values as part of the calculation), you
add the signature to the query string as the X-Amz-Signature parameter:
querystring += &X-Amz-Signature=signature
The following example shows what a request might look like when all the request parameters and the
signing information are included in query string parameters.
Note that in the actual request, the authorization header would appear as a continuous line of text. The
version below has been formatted for readability.
https://iam.amazonaws.com?Action=ListUsers&Version=2010-05-08
&X-Amz-Credential=AKIDEXAMPLE%2F20150830%2Fus-east-1%2Fiam%2Faws4_request
&X-Amz-Date=20150830T123600Z
&X-Amz-Expires=60
Version 1.0
164
Handling Dates
&X-Amz-SignedHeaders=content-type%3Bhost
&X-Amz-Signature=37ac2f4fde00b0ac9bd9eadeb459b1bbee224158d66e7ae5fcadb70b2d181d02
Note the following:
• For the signature calculation, query string parameters must be sorted in code point order from low to
high, and their values must be URI-encoded. See the step about creating a canonical query string in
Task 1: Create a Canonical Request for Signature Version 4 (p. 155).
• Set the timeout interval (X-Amz-Expires) to the minimal viable time for the operation you're
requesting.
Handling Dates in Signature Version 4

The date that you use as part of your credential scope must match the date of your request. You can
include the date as part of your request in several ways. You can use a date header, an x-amz-date
header or include x-amz-date as a query parameter. For example requests, see Examples of the
Complete Version 4 Signing Process (Python) (p. 168).
The time stamp must be in UTC and in the following ISO 8601 format: YYYYMMDD'T'HHMMSS'Z'. For
example, 20150830T123600Z is a valid time stamp. Do not include milliseconds in the time stamp.
AWS first checks the x-amz-date header or parameter for a time stamp. If AWS can't find a value for x-
amz-date, it looks for the date header. AWS then checks the credential scope for an eight-digit string
representing the year (YYYY), month (MM), and day (DD) of the request. For example, if the x-amz-date
header value is 20111015T080000Z and the date component of the credential scope is 20111015, AWS
allows the authentication process to proceed.
If the dates don't match, AWS rejects the request, even if the time stamp is only seconds away from the
date in the credential scope. For example, AWS will reject a request that has an x-amz-date header
value of 20151014T235959Z and a credential scope that has the date 20151015.
Examples of How to Derive a Signing Key for

Signature Version 4
This page shows examples in several programming languages for how to derive a signing key for
Signature Version 4. The examples on this page show only how to derive a signing key, which is just
one part of signing AWS requests. For examples that show the complete process, see Examples of the
Complete Version 4 Signing Process (Python) (p. 168).
Note
If you are using one of the AWS SDKs (including the SDK for Java, .NET, Python, Ruby, or
JavaScript), you do not have to manually perform the steps of deriving a signing key and adding
authentication information to a request. The SDKs perform this work for you. You need to
manually sign requests only if you are directly making HTTP or HTTPS requests.
Topics
• Deriving the Signing Key with Java (p. 166)
• Deriving the Signing Key with .NET (C#) (p. 166)
• Deriving the Signing Key with Python (p. 166)
• Deriving the Signing Key with Ruby (p. 166)
• Deriving the Signing Key with JavaScript (Node.js) (p. 167)
• Deriving the Signing Key with Other Languages (p. 167)
• Common Coding Mistakes (p. 167)
Version 1.0
165
Examples of How to Derive a Signing Key
Deriving the Signing Key with Java

static byte[] HmacSHA256(String data, byte[] key) throws Exception {
String algorithm="HmacSHA256";
Mac mac = Mac.getInstance(algorithm);
mac.init(new SecretKeySpec(key, algorithm));
return mac.doFinal(data.getBytes("UTF8"));
}
static byte[] getSignatureKey(String key, String dateStamp, String regionName, String

serviceName) throws Exception {
byte[] kSecret = ("AWS4" + key).getBytes("UTF8");
byte[] kDate = HmacSHA256(dateStamp, kSecret);
byte[] kRegion = HmacSHA256(regionName, kDate);
byte[] kService = HmacSHA256(serviceName, kRegion);
byte[] kSigning = HmacSHA256("aws4_request", kService);
return kSigning;
}
Deriving the Signing Key with .NET (C#)

static byte[] HmacSHA256(String data, byte[] key)
{
String algorithm = "HmacSHA256";
KeyedHashAlgorithm kha = KeyedHashAlgorithm.Create(algorithm);
kha.Key = key;
return kha.ComputeHash(Encoding.UTF8.GetBytes(data));
}
static byte[] getSignatureKey(String key, String dateStamp, String regionName, String

serviceName)
{
byte[] kSecret = Encoding.UTF8.GetBytes(("AWS4" + key).ToCharArray());
byte[] kDate = HmacSHA256(dateStamp, kSecret);
byte[] kRegion = HmacSHA256(regionName, kDate);
byte[] kService = HmacSHA256(serviceName, kRegion);
byte[] kSigning = HmacSHA256("aws4_request", kService);
return kSigning;
}
Deriving the Signing Key with Python

def sign(key, msg):
return hmac.new(key, msg.encode("utf-8"), hashlib.sha256).digest()
def getSignatureKey(key, dateStamp, regionName, serviceName):

kDate = sign(("AWS4" + key).encode("utf-8"), dateStamp)
kRegion = sign(kDate, regionName)
kService = sign(kRegion, serviceName)
kSigning = sign(kService, "aws4_request")
return kSigning
Deriving the Signing Key with Ruby

def getSignatureKey key, dateStamp, regionName, serviceName
kDate = OpenSSL::HMAC.digest('sha256', "AWS4" + key, dateStamp)
kRegion = OpenSSL::HMAC.digest('sha256', kDate, regionName)
Version 1.0
166
Examples of How to Derive a Signing Key
kService = OpenSSL::HMAC.digest('sha256', kRegion, serviceName)

kSigning = OpenSSL::HMAC.digest('sha256', kService, "aws4_request")
kSigning
end
Deriving the Signing Key with JavaScript (Node.js)

The following example uses the crypto-js library. For more information, see https://www.npmjs.com/
package/crypto-js and https://code.google.com/archive/p/crypto-js/.
var crypto = require("crypto-js");
function getSignatureKey(Crypto, key, dateStamp, regionName, serviceName) {

var kDate = Crypto.HmacSHA256(dateStamp, "AWS4" + key);
var kRegion = Crypto.HmacSHA256(regionName, kDate);
var kService = Crypto.HmacSHA256(serviceName, kRegion);
var kSigning = Crypto.HmacSHA256("aws4_request", kService);
return kSigning;
}
Deriving the Signing Key with Other Languages

If you need to implement this logic in a different programming language, we recommend testing the
intermediary steps of the key derivation algorithm against the values in this section. The following
example in Ruby prints the results using the hexEncode function after each step in the algorithm.
def hexEncode bindata

result=""
data=bindata.unpack("C*")
data.each {|b| result+= "%02x" % b}
result
end
Given the following test input:
key = 'wJalrXUtnFEMI/K7MDENG+bPxRfiCYEXAMPLEKEY'
dateStamp = '20120215'
regionName = 'us-east-1'
serviceName = 'iam'
Your program should generate the following values for the values in getSignatureKey. Note that
these are hex-encoded representations of the binary data; the key itself and the intermediate values
should be in binary format.
kSecret =
'41575334774a616c725855746e46454d492f4b374d44454e472b62507852666943594558414d504c454b4559'
kDate = '969fbb94feb542b71ede6f87fe4d5fa29c789342b0f407474670f0c2489e0a0d'
kRegion = '69daa0209cd9c5ff5c8ced464a696fd4252e981430b10e3d3fd8e2f197d7a70c'
kService = 'f72cfd46f26bc4643f06a11eabb6c0ba18780c19a8da0c31ace671265e3c87fa'
kSigning = 'f4780e2d9f65fa895f9c67b32ce1baf0b0d8a43505a000a1a9e090d414db404d'
Common Coding Mistakes

To simplify your task, avoid the following common coding errors.
Tip
Examine the HTTP request that you're sending to AWS with a tool that shows you what your raw
HTTP requests look like. This can help you spot issues that aren't evident from your code.
Version 1.0
167
Signing Examples (Python)
• Don't include an extra newline character, or forget one where it's required.
• Don't format the date incorrectly in the credential scope, such as using a time stamp instead of
YYYYMMDD format.
• Make sure the headers in the canonical headers and the signed headers are the same.
• Don't inadvertently swap the key and the data (message) when calculating intermediary keys. The
result of the previous step's computation is the key, not the data. Check the documentation for your
cryptographic primitives carefully to ensure that you place the parameters in the proper order.
• Don't forget to add the string "AWS4" in front of the key for the first step. If you implement the key
derivation using a for loop or iterator, don't forget to special-case the first iteration so that it includes
the "AWS4" string.
For more information about possible errors, see Troubleshooting AWS Signature Version 4
Errors (p. 177).
Examples of the Complete Version 4 Signing Process

(Python)
This section shows example programs written in Python that illustrate how to work with Signature
Version 4 in AWS. We deliberately wrote these example programs to be simple (to use few Python-
specific features) to make it easier to understand the overall process of signing AWS requests.
In order to work with these example programs, you need the following:
• Python 2.x installed on your computer, which you can get from the Python site. These programs were
tested using Python 2.7.
• The Python requests library, which is used in the example script to make web requests. A convenient
way to install Python packages is to use pip, which gets packages from the Python package index site.
You can then install requests by running pip install requests at the command line.
• An access key (access key ID and secret access key) in environment variables named
AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. Alternatively, you can keep these values in a
credentials file and read them from that file. As a best practice, we recommend that you do not embed
credentials in code. For more information, see Best Practices for Managing AWS Access Keys in the
Amazon Web Services General Reference.
Note
The following examples use UTF-8 to encode the canonical request and string to sign, but
Signature Version 4 does not require that you use a particular character encoding. However,
some AWS services might require a specific encoding. For more information, consult the
Topics
• Using GET with an Authorization Header (Python) (p. 168)
• Using POST (Python) (p. 170)
• Using GET with Authentication Information in the Query String (Python) (p. 173)
Using GET with an Authorization Header (Python)

The following example shows how to make a request using the Amazon EC2 query API. The request
makes a GET request and passes authentication information to AWS using the Authorization header.
# AWS Version 4 signing example
Version 1.0
168
# EC2 API (DescribeRegions)
# See: http://docs.aws.amazon.com/general/latest/gr/sigv4_signing.html
# This version makes a GET request and passes the signature
# in the Authorization header.
import sys, os, base64, datetime, hashlib, hmac
import requests # pip install requests
# ************* REQUEST VALUES *************

method = 'GET'
service = 'ec2'
host = 'ec2.amazonaws.com'
region = 'us-east-1'
endpoint = 'https://ec2.amazonaws.com'
request_parameters = 'Action=DescribeRegions&Version=2013-10-15'
# Key derivation functions. See:

# http://docs.aws.amazon.com/general/latest/gr/signature-v4-examples.html#signature-v4-
examples-python
def sign(key, msg):
return hmac.new(key, msg.encode('utf-8'), hashlib.sha256).digest()

kDate = sign(('AWS4' + key).encode('utf-8'), dateStamp)
kSigning = sign(kService, 'aws4_request')
return kSigning
# Read AWS access key from env. variables or configuration file. Best practice is NOT
# to embed credentials in code.
access_key = os.environ.get('AWS_ACCESS_KEY_ID')
secret_key = os.environ.get('AWS_SECRET_ACCESS_KEY')
if access_key is None or secret_key is None:
print 'No access key is available.'
sys.exit()
# Create a date for headers and the credential string

t = datetime.datetime.utcnow()
amzdate = t.strftime('%Y%m%dT%H%M%SZ')
datestamp = t.strftime('%Y%m%d') # Date w/o time, used in credential scope
# ************* TASK 1: CREATE A CANONICAL REQUEST *************

# http://docs.aws.amazon.com/general/latest/gr/sigv4-create-canonical-request.html
# Step 1 is to define the verb (GET, POST, etc.)--already done.
# Step 2: Create canonical URI--the part of the URI from domain to query
# string (use '/' if no path)
canonical_uri = '/'
# Step 3: Create the canonical query string. In this example (a GET request),
# request parameters are in the query string. Query string values must
# be URL-encoded (space=%20). The parameters must be sorted by name.
# For this example, the query string is pre-formatted in the request_parameters variable.
canonical_querystring = request_parameters
# Step 4: Create the canonical headers and signed headers. Header names
# must be trimmed and lowercase, and sorted in code point order from
# low to high. Note that there is a trailing \n.
canonical_headers = 'host:' + host + '\n' + 'x-amz-date:' + amzdate + '\n'
# Step 5: Create the list of signed headers. This lists the headers
# in the canonical_headers list, delimited with ";" and in alpha order.
Version 1.0
169
# Note: The request can include any headers; canonical_headers and

# signed_headers lists those that you want to be included in the
# hash of the request. "Host" and "x-amz-date" are always required.
signed_headers = 'host;x-amz-date'
# Step 6: Create payload hash (hash of the request body content). For GET
# requests, the payload is an empty string ("").
payload_hash = hashlib.sha256('').hexdigest()
# Step 7: Combine elements to create canonical request

canonical_request = method + '\n' + canonical_uri + '\n' + canonical_querystring + '\n' +
canonical_headers + '\n' + signed_headers + '\n' + payload_hash
# ************* TASK 2: CREATE THE STRING TO SIGN*************

# Match the algorithm to the hashing algorithm you use, either SHA-1 or
# SHA-256 (recommended)
algorithm = 'AWS4-HMAC-SHA256'
credential_scope = datestamp + '/' + region + '/' + service + '/' + 'aws4_request'
string_to_sign = algorithm + '\n' + amzdate + '\n' + credential_scope + '\n' +
hashlib.sha256(canonical_request).hexdigest()
# ************* TASK 3: CALCULATE THE SIGNATURE *************

# Create the signing key using the function defined above.
signing_key = getSignatureKey(secret_key, datestamp, region, service)
# Sign the string_to_sign using the signing_key

signature = hmac.new(signing_key, (string_to_sign).encode('utf-8'),
hashlib.sha256).hexdigest()
# ************* TASK 4: ADD SIGNING INFORMATION TO THE REQUEST *************

# The signing information can be either in a query string value or in
# a header named Authorization. This code shows how to use a header.
# Create authorization header and add to request headers
authorization_header = algorithm + ' ' + 'Credential=' + access_key + '/' +
credential_scope + ', ' + 'SignedHeaders=' + signed_headers + ', ' + 'Signature=' +
signature
# The request can include any headers, but MUST include "host", "x-amz-date",
# and (for this scenario) "Authorization". "host" and "x-amz-date" must
# be included in the canonical_headers and signed_headers, as noted
# earlier. Order here is not significant.
# Python note: The 'host' header is added automatically by the Python 'requests' library.
headers = {'x-amz-date':amzdate, 'Authorization':authorization_header}
# ************* SEND THE REQUEST *************

request_url = endpoint + '?' + canonical_querystring
print '\nBEGIN REQUEST++++++++++++++++++++++++++++++++++++'

print 'Request URL = ' + request_url
r = requests.get(request_url, headers=headers)
print '\nRESPONSE++++++++++++++++++++++++++++++++++++'
print 'Response code: %d\n' % r.status_code
print r.text
Using POST (Python)

The following example shows how to make a request using the Amazon DynamoDB query API. The
request makes a POST request and passes values to AWS in the body of the request. Authentication
information is passed using the Authorization request header.
Version 1.0
170
# DynamoDB API (CreateTable)
# This version makes a POST request and passes request parameters
# in the body (payload) of the request. Auth information is passed in
# an Authorization header.
import sys, os, base64, datetime, hashlib, hmac
# ************* REQUEST VALUES *************

method = 'POST'
service = 'dynamodb'
host = 'dynamodb.us-west-2.amazonaws.com'
region = 'us-west-2'
endpoint = 'https://dynamodb.us-west-2.amazonaws.com/'
# POST requests use a content type header. For DynamoDB,
# the content is JSON.
content_type = 'application/x-amz-json-1.0'
# DynamoDB requires an x-amz-target header that has this format:
# DynamoDB_<API version>.<operationName>
amz_target = 'DynamoDB_20120810.CreateTable'
# Request parameters for CreateTable--passed in a JSON block.

request_parameters = '{'
request_parameters += '"KeySchema": [{"KeyType": "HASH","AttributeName": "Id"}],'
request_parameters += '"TableName": "TestTable","AttributeDefinitions": [{"AttributeName":
"Id","AttributeType": "S"}],'
request_parameters += '"ProvisionedThroughput": {"WriteCapacityUnits":
5,"ReadCapacityUnits": 5}'
request_parameters += '}'

examples-python
def sign(key, msg):
return hmac.new(key, msg.encode("utf-8"), hashlib.sha256).digest()
def getSignatureKey(key, date_stamp, regionName, serviceName):

kDate = sign(('AWS4' + key).encode('utf-8'), date_stamp)
return kSigning
sys.exit()

amz_date = t.strftime('%Y%m%dT%H%M%SZ')
date_stamp = t.strftime('%Y%m%d') # Date w/o time, used in credential scope

# Step 1 is to define the verb (GET, POST, etc.)--already done.
Version 1.0
171
canonical_uri = '/'
## Step 3: Create the canonical query string. In this example, request

# parameters are passed in the body of the request and the query string
# is blank.
canonical_querystring = ''
# Step 4: Create the canonical headers. Header names must be trimmed

# and lowercase, and sorted in code point order from low to high.
# Note that there is a trailing \n.
canonical_headers = 'content-type:' + content_type + '\n' + 'host:' + host + '\n' + 'x-amz-
date:' + amz_date + '\n' + 'x-amz-target:' + amz_target + '\n'
# Step 5: Create the list of signed headers. This lists the headers
# in the canonical_headers list, delimited with ";" and in alpha order.
# Note: The request can include any headers; canonical_headers and
# signed_headers include those that you want to be included in the
# hash of the request. "Host" and "x-amz-date" are always required.
# For DynamoDB, content-type and x-amz-target are also required.
signed_headers = 'content-type;host;x-amz-date;x-amz-target'
# Step 6: Create payload hash. In this example, the payload (body of

# the request) contains the request parameters.
payload_hash = hashlib.sha256(request_parameters).hexdigest()


credential_scope = date_stamp + '/' + region + '/' + service + '/' + 'aws4_request'
string_to_sign = algorithm + '\n' + amz_date + '\n' + credential_scope + '\n' +

# Create the signing key using the function defined above.
signing_key = getSignatureKey(secret_key, date_stamp, region, service)

signature = hmac.new(signing_key, (string_to_sign).encode('utf-8'),

# Put the signature information in a header named Authorization.
authorization_header = algorithm + ' ' + 'Credential=' + access_key + '/' +
credential_scope + ', ' + 'SignedHeaders=' + signed_headers + ', ' + 'Signature=' +
signature
# For DynamoDB, the request can include any headers, but MUST include "host", "x-amz-date",
# "x-amz-target", "content-type", and "Authorization". Except for the authorization
# header, the headers must be included in the canonical_headers and signed_headers values,
as
# noted earlier. Order here is not significant.
# # Python note: The 'host' header is added automatically by the Python 'requests' library.
headers = {'Content-Type':content_type,
'X-Amz-Date':amz_date,
'X-Amz-Target':amz_target,
'Authorization':authorization_header}
Version 1.0
172
# ************* SEND THE REQUEST *************

print 'Request URL = ' + endpoint
r = requests.post(endpoint, data=request_parameters, headers=headers)
print '\nRESPONSE++++++++++++++++++++++++++++++++++++'
print r.text
Using GET with Authentication Information in the Query String

(Python)
The following example shows how to make a request using the IAM query API. The request makes a GET
request and passes parameters and signing information using the query string.
# IAM API (CreateUser)
# This version makes a GET request and passes request parameters
# and authorization information in the query string
import sys, os, base64, datetime, hashlib, hmac, urllib
# ************* REQUEST VALUES *************

method = 'GET'
service = 'iam'
host = 'iam.amazonaws.com'
region = 'us-east-1'
endpoint = 'https://iam.amazonaws.com'

examples-python
def sign(key, msg):
return hmac.new(key, msg.encode('utf-8'), hashlib.sha256).digest()

kDate = sign(('AWS4' + key).encode('utf-8'), dateStamp)
return kSigning
sys.exit()

amz_date = t.strftime('%Y%m%dT%H%M%SZ') # Format date as YYYYMMDD'T'HHMMSS'Z'
datestamp = t.strftime('%Y%m%d') # Date w/o time, used in credential scope
Version 1.0
173
# Because almost all information is being passed in the query string,

# the order of these steps is slightly different than examples that
# use an authorization header.
# Step 1: Define the verb (GET, POST, etc.)--already done.
canonical_uri = '/'
# Step 3: Create the canonical headers and signed headers. Header names
# must be trimmed and lowercase, and sorted in code point order from
# low to high. Note trailing \n in canonical_headers.
# signed_headers is the list of headers that are being included
# as part of the signing process. For requests that use query strings,
# only "host" is included in the signed headers.
canonical_headers = 'host:' + host + '\n'
signed_headers = 'host'
credential_scope = datestamp + '/' + region + '/' + service + '/' + 'aws4_request'
# Step 4: Create the canonical query string. In this example, request

# parameters are in the query string. Query string values must
# be URL-encoded (space=%20). The parameters must be sorted by name.
canonical_querystring = 'Action=CreateUser&UserName=NewUser&Version=2010-05-08'
canonical_querystring += '&X-Amz-Algorithm=AWS4-HMAC-SHA256'
canonical_querystring += '&X-Amz-Credential=' + urllib.quote_plus(access_key + '/' +
credential_scope)
canonical_querystring += '&X-Amz-Date=' + amz_date
canonical_querystring += '&X-Amz-Expires=30'
canonical_querystring += '&X-Amz-SignedHeaders=' + signed_headers
# Step 5: Create payload hash. For GET requests, the payload is an

# empty string ("").
payload_hash = hashlib.sha256('').hexdigest()


string_to_sign = algorithm + '\n' + amz_date + '\n' + credential_scope + '\n' +

# Create the signing key
signing_key = getSignatureKey(secret_key, datestamp, region, service)

signature = hmac.new(signing_key, (string_to_sign).encode("utf-8"),

# The auth information can be either in a query string
# value or in a header named Authorization. This code shows how to put
# everything into a query string.
canonical_querystring += '&X-Amz-Signature=' + signature
Version 1.0
174
Test Suite
# ************* SEND THE REQUEST *************

# The 'host' header is added automatically by the Python 'request' lib. But it
# must exist as a header in the request.
request_url = endpoint + "?" + canonical_querystring

print 'Request URL = ' + request_url
r = requests.get(request_url)
print '\nRESPONSE++++++++++++++++++++++++++++++++++++'
print r.text
Signature Version 4 Test Suite

To assist you in the development of an AWS client that supports Signature Version 4, you can use the
files in the test suite to ensure your code is performing each step of the signing process correctly.
To get the test suite, download aws-sig-v4-test-suite.zip.
Topics
• Credential Scope and Secret Key (p. 175)
• Example—A Simple GET Request with Parameters (p. 175)
Each test group contains five files that you can use to validate each of the tasks described in Signature
Version 4 Signing Process (p. 152). The following list describes the contents of each file.
• file-name.req—the web request to be signed.

• file-name.creq—the resulting canonical request.
• file-name.sts—the resulting string to sign.
• file-name.authz—the Authorization header.
• file-name.sreq— the signed request.
Credential Scope and Secret Key

The examples in the test suite use the following credential scope:
AKIDEXAMPLE/20150830/us-east-1/service/aws4_request
The example secret key used for signing is:
wJalrXUtnFEMI/K7MDENG+bPxRfiCYEXAMPLEKEY
Example—A Simple GET Request with Parameters

The following example shows the web request to be signed from the get-vanilla-query-order-
key-case.req file. This is the original request.
GET /?Param2=value2&Param1=value1 HTTP/1.1

Host:example.amazonaws.com
X-Amz-Date:20150830T123600Z
Version 1.0
175
Test Suite
Task 1: Create a Canonical Request

In the steps outlined in Task 1: Create a Canonical Request for Signature Version 4 (p. 155), change the
request in the get-vanilla-query-order-key-case.req file.

X-Amz-Date:20150830T123600Z
This creates the canonical request in the get-vanilla-query-order-key-case.creq file.
GET
/
Param1=value1&Param2=value2
host:example.amazonaws.com
x-amz-date:20150830T123600Z
host;x-amz-date
Notes
• The parameters are sorted alphabetically (by character code).

• The header names are lowercase.
• There is a line break between the x-amz-date header and the signed headers.
• The hash of the payload is the hash of the empty string.
Task 2: Create a String to Sign

The hash of the canonical request returns the following value:
816cd5b414d056048ba4f7c5386d6e0533120fb1fcfa93762cf0fc39e2cf19e0
In the steps outlined in Task 2: Create a String to Sign for Signature Version 4 (p. 160), add the
algorithm, request date, credential scope, and the canonical request hash to create the string to sign.
The result is the get-vanilla-query-order-key-case.sts file.
AWS4-HMAC-SHA256
20150830T123600Z
20150830/us-east-1/service/aws4_request
816cd5b414d056048ba4f7c5386d6e0533120fb1fcfa93762cf0fc39e2cf19e0
Notes
• The date on the second line matches the x-amz-date header, as well as the first element in the
credential scope.
• The last line is the hex-encoded value for the hash of the canonical request.
Task 3: Calculate the Signature

In the steps outlined in Task 3: Calculate the Signature for AWS Signature Version 4 (p. 161), create
a signature with your signing key and the string to sign from the get-vanilla-query-order-key-
case.sts file.
The result generates the contents in the get-vanilla-query-order-key-case.authz file.
Version 1.0
176
Troubleshooting
AWS4-HMAC-SHA256 Credential=AKIDEXAMPLE/20150830/us-east-1/
service/aws4_request, SignedHeaders=host;x-amz-date,
Signature=b97d918cfa904a5beff61c982a1b6f458b799221646efd99d3219ec94cdf2500
Task 4: Add the Signing Information to the Request

In the steps outlined in Task 4: Add the Signing Information to the Request (p. 163), add the signing
information generated in task 3 to the original request. For example, take the contents in the get-
vanilla-query-order-key-case.authz, add it to the Authorization header, and then add the
result to the get-vanilla-query-order-key-case.req.
This creates the signed request in the get-vanilla-query-order-key-case.sreq file.

X-Amz-Date:20150830T123600Z
Authorization: AWS4-HMAC-SHA256 Credential=AKIDEXAMPLE/20150830/
us-east-1/service/aws4_request, SignedHeaders=host;x-amz-date,
Signature=b97d918cfa904a5beff61c982a1b6f458b799221646efd99d3219ec94cdf2500
Troubleshooting AWS Signature Version 4 Errors

Topics
• Troubleshooting AWS Signature Version 4 Canonicalization Errors (p. 177)
• Troubleshooting AWS Signature Version 4 Credential Scope Errors (p. 178)
• Troubleshooting AWS Signature Version 4 Key Signing Errors (p. 179)
When you develop code that implements Signature Version 4, you might receive errors from AWS
products that you test against. The errors typically come from an error in the canonicalization of the
request, the incorrect derivation or use of the signing key, or a validation failure of signature-specific
parameters sent along with the request.
Troubleshooting AWS Signature Version 4 Canonicalization

Errors
Consider the following request:
https://iam.amazonaws.com/?MaxItems=100
&Action=ListGroupsForUser
&UserName=Test
&Version=2010-05-08
&X-Amz-Date=20120223T063000Z
&X-Amz-Credential=AKIAIOSFODNN7EXAMPLE/20120223/us-east-1/iam/aws4_request
&X-Amz-SignedHeaders=host
&X-Amz-Signature=<calculated value>
If you incorrectly calculate the canonical request or the string to sign, the signature verification step
performed by the service fails. The following example is a typical error response, which includes the
canonical string and the string to sign as computed by the service. You can troubleshoot your calculation
error by comparing the returned strings with the canonical string and your calculated string to sign.
<ErrorResponse xmlns="https://iam.amazonaws.com/doc/2010-05-08/">
<Error>
<Type>Sender</Type>
Version 1.0
177
Troubleshooting
<Code>SignatureDoesNotMatch</Code>
<Message>The request signature we calculated does not match the signature you provided.
Check your AWS Secret Access Key and signing method. Consult the service documentation for
details.
The canonical string for this request should have been 'GET /
Action=ListGroupsForUser&MaxItems=100&UserName=Test&Version=2010-05-08&X-Amz-
Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential
=AKIAIOSFODNN7EXAMPLE%2F20120223%2Fus-east-1%2Fiam%2Faws4_request&X-Amz-
Date=20120223T063000Z&X-Amz-SignedHeaders=host
host:iam.amazonaws.com
host
<hashed-value>'
The String-to-Sign should have been

'AWS4-HMAC-SHA256
20120223T063000Z
20120223/us-east-1/iam/aws4_request
<hashed-value>'
</Message>
</Error>
<RequestId>4ced6e96-5de8-11e1-aa78-a56908bdf8eb</RequestId>
</ErrorResponse>
For testing with an SDK, we recommend troubleshooting by verifying each derivation step against known
values. For more information, see Signature Version 4 Test Suite (p. 175).
Troubleshooting AWS Signature Version 4 Credential Scope

Errors
AWS products validate credentials for proper scope; the credential parameter must specify the correct
service, region, and date. For example, the following credential references the Amazon RDS service:
Credential=AKIAIOSFODNN7EXAMPLE/20120224/us-east-1/rds/aws4_request
If you use the same credentials to submit a request to IAM, you'll receive the following error response:
<Error>
<Type>Sender</Type>
<Message>Credential should be scoped to correct service: 'iam'. </Message>
</Error>
<RequestId>aa0da9de-5f2b-11e1-a2c0-c1dc98b6c575</RequestId>
The credential must also specify the correct region. For example, the following credential for an IAM
request incorrectly specifies the US West (N. California) region.
Credential=AKIAIOSFODNN7EXAMPLE/20120224/us-west-1/iam/aws4_request
If you use the credential to submit a request to IAM, which accepts only the us-east-1 region
specification, you'll receive the following response:
<Error>
<Type>Sender</Type>
<Message>Credential should be scoped to a valid region, not 'us-east-1'. </Message>
Version 1.0
178
Troubleshooting
</Error>
<RequestId>8e229682-5f27-11e1-88f2-4b1b00f424ae</RequestId>
</ErrorResponse>
You'll receive the same type of invalid region response from AWS products that are available in multiple
regions if you submit requests to a region that differs from the region specified in your credential scope.
The credential must also specify the correct region for the service and action in your request.
The date that you use as part of the credential must match the date value in the x-amz-date header.
For example, the following x-amz-date header value does not match the date value used in the
Credential parameter that follows it.
x-amz-date:"20120224T213559Z"
Credential=AKIAIOSFODNN7EXAMPLE/20120225/us-east-1/iam/aws4_request
If you use this pairing of x-amz-date header and credential, you'll receive the following error response:
<Error>
<Type>Sender</Type>
<Message>Date in Credential scope does not match YYYYMMDD from ISO-8601 version of date
from HTTP: '20120225' != '20120224', from '20120 224T213559Z'.</Message>
</Error>
<RequestId>9d6ddd2b-5f2f-11e1-b901-a702cd369eb8</RequestId>
</ErrorResponse>
An expired signature can also generate an error response. For example, the following error response was
generated due to an expired signature.
<Error>
<Type>Sender</Type>
<Message>Signature expired: 20120306T074514Z is now earlier than 20120306T074556Z
(20120306T080056Z - 15 min.)</Message>
</Error>
<RequestId>fcc88440-5dec-11e1-b901-a702cd369eb8</RequestId>
</ErrorResponse>
Troubleshooting AWS Signature Version 4 Key Signing Errors

Errors that are caused by an incorrect derivation of the signing key or improper use of cryptography are
more difficult to troubleshoot. The error response will tell you that the signature does not match. If you
verified that the canonical string and the string to sign are correct, the cause of the signature mismatch
is most likely one of the two following issues:
• The secret access key does not match the access key ID that you specified in the Credential
parameter.
• There is a problem with your key derivation code.
To check whether the secret key matches the access key ID, you can use your secret key and access key ID
with a known working implementation. One way is to use one of the AWS SDKs to write a program that
makes a simple request to AWS using the access key ID and secret access key that you want to use.
To check whether your key derivation code is correct, you can compare it to our example derivation code.
For more information, see Examples of How to Derive a Signing Key for Signature Version 4 (p. 165).
Version 1.0
179
Service-Specific Reference
Service-Specific Reference for Signature Version 4

To learn more about making and signing HTTP requests in the context of specific AWS services, see the
documentation for the following services:
• Amazon API Gateway

• Amazon CloudSearch
• Amazon CloudWatch
• AWS Data Pipeline
• Amazon Elastic Compute Cloud (Amazon EC2)
• Amazon Elastic Transcoder
• Amazon Glacier
• Amazon Mobile Analytics
• Amazon Relational Database Service (Amazon RDS)
• Amazon Simple Email Service (Amazon SES)
• Amazon Simple Queue Service (Amazon SQS)
• Amazon Simple Storage Service (Amazon S3)
• Amazon Simple Workflow Service (Amazon SWF)
• AWS WAF

You can use Signature Version 2 to sign API requests. However, we recommend that you sign
your request with Signature Version 4. For more information, see Signature Version 4 Signing
Process (p. 152).
Supported Regions and Services

The following regions don't support Signature Version 2. You must use Signature Version 4 to sign API
requests in these regions:
• US East (Ohio) Region

• Canada (Central) Region
• Asia Pacific (Mumbai) Region
• Asia Pacific (Seoul) Region
• EU (Frankfurt) Region
• EU (London) Region
• China (Beijing) Region
The following services support Signature Version 2 in all other regions.
AWS services that support Signature Version 2
Amazon EC2 Auto Scaling Amazon EC2 Auto Scaling API Reference
AWS CloudFormation AWS CloudFormation API Reference
Amazon CloudWatch Amazon CloudWatch API Reference
Version 1.0
180
Components of a Query Request for Signature Version 2
AWS Elastic Beanstalk AWS Elastic Beanstalk API Reference
Amazon Elastic Compute Cloud (Amazon Amazon EC2 API Reference

EC2)
Elastic Load Balancing Elastic Load Balancing API Reference version

2012-06-01
Amazon EMR Amazon EMR API Reference
Amazon ElastiCache Amazon ElastiCache API Reference
AWS Identity and Access Management (IAM) IAM API Reference
AWS Import/Export AWS Import/Export API Reference
Amazon Relational Database Service Amazon Relational Database Service API Reference
(Amazon RDS
Amazon Simple Notification Service (Amazon Amazon Simple Notification Service API Reference
SNS)
Amazon Simple Queue Service (Amazon Amazon Simple Queue Service API Reference
SQS)
Amazon SimpleDB Amazon SimpleDB API Reference
Components of a Query Request for Signature

Version 2
AWS requires that each HTTP or HTTPS Query request formatted for Signature Version 2 contains the
following:
Endpoint
Also known as the host part of an HTTP request. This is the DNS name of the computer where you
send the Query request. This is different for each AWS region. For the list of endpoints for each
service, see AWS Regions and Endpoints (p. 2).
Action
The action you want a web service to perform. This value determines the parameters used in the
request.
AWSAccessKeyId
A value distributed by AWS when you sign up for an AWS account.

SignatureMethod
The hash-based protocol used to calculate the signature. This can be either HMAC-SHA1 or HMAC-
SHA256 for Signature Version 2.
SignatureVersion
The version of the AWS signature protocol.

Timestamp
The time at which you make the request. Include this in the Query request to help prevent third
parties from intercepting your request.
Version 1.0
181
How to Generate a Signature Version 2 for a Query Request
Required and optional parameters
Each action has a set of required and optional parameters that define the API call.
Signature
The calculated value that ensures the signature is valid and has not been tampered.
The following is an example Amazon EMR Query request formatted as an HTTPS GET request.
• The endpoint, elasticmapreduce.amazonaws.com, is the default endpoint and maps to the region
us-east-1.
• The action is DescribeJobFlows, which requests information about one or more job flows.
Note
In the actual Query request, there are no spaces or newline characters. The request is a
continuous line of text. The version below is formatted for human readability.
https://elasticmapreduce.amazonaws.com?
&AWSAccessKeyId=AKIAIOSFODNN7EXAMPLE
&Action=DescribeJobFlows
&SignatureMethod=HmacSHA256
&SignatureVersion=2
&Timestamp=2011-10-03T15%3A19%3A30
&Version=2009-03-31
&Signature=calculated value
How to Generate a Signature Version 2 for a Query

Request
Web service requests are sent across the Internet and are vulnerable to tampering. To check that the
request has not been altered, AWS calculates the signature to determine if any of the parameters or
parameter values were changed en route. AWS requires a signature as part of every request.
Note
Be sure to URI encode the request. For example, blank spaces in your request should be encoded
as %20. Although an unencoded space is normally allowed by the HTTP protocol specification,
unencoded characters create an invalid signature in your Query request. Do not encode spaces
as a plus sign (+) as this will cause errors.
The following topics describe the steps needed to calculate a signature using AWS Signature Version 2.
Task 1: Format the Query Request

Before you can sign the Query request, format the request in a standardized (canonical) format. This is
needed because the different ways to format a Query request will result in different HMAC signatures.
Format the request in a canonical format before signing. This ensures your application and AWS will
calculate the same signature for a request.
To create the string to sign, you concatenate the Query request components. The following example
generates the string to sign for the following call to the Amazon EMR API.
Action=DescribeJobFlows
&Version=2009-03-31
&AWSAccessKeyId=AKIAIOSFODNN7EXAMPLE
Version 1.0
182
&SignatureVersion=2
&Timestamp=2011-10-03T15:19:30
Note
In the preceding request, the last four parameters (AWSAccessKeyID through Timestamp) are
called authentication parameters. They're required in every Signature Version 2 request. AWS
uses them to identify who is sending the request and whether to grant the requested access.
To create the string to sign (Signature Version 2)
1. Start with the request method (either GET or POST), followed by a newline character. For human
readability, the newline character is represented as \n.
GET\n
2. Add the HTTP host header (endpoint) in lowercase, followed by a newline character. The port
information is omitted if it is the standard port for the protocol (port 80 for HTTP and port 443 for
HTTPS), but included if it is a nonstandard port.
elasticmapreduce.amazonaws.com\n
3. Add the URL-encoded version of each path segment of the URI, which is everything between the
HTTP host header to the question mark character (?) that begins the query string parameters,
followed by a newline character. Don't encode the forward slash (/) that delimits each path
segment.
In this example, if the absolute path is empty, use a forward slash (/).
/\n
4. a. Add the query string components, as UTF-8 characters which are URL encoded (hexadecimal
characters must be uppercase). You do not encode the initial question mark character (?) in the
request. For more information, see RFC 3986.
b. Sort the query string components by byte order. Byte ordering is case sensitive. AWS sorts these
components based on the raw bytes.
For example, this is the original order for the query string components.
Version=2009-03-31
AWSAccessKeyId=AKIAIOSFODNN7EXAMPLE
SignatureVersion=2
SignatureMethod=HmacSHA256
Timestamp=2011-10-03T15%3A19%3A30
The query string components would be reorganized as the following:
AWSAccessKeyId=AKIAIOSFODNN7EXAMPLE
SignatureMethod=HmacSHA256
SignatureVersion=2
Timestamp=2011-10-03T15%3A19%3A30
Version=2009-03-31
c. Separate parameter names from their values with the equal sign character (=), even if the value
is empty. Separate parameter and value pairs with the ampersand character (&). Concatenate
Version 1.0
183
the parameters and their values to make one long string with no spaces. Spaces within a
parameter value are allowed, but must be URL encoded as %20. In the concatenated string,
period characters (.) are not escaped. RFC 3986 considers the period character an unreserved
character, so it is not URL encoded.
Note
RFC 3986 does not specify what happens with ASCII control characters, extended
UTF-8 characters, and other characters reserved by RFC 1738. Since any values may be
passed into a string value, these other characters should be percent encoded as %XY
where X and Y are uppercase hex characters. Extended UTF-8 characters take the form
%XY%ZA... (this handles multibytes).
The following example shows the query string components, with the parameters concatenated with
the ampersand character (&), and sorted by byte order.
AWSAccessKeyId=AKIAIOSFODNN7EXAMPLE&Action=DescribeJobFlows&SignatureMethod=HmacSHA256&SignatureVer
5. To construct the finished canonical request, combine all the components from each step. As shown,
each component ends with a newline character.
GET\n
/\n
AWSAccessKeyId=AKIAIOSFODNN7EXAMPLE&Action=DescribeJobFlows&SignatureMethod=HmacSHA256&SignatureVer
Task 2: Calculate the Signature

After you've created the canonical string as described in Task 1: Format the Query Request (p. 182),
calculate the signature by creating a hash-based message authentication code (HMAC) that uses either
the HMAC-SHA1 or HMAC-SHA256 protocols. The HMAC-SHA256 is preferred.
In this example, the signature is calculated with the following canonical string and secret key as inputs to
a keyed hash function:
• Canonical query string:
GET\n
/\n
AWSAccessKeyId=AKIAIOSFODNN7EXAMPLE&Action=DescribeJobFlows&SignatureMethod=HmacSHA256&SignatureVersi
• Sample secret key:
wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
The resulting signature must be base-64 encoded.
i91nKc4PWAt0JJIdXwz9HxZCJDdiy6cf%2FMj6vPxyYIs%3D
Add the resulting value to the query request as a Signature parameter. When you add this parameter
to the request, you must URI encode it just like any other parameter. You can use the signed request in
an HTTP or HTTPS call.
Version 1.0
184
AWSAccessKeyId=AKIAIOSFODNN7EXAMPLE&Action=DescribeJobFlows&SignatureMethod=HmacSHA256&SignatureVersion
%2FMj6vPxyYIs%3D
Note
You can use temporary security credentials provided by AWS Security Token Service (AWS STS)
to sign a request. The process is the same as using long-term credentials, but requests require
an additional parameter for the security token.
The following request uses a temporary access key ID and the SecurityToken parameter.
Example Example request with temporary security credentials
https://sdb.amazonaws.com/
?Action=GetAttributes
&AWSAccessKeyId=access-key-from-AWS Security Token Service
&DomainName=MyDomain
&ItemName=MyItem
&SignatureVersion=2
&Timestamp=2010-01-25T15%3A03%3A07-07%3A00
&Version=2009-04-15
&Signature=signature-calculated-using-the-temporary-access-key
&SecurityToken=session-token
For more information, see the following resources:
• The Amazon EMR Developer Guide has information about Amazon EMR API calls.
• The API documentation for each service has information about requirements and specific parameters
for an action.
• The AWS SDKs offer functions to generate Query request signatures. To see an example using the AWS
SDK for Java, see Using the Java SDK to Sign a Query Request (p. 186).
Troubleshooting Request Signatures Version 2

This section describes some error codes you might see when you are initially developing code to generate
the signature to sign Query requests.
SignatureDoesNotMatch Signing Error in a web service

The following error response is returned when a web service attempts to validate the request signature
by recalculating the signature value and generates a value that does not match the signature you
appended to the request. This can occur because the request was altered between the time you sent it
and the time it reached a web service endpoint (which is what the signature is designed to detect) or
because the signature was calculated improperly. A common cause of the following error message is not
properly creating the string to sign, such as forgetting to URL-encode characters such as the colon (:) and
the forward slash (/) in Amazon S3 bucket names.
<ErrorResponse xmlns="http://elasticmapreduce.amazonaws.com/doc/2009-03-31">
<Error>
<Type>Sender</Type>
<Message>The request signature we calculated does not match the signature you
provided.
Version 1.0
185
Check your AWS Secret Access Key and signing method.

Consult the service documentation for details.</Message>
</Error>
<RequestId>7589637b-e4b0-11e0-95d9-639f87241c66</RequestId>
</ErrorResponse>
IncompleteSignature Signing Error in a web service

The following error indicates that signature is missing information or has been improperly formed.
<ErrorResponse xmlns="http://elasticmapreduce.amazonaws.com/doc/2009-03-31">
<Error>
<Type>Sender</Type>
<Code>IncompleteSignature</Code>
<Message>Request must contain a signature that conforms to AWS standards</Message>
</Error>
<RequestId>7146d0dd-e48e-11e0-a276-bd10ea0cbb74</RequestId>
</ErrorResponse>
Using the Java SDK to Sign a Query Request

The following example uses the amazon.webservices.common package of the AWS SDK for Java to
generate an AWS Signature Version 2 Query request signature. To do so, it creates an RFC 2104-
compliant HMAC signature. For more information about HMAC, see HMAC: Keyed-Hashing for Message
Authentication.
Note
Java is used as an example implementation. You can use the programming language of your
choice to implement the HMAC algorithm to sign Query requests.
import java.security.SignatureException;
import javax.crypto.Mac;
import javax.crypto.spec.SecretKeySpec;
import com.amazonaws.util.*;
/**
* This class defines common routines for generating
* authentication signatures for AWS Platform requests.
*/
public class Signature {
private static final String HMAC_SHA256_ALGORITHM = "HmacSHA256";
/**
* Computes RFC 2104-compliant HMAC signature.
* * @param data
* The signed data.
* @param key
* The signing key.
* @return
* The Base64-encoded RFC 2104-compliant HMAC signature.
* @throws
* java.security.SignatureException when signature generation fails
*/
public static String calculateRFC2104HMAC(String data, String key)
throws java.security.SignatureException
{
String result;
try {
Version 1.0
186
// Get an hmac_sha256 key from the raw key bytes.

SecretKeySpec signingKey = new SecretKeySpec(key.getBytes("UTF8"),
HMAC_SHA256_ALGORITHM);
// Get an hmac_sha256 Mac instance and initialize with the signing key.
Mac mac = Mac.getInstance(HMAC_SHA256_ALGORITHM);
mac.init(signingKey);
// Compute the hmac on input data bytes.

byte[] rawHmac = mac.doFinal(data.getBytes("UTF8"));
// Base64-encode the hmac by using the utility in the SDK

result = BinaryUtils.toBase64(rawHmac);
} catch (Exception e) {
throw new SignatureException("Failed to generate HMAC : " + e.getMessage());
}
return result;
}
}
Version 1.0
187
AWS Service Limits

The following tables provide the default limits for AWS services for an AWS account. Unless otherwise
noted, each limit is region-specific. Many services contain limits that cannot be changed. For more
information about the limits for a specific service, see the documentation for that service.
AWS Trusted Advisor offers a Service Limits check (in the Performance category) that displays your usage
and limits for some aspects of some services. For more information, see Service Limits Check Questions
in the Trusted Advisor FAQs.
You can take the following steps to request an increase for limits. These increases are not granted
immediately, so it may take a couple of days for your increase to become effective.
To request a limit increase
1. Open the AWS Support Center page, sign in if necessary, and choose Create Case.
2. For Regarding, choose Service Limit Increase.
3. Complete Limit Type, Use Case Description, and Contact method. If this request is urgent, choose
Phone as the method of contact instead of Web.
4. Choose Submit.
Default Limits
• Amazon API Gateway Limits (p. 190)
• Application Auto Scaling Limits (p. 191)
• AWS Application Discovery Service Limits (p. 191)
• Amazon AppStream 2.0 Limits (p. 191)
• AWS AppSync Limits (p. 192)
• Amazon Athena Limits (p. 192)
• AWS Auto Scaling Limits (p. 192)
• Auto Scaling Limits (p. 193)
• AWS Batch Limits (p. 193)
• AWS Certificate Manager (ACM) Limits (p. 193)
• AWS Cloud9 Limits (p. 194)
• AWS CloudFormation Limits (p. 194)
• Amazon CloudFront Limits (p. 194)
• AWS CloudHSM Limits (p. 195)
• AWS CloudHSM Classic Limits (p. 196)
• Amazon CloudSearch Limits (p. 196)
• AWS CloudTrail Limits (p. 196)
• Amazon CloudWatch Limits (p. 196)
• Amazon CloudWatch Events Limits (p. 197)
• Amazon CloudWatch Logs Limits (p. 198)
• AWS CodeBuild Limits (p. 199)
• AWS CodeCommit Limits (p. 199)
• AWS CodeDeploy Limits (p. 199)
• AWS CodePipeline Limits (p. 200)
Version 1.0
188
• Amazon Cognito User Pools Limits (p. 201)

• Amazon Cognito Federated Identities Limits (p. 201)
• Amazon Cognito Sync Limits (p. 201)
• Amazon Comprehend Limits (p. 202)
• AWS Config Limits (p. 202)
• Amazon Connect Limits (p. 202)
• AWS Data Pipeline Limits (p. 203)
• AWS Database Migration Service Limits (p. 204)
• AWS Device Farm Limits (p. 204)
• AWS Direct Connect Limits (p. 204)
• AWS Directory Service Limits (p. 205)
• Amazon DynamoDB Limits (p. 205)
• AWS Elastic Beanstalk Limits (p. 205)
• Amazon Elastic Block Store (Amazon EBS) Limits (p. 206)
• Amazon Elastic Compute Cloud (Amazon EC2) Limits (p. 206)
• Amazon Elastic Container Registry (Amazon ECR) Limits (p. 207)
• Amazon Elastic Container Service (Amazon ECS) Limits (p. 208)
• Amazon Elastic File System Limits (p. 208)
• Elastic Load Balancing Limits (p. 208)
• Amazon Elastic Transcoder Limits (p. 210)
• Amazon ElastiCache Limits (p. 210)
• Amazon Elasticsearch Service Limits (p. 211)
• Amazon GameLift Limits (p. 211)
• Amazon Glacier Limits (p. 212)
• AWS Glue Limits (p. 212)
• AWS Greengrass Limits (p. 213)
• Amazon GuardDuty Limits (p. 214)
• AWS Identity and Access Management (IAM) Limits (p. 215)
• AWS Import/Export Limits (p. 215)
• Amazon Inspector Limits (p. 215)
• AWS IoT Limits (p. 216)
• AWS Key Management Service (AWS KMS) Limits (p. 225)
• Amazon Kinesis Data Firehose Limits (p. 226)
• Amazon Kinesis Data Streams Limits (p. 226)
• Amazon Kinesis Data Analytics Limits (p. 226)
• Amazon Kinesis Video Streams Limits (p. 227)
• AWS Lambda Limits (p. 229)
• Amazon Lightsail Limits (p. 230)
• Amazon Machine Learning (Amazon ML) Limits (p. 230)
• AWS Elemental MediaConvert Limits (p. 231)
• AWS Elemental MediaLive Limits (p. 231)
• AWS Elemental MediaPackage Limits (p. 231)
• AWS Elemental MediaStore Limits (p. 232)
• AWS Elemental MediaTailor Limits (p. 232)
• Amazon MQ Limits (p. 232)
• Amazon Neptune Limits (p. 232)
Version 1.0
189
Amazon API Gateway Limits
• AWS OpsWorks for Chef Automate and AWS OpsWorks for Puppet Enterprise Limits (p. 233)
• AWS OpsWorks Stacks Limits (p. 233)
• AWS Organizations Limits (p. 233)
• Amazon Pinpoint Limits (p. 233)
• Amazon Polly Limits (p. 234)
• Amazon Redshift Limits (p. 235)
• Amazon Rekognition Limits (p. 235)
• Amazon Relational Database Service (Amazon RDS) Limits (p. 235)
• AWS Resource Groups Limits (p. 236)
• Amazon Route 53 Limits (p. 236)
• Amazon SageMaker Limits (p. 237)
• AWS Server Migration Service Limits (p. 238)
• AWS Serverless Application Repository Limits (p. 239)
• AWS Service Catalog Limits (p. 239)
• AWS Shield Advanced Limits (p. 239)
• Amazon Simple Email Service (Amazon SES) Limits (p. 239)
• Amazon Simple Notification Service (Amazon SNS) Limits (p. 240)
• Amazon Simple Storage Service (Amazon S3) Limits (p. 241)
• Amazon Simple Workflow Service (Amazon SWF) Limits (p. 241)
• Amazon SimpleDB Limits (p. 241)
• AWS Step Functions Limits (p. 241)
• AWS Storage Gateway Limits (p. 241)
• AWS Systems Manager Limits (p. 242)
• Amazon Virtual Private Cloud (Amazon VPC) Limits (p. 244)
• Amazon VPC DNS Limits (p. 247)
• AWS WAF Limits (p. 247)
• Amazon WorkMail Limits (p. 248)
• Amazon WorkSpaces Limits (p. 248)
• AWS X-Ray Limits (p. 248)
Amazon API Gateway Limits

The following limits apply to configuring and running an API in Amazon API Gateway and can be
increased upon request to optimize performances of a deployed API in Amazon API Gateway.
Resource or Operation Default Limit
Throttle rate per account per 10000 request per second (rps) with an additional burst capacity
region provided by the token bucket algorithm, using a maximum bucket
capacity of 5000 requests.
APIs (or RestApis) per account 60

per region
API keys per account per region 500
Custom authorizers per API 10
Version 1.0
190
Application Auto Scaling Limits
Resource or Operation Default Limit
Client certificates per account 60

per region
Documentation parts per API 2000
Resources per API 300
Stages per API 10
Usage plans per account per 300

region
Usage plans per API key 10
VPC links per account per region 5
All of the per API limits can only be increased on specific APIs.
For more information about these limits, see Limits in Amazon API Gateway in the API Gateway Developer
Guide.
Application Auto Scaling Limits

Resource Default Limit
Scalable targets 500
Scaling policies per scalable target 50
Step adjustments per scaling policy 20
AWS Application Discovery Service Limits

Inactive agents heartbeating but not collecting data 10,000
Active agents sending data to the service 250
Total collected data for all agents, per day 10 GB
Data storage duration before being purged 90 days
Amazon AppStream 2.0 Limits

Default Limits Per Region Per Account
Stacks 5
Version 1.0
191
AWS AppSync Limits
Fleets 5
Streaming instances 5*
Images 5
Image builders 5†
Users 5
* This is the total limit across all instance families. Certain instance families have additional limits. For
the Graphics Desktop and Graphics Pro instance families, the default limit is 0. For the Graphics Design
instance family, the default limit is 2.
† This is the total limit across all instance families. Certain instance families have additional limits. For
the Graphics Desktop and Graphics Pro instance families, the default limit is 0. For the Graphics Design
instance family, the default limit is 1.
AWS AppSync Limits

Maximum number of APIs per region 5 per account
Maximum number of API keys 50 per API
Maximum schema document size 5 MB
Maximum GraphQL query execution time 30 seconds
Maximum request/response mapping template size 64 KB
Amazon Athena Limits

Number of concurrent queries 5
Query timeout 30 minutes
For information about limits for databases, tables, and partitions, see AWS Glue Limits (p. 212).
AWS Auto Scaling Limits

Scaling plans 100
Version 1.0
192
Auto Scaling Limits
Target tracking configurations per scaling instruction 10
Target tracking configurations per scaling plan 500
Auto Scaling Limits

Launch configurations per region 200
Auto Scaling groups per region 200
Scaling policies per Auto Scaling group 50
Scheduled actions per Auto Scaling group 125
Lifecycle hooks per Auto Scaling group 50
SNS topics per Auto Scaling group 10
Load balancers per Auto Scaling group 50
Target groups per Auto Scaling group 50
Step adjustments per scaling policy 20
For more information about these limits, see Amazon EC2 Auto Scaling Limits in the Amazon EC2 Auto
Scaling User Guide.
AWS Batch Limits

Item Default Limit
Maximum number of job queues 20
Maximum number of compute environments per 3

job queue
For more information about these limits, see Service Limits in the AWS Batch User Guide.
AWS Certificate Manager (ACM) Limits

Item Default Limit
Number of ACM-provided certificates 100
Version 1.0
193
AWS Cloud9 Limits
Item Default Limit
Number of imported certificates 100
Number of domain names per ACM-provided 10

certificate
For more information about these limits, see Limits in the AWS Certificate Manager User Guide.
AWS Cloud9 Limits

Item Default Limit
Maximum number of AWS Cloud9 EC2 • 20 per IAM user

development environments • 100 per AWS account
Maximum number of SSH environments • 10 per IAM user

• 100 per AWS account
Maximum number of members in an environment 8
Maximum number of environments open at the 10 total per IAM user, regardless of environment
same time type (EC2 or SSH)
For more information about these limits, see Limits in the AWS Cloud9 User Guide.
AWS CloudFormation Limits

Stacks 200
Stack sets 20
Stack instances per stack set 500
For more information about these limits, see AWS CloudFormation Limits in the AWS CloudFormation
User Guide.
Amazon CloudFront Limits

General Limits
Data transfer rate per distribution 40 Gbps
Version 1.0
194
AWS CloudHSM Limits
Requests per second per distribution 100,000
Web distributions per account 200
RTMP distributions per account 100
Alternate domain names (CNAMEs) per distribution 100
Origins per distribution 25
Cache behaviors per distribution 25
Whitelisted headers per cache behavior 10
Whitelisted cookies per cache behavior 10
SSL certificates per account when serving HTTPS requests using dedicated IP addresses (no limit 2
when serving HTTPS requests using SNI)
Custom headers that you can have Amazon CloudFront forward to the origin 10 name–value
Whitelisted query strings per cache behavior For more inform

CloudFront to C
String Paramet
CloudFront Dev
Response timeout per origin For more inform

Timeout in the
Developer Guide
Lambda@Edge Limits
Distributions per AWS account that you can create triggers for 25
Triggers per distribution 25
Requests per second 10,000
Concurrent executions 1,000
For more information about these limits, see Limits in the Amazon CloudFront Developer Guide.
AWS CloudHSM Limits

Clusters 4
HSMs 6
For more information about these limits, see Limits in the AWS CloudHSM User Guide.
Version 1.0
195
AWS CloudHSM Classic Limits
AWS CloudHSM Classic Limits

HSM appliances 3
High-availability partition groups 20
For more information about these limits, see Limits in the AWS CloudHSM Classic User Guide.
Amazon CloudSearch Limits

Partitions 10
Search instances 50
For more information about these limits, see Understanding Amazon CloudSearch Limits in the Amazon
CloudSearch Developer Guide.
AWS CloudTrail Limits

CloudTrail has no increaseable limits. For more information, see Limits in AWS CloudTrail.
Amazon CloudWatch Limits

Resource Default Limit Comments
Alarms 10 per month per customer For the 5000 per region per
for free. 5000 per region per account limit, you can request a
account. limit increase.
DescribeAlarms 9 transactions per second (TPS) The maximum number of

operation requests you can
make per second without being
throttled.
You can request a limit increase.
GetMetricStatistics 400 transactions per second The maximum number of

(TPS) operation requests you can
throttled.
Version 1.0
196
Amazon CloudWatch Events Limits
ListMetrics 25 transactions per second (TPS) The maximum number of

throttled.
PutMetricAlarm 3 transactions per second (TPS) The maximum number of

throttled.
PutMetricData 150 transactions per second The maximum number of

(TPS) operation requests you can
throttled.
For more information about these and other CloudWatch limits, see CloudWatch Limits in the Amazon
CloudWatch User Guide.
Amazon CloudWatch Events Limits

Invocations 750 per second (after 750 You can request a limit increase.
invocations, the invocations
are throttled; that is, they still
happen but they are delayed). If
the invocation of a target fails
due to a problem with the target
service, account throttling, etc.,
new attempts are made for
up to 24 hours for a specific
invocation.
Rules 100 per region per account You can request a limit increase.
Before requesting a limit

increase, examine your rules.
You may have multiple rules
each matching to very specific
events. Consider broadening
their scope by using fewer
identifiers in your Events and
Event Patterns. In addition, a
rule can invoke several targets
each time it matches an event.
Consider adding more targets to
your rules.
Version 1.0
197
Amazon CloudWatch Logs Limits
PutEvents 10 entries per request and You can request a limit increase.
400 requests per second. Each
request can be up to 256 KB in
size.
For more information about these and other CloudWatch Events limits, see CloudWatch Events Limits in
the Amazon CloudWatch Events User Guide.
Amazon CloudWatch Logs Limits

CreateLogGroup 5000 log groups/account/ If you exceed your log

Region group limit, you get a
ResourceLimitExceeded
exception.
DescribeLogStreams 5 transactions per second (TPS)/ If you experience frequent

account/Region throttling, you can request a
limit increase.
FilterLogEvents 5 transactions per second (TPS)/ This limit can be changed only
account/region in special circumstances. If you
experience frequent throttling,
contact AWS Support.
GetLogEvents 10 transactions per second We recommend subscriptions if

(TPS)/account/Region you are continuously processing
new data. If you need historical
data, we recommend exporting
your data to Amazon S3. This
limit can be changed only in
special circumstances. If you
experience frequent throttling,
contact AWS Support.
PutLogEvents 1500 transactions per second You can request a limit increase.
per account per Region, except
for the following Regions where The maximum batch size of a
the limit is 800 transactions per PutLogEvents request is 1MB.
second per account per Region:
ap-south-1, ap-northeast-1, ap- 5 requests per second per log
northeast-2, ap-southeast-1, ap- stream. Additional requests are
southeast-2, eu-central-1, eu- throttled. This limit cannot be
west-2, sa-east-1, us-east-2, and changed.
us-west-1.
For more information about these and other CloudWatch Logs limits, see CloudWatch Logs Limits in the
Amazon CloudWatch Logs User Guide.
Version 1.0
198
AWS CodeBuild Limits
AWS CodeBuild Limits

Maximum number of build 1,000

projects
Maximum number of concurrent 20

running builds *
* Limits for the maximum number of concurrent running builds vary, depending on the compute type.
For some compute types, the default is 20. To request a higher concurrent build limit or if you get a
"Cannot have more than X active builds for the account" error, contact AWS support.
For more information about these limits, see Limits for AWS CodeBuild in the AWS CodeBuild User Guide.
AWS CodeCommit Limits

Number of repositories 1,000 per AWS account
For more information about these limits, see Limits in AWS CodeCommit in the AWS CodeCommit User
Guide.
AWS CodeDeploy Limits

Maximum number of applications associated with an AWS account 100

in a single region
Maximum number of concurrent deployments associated with an 10

AWS account
Maximum number of deployment groups associated with a single 100

application
Maximum number of instances in a single deployment 500
Maximum number of event notification triggers in a deployment 10

group
For more information about these limits, see Limits in AWS CodeDeploy in the AWS CodeDeploy User
Guide.
Version 1.0
199
AWS CodePipeline Limits
AWS CodePipeline Limits

Maximum number of pipelines per region in an AWS account US East (N. Virginia)
(us-east-1): 40
US West (Oregon) (us-

west-2): 60
EU (Ireland) (eu-
west-1): 60
All other supported

regions: 20
Number of stages in a pipeline Minimum of 2, maxi-

mum of 10
Number of actions in a stage Minimum of 1, maxi-

mum of 20
Maximum number of parallel actions in a stage Maximum of 10
Maximum number of sequential actions in a stage Maximum of 10
Number of custom actions per region in an AWS account 50
Maximum size of artifacts in a source stage Artifacts stored in

Amazon S3 buckets: 2
GB
Artifacts stored in AWS

CodeCommit or GitHub
repositories: 1 GB
Exception: If you are

using Amazon EBS to
deploy applications, the
maximum artifact size
is always 512 MB.
Exception: If you
are using AWS
CloudFormation to
deploy applications, the
maximum artifact size
is always 256 MB.
It may take up to two weeks to process requests for a limit increase.
For more information about these limits, see Limits in AWS CodePipeline in the AWS CodePipeline User
Guide.
Version 1.0
200
Amazon Cognito User Pools Limits
Amazon Cognito User Pools Limits

Maximum number of apps per user pool 25
Maximum number of user pools per account 60
Maximum number of user import jobs per user 50

pool
Maximum number of identity providers per user 25

pool
Maximum number of resource servers per user 20

pool
Maximum number of scopes per user pool 20
For information about additional documented limits, see Limits in Amazon Cognito in the Amazon
Cognito Developer Guide.
Amazon Cognito Federated Identities Limits

Maximum number of identity pools per account 60
Amazon Cognito Sync Limits

Maximum number of datasets per identity 20
Maximum number of records per dataset 1024
Maximum size of a single dataset 1 MB
Version 1.0
201
Amazon Comprehend Limits
Amazon Comprehend Limits

Transactions per second for the 20

DetectDominantLanguage, DetectEntities,
DetectKeyPhrases, and DetectSentiment
operations

BatchDetectDominantLanguage,
BatchDetectEntities,
BatchDetectKeyPhrases, and
BatchDetectSentiment operations

StartTopicsDetectionJob operation

DescribeTopicsDetectionJob and
ListTopicDetectionJobs operations
Maximum concurrent jobs 10
You can request an increase for any of the limits using the Amazon Comprehend service limits increase
form.
For information about additional documented limits, see Guidelines and Limits in the Amazon
Comprehend Developer Guide.
AWS Config Limits

Resource Default Limit Notes
Number of AWS Config rules per region 50 You can request a

in your account limit increase.
Amazon Connect Limits

Item Default limit
Amazon Connect instances per account 2
Users per instance 500
Phone numbers per instance 10
Queues per instance 50
Queues per routing profile 50
Routing profiles per instance 100
Version 1.0
202
AWS Data Pipeline Limits
Item Default limit
Hours of operation per instance 100
Quick connects per instance 100
Prompts per instance 500
Agent status per instance 50
Security profiles per instance 100
Contact flows per instance 100
Groups per level 50
Reports per instance 500
Scheduled reports per instance 50
Concurrent active calls per instance 10
These are the default limits for new Amazon Connect instances. You can create two instances per AWS
account to start, but if you need more instances it is easy to request an increase. You can also request
an increase for any of the limits using the Amazon Connect service limits increase form. You need to be
signed in to your AWS account to access the form.
AWS Data Pipeline Limits

Attribute Limit Adjustable
Number of pipelines 100 Yes
Number of objects per pipeline 100 Yes
Number of active instances per object 5 Yes
Number of fields per object 50 No
Number of UTF8 bytes per field name 256 No

or identifier
Number of UTF8 bytes per field 10,240 No
Number of UTF8 bytes per object 15,360 (including field names) No
Rate of creation of an instance from an 1 per 5 minutes No

object
Retries of a pipeline activity 5 per task No
Minimum delay between retry attempts 2 minutes No
Minimum scheduling interval 15 minutes No
Maximum number of roll-ups into a 32 No

single object
Version 1.0
203
AWS Database Migration Service Limits
Attribute Limit Adjustable
Maximum number of EC2 instances per 1 No

Ec2Resource object
For additional limits, see AWS Data Pipeline Limits in the AWS Data Pipeline Developer Guide.
AWS Database Migration Service Limits

Replication instances 20
Total amount of storage 6 TB
Replication subnet groups 20
Subnets per replication subnet group 20
Endpoints 100
Tasks 200
Endpoints per instance 20
AWS Device Farm Limits

App file size you can upload 4 GB
Number of devices that AWS Device Farm can test during a 5 This limit can be
run increased to 100
upon request.
Number of devices you can include in a test run None
Number of runs you can schedule None
Duration of a remote access session 60 minutes
AWS Direct Connect Limits

For more information about these limits, see AWS Direct Connect Limits in the AWS Direct Connect User
Guide.
Version 1.0
204
AWS Directory Service Limits
AWS Directory Service Limits

AD Connector directories 10
AWS Directory Service for Microsoft Active 10

Directory (Enterprise Edition) directories
Simple AD directories 10
Manual snapshots 5 per Microsoft AD
Manual snapshots 5 per Simple AD
For information about additional documented limits, including limits on Amazon Cloud Directory, see
AWS Directory Service Limits in the AWS Directory Service Admin Guide.
Amazon DynamoDB Limits

US East (N. Virginia) Region: 40,000 read capacity units and

40,000 write capacity units
Maximum capacity units per table or global secondary index
US East (N. Virginia) Region: 80,000 read capacity units and

Maximum capacity units per account
All other regions: 10,000 read capacity units and

Maximum capacity units per table or global secondary index
All other regions: 20,000 read capacity units and

Maximum capacity units per account
Maximum number of tables 256
For more information about these limits, see Limits in Amazon DynamoDB in the Amazon DynamoDB
Developer Guide.
AWS Elastic Beanstalk Limits

Applications 75
Application Versions 1000
Version 1.0
205
Amazon Elastic Block Store (Amazon EBS) Limits
Environments 200
Amazon Elastic Block Store (Amazon EBS) Limits

Number of EBS snapshots 10,000
Concurrent snapshots allowed for a single volume 5 for io1, gp2, magnetic; 1 for
st1, sc1
Concurrent snapshot copy requests to a single destination region 5
Total volume storage of General Purpose SSD (gp2) volumes 100 TiB
Total volume storage of Provisioned IOPS SSD (io1) volumes 100 TiB
Total volume storage of Throughput Optimized HDD (st1) 300 TiB
Total volume storage of Cold HDD (sc1) 300 TiB
Total volume storage of Magnetic volumes (standard) 20 TiB
Total provisioned IOPS 200,000
For more information about these limits, see Amazon EC2 Service Limits in the Amazon EC2 User Guide
for Linux Instances.

Limits
Elastic IP addresses for EC2-Classic 5
Security groups for EC2-Classic per instance 500
Rules per security group for EC2-Classic 100
Key pairs 5,000
Throttle on the emails that can be sent from your Amazon EC2 Throttle applied
account
On-Demand Instances Limits vary depending on

instance type. For more
information, see How many
instances can I run in Amazon
EC2.
Version 1.0
206
Amazon Elastic Container Registry (Amazon ECR) Limits
Spot Instances Limits vary depending on

instance type, region, and
account. For more information,
see Spot Instance Limits.
Reserved Instances 20 Reserved Instances per

Availability Zone, per month,
plus 20 regional Reserved
Instances. For more information,
see Reserved Instance Limits.
Dedicated Hosts Up to two Dedicated Hosts per

instance family, per region can
be allocated.
AMI Copies Destination regions are limited

to 50 concurrent AMI copies at
a time, with no more than 25
of those coming from a single
source region.
Launch Templates 1,000 launch templates per

region and 10,000 versions per
launch template.
For information about related limits for EC2-VPC, see Amazon Virtual Private Cloud (Amazon VPC)
Limits (p. 244).
For information about viewing your current limits, see Amazon EC2 Service Limits in the Amazon EC2
User Guide for Linux Instances.

Limits
Maximum number of repositories per account 1,000
Maximum number of images per repository 1,000
For information about additional documented limits, see Amazon ECR Service Limits in the Amazon
Elastic Container Registry User Guide.
Version 1.0
207
Amazon Elastic Container Service (Amazon ECS) Limits
Amazon Elastic Container Service (Amazon ECS)

Limits
Number of clusters per region per account 1000
Number of container instances per cluster 1000
Number of services per cluster 500
Number of tasks using the EC2 launch type per 1000

service (the desired count)
Number of tasks using the Fargate launch type, 20

per region, per account
Number of public IP addresses for tasks using the 20

Fargate launch type
For information about additional documented limits, see Amazon ECS Service Limits in the Amazon
Elastic Container Service Developer Guide.
Amazon Elastic File System Limits

Following are the limits for Amazon EFS that can be increased by contacting AWS Support.
Total throughput per file system for all connected US East (Ohio) Region – 3 GB/s
clients
US East (N. Virginia) Region – 3 GB/s
US West (N. California) Region – 1 GB/s
US West (Oregon) Region – 3 GB/s
EU (Frankfurt) Region – 1 GB/s
EU (Ireland) Region – 3 GB/s
Asia Pacific (Sydney) Region – 3 GB/s
For more information about these limits, see Amazon EFS Limits in the Amazon Elastic File System User
Guide.
Elastic Load Balancing Limits

Elastic Load Balancing supports three types of load balancers: Application Load Balancers, Network Load
Balancers, and Classic Load Balancers.
Version 1.0
208
Elastic Load Balancing Limits
Application Load Balancers
Load balancers per region 20 †
Target groups per region 3000
Listeners per load balancer 50
Targets per load balancer 1000
Subnets per Availability Zone per load balancer 1
Security groups per load balancer 5
Rules per load balancer (not counting default rules) 100
Certificates per load balancer (not counting default certificates) 25
Number of times a target can be registered per load balancer 100
Load balancers per target group 1
Targets per target group 1000
† This limit includes both your Application Load Balancers and your Classic Load Balancers. This limit can
be increased upon request.
Network Load Balancers
Network Load Balancers per region 20
Target groups per region 3000 *
Targets per load balancer per Availability Zone 200
Load balancers per target group 1
* This limit is shared by target groups for your Application Load Balancers and Network Load Balancers.
Classic Load Balancers
Load balancers per region 20 †
Security groups per load balancer 5
Version 1.0
209
Amazon Elastic Transcoder Limits
† This limit includes both your Application Load Balancers and your Classic Load Balancers. This limit can
be increased upon request.
Amazon Elastic Transcoder Limits

Pipelines per region 4
User-defined presets 50
Maximum number of jobs processed US East (N. Virginia) Region – 20

simultaneously by each pipeline
US West (N. California) Region – 12
US West (Oregon) Region – 20
Asia Pacific (Mumbai) Region – 12
Asia Pacific (Singapore) Region – 12
Asia Pacific (Sydney) Region – 12
Asia Pacific (Tokyo) Region – 12
EU (Ireland) Region – 20
It may take up to two weeks to process requests for a limit increase.
For more information about these limits, see Amazon Elastic Transcoder limits in the Amazon Elastic
Transcoder Developer Guide.
Amazon ElastiCache Limits

For information on ElastiCache terminology, see ElastiCache Components and Features.
Resource Default Limit Description
Nodes per region 100 The maximum number of nodes

across all clusters in a region.
This limit applies to both your
reserved and nonreserved nodes
within the given region. You can
have up to 100 reserved nodes
and 100 nonreserved nodes in
the same region.
Nodes per cluster (Memcached) 20 The maximum number of nodes

in an individual Memcached
cluster.
Nodes per shard (Redis) 6 The maximum number of nodes

in an individual Redis shard
(node group). One node is the
Version 1.0
210
Amazon Elasticsearch Service Limits
Resource Default Limit Description

read/write Primary. All other
nodes are read-only Replicas.
Shards per Cluster 1 The maximum number of shards

(Redis cluster mode disabled) (node groups) in a Redis (cluster
mode disabled) cluster.
Shards per Cluster 15 The maximum number of shards

(Redis cluster mode enabled) (node groups) in a Redis (cluster
mode enabled) cluster.
Parameter groups per region 20 The maximum number of

parameters groups you can
create in a region.
Security groups per region 50 The maximum number of

security groups you can create in
a region.
Subnet groups per region 50 The maximum number of subnet

groups you can create in a
region.
Subnets per subnet group 20 The maximum number of

subnets you can define for a
subnet group.
These limits are global limits per customer account. To exceed these limits, make your request using the
ElastiCache Node request form.
Amazon Elasticsearch Service Limits

Number of Amazon ES instances per cluster 20 (except for T2 instance types, which have a
maximum of 10).
Note
The default limit is 20 instances per
domain. To request an increase up to 100
instances per domain, create a case with
the AWS Support Center.
Amazon GameLift Limits

Aliases 20
Fleets 20
Builds 1000
Version 1.0
211
Amazon Glacier Limits
Total size of builds 100 GB
Log upload size per game session 200 MB
On-demand instances Per instance type: limits vary.
Per account: 20 instances max, regardless of

instance type.
For more information, see Scaling Amazon Elastic

Compute Cloud (Amazon EC2) Instances for
Amazon GameLift.
Server processes per instance GameLift SDK v2.x: 1
GameLift SDK v3.x and up: 50
Player sessions per game session 200
Matchmakers per account 100
VPC peering connections For limits on active and pending VPC peering
connections, see Amazon Virtual Private Cloud
(Amazon VPC) Limits (p. 244).
The expiry time for an Amazon GameLift VPC

peering authorization is 24 hours.
Amazon Glacier Limits

Number of vaults per account 1000
Number of provisioned capacity units 2
AWS Glue Limits

Number of databases per account 100
Number of tables per database 1000
Number of partitions per table 20,000
Number of crawlers per account 25
Number of jobs per account 25
Number of triggers per account 25
Number of concurrent job runs per account 30
Version 1.0
212
AWS Greengrass Limits
Number of concurrent job runs per job 3
Number of jobs per trigger 10
Number of development endpoints per account 2
Maximum DPUs used by a development endpoint at one time 5
Maximum DPUs used by a role at one time 100
AWS Greengrass Limits

AWS Greengrass Cloud API Limits
Description Limit
Maximum number of AWS IoT devices in a group. 200
Maximum number of Lambda functions in a 200

group.
Maximum number of resources per Lambda 10

function.
Maximum number of resources per group. 50
Maximum number of transactions per second 30

(TPS) on the AWS Greengrass API.
Maximum number of subscriptions per AWS 1000

Greengrass group.
Maximum number of subscriptions that specify 50

Cloud as the source per AWS Greengrass group.
Maximum length of a Core thing name. 124 bytes of UTF-8 encoded characters.
AWS Greengrass core Limits

Description Limit
Maximum number of routing table entries that 50 (matches AWS IoT subscription limit)
specify "Cloud" as the source.
Maximum size of messages sent by an AWS IoT 128 KB (matches AWS IoT message size limit)
device.
Maximum message queue size in the Greengrass 2.5 MB

core router.
Maximum length of a topic string 256 bytes of UTF-8 encoded characters.
Version 1.0
213
Amazon GuardDuty Limits
Description Limit
Maximum number of forward slashes '/' in a topic 7

or topic filter.
Minimum disk space needed to run the Greengrass 128 MB

core software
Minimum RAM to run the Greengrass core 128 MB

software
Automatic IP detection should not be used when: • IP address changes are frequent.
• Interruption of the Greengrass core service is
unacceptable.
• The Greengrass core is multi-homed or
Greengrass devices cannot reliably determine
which IP address to use.
• Reporting of Greengrass core IP addresses to
the cloud may raise security concerns.
The Greengrass core software provides a service to automatically detect the IP address(es) of your
Greengrass core devices. It sends this information to the AWS Greengrass cloud service and allows AWS
IoT devices to download the IP address of the Greengrass core they need to connect to. This feature
should not be used in the following circumstances:
• The IP address of a Greengrass core device changes frequently.

• The Greengrass core device must always be available to AWS IoT devices in it's group.
• The Greengrass core has multiple IP addresses and an AWS IoT device is unable to reliably determine
which address to use.
• Sending IP addresses to the cloud raises security concerns.
Amazon GuardDuty Limits

Detectors 1
Trusted IP sets 1
Threat intel sets 6
GuardDuty member accounts 1000
GuardDuty finding retention time 90 days
For more information, see the Amazon GuardDuty User Guide.
Version 1.0
214
AWS Identity and Access Management (IAM) Limits
AWS Identity and Access Management (IAM) Limits

Customer managed policies in an AWS account 1500
Groups in an AWS account 300
Roles in an AWS account 1000
Users in an AWS account 5000 (If you need to add a large number of users,
consider using temporary security credentials.)
Virtual MFA devices (assigned or unassigned) in an Equal to the user quota for the account
AWS account
Instance profiles in an AWS account 1000
Server certificates stored in an AWS account 20
For more information about these limits, see Limitations on IAM Entities and Objects in the IAM User
Guide.
AWS Import/Export Limits

AWS Snowball (Snowball)
Resource Default Comments

Limit
Snowball 1 To increase this limit, contact AWS Support.
Amazon Inspector Limits

Running agents 500
Assessment runs 50,000
Assessment templates 500
Assessment targets 50
For more information, see the Amazon Inspector User Guide.
Version 1.0
215
AWS IoT Limits
AWS IoT Limits

Thing Limits
Resource Limit
Thing name size 128 bytes of UTF-8 encoded characters. This limit
applies for both the thing registry and Thing
Shadow services.
Maximum number of thing attributes for a thing 50

with a thing type
Maximum number of thing attribute for a thing 3

without a thing type
Number of thing types that can be associated with 1

a thing
Maximum number of thing types in an AWS Unlimited

account
Message Broker Limits

Resource Description Limit Adjustable
Maximum concurrent The maximum 500,000 Yes

client connections per number of concurrent
account connections allowed
per account.
Connect requests per AWS IoT limits an 500 Yes

second per account account to a maximum
number of MQTT
CONNECT requests per
second.
Connect requests per AWS IoT limits MQTT 1 No

second per client ID CONNECT requests from
the same accountId
and clientId to
1 MQTT CONNECT
operation per second.
Subscriptions per AWS IoT limits an 500,000 Yes

account account to a maximum
number of subscriptions
across all active
connections.
Subscriptions per AWS IoT limits 500 Yes

second per account an account to a
maximum number
of subscriptions per
Version 1.0
216

second. For example,
if there are two MQTT
SUBSCRIBE requests
within a second with
3 subscriptions (topic
filters) each, AWS
IoT counts those as 6
subscriptions towards
this limit.
Subscriptions per AWS IoT supports 50 No

connection 50 subscriptions
per connection.
Subscription requests
on the same connection
in excess of this amount
may be rejected by AWS
IoT and the connection
will be closed. Clients
should validate the
SUBACK message
to ensure that their
subscription requests
have been successfully
processed.
Publish requests per AWS IoT limits each 100 No

second per connection client connection to a
maximum number of
inbound and outbound
publish requests
per second. Publish
requests exceeding that
limit will be discarded.
Version 1.0
217
Inbound publish Inbound publish 10,000 Yes

requests per second per requests count for all
account the messages that AWS
IoT processes before
routing the messages
to the subscribed
clients or the rules
engine. For example,
a single message
published on $aws/
things/device/
shadow/update topic
can result in publishing
three additional
messages to $aws/
things/device/
shadow/update/
accepted, $aws/
things/device/
shadow/update/
documents, and $aws/
things/device/
shadow/delta topics.
In this case, AWS
IoT counts those as
4 inbound publish
requests towards
this limit. However, a
single message to an
unreserved topic like a/
b is counted only as a
single inbound publish
request.
Outbound publish Outbound publish 20,000 Yes

requests per second per requests count for
account every message that
resulted in matching
a client's subscription
or matching a rules
engine subscription. For
example, two clients
are subscribed to topic
filter a/b and a rule
is subscribed to topic
filter a/#. An inbound
publish requests on
topic a/b results in a
total of 3 outbound
publish requests.
Version 1.0
218
Protocol Limits
Throughput per second Data received or sent 512 KiB No

per connection over a client connection
is processed at a
maximum throughput
rate. Data exceeding
the maximum
throughput will be
delayed in processing.
Maximum inbound AWS IoT limits 100 No

unacknowledged QoS 1 the number of
publish requests unacknowledged
inbound publish
requests per client.
When this limit is
reached, no new
publish requests are
accepted from this
client until a PUBACK
message is returned by
the server.
Maximum outbound AWS IoT limits 100 No

unacknowledged QoS the number of
1publish requests unacknowledged
outbound publish
requests per client.
When this limit is
reached, no new
publish requests are
sent to the client until
the client acknowledges
the publish requests.
Maximum retry interval AWS IoT will 1 hour No

for delivering QoS 1 retry delivery of
messages unacknowledged
quality-of-service
1 (QoS 1) publish
requests to a client for
up to one hour. If AWS
IoT does not receive a
PUBACK message from
the client after one
hour, it will drop the
publish requests.
Protocol Limits
Resource Description
Connection inactivity (keep-alive interval) For MQTT (or MQTT over WebSockets)
connections, a client can request a keep-alive
Version 1.0
219
Device Shadow Limits
Resource Description
interval between 30 - 1200 seconds as part of
the MQTT CONNECT message. AWS IoT starts
the keep-alive timer for a client when sending
CONNACK in response to the CONNECT message.
This timer is reset whenever AWS IoT receives a
PUBLISH, SUBSCRIBE, PING, or PUBACK message
from the client. AWS IoT will disconnect a client
whose keep-alive timer has reached 1.5x the
specified keep-alive interval (i.e., by a factor
of 1.5).The default keep-alive interval is 1200
seconds. If a client requests a keep-alive interval
of zero, the default keep-alive interval will be
used. If a client requests a keep-alive interval
greater than 1200 seconds, the default keep-alive
interval will be used. If a client requests a keep-
alive interval shorter than 30 seconds but greater
than zero, the server treats the client as though it
requested a keep-alive interval of 30 seconds.
WebSocket connection duration WebSocket connections are limited to 24 hours. If

the limit is exceeded, the WebSocket connection is
automatically closed when an attempt is made to
send a message by the client or server.
Maximum subscriptions per subscribe request A single SUBSCRIBE request is limited a maximum
of eight subscriptions.
Message size The payload for every publish request is limited to

128 KB. The AWS IoT service rejects publish and
connect requests larger than this size.
Client ID size 128 bytes of UTF-8 encoded characters.
Restricted client ID prefix $ is reserved for AWS IoT generated client IDs.
Topic size The topic passed to the AWS IoT when sending a
publish request is limited to 256 bytes of UTF-8
encoded characters.
Restricted topic prefix Topics beginning with $ are reserved by AWS

IoT and are not supported for publishing and
subscribing except for using the specific topic
names defined by AWS IoT services (i.e., Thing
Shadow).
Maximum number of slashes in topic and topic A topic in a publish or subscribe request is limited
filter to 7 forward slashes (/).
Device Shadow Limits
Maximum depth of JSON device state documents The maximum number of levels in the desired
or reported section of the JSON device state
document is 5. For example:
Version 1.0
220
Security and Identity Limits
"desired": {
"one": {
"two": {
"three": {
"four": {
"five":{
}
}
}
}
}
}
Maximum number of in-flight, unacknowledged The Thing Shadows service supports up to 10 in-
messages per thing flight unacknowledged messages per thing. When
this limit is reached, all new shadow requests are
rejected with a 429 error code.
Maximum number of JSON objects per AWS There is no limit on the number of JSON objects
account per AWS account.
Maximum size of a JSON state document 8 KB.
Maximum size of a thing name 128 bytes of UTF-8 encoded characters.
Shadow lifetime A thing shadow is deleted by AWS IoT up to six

months after the creating account is deleted or
per customer request. For operational purposes,
AWS IoT service backups are kept for 6 months
Maximum number of shadows in an AWS account Unlimited
Requests per second per thing The Thing Shadows service supports up to 20
requests per second per thing. Note that this limit
is per thing and not per API.
Security and Identity Limits
Maximum number of CA certificates with the 10

same subject field allowed per AWS account per
region
Maximum number of policies that can be attached 10

to a certificate or Amazon Cognito identity
Maximum number of named policy versions 5
Maximum policy document size 2048 characters (excluding white space)
Maximum number of device certificates that can 15

be registered per second
Version 1.0
221
Throttling Limits
Throttling Limits
API Transaction per Second
AcceptCertificateTransfer 10
AttachPrincipalPolicy 15
AttachThingPrincipal 15
CancelCertificateTransfer 10
CreateCertificateFromCsr 15
CreatePolicy 10
CreatePolicyVersion 10
CreateThing 15
CreateThingType 15
DeleteCertificate 10
DeleteCACertificate 10
DeletePolicy 10
DeletePolicyVersion 10
DeleteThing 15
DeleteThingType 15
DeprecateThingType 15
DescribeCertificate 10
DescribeCACertificate 10
DescribeThing 10
DescribeThingType 10
DetachThingPrincipal 15
DetachPrincipalPolicy 15
DeleteRegistrationCode 10
GetPolicy 10
GetPolicyVersion 15
GetRegistrationCode 10
ListCACertificates 10
ListCertificates 10
ListCertificatesByCA 10
Version 1.0
222
AWS IoT Rules Engine Limits
API Transaction per Second
ListOutgoingCertificates 10
ListPolicies 10
ListPolicyPrincipals 10
ListPolicyVersions 10
ListPrincipalPolicies 15
ListPrincipalThings 10
ListThings 10
ListThingPrincipals 10
ListThingTypes 10
RegisterCertificate 10
RegisterCACertificate 10
RejectCertificateTransfer 10
SetDefaultPolicyVersion 10
TransferCertificate 10
UpdateCertificate 10
UpdateCACertificate 10
UpdateThing 10
AWS IoT Rules Engine Limits
Maximum number of rules per AWS account 1000
Actions per rule A maximum of 10 actions can be defined per rule.
Rule size Up to 256 KB of UTF-8 encoded characters

(including white space).
AWS IoT Job Limits
Resource Min Max Note
JobId 1 character 64 characters The JobId length

must not exceed 64
characters.
Document N/A 32768 bytes The maximum size of

a document that can
Version 1.0
223
AWS IoT Job Limits

be sent to an AWS IoT
device is 32 KB.
DocumentSource N/A 1350 characters The maximum job

document source size is
1350 characters.
Description N/A 2028 characters The maximum job

description size is 2028
characters.
Targets 1 100 The number of targets a

job can have.
ExpiresInSec 60 seconds 3600 seconds The lifetime of pre-

signed URLs must be
configured greater than
60 seconds and less
than 1 hour.
Comment N/A 2028 characters The maximum

comment size is 2028
characters.
MaxResults 1 250 The maximum list result

per page is 250.
1
MaximumJobExecutionsPerMinute 1000 Configures the rollout
speed for a job.
Active snapshot jobs 0 100 The maximum number

of active snapshot jobs
is 100 (irrespective of
the number of active
continuous jobs).
Active continuous jobs 0 100 The maximum number

of active continuous
jobs is 100 (irrespective
of the number of active
snapshot jobs).
Job document variable 0 10 Up to 10 variables

substitution substitutions, including
the presign URL,
are allowed in a job
document.
Data retention N/A 90 days Job data and job

execution data will be
purged after 90 days.
StatusDetail map 1 character 128 characters

key size
StatusDetail map 1 character 128 characters

value size
Version 1.0
224
AWS IoT Bulk Thing Registration Limits
Job management APIs N/A 30 TPS The AWS IoT Job

Management and
Control APIs have
a maximum of 30
transactions per second
(TPS).
Job messaging APIs N/A 200 MPS The AWS IoT Jobs
Device MQTT and
HTTPS APIs have a
maximum of 200
messages per second
(MPS).
AWS IoT Bulk Thing Registration Limits

Resource Limit Note
Registration task termination 30 days Any pending/uncompleted bulk

registration tasks are terminated
after 30 days.
Data retention policy 30 days Once the associated bulk

registration task has completed
(which can be long lived), bulk
Thing registration related data
is permanently deleted after 30
days.
Allowed registration tasks 1 For any given AWS account, only

one bulk registration task can
run at a time.
Maximum line length 256K Each line in an Amazon S3 input

JSON file cannot exceed 256K in
length.
AWS Key Management Service (AWS KMS) Limits

Customer Master Keys (CMKs) 1000
Aliases 1100
Grants per CMK 2500
Grants for a given principal per CMK 500
Requests per second Varies by API operation; see Limits in the AWS Key
Management Service Developer Guide.
Version 1.0
225
Amazon Kinesis Data Firehose Limits
All limits in the preceding table apply per region and per AWS account.
For more information about these limits, see Limits in the AWS Key Management Service Developer Guide.
Amazon Kinesis Data Firehose Limits

Delivery streams per region 50
Delivery stream capacity for US East (N. Virginia), US West (Oregon), 2,000 transactions/second
and EU (Ireland) †
5,000 records/second
5 MB/second
Delivery stream capacity for other Regions where Kinesis Data 1,000 transactions/second
Firehose is available †
1,000 records/second
1 MB/second
† The three capacity limits scale proportionally. For example, if you increase the throughput limit to 2
MB/second in Asia Pacific (Singapore), the other limits increase to 2,000 transactions/second and 2,000
records/second.
For more information about these limits, see Amazon Kinesis Data Firehose Limits in the Amazon Kinesis
Data Firehose Developer Guide.
Amazon Kinesis Data Streams Limits

Shards per region US East (N. Virginia) Region – 500
All other supported regions – 200
For more information about these limits, see Amazon Kinesis Data Streams Limits in the Amazon Kinesis
Data Streams Developer Guide.
Amazon Kinesis Data Analytics Limits

Kinesis Processing Units (KPUs) US East (N. Virginia) Region – 8
Version 1.0
226
Amazon Kinesis Video Streams Limits

Input Parallelism 64 input streams
Applications 50
For more information about these limits, see Limits in the Amazon Kinesis Data Analytics Developer Guide.
Amazon Kinesis Video Streams Limits

The limits below are either soft [s], which can be upgraded by submitting a support ticket, or hard [h],
which cannot be increased.
Control Plane API limits

The following section describes limits for control-plane APIs.
When an account-level Request limit is reached, a ClientLimitExceededException is thrown.
When an account-level Streams limit is reached, or a stream-level limit is reached, a

StreamLimitExceededException is thrown.
Control Plane API limits
API Account Limit: Account Limit: Stream-level Relevant Exceptions and Notes
Request Streams limit
CreateStream 50 TPS [s] 100 streams 5 TPS [h] Devices, CLIs, SDK-driven access
per account [s] and the console can all invoke
this API. Only one API call
succeeds if the stream doesn’t
already exist.
DescribeStream 300 TPS [h] N/A 5 TPS [h]
UpdateStream 50 TPS [h] N/A 5 TPS [h]
ListStreams 300 TPS [h] N/A 5 TPS [h]
DeleteStream 50 TPS [h] N/A 5 TPS [h]
GetDataEndpoint300 TPS [h] N/A 5 TPS [h] When combined with account
limit, this implies a maximum
of 60 streams can be Put to and
Read from (with 4 consumers).
Data Plane API limits

The following section describes limits for control-plane APIs.
When a stream-level limit is exceeded, a StreamLimitExceededException is thrown.
Version 1.0
227
When a connection-level limit is reached, a ConnectionLimitExceededException is thrown.
The following errors or acks are thrown when a fragment-level limit is reached:
• A MIN_FRAGMENT_DURATION_REACHED ack is returned for a fragment below the minumum duration.

• A MAX_FRAGMENT_DURATION_REACHED ack is returned for a fragment above the maximum duration.
• A MAX_FRAGMENT_SIZE ack is returned for a fragment above the maximum data size.
• A FragmentLimitExceeded exception is thrown if a fragment limit is reached in a
GetMediaForFragmentList operation.
API Stream- Connection- Bandwidth Fragment- Relevant Exceptions and

level limit level limit limit level limit Notes
PutMedia 5 TPS [h] 1 [s] 12.5 MB/ • Minimum A typical PutMedia request
second, or fragment will contain data for several
100 Mbps [s] duration: seconds, resulting in a
1 second lower TPS per stream.
[h] In the case of multiple
• Maximum concurrent connections
fragment that exceed limits, the last
duration: connection is accepted.
10
seconds
[h]
• Maximum
fragment
size: 50
MB [h]
GetMedia 5 TPS [h] 3 [s] 25 MB/s or N/A Only three clients can
200 Mbps [s] concurrently receive
content from the media
stream at any moment
of time. Further client
connections are rejected.
A unique consuming client
shouldn’t need more
than 2 or 3 TPS, since
once the connection is
established, we anticipate
that the application will
read continuously.
If a typical fragment is
approximately 5 MB, this
limit will mean ~75 MB/ sec
per Kinesis video stream.
Such a stream would have
an outgoing bit rate of 2x
the streams' maximum
incoming bit rate.
ListFragments 5 TPS [h] 5 [s] N/A N/A Five fragment-based

consuming applications can
Version 1.0
228
AWS Lambda Limits
API Stream- Connection- Bandwidth Fragment- Relevant Exceptions and

level limit level limit limit level limit Notes
concurrently list fragments
based on processing
requirements.
GetMediaForFragmentList
5 TPS [h] 5 [s] 25 MB/s or Maximum Five fragment-based
200 Mbps [s] number of consuming applications can
fragments: concurrently get media.
1000 [h] Further connections are
rejected.
AWS Lambda Limits

Resource Limit
Concurrent executions 1000
For more information about these limits, see AWS Lambda Limits in the AWS Lambda Developer Guide.
AWS Lambda dynamically scales capacity in response to increased traffic, subject to your account's
concurrent execution limit. For more information, see Managing Concurrency. To handle a burst in traffic,
Lambda immediately increases your concurrently executing functions by a predetermined amount,
dependent on which region it's executed (see table below).
If the default Immediate Concurrency Increase value, as noted in the table below, is not sufficient
to accommodate the traffic surge, Lambda continues to increase the number of concurrent function
executions by 500 per minute until your account safety limit has been reached or the number of
concurrently executing functions is sufficient to successfully process the increased load.
Region Immediate Concurrency Increase

(function executions)
Asia Pacific (Tokyo) 1000
Asia Pacific (Seoul) 500
Asia Pacific (Mumbai) 500
Asia Pacific (Singapore) 500
Asia Pacific (Sydney) 500
Canada (Central) 500
EU (Frankfurt) 1000
EU (London) 500
EU (Ireland) 3000
EU (Paris) 500
US East (Ohio) 500
Version 1.0
229
Amazon Lightsail Limits
Region Immediate Concurrency Increase

(function executions)
US West (N. California) 500
US West (Oregon) 3000
US East (N. Virginia) 3000
South America (São Paulo) 500
China (Beijing) 500
AWS GovCloud (US) 500
Amazon Lightsail Limits

Resource Default Limit Comment
Number of instances 20 per account This limit cannot be increased.
Number of Elastic IP addresses 5 per account This limit cannot be increased.
Number of parallel SSH connections 3 x the number of This limit cannot be increased.
instances in the
account
Number of hosted zones 3 per account This limit cannot be increased.
Amazon Machine Learning (Amazon ML) Limits

Data file size* 100 GB
Batch prediction input size 1 TB
Batch prediction input (number of records) 100 million
Number of variables in a data file (schema) 1,000
Recipe complexity (number of processed output variables) 10,000
Transactions Per Second for each real-time prediction endpoint 200
Total Transactions Per Second for all real-time prediction endpoints 10,000
Total RAM for all real-time prediction endpoints 10 GB
Number of simultaneous jobs 25
Longest run time for any job 7 days
Number of classes for multiclass ML models 100
ML model size 2 GB
Version 1.0
230
AWS Elemental MediaConvert Limits
Note
The size of your data files is limited to ensure that jobs finish in a timely manner. Jobs that have
been running for more than seven days are automatically terminated, resulting in a FAILED
status.
For more information about these limits, see Amazon ML Limits in the Amazon Machine Learning
Developer Guide.
AWS Elemental MediaConvert Limits

Number of queues 10
Concurrent jobs processed across all 100

queues
Concurrent jobs processed from a 100 divided by

queue number of queues
Number of custom output presets 100
Number of custom output job 100

templates
DescribeEndpoints API calling rate per 0.01667 TPS

second (Once per 60
seconds, burst
zero)
Aggregate API calling rate per second 2 TPS (2 per

for job, queue, preset and template second, burst
100)]
AWS Elemental MediaLive Limits

Maximum inputs 5
Maximum input security groups 5
Maximum channels 5
AWS Elemental MediaPackage Limits

Maximum channels per account 10
Version 1.0
231
AWS Elemental MediaStore Limits
Maximum endpoints per channel 10
AWS Elemental MediaStore Limits

Containers 100
For information about AWS Elemental MediaStore limits, including limits that can't be increased, see
Limits in the AWS Elemental MediaStore User Guide.
AWS Elemental MediaTailor Limits

Resource Default Limit Comment
Transactions 3,000 concurrent This is an account-level limit.

transactions per
second across Your transactions per second are
all request types largely dependent on how often the
(such as manifest player requests updated manifests. For
requests and example, a player with eight second
tracking requests segments might update the manifest
for client-side every eight seconds. The player, then,
reporting). generates 0.125 transactions per
second.
For more information about AWS Elemental MediaTailor limits, including limits that can't be increased,
see Limits in the AWS Elemental MediaTailor User Guide.
Amazon MQ Limits
For information about these limits, see Amazon MQ Limits in the Amazon MQ Developer Guide.
Amazon Neptune Limits

US East (N. Virginia) Region: Maximum instances is 3.
Maximum instances
You can request an increase on this limit. For more information, see https://aws.amazon.com/support.
Version 1.0
232
AWS OpsWorks for Chef Automate and
AWS OpsWorks for Puppet Enterprise Limits
AWS OpsWorks for Chef Automate and AWS

OpsWorks for Puppet Enterprise Limits
Chef or Puppet servers 5
User-initiated (manual) backup generations 10
Automated (scheduled) backup generations 30
AWS OpsWorks Stacks Limits

Stacks 40
Layers per stack 40
Instances per stack 40
Apps per stack 40
AWS Organizations Limits

Accounts per organization Varies. Contact Customer

Support.
Invitations sent per day 20
For more information about these limits, see Limits of AWS Organizations in the AWS Organizations User
Guide.
Amazon Pinpoint Limits

Active campaigns per account 200 per account.

Note
An active campaign is
a campaign that hasn't
completed or failed.
Active campaigns have
Version 1.0
233
Amazon Polly Limits

a status of SCHEDULED,
EXECUTING, or
PENDING_NEXT_RUN.
Concurrent endpoint import jobs per account 2 per account.
Message sends per campaign activity 100 million.
Total file size per endpoint import job 1 GB per import job.
SMS account spend threshold USD$1.00 per account.
Maximum number of Amazon SNS topics for two-way SMS 100,000 per account.
Number of emails that can be sent per 24-hour period (sending 200 emails per 24-hour period
quota) for accounts in the sandbox
environment.
Number of emails that can be sent each second (sending rate) 1 email per second for accounts
in the sandbox environment.
Email recipient addresses Accounts in the sandbox

environment may only send
email to recipients whose email
addresses or domains have been
verified.
To increase any of the limits above, submit a Amazon Pinpoint Limit Increase case.
For more information about Amazon Pinpoint limits, including limits that can't be increased, see Limits in
the Amazon Pinpoint Developer Guide.
Amazon Polly Limits

• Throttle rate per IP address: 100 transactions (requests) per second (tps) with a burst limit of 120 tps.
• Throttle rate per operation:
Throttle Rate per Operation
Operation Limit
Lexicon
DeleteLexicon Any 2 transactions per second (tps) from these operations

combined.
PutLexicon
Maximum allowed burst of 4 tps.
GetLexicon
ListLexicons
Speech
DescribeVoices 80 rps with a burst limit of 100 tps
SynthesizeSpeech 80 rps with a burst limit of 100 tps
Version 1.0
234
Amazon Redshift Limits
Amazon Redshift Limits

Nodes per cluster 101
Nodes 200
Reserved Nodes 200
Snapshots 20
Parameter Groups 20
Security Groups 20
Subnet Groups 20
Subnets per Subnet Group 20
Event Subscriptions 20
For more information about these limits, see Limits in Amazon Redshift in the Amazon Redshift Cluster
Management Guide.
Amazon Rekognition Limits

Amazon Rekognition does not have service limits that you can change. For information about Amazon
Rekognition service limits, see Amazon Rekognition Limits.
Amazon Relational Database Service (Amazon

RDS) Limits
Clusters 40
Cluster parameter groups 50
DB Instances 40
Event subscriptions 20
Manual snapshots 100
Option groups 20
Parameter groups 50
Read replicas per master 5
Reserved instances (purchased per month) 40
Version 1.0
235
AWS Resource Groups Limits
Rules per security group 20
Security groups 25
Security groups (VPC) 5
Subnet groups 50
Subnets per subnet group 20
Tags per resource 50
Total storage for all DB instances 100 TB
AWS Resource Groups Limits

Resource groups per account 100
Amazon Route 53 Limits

DNS and Domain Registration
Hosted zones 500
Domains 50
Resource record sets per hosted zone 10,000
Reusable delegation sets 100
Hosted zones that can use the same reusable delegation set 100
Amazon VPCs that you can associate with a private hosted zone 100
Health checks 200
Traffic policies 50
Traffic policy records 5
Auto Naming
Namespaces per AWS account 50 per region
Instances per namespace 2,000 per region
Version 1.0
236
Amazon SageMaker Limits
Instances per service 100 per region
For more information about these limits, see Route 53 Limits in the Amazon Route 53 Developer Guide.
Amazon SageMaker Limits

The following tables group Amazon SageMaker limits by components.
Amazon SageMaker Notebooks
ml.t2.medium instances 20
ml.m4.xlarge instances 20
ml.p2.xlarge instances 1
ml.p3.2xlarge instances 1
Number of notebook instances 100
Number of running notebook instances 20
Amazon SageMaker Training
ml.m4.4xlarge instances 10
ml.m4.10xlarge instances 5
ml.c4.xlarge instances 20
ml.c4.2xlarge instances 20
Version 1.0
237
AWS Server Migration Service Limits
Longest run time for a training job 5 days
Number of instances across training jobs 20
Number of instances for a training job 20
Size of EBS volume for an instance 1 TB
Amazon SageMaker Hosting
ml.t2.medium instances 20
Number of instances across active endpoints 20
Number of instances for an endpoint 20
Total TPS for all endpoints 10,000
Maximum payload size for endpoint invocation 5 MB
AWS Server Migration Service Limits

Concurrent VM migrations 50 per account
Maximum duration of service usage per VM (not per account), 90 days

beginning with the initial replication of a VM. We terminate an
Version 1.0
238
AWS Serverless Application Repository Limits

ongoing replication after this period, unless a customer requests a
limit increase.
AWS Serverless Application Repository Limits

Limits Per Account Per Region
Public Applications 100
Free Amazon S3 Storage for Code Packages 5 GB
AWS Service Catalog Limits

Portfolios 25 per account
Users, groups, and roles 25 per portfolio
Products 25 per portfolio, 100 total per

account
Product versions 50 per product
Constraints 25 per product per portfolio
Tags 20 per product, 20 per portfolio,

50 per provisioned product
Stacks 200 (AWS CloudFormation limit)
AWS Shield Advanced Limits

offers advanced monitoring and protection for Elastic IP addresses, CloudFront distributions, Route 53
hosted zones, or Elastic Load Balancing load balancers. You can monitor and protect up to 100 of each of
these resource types per account. If you want to increase these limits, contact the AWS Support Center.
Amazon Simple Email Service (Amazon SES) Limits

The following are the default limits for Amazon SES in the sandbox environment.
Daily sending quota 200 messages per 24-hour

period.
Maximum send rate 1 email per second.
Version 1.0
239
Amazon Simple Notification Service (Amazon SNS) Limits

Note
The rate at which
Amazon SES accepts
your messages might be
less than the maximum
send rate.
Recipient address verification All recipient addresses must be

verified.
For more information about these limits, see Limits in Amazon SES in the Amazon Simple Email Service
Developer Guide.

Limits
Topics 100,000 per account
Subscriptions 12,500,000 per topic
Pending subscriptions 5,000 per account
Account spend threshold for SMS 1.00 USD per account
Delivery rate for promotional SMS messages 20 messages per second
Delivery rate for transactional SMS messages 20 messages per second
Message filter policies 100 per account
To increase any of the limits above, submit an SNS Limit Increase case.
Amazon SNS API Throttling Limits

API Transactions per Second
ListEndpointsByPlatformApplication 30
ListTopics 30
ListPlatformApplications 15
ListSubscriptions 30
ListSubscriptionsByTopic 30
Subscribe 100
Unsubscribe 100
Version 1.0
240
The Amazon SNS API throttling limits cannot be increased.

For more information about these limits, see Amazon SQS Limits in the Amazon Simple Queue Service
Developer Guide and the "Limits and Restrictions" section of the Amazon SQS FAQs.

Limits
Buckets 100 per account
For more information about these limits, see Amazon S3 limits in the Amazon Simple Storage Service
Developer Guide.

Limits
For more information about these limits, see Amazon SWF Limits in the Amazon Simple Workflow Service
Developer Guide.
Amazon SimpleDB Limits

Domains 250
For more information about these limits, see Amazon SimpleDB Limits in the Amazon SimpleDB
Developer Guide.
AWS Step Functions Limits

For more information about these limits, see AWS Step Functions Limits in the AWS Step Functions
Developer Guide.
AWS Storage Gateway Limits

For more information about these limits, see AWS Storage Gateway Limits in the AWS Storage Gateway
User Guide.
Version 1.0
241
AWS Systems Manager Limits

Concurrently executing 25
Automations
Each AWS account can execute a maximum of 25 Automations at one
time. Concurrent executions greater than 25 are automatically added to
an execution queue.
Additional Automation 75
executions that can be
queued
Maximum duration an 12 hours

Automation execution can
run when running in the If you expect an Automation to run longer than 12 hours, then you must
context of a user execute the Automation by using a service role (or assume role).
Run Command execution 30 days

history retention
The history of each command is available for up to 30 days. In addition,
you can store a copy of all log files in Amazon Simple Storage Service or
have an audit trail of all API calls in AWS CloudTrail.
On-premises managed Each AWS account can activate a maximum of 1,000 on-premises
instances registered instances in a region for use with Systems Manager.
through Amazon EC2
activation For more information about activating on-premises instances for use in
your hybrid environment, see Create a Managed-Instance Activation in the
AWS Systems Manager User Guide.
Note
Activation limits apply only to the on-premises instances you add
to your hybrid environment, and not to registered Amazon EC2
instances.
Systems Manager 200

documents
Each AWS account can create a maximum of 200 documents per region.
Privately shared Systems 1000

Manager document
A single Systems Manager document can be shared with a maximum of
1000 AWS accounts.
Publicly shared Systems 5

Manager document
Each AWS account can publicly share a maximum of five documents.
State Manager 10,000

associations
Each Systems Manager document can be associated with a maximum of
10,000 instances.
State Manager association 1,000

versions
You can created a maximum of 1,000 versions of a State Manager
association.
Version 1.0
242
Inventory data collected 1 MB

per instance per call
This maximum adequately supports most inventory collection scenarios.
When this limit is reached, no new inventory data is collected for the
instance. Inventory data previously collected is stored until the expiration.
Inventory data collected 5 MB

per instance per day
When this limit is reached, no new inventory data is collected for the
instance. Inventory data previously collected is stored until the expiration.
Custom Inventory Types 20
You can add up to 20 custom inventory types.
Custom Inventory Type 200 KB

Size
This is the maximum size of the type, not the inventory collected.
Custom Inventory Type 50

Attributes
This is the maximum number of attributes within the custom inventory
type.
Inventory data expiration 30 days
If you terminate an instance, inventory data for that instance is deleted

immediately. For running instances, inventory data older than 30 days
is deleted. If you need to store inventory data longer than 30 days, you
can use AWS Config to record history or periodically query and upload
the data to an Amazon S3 bucket. For more information, see, Recording
Amazon EC2 managed instance inventory in the AWS Config Developer
Guide.
Maintenance Windows 50
per account
Tasks per Maintenance 20

Window
Targets per Maintenance 50

Window
Instance IDs per target 50
Targets per task 10
Concurrent executions 1
of a single Maintenance
Window
Concurrent executions of 5
Maintenance Windows
Maintenance Window 30 days

execution history
retention
Version 1.0
243
Amazon Virtual Private Cloud (Amazon VPC) Limits
Maximum number of 10,000

parameters per account
Max size for parameter 4096 characters

value
Max history for a 100 past values

parameter
Patch baselines per 25

account
Patch groups per patch 25

baseline

Unless otherwise noted, submit a request to increase these limits.

limit
VPCs per region 5 Increasing this limit increases the limit

on Internet gateways per region by the
same amount. The multiple of the number
of VPCs in the region and the number of
security groups per VPC cannot exceed
5000.
Subnets per VPC 200 -
IPv4 CIDR blocks per VPC 5 This limit is made up of the primary CIDR
block plus 4 secondary CIDR blocks.
IPv6 CIDR blocks per VPC 1 This limit cannot be increased.
Internet gateways per region 5 This limit is directly correlated with the
limit on VPCs per region. To increase this
limit, increase the limit on VPCs per region.
Only one Internet gateway can be attached
to a VPC at a time.
Egress-only Internet gateways per region 5 This limit is directly correlated with the
limit on VPCs per region. To increase this
limit, increase the limit on VPCs per region.
Only one egress-only Internet gateway can
be attached to a VPC at a time.
Virtual private gateways per region 5 Only one virtual private gateway can be
attached to a VPC at a time.
Customer gateways per region 50 To increase this limit, contact AWS Support.
VPN connections per region 50 -
Version 1.0
244

limit
VPN connections per VPC (per virtual private 10 -

gateway)
Route tables per VPC 200 This limit includes the main route table.
Routes per route table (non-propagated 50 You can increase this limit up to a
routes) maximum of 100; however, network
performance may be impacted. This limit
is enforced separately for IPv4 routes and
IPv6 routes (50 each, and a maximum of
100 each).
BGP advertised routes per route table 100 This limit cannot be increased. If you
(propagated routes) require more than 100 prefixes, advertise a
default route.
Elastic IP addresses per region for EC2-VPC 5 This is the limit for the number of Elastic
IP addresses for use in EC2-VPC. For Elastic
IP addresses for EC2-Classic, see Amazon
Elastic Compute Cloud (Amazon EC2)
Limits (p. 206).
Security groups per VPC 500 The multiple of the number of VPCs in the
region and the number of security groups
per VPC cannot exceed 5000.
Inbound or outbound rules per security 50 You can have 50 inbound and 50 outbound
group rules per security group (giving a total of
100 rules). To change this limit, contact
AWS Support — a limit change applies
to both inbound and outbound rules.
The multiple of the limit for inbound or
outbound rules per security group and
the limit for security groups per network
interface cannot exceed 250. For example,
if you increase the limit to 100, we decrease
your number of security groups per
network interface to 2.
This limit is enforced separately for IPv4

rules and IPv6 rules. A rule that references
a security group counts as one rule for IPv4
and one rule for IPv6.
Security groups per network interface 5 To increase or decrease this limit, contact
AWS Support. The maximum is 16. The
multiple of the limit for security groups per
network interface and the limit for rules
per security group cannot exceed 250. For
example, if you increase the limit to 10, we
decrease your number of rules per security
group to 25.
Version 1.0
245

limit
Network interfaces per instance - This limit varies by instance type. For more
information, see IP Addresses Per ENI Per
Instance Type.
Network interfaces per region 350 This limit is the greater of either the default
limit (350) or your On-Demand Instance
limit multiplied by 5. The default limit for
On-Demand Instances is 20. If your On-
Demand Instance limit is below 70, the
default limit of 350 applies. To increase this
limit, submit a request or increase your On-
Demand Instance limit.
Network ACLs per VPC 200 You can associate one network ACL to
one or more subnets in a VPC. This limit is
not the same as the number of rules per
network ACL.
Rules per network ACL 20 This is the one-way limit for a single
network ACL, where the limit for ingress
rules is 20, and the limit for egress rules is
20. This limit includes both IPv4 and IPv6
rules, and includes the default deny rules
(rule number 32767 for IPv4 and 32768 for
IPv6, or an asterisk * in the Amazon VPC
console).
This limit can be increased up to a

maximum if 40; however, network
performance may be impacted.
Active VPC peering connections per VPC 50 The maximum limit is 125 peering
connections per VPC. The number of
entries per route table should be increased
accordingly; however, network performance
may be impacted.
Outstanding VPC peering connection 25 This is the limit for the number of
requests outstanding VPC peering connection
requests that you've requested from your
account. To increase this limit, contact AWS
Support.
Expiry time for an unaccepted VPC peering 1 week To increase this limit, contact AWS Support.
connection request (168
hours)
VPC endpoints per region 20 You can have 20 interface endpoints and
20 gateway endpoints. The maximum limit
for gateway endpoints is 255 endpoints per
VPC, regardless of your endpoint limit per
region.
Version 1.0
246
Amazon VPC DNS Limits

limit
Flow logs per single network interface, 2 This limit cannot be increased. You can
single subnet, or single VPC in a region effectively have 6 flow logs per network
interface if you create 2 flow logs for the
subnet, and 2 flow logs for the VPC in
which your network interface resides.
NAT gateways per Availability Zone 5 A NAT gateway in the pending, active, or
deleting state counts against your limit.
For more information about these limits, see Amazon VPC Limits in the Amazon VPC User Guide.
Amazon VPC DNS Limits

For more information about these limits, see DNS Limits in the Amazon VPC User Guide.
AWS WAF Limits

AWS WAF has default limits on the number of entities per account. You can request an increase in these
limits.
Web ACLs per AWS account 50
Rules per AWS account 100
Conditions per AWS account 100 of each

condition type
(For example: 100
Size constraint
conditions, 100 IP
match conditions,
etc.)
Requests per Second 10,000 per web

ACL*
*This limit applies only to AWS WAF on an Application Load Balancer. Requests per Second (RPS) limits
for AWS WAF on CloudFront are the same as the RPS limits support by CloudFront described in the
CloudFront developer guide.
The following limits on AWS WAF entities can't be changed.
Resource Limit
Rules per web ACL 10
Conditions per rule 10
Version 1.0
247
Amazon WorkMail Limits
Resource Limit
IP address ranges (in CIDR notation) per IP match condition 10,000
Filters per cross-site scripting match condition 10
Filters per size constraint condition 10
Filters per SQL injection match condition 10
Filters per string match condition 10
In string match conditions, the number of characters in HTTP header names, 40

when you've configured AWS WAF to inspect the headers in web requests for a
specified value
In string match conditions, the number of characters in the value that you want 50
AWS WAF to search for
In regex match conditions, the number of characters in the pattern that you want 70
AWS WAF to search for
These limits are the same for all regions in which AWS WAF is available. Each region is subject to these
limits individually. That is, the limits are not cumulative across regions.
Amazon WorkMail Limits

For more information about these limits, see Amazon WorkMail Limits.
Amazon WorkSpaces Limits

WorkSpaces 1
Graphics WorkSpaces 0
Images 5
AWS X-Ray Limits

Trace and service graph retention 30 days
Segment document size 64kB
Indexed annotations per trace 50
Version 1.0
248
Download
AWS IP Address Ranges

Amazon Web Services (AWS) publishes its current IP address ranges in JSON format. To view the current
ranges, download the .json file. To maintain history, save successive versions of the .json file on your
system. To determine whether there have been changes since the last time that you saved the file, check
the publication time in the current file and compare it to the publication time in the last file that you
saved.
Contents
• Download (p. 249)
• Syntax (p. 249)
• Filtering the JSON File (p. 251)
• Implementing Egress Control (p. 252)
• AWS IP Address Ranges Notifications (p. 252)
Download
Download ip-ranges.json
If you access this file programmatically, it is your responsibility to ensure that the application downloads
the file only after successfully verifying the TLS certificate presented by the server.
Syntax
The syntax of ip-ranges.json is as follows.
{
"syncToken": "0123456789",
"createDate": "yyyy-mm-dd-hh-mm-ss",
"prefixes": [
{
"ip_prefix": "cidr",
"region": "region",
"service": "subset"
}
],
"ipv6_prefixes": [
{
"ipv6_prefix": "cidr",
"region": "region",
"service": "subset"
}
]
}
syncToken
The publication time, in Unix epoch time format.
Type: String
Version 1.0
249
Syntax
Example: "syncToken": "1416435608"

createDate
The publication date and time.
Type: String
Example: "createDate": "2014-11-19-23-29-02"

prefixes
The IP prefixes for the IPv4 address ranges.
Type: Array
ipv6_prefixes
The IP prefixes for the IPv6 address ranges.
Type: Array
ip_prefix
The public IPv4 address range, in CIDR notation. Note that AWS may advertise a prefix in more
specific ranges. For example, prefix 96.127.0.0/17 in the file may be advertised as 96.127.0.0/21,
96.127.8.0/21, 96.127.32.0/19, and 96.127.64.0/18.
Type: String
Example: "ip_prefix": "198.51.100.2/24"

ipv6_prefix
The public IPv6 address range, in CIDR notation. Note that AWS may advertise a prefix in more
specific ranges.
Type: String
Example: "ipv6_prefix": "2001:db8:1234::/64"

region
The AWS region or GLOBAL for edge locations. Note that the CLOUDFRONT and ROUTE53 ranges are
GLOBAL.
Type: String
Valid values: ap-northeast-1 | ap-northeast-2 | ap-south-1 | ap-southeast-1 | ap-

southeast-2 | ca-central-1 | cn-north-1 | eu-central-1 | eu-west-1 | eu-west-2 | eu-
west-3 | sa-east-1 | us-east-1 | us-east-2 | us-gov-west-1 | us-west-1 | us-west-2 |
GLOBAL
Example: "region": "us-east-1"

service
The subset of IP address ranges. Specify AMAZON to get all IP address ranges (for example, the
ranges in the EC2 subset are also in the AMAZON subset). Note that some IP address ranges are only
in the AMAZON subset.
Type: String
Valid values: AMAZON | EC2 | CLOUDFRONT | ROUTE53 | ROUTE53_HEALTHCHECKS | S3
Example: "service": "AMAZON"
Version 1.0
250
Filtering the JSON File
Filtering the JSON File

You can download a command line tool to help you filter the information to just what you are looking
for.
Windows
The AWS Tools for Windows PowerShell includes a cmdlet, Get-AWSPublicIpAddressRange, to parse
this JSON file. The following examples demonstrate its use. For more information, see Querying the
Public IP Address Ranges for AWS.
Example 1. Get the creation date
PS C:\> Get-AWSPublicIpAddressRange -OutputPublicationDate
Thursday, February 18, 2016 5:22:15 PM
Example 2. Get the information for a specific region
PS C:\> Get-AWSPublicIpAddressRange -Region us-east-1
IpPrefix Region Service

-------- ------ -------
23.20.0.0/14 us-east-1 AMAZON
...
Example 3. Get all IP addresses
PS C:\> (Get-AWSPublicIpAddressRange).IpPrefix
23.20.0.0/14
27.0.0.0/22
43.250.192.0/24
...
Linux
The following example commands use the jq tool to parse a local copy of the JSON file.
Example 1. Get the creation date
$ jq .createDate < ipranges.json
"2016-02-18-17-22-15"
Example 2. Get the information for a specific region
$ jq '.prefixes[] | select(.region=="us-east-1")' < ipranges.json
{
"ip_prefix": "23.20.0.0/14",
"region": "us-east-1",
"service": "AMAZON"
Version 1.0
251
Implementing Egress Control
},
{
"ip_prefix": "50.16.0.0/15",
"service": "AMAZON"
},
{
"ip_prefix": "50.19.0.0/16",
"service": "AMAZON"
},
...
Example 3. Get all IP addresses
$ jq -r '.prefixes | .[].ip_prefix' < ipranges.json
23.20.0.0/14
27.0.0.0/22
43.250.192.0/24
...
Implementing Egress Control

To allow an instance to access only AWS services, create a security group with rules that allow outbound
traffic to the CIDR blocks in the AMAZON list, minus the CIDR blocks that are also in the EC2 list.
AWS IP Address Ranges Notifications

Whenever there is a change to the AWS IP address ranges, we send notifications to subscribers of the
AmazonIpSpaceChanged topic. The payload contains information in the following format:
{
"create-time":"yyyy-mm-ddThh:mm:ss+00:00",
"synctoken":"0123456789",
"md5":"6a45316e8bc9463c9e926d5d37836d33",
"url":"https://ip-ranges.amazonaws.com/ip-ranges.json"
}
create-time
The creation date and time.
Notifications could be delivered out of order. Therefore, we recommend that you check the
timestamps to ensure the correct order.
synctoken
The publication time, in Unix epoch time format.

md5
The cryptographic hash value of the ip-ranges.json file. You can use this value to check whether
the downloaded file is corrupted.
url
The location of the ip-ranges.json file.
Version 1.0
252
AWS IP Address Ranges Notifications
If you want to be notified whenever there is a change to the AWS IP address ranges, you can subscribe as
follows to receive notifications using Amazon SNS.
To subscribe to AWS IP address range notifications
1. Open the Amazon SNS console at https://console.aws.amazon.com/sns/v2/home.

2. In the navigation bar, change the region to US East (N. Virginia), if necessary. You must select this
region because the SNS notifications that you are subscribing to were created in this region.
3. In the navigation pane, choose Subscriptions.
4. Choose Create subscription.
5. In the Create subscription dialog box, do the following:
a. For Topic ARN, copy the following Amazon Resource Name (ARN):
arn:aws:sns:us-east-1:806199016981:AmazonIpSpaceChanged
b. For Protocol, choose the protocol to use (for example, Email).

c. For Endpoint, type the endpoint to receive the notification (for example, your email address).
d. Choose Create subscription.
6. You'll be contacted on the endpoint that you specified and asked to confirm your subscription. For
example, if you specified an email address, you'll receive an email message with the subject line
AWS Notification - Subscription Confirmation. Follow the directions to confirm your
subscription.
Notifications are subject to the availability of the endpoint. Therefore, you might want to check the
JSON file periodically to ensure that you've got the latest ranges. For more information about Amazon
SNS reliability, see https://aws.amazon.com/sns/faqs/#Reliability.
If you no longer want to receive these notifications, use the following procedure to unsubscribe.
To unsubscribe from AWS IP address ranges notifications
1. Open the Amazon SNS console at https://console.aws.amazon.com/sns/v2/home.

2. In the navigation pane, choose Subscriptions.
3. Select the check box for the subscription.
4. Choose Actions, Delete subscriptions.
5. When prompted for confirmation, choose Delete.
For more information about Amazon SNS, see the Amazon Simple Notification Service Developer Guide.
Version 1.0
253
Error Retries and Exponential

Backoff in AWS
Numerous components on a network, such as DNS servers, switches, load balancers, and others can
generate errors anywhere in the life of a given request. The usual technique for dealing with these error
responses in a networked environment is to implement retries in the client application. This technique
increases the reliability of the application and reduces operational costs for the developer.
Each AWS SDK implements automatic retry logic. The AWS SDK for Java automatically retries requests,
and you can configure the retry settings using the ClientConfiguration class. For example, you
might want to turn off the retry logic for a web page that makes a request with minimal latency and no
retries. Use the ClientConfiguration class and provide a maxErrorRetry value of 0 to turn off the
retries.
If you're not using an AWS SDK, you should retry original requests that receive server (5xx) or throttling
errors. However, client errors (4xx) indicate that you need to revise the request to correct the problem
before trying again.
In addition to simple retries, each AWS SDK implements exponential backoff algorithm for better flow
control. The idea behind exponential backoff is to use progressively longer waits between retries for
consecutive error responses. You should implement a maximum delay interval, as well as a maximum
number of retries. The maximum delay interval and maximum number of retries are not necessarily fixed
values, and should be set based on the operation being performed, as well as other local factors, such as
network latency.
Most exponential backoff algorithms use jitter (randomized delay) to prevent successive collisions.
Because you aren't trying to avoid such collisions in these cases, you don't need to use this random
number. However, if you use concurrent clients, jitter can help your requests succeed faster. For more
information, see the blog post for Exponential Backoff and Jitter.
The following pseudo code shows one way to poll for a status using an incremental delay.
Do some asynchronous operation.
retries = 0
DO
wait for (2^retries * 100) milliseconds
status = Get the result of the asynchronous operation.
IF status = SUCCESS
retry = false
ELSE IF status = NOT_READY
retry = true
ELSE IF status = THROTTLED
retry = true
ELSE
Some other error occurred, so stop calling the API.
retry = false
END IF
retries = retries + 1
WHILE (retry AND (retries < MAX_RETRIES))
Version 1.0
254
The following code demonstrates how to implement this incremental delay in Java.
public enum Results {

SUCCESS,
NOT_READY,
THROTTLED,
SERVER_ERROR
}
/*
* Performs an asynchronous operation, then polls for the result of the
* operation using an incremental delay.
*/
public static void doOperationAndWaitForResult() {
try {
// Do some asynchronous operation.
long token = asyncOperation();
int retries = 0;
boolean retry = false;
do {
long waitTime = Math.min(getWaitTimeExp(retries), MAX_WAIT_INTERVAL);
System.out.print(waitTime + "\n");
// Wait for the result.

Thread.sleep(waitTime);
// Get the result of the asynchronous operation.

Results result = getAsyncOperationResult(token);
if (Results.SUCCESS == result) {
retry = false;
} else if (Results.NOT_READY == result) {
retry = true;
} else if (Results.THROTTLED == result) {
retry = true;
} else if (Results.SERVER_ERROR == result) {
retry = true;
}
else {
// Some other error occurred, so stop calling the API.
retry = false;
}
} while (retry && (retries++ < MAX_RETRIES));

}
catch (Exception ex) {

}
}
/*
* Returns the next wait interval, in milliseconds, using an exponential
* backoff algorithm.
*/
public static long getWaitTimeExp(int retryCount) {
long waitTime = ((long) Math.pow(2, retryCount) * 100L);
return waitTime;
}
Version 1.0
255
AWS SDK Features for Amazon S3 Client-Side Encryption
AWS SDK Support for Amazon S3

Client-Side Encryption
The following tables provide lists of cryptographic algorithms and features that are supported by the
language–specific AWS SDKs. For details about how to use the features for a particular SDK, see that
SDK's developer guide.
If you are new to cryptography, see Cryptography Basics in the AWS Key Management Service Developer
Guide to get familiar with terms and concepts.
Note
The AWS Encryption SDK is an encryption library that is separate from the language–specific
SDKs. You can use this encryption library to more easily implement encryption best practices in
your application. Unlike the Amazon S3 encryption clients in the language–specific AWS SDKs,
the AWS Encryption SDK is not tied to Amazon S3 and can be used to encrypt or decrypt data to
be stored anywhere.
The AWS Encryption SDK and the Amazon S3 encryption clients are not compatible because
they produce ciphertexts with different data formats. For more details on the AWS Encryption
SDK see the AWS Encryption SDK Developer Guide.
AWS SDK Features for Amazon S3 Client-Side

Encryption
In the following table, each column indicates whether an AWS SDK for a specific language supports the
features used in client-side encryption.
To use the Amazon S3 client-side encryption feature to encrypt data before uploading to Amazon S3,
you must provide a master key to the Amazon S3 encryption client. You can provide a client-side master
key or use the AWS KMS–managed master keys feature. The AWS KMS–managed master keys feature
provides an easy way to create and manage keys used to encrypt data. For more details about these
features, choose the links provided in the Feature column.
For details about how to use the features for a particular SDK, see the SDK's developer guide.
Feature Java .NET Ruby v2 CLI Boto3 PHP v3 JavaScriptGo C++
Amazon Yes Yes Yes No No Yes No Yes Yes

S3
client-
side
encryption
AWS Yes No Yes No No Yes No Yes Yes

KMS–
managed
master
keys
Version 1.0
256
Amazon S3 Encryption Client Cryptographic Algorithms
For more details about the Amazon S3 encryption client in each language–specific SDK that supports
client-side encryption, see the following blog posts.
• Client-Side Data Encryption for Amazon S3 Using the AWS SDK for Java
• Client Side Data Encryption with AWS SDK for .NET and Amazon S3
• Using Client-Side Encryption for S3 in the AWS SDK for Ruby
• Using the AWS SDK for Go Encryption Client
• Amazon S3 Encryption Client Now Available for C++ Developers
Amazon S3 Encryption Client Cryptographic

Algorithms
The following table lists the algorithms that each language–specific AWS SDK supports for encrypting
keys and data when using the Amazon S3 encryption client.
AlgorithmJava .NET Ruby v2 CLI Boto3 PHP v3 JavaScriptGo C++
AES/ Yes Yes Yes No No No No No No

ECB key
wrap
(not
recommended)
AES/ Yes No No No No No No No Yes

Wrap
key
wrap
RSA key Yes No Yes No No No No No No

wrap
AES/ Yes Yes Yes No No Yes No Yes Yes

CBC
content
encryption
(Encryption
Only
mode)
AES/ Yes No Yes No No Yes No Yes Yes

GCM
content
encryption
(Strict
Authentication
mode)
AES/ Yes No Yes No No No No No Yes

CTR
content
encryption
(Authenticated
mode
only
Version 1.0
257
Amazon S3 Encryption Client Cryptographic Algorithms
AlgorithmJava .NET Ruby v2 CLI Boto3 PHP v3 JavaScriptGo C++

used for
decrypting
in range
GETs)
For more details on Authenticated and Encryption-only modes, see the Amazon S3 Client-Side
Authenticated Encryption blog post.
Version 1.0
258
Paragraphs, Line Spacing, and Horizontal Lines
Using Markdown in AWS

The AWS Management Console supports the use of Markdown, a markup language, in certain fields. This
topic explains the types of Markdown formatting supported in the console.
Topics
• Paragraphs, Line Spacing, and Horizontal Lines (p. 259)
• Headings (p. 259)
• Text Formatting (p. 260)
• Links (p. 260)
• Lists (p. 260)
• Tables and Buttons (CloudWatch Dashboards) (p. 261)
Paragraphs, Line Spacing, and Horizontal Lines

Paragraphs are separated by a blank line. To insert a line break, use followed by a blank line.
Repeat this pair of lines to insert multiple blank lines in a row, as in the following example which inserts
two blank lines:

To create a horizontal line, type three hyphens in a row: ---
To create a text block with monospace type, first type a line that has only three of these characters: ```.
Then type the text, then another line that has only ```
```
This appears in a text box with a background shading.
The text is in monospace.
```
Headings
Headings are designated by the number sign (#). A single number sign and a space indicate a top-level
heading, two number signs create a second-level heading, and three number signs create a third-level
heading, as in the following examples.
# Top-level heading
## Second-level heading
### Third-level heading
Version 1.0
259
Text Formatting
Text Formatting
To format text as italic, surround it with a single underscore or asterisk on each side.
*This text appears in italics.*
To format text as bold, surround it with double underscores or double asterisks on each side.
**This text appears in bold.**
To format text as strikethrough, surround it with two tildes on each side.
~~This text appears in strikethrough.~~
Links
To add a clickable web link that appears as text, enter the link_text surrounded by square brackets,
followed by the full URL in parentheses.
Choose [link_text](http://aws.amazon.com).
Lists
To format lines as part of a bulleted list, type them on separate lines with a single asterisk and then a
space, at the beginning of the line:
Here is a bulleted list:
* Ant
* Bug
* Caterpillar
To format lines as part of a numbered list, type them on separate lines with a number, period, and tspace
at the beginning of the line:
Here is a numbered list:
1. Do the first step
2. Do the next step
3. Do the final step
Version 1.0
260
Tables and Buttons (CloudWatch Dashboards)
Tables and Buttons (CloudWatch Dashboards)

CloudWatch dashboards text widgets support Markdown tables and buttons.
To create a table, use pipe marks (|). To distinguish the first row as a header row, insert a line with at
least three hyphens in each entry to distinguish the first row as a header row. The following example
Markdown text creates the table below.
Table | Header
----|-----
Amazon Web Services | AWS
1 | 2
Table Header
Amazon Web Services AWS
1 2
In a CloudWatch dashboard text widget, you can also format a web link to appear as a button by using
[button:Button text].
[button:Go to AWS](http://aws.amazon.com)
[button:primary:This button stands out even more](http://aws.amazon.com)
Version 1.0
261
Document Conventions
The following are the common typographical conventions for AWS technical publications.
Inline code (for example, commands, operations, parameters, constants, XML elements, and regular
expressions)
Formatting: Text in a monospace font
Example: java -version

Example blocks (for example, sample code and scripts)
Formatting: Text in a monospace font inside a shaded block
Example:
# ls -l /var/www/html/index.html
-rw-rw-r-- 1 root root 1872 Jun 21 09:33 /var/www/html/index.html
# date
Wed Jun 21 09:33:42 EDT 2006
Mutually exclusive options
Formatting: Text separated by vertical bars
Example: (start | stride | edge)

Optional parameters
Formatting: Text enclosed in square brackets
Example: [-n, -quiet]

Definitions
Formatting: Text in italics
Example: Amazon Machine Image (AMI)

Technical publications
Formatting: Text in italics
Example: Amazon Simple Storage Service Developer Guide

Elements in the user interface
Formatting: Text in bold
Example: Choose File, Properties.

User input (text that a user types)
Formatting: Text in a monospace font
Example: For the name, type my-new-resource.

Placeholder text for a required value
Formatting: Text in red italics
Version 1.0
262
Example:
aws ec2 register-image --image-location my-s3-bucket/image.manifest.xml
Version 1.0
263
AWS Glossary
Numbers and Symbols (p. 264) | A (p. 264) | B (p. 276) | C (p. 278) | D (p. 282) | E (p. 284) | F (p. 287) |
G (p. 288) | H (p. 289) | I (p. 290) | J (p. 292) | K (p. 292) | L (p. 293) | M (p. 294) | N (p. 296) | O (p. 297)
| P (p. 298) | Q (p. 301) | R (p. 301) | S (p. 304) | T (p. 310) | U (p. 312) | V (p. 313) | W (p. 314) | X, Y,
Z (p. 314)
Numbers and Symbols

100-continue A method that enables a client to see if a server can accept a request before
actually sending it. For large PUT requests, this method can save both time and
bandwidth charges.
A
Z (p. 314)
AAD See additional authenticated data.
access control list (ACL) A document that defines who can access a particular bucket (p. 277) or
object. Each bucket (p. 277) and object in Amazon S3 (p. 269) has an ACL.
The document defines what each type of user can do, such as write and read
permissions.
access identifiers See credentials.
access key The combination of an access key ID (p. 264) (like AKIAIOSFODNN7EXAMPLE)
and a secret access key (p. 306) (like wJalrXUtnFEMI/K7MDENG/
bPxRfiCYEXAMPLEKEY). You use access keys to sign API requests that you make
to AWS.
access key ID A unique identifier that's associated with a secret access key (p. 306); the
access key ID and secret access key are used together to sign programmatic AWS
requests cryptographically.
access key rotation A method to increase security by changing the AWS access key ID. This method
enables you to retire an old key at your discretion.
Version 1.0
264
access policy language A language for writing documents (that is, policies (p. 299)) that specify who can
access a particular AWS resource (p. 303) and under what conditions.
account A formal relationship with AWS that is associated with (1) the owner email
address and password, (2) the control of resource (p. 303)s created under
its umbrella, and (3) payment for the AWS activity related to those resources.
The AWS account has permission to do anything and everything with all the
AWS account resources. This is in contrast to a user (p. 312), which is an entity
contained within the account.
account activity A web page showing your month-to-date AWS usage and costs. The account
activity page is located at https://aws.amazon.com/account-activity/.
ACL See access control list (ACL).
ACM See AWS Certificate Manager (ACM).
action An API function. Also called operation or call. The activity the principal (p. 300)
has permission to perform. The action is B in the statement "A has permission
to do B to C where D applies." For example, Jane sends a request to Amazon
SQS (p. 269) with Action=ReceiveMessage.
Amazon CloudWatch (p. 266): The response initiated by the change in an

alarm's state: for example, from OK to ALARM. The state change may be triggered
by a metric reaching the alarm threshold, or by a SetAlarmState request.
Each alarm can have one or more actions assigned to each state. Actions are
performed once each time the alarm changes to a state that has an action
assigned, such as an Amazon Simple Notification Service (p. 269) notification,
an Auto Scaling (p. 271) policy (p. 299) execution or an Amazon EC2 (p. 267)
instance (p. 291) stop/terminate action.
active trusted signers A list showing each of the trusted signers you've specified and the IDs of the
corresponding active key pairs that Amazon CloudFront (p. 266) is aware of. To
be able to create working signed URLs, a trusted signer must appear in this list
with at least one key pair ID.
additional authenticated data Information that is checked for integrity but not encrypted, such as headers or
other contextual metadata.
administrative suspension Auto Scaling (p. 271) might suspend processes for Auto Scaling group (p. 271)
that repeatedly fail to launch instances. Auto Scaling groups that most commonly
experience administrative suspension have zero running instances, have been
trying to launch instances for more than 24 hours, and have not succeeded in that
time.
alarm An item that watches a single metric over a specified time period, and triggers
an Amazon SNS (p. 269) topic (p. 312) or an Auto Scaling (p. 271)
policy (p. 299) if the value of the metric crosses a threshold value over a
predetermined number of time periods.
allow One of two possible outcomes (the other is deny (p. 283)) when an
IAM (p. 274) access policy (p. 299) is evaluated. When a user makes a request
to AWS, AWS evaluates the request based on all permissions that apply to the
user and then returns either allow or deny.
Amazon API Gateway A fully managed service that makes it easy for developers to create, publish,
maintain, monitor, and secure APIs at any scale.
See Also https://aws.amazon.com/api-gateway.
Version 1.0
265
Amazon AppStream A web service for streaming existing Windows applications from the cloud to any
device.
See Also https://aws.amazon.com/appstream/.
Amazon Aurora A fully managed MySQL-compatible relational database engine that combines
the speed and availability of commercial databases with the simplicity and cost-
effectiveness of open source databases.
See Also https://aws.amazon.com/rds/aurora/.
Amazon CloudFront An AWS content delivery service that helps you improve the performance,
reliability, and availability of your websites and applications.
See Also https://aws.amazon.com/cloudfront.
Amazon CloudSearch A fully managed service in the AWS cloud that makes it easy to set up, manage,
and scale a search solution for your website or application.
Amazon CloudWatch A web service that enables you to monitor and manage various metrics, and
configure alarm actions based on data from those metrics.
See Also https://aws.amazon.com/cloudwatch.
Amazon CloudWatch Events A web service that enables you to deliver a timely stream of system events that
describe changes in AWS resource (p. 303)s to AWS Lambda (p. 274) functions,
streams in Amazon Kinesis Data Streams (p. 268), Amazon Simple Notification
Service (p. 269) topics, or built-in targets.
Amazon CloudWatch Logs A web service for monitoring and troubleshooting your systems and applications
from your existing system, application, and custom log files. You can send your
existing log files to CloudWatch Logs and monitor these logs in near real-time.
Amazon Cognito A web service that makes it easy to save mobile user data, such as app
preferences or game state, in the AWS cloud without writing any back-end
code or managing any infrastructure. Amazon Cognito offers mobile identity
management and data synchronization across devices.
See Also https://aws.amazon.com/cognito/.
Amazon DynamoDB A fully managed NoSQL database service that provides fast and predictable
performance with seamless scalability.
See Also https://aws.amazon.com/dynamodb/.
Amazon DynamoDB Storage A storage backend for the Titan graph database implemented on top of Amazon
Backend for Titan DynamoDB. Titan is a scalable graph database optimized for storing and querying
graphs.
Amazon DynamoDB Streams An AWS service that captures a time-ordered sequence of item-level
modifications in any Amazon DynamoDB table, and stores this information in a
log for up to 24 hours. Applications can access this log and view the data items as
they appeared before and after they were modified, in near real time.
Amazon Elastic Block Store A service that provides block level storage volume (p. 313)s for use with EC2
(Amazon EBS) instance (p. 285)s.
See Also https://aws.amazon.com/ebs.
Amazon EBS-backed AMI A type of Amazon Machine Image (AMI) (p. 268) whose instance (p. 291)s use
an Amazon EBS (p. 266) volume (p. 313) as their root device. Compare this
with instances launched from instance store-backed AMI (p. 291)s, which use the
instance store (p. 291) as the root device.
Version 1.0
266
Amazon Elastic Container A fully managed Docker container registry that makes it easy for developers to
Registry (Amazon ECR) store, manage, and deploy Docker container images. Amazon ECR is integrated
with Amazon Elastic Container Service (Amazon ECS) (p. 267) and AWS Identity
and Access Management (IAM) (p. 274).
See Also https://aws.amazon.com/ecr.
Amazon Elastic Container A highly scalable, fast, container (p. 280) management service that makes it
Service (Amazon ECS) easy to run, stop, and manage Docker containers on a cluster (p. 279) of EC2
instance (p. 285)s.
See Also https://aws.amazon.com/ecs.
Amazon ECS service A service for running and maintaining a specified number of task (p. 311)s
(instantiations of a task definition (p. 311)) simultaneously.
Amazon EC2 VM Import See https://aws.amazon.com/ec2/vm-import.

Connector
Amazon Elastic Compute A web service that enables you to launch and manage Linux/UNIX and Windows
Cloud (Amazon EC2) server instance (p. 291)s in Amazon's data centers.
See Also https://aws.amazon.com/ec2.
Amazon Elastic File System A file storage service for EC2 (p. 267) instance (p. 291)s. Amazon EFS is easy
(Amazon EFS) to use and provides a simple interface with which you can create and configure
file systems. Amazon EFS storage capacity grows and shrinks automatically as you
add and remove files.
See Also https://aws.amazon.com/efs/.
Amazon EMR (Amazon EMR) A web service that makes it easy to process large amounts of data efficiently.
Amazon EMR uses Hadoop (p. 289) processing combined with several AWS
products to do such tasks as web indexing, data mining, log file analysis, machine
learning, scientific simulation, and data warehousing.
See Also https://aws.amazon.com/elasticmapreduce.
Amazon Elastic Transcoder A cloud-based media transcoding service. Elastic Transcoder is a highly scalable
tool for converting (or transcoding) media files from their source format into
versions that will play on devices like smartphones, tablets, and PCs.
See Also https://aws.amazon.com/elastictranscoder/.
Amazon ElastiCache A web service that simplifies deploying, operating, and scaling an in-memory
cache in the cloud. The service improves the performance of web applications by
providing information retrieval from fast, managed, in-memory caches, instead of
relying entirely on slower disk-based databases.
See Also https://aws.amazon.com/elasticache/.
Amazon Elasticsearch Service An AWS managed service for deploying, operating, and scaling Elasticsearch, an
(Amazon ES) open-source search and analytics engine, in the AWS Cloud. Amazon Elasticsearch
Service (Amazon ES) also offers security options, high availability, data durability,
and direct access to the Elasticsearch APIs.
See Also https://aws.amazon.com/elasticsearch-service.
Amazon GameLift A managed service for deploying, operating, and scaling session-based
multiplayer games.
See Also https://aws.amazon.com/gamelift/.
Amazon Glacier A secure, durable, and low-cost storage service for data archiving and long-term
backup. You can reliably store large or small amounts of data for significantly
less than on-premises solutions. Amazon Glacier is optimized for infrequently
accessed data, where a retrieval time of several hours is suitable.
See Also https://aws.amazon.com/glacier/.
Version 1.0
267
Amazon GuardDuty A continuous security monitoring service. Amazon GuardDuty can help to identify
unexpected and potentially unauthorized or malicious activity in your AWS
environment.
See Also https://aws.amazon.com/guardduty/.
Amazon Inspector An automated security assessment service that helps improve the security and
compliance of applications deployed on AWS. Amazon Inspector automatically
assesses applications for vulnerabilities or deviations from best practices. After
performing an assessment, Amazon Inspector produces a detailed report with
prioritized steps for remediation.
See Also https://aws.amazon.com/inspector.
Amazon Kinesis A platform for streaming data on AWS. Kinesis offers services that simplify the
loading and analysis of streaming data.
See Also https://aws.amazon.com/kinesis/.
Amazon Kinesis Data Firehose A fully managed service for loading streaming data into AWS. Kinesis Data
Firehose can capture and automatically load streaming data into Amazon
S3 (p. 269) and Amazon Redshift (p. 269), enabling near real-time analytics
with existing business intelligence tools and dashboards. Kinesis Data Firehose
automatically scales to match the throughput of your data and requires no
ongoing administration. It can also batch, compress, and encrypt the data before
loading it.
See Also https://aws.amazon.com/kinesis/firehose/.
Amazon Kinesis Data Streams A web service for building custom applications that process or analyze streaming
data for specialized needs. Amazon Kinesis Data Streams can continuously
capture and store terabytes of data per hour from hundreds of thousands of
sources.
See Also https://aws.amazon.com/kinesis/streams/.
Amazon Lightsail Lightsail is designed to be the easiest way to launch and manage a virtual private
server with AWS. Lightsail offers bundled plans that include everything you need
to deploy a virtual private server, for a low monthly rate.
See Also https://aws.amazon.com/lightsail/.
Amazon Lumberyard A cross-platform, 3D game engine for creating high-quality games. You can
connect games to the compute and storage of the AWS cloud and engage fans on
Twitch.
See Also https://aws.amazon.com/lumberyard/.
Amazon Machine Image (AMI) An encrypted machine image stored in Amazon Elastic Block Store (Amazon
EBS) (p. 266) or Amazon Simple Storage Service (p. 269). AMIs are like a
template of a computer's root drive. They contain the operating system and can
also include software and layers of your application, such as database servers,
middleware, web servers, and so on.
Amazon Machine Learning A cloud-based service that creates machine learning (ML) models by finding
patterns in your data, and uses these models to process new data and generate
predictions.
See Also http://aws.amazon.com/machine-learning/.
Amazon Macie A security service that uses machine learning to automatically discover, classify,
and protect sensitive data in AWS.
See Also http://aws.amazon.com/macie/.
Amazon ML See Amazon Machine Learning.
Amazon Mobile Analytics A service for collecting, visualizing, understanding, and extracting mobile app
usage data at scale.
Version 1.0
268
See Also https://aws.amazon.com/mobileanalytics.
Amazon MQ A managed message broker service for Apache ActiveMQ that makes it easy to set
up and operate message brokers in the cloud.
See Also https://aws.amazon.com/amazon-mq/.
Amazon Redshift A fully managed, petabyte-scale data warehouse service in the cloud. With
Amazon Redshift you can analyze your data using your existing business
intelligence tools.
See Also https://aws.amazon.com/redshift/.
Amazon Relational Database A web service that makes it easier to set up, operate, and scale a relational
Service (Amazon RDS) database in the cloud. It provides cost-efficient, resizable capacity for an industry-
standard relational database and manages common database administration
tasks.
See Also https://aws.amazon.com/rds.
Amazon Resource Name A standardized way to refer to an AWS resource (p. 303). For example:
(ARN) arn:aws:iam::123456789012:user/division_abc/subdivision_xyz/Bob.
Amazon Route 53 A web service you can use to create a new DNS service or to migrate your existing
DNS service to the cloud.
See Also https://aws.amazon.com/route53.
Amazon S3 See Amazon Simple Storage Service (Amazon S3).
Amazon S3-Backed AMI See instance store-backed AMI.
Amazon Silk A next-generation web browser available only on Fire OS tablets and phones.
Built on a split architecture that divides processing between the client and the
AWS cloud, Amazon Silk is designed to create a faster, more responsive mobile
browsing experience.
Amazon Simple Email Service An easy-to-use, cost-effective email solution for applications.
(Amazon SES) See Also https://aws.amazon.com/ses.
Amazon Simple Notification A web service that enables applications, end-users, and devices to instantly send
Service (Amazon SNS) and receive notifications from the cloud.
See Also https://aws.amazon.com/sns.
Amazon Simple Queue Reliable and scalable hosted queues for storing messages as they travel between
Service (Amazon SQS) computers.
See Also https://aws.amazon.com/sqs.
Amazon Simple Storage Storage for the internet. You can use it to store and retrieve any amount of data
Service (Amazon S3) at any time, from anywhere on the web.
See Also https://aws.amazon.com/s3.
Amazon Simple Workflow A fully managed service that helps developers build, run, and scale background
Service (Amazon SWF) jobs that have parallel or sequential steps. Amazon SWF is like a state tracker and
task coordinator in the cloud.
See Also https://aws.amazon.com/swf/.
Amazon Sumerian A set of tools for creating and running high-quality 3D, augmented reality (AR),
and virtual reality (VR) applications on the web.
See Also https://aws.amazon.com/sumerian/.
Amazon Virtual Private Cloud A web service for provisioning a logically isolated section of the AWS cloud where
(Amazon VPC) you can launch AWS resource (p. 303)s in a virtual network that you define.
You control your virtual networking environment, including selection of your
Version 1.0
269
own IP address range, creation of subnet (p. 310)s, and configuration of route
table (p. 304)s and network gateways.
See Also https://aws.amazon.com/vpc.
Amazon VPC See Amazon Virtual Private Cloud (Amazon VPC).
Amazon Web Services (AWS) An infrastructure web services platform in the cloud for companies of all sizes.
See Also https://aws.amazon.com/what-is-cloud-computing/.
Amazon WorkDocs A managed, secure enterprise document storage and sharing service with
administrative controls and feedback capabilities.
See Also https://aws.amazon.com/workdocs/.
Amazon WorkMail A managed, secure business email and calendar service with support for existing
desktop and mobile email clients.
See Also https://aws.amazon.com/workmail/.
Amazon WorkSpaces A managed, secure desktop computing service for provisioning cloud-
based desktops and providing users access to documents, applications, and
resource (p. 303)s from supported devices.
See Also https://aws.amazon.com/workspaces/.
Amazon WorkSpaces A web service for deploying and managing applications for Amazon WorkSpaces.
Application Manager (Amazon Amazon WAM accelerates software deployment, upgrades, patching, and
WAM) retirement by packaging Windows desktop applications into virtualized
application containers.
See Also https://aws.amazon.com/workspaces/applicationmanager.
AMI See Amazon Machine Image (AMI).
analysis scheme Amazon CloudSearch (p. 266): Language-specific text analysis options that
are applied to a text field to control stemming and configure stopwords and
synonyms.
application AWS Elastic Beanstalk (p. 273): A logical collection of components, including
environments, versions, and environment configurations. An application is
conceptually similar to a folder.
AWS CodeDeploy (p. 272): A name that uniquely identifies the application to be
deployed. AWS CodeDeploy uses this name to ensure the correct combination of
revision, deployment configuration, and deployment group are referenced during
a deployment.
Application Billing The location where your customers manage the Amazon DevPay products they've
purchased. The web address is http://www.amazon.com/dp-applications.
application revision AWS CodeDeploy (p. 272): An archive file containing source content—such
as source code, web pages, executable files, and deployment scripts—along
with an application specification file (p. 270). Revisions are stored in Amazon
S3 (p. 269) bucket (p. 277)s or GitHub (p. 289) repositories. For Amazon S3, a
revision is uniquely identified by its Amazon S3 object key and its ETag, version, or
both. For GitHub, a revision is uniquely identified by its commit ID.
application specification file AWS CodeDeploy (p. 272): A YAML-formatted file used to map the source
files in an application revision to destinations on the instance; specify custom
permissions for deployed files; and specify scripts to be run on each instance at
various stages of the deployment process.
application version AWS Elastic Beanstalk (p. 273): A specific, labeled iteration of an application
that represents a functionally consistent set of deployable application code. A
Version 1.0
270
version points to an Amazon S3 (p. 269) object (a JAVA WAR file) that contains
the application code.
AppSpec file See application specification file.
AUC Area Under a Curve. An industry-standard metric to evaluate the quality of a

binary classification machine learning model. AUC measures the ability of the
model to predict a higher score for positive examples, those that are “correct,”
than for negative examples, those that are “incorrect.” The AUC metric returns a
decimal value from 0 to 1. AUC values near 1 indicate an ML model that is highly
accurate.
ARN See Amazon Resource Name (ARN).
artifact AWS CodePipeline (p. 272): A copy of the files or changes that will be worked
upon by the pipeline.
asymmetric encryption Encryption (p. 286) that uses both a public key and a private key.
asynchronous bounce A type of bounce (p. 277) that occurs when a receiver (p. 302) initially accepts
an email message for delivery and then subsequently fails to deliver it.
atomic counter DynamoDB: A method of incrementing or decrementing the value of an existing

attribute without interfering with other write requests.
attribute A fundamental data element, something that does not need to be broken
down any further. In DynamoDB, attributes are similar in many ways to fields or
columns in other database systems.
Amazon Machine Learning: A unique, named property within an observation in a

data set. In tabular data, such as spreadsheets or comma-separated values (.csv)
files, the column headings represent the attributes, and the rows contain values
for each attribute.
Aurora See the section called “Amazon Aurora”.
authenticated encryption Encryption (p. 286) that provides confidentiality, data integrity, and authenticity
assurances of the encrypted data.
authentication The process of proving your identity to a system.
Auto Scaling A web service designed to launch or terminate instance (p. 291)s automatically
based on user-defined policies (p. 299), schedules, and health check (p. 289)s.
See Also https://aws.amazon.com//autoscaling.
Auto Scaling group A representation of multiple EC2 instance (p. 285)s that share similar
characteristics, and that are treated as a logical grouping for the purposes of
instance scaling and management.
Availability Zone A distinct location within a Region (p. 302) that is insulated from failures
in other Availability Zones, and provides inexpensive, low-latency network
connectivity to other Availability Zones in the same Region.
AWS See Amazon Web Services (AWS).
AWS Application Discovery A web service that helps you plan to migrate to AWS by identifying IT assets
Service in a data center—including servers, virtual machines, applications, application
dependencies, and network infrastructure.
See Also https://aws.amazon.com/about-aws/whats-new/2016/04/aws-
application-discovery-service/.
Version 1.0
271
AWS AppSync An enterprise level, fully managed GraphQL service with real-time data
synchronization and offline programming features.
See Also https://aws.amazon.com/appsync/.
AWS Billing and Cost The AWS cloud computing model in which you pay for services on demand and
Management use as much or as little at any given time as you need. While resource (p. 303)s
are active under your account, you pay for the cost of allocating those resources
and for any incidental usage associated with those resources, such as data
transfer or allocated storage.
See Also https://aws.amazon.com/billing/new-user-faqs/.
AWS Certificate Manager A web service for provisioning, managing, and deploying Secure Sockets
(ACM) Layer/Transport Layer Security (p. 312) (SSL/TLS) certificates for use with AWS
services.
See Also https://aws.amazon.com/certificate-manager/.
AWS Cloud9 A cloud-based integrated development environment (IDE) that you use to write,
run, and debug code.
See Also https://aws.amazon.com/cloud9/.
AWS CloudFormation A service for writing or changing templates that create and delete related AWS
resource (p. 303)s together as a unit.
See Also https://aws.amazon.com/cloudformation.
AWS CloudHSM A web service that helps you meet corporate, contractual, and regulatory
compliance requirements for data security by using dedicated hardware security
module (HSM) appliances within the AWS cloud.
See Also https://aws.amazon.com/cloudhsm/.
AWS CloudTrail A web service that records AWS API calls for your account and delivers log files to
you. The recorded information includes the identity of the API caller, the time of
the API call, the source IP address of the API caller, the request parameters, and
the response elements returned by the AWS service.
See Also https://aws.amazon.com/cloudtrail/.
AWS CodeCommit A fully managed source control service that makes it easy for companies to host
secure and highly scalable private Git repositories.
See Also https://aws.amazon.com/codecommit.
AWS CodeDeploy A service that automates code deployments to any instance, including EC2
instance (p. 285)s and instance (p. 291)s running on-premises.
See Also https://aws.amazon.com/codedeploy.
AWS CodeDeploy agent A software package that, when installed and configured on an instance, enables
that instance to be used in AWS CodeDeploy deployments.
AWS CodePipeline A continuous delivery service for fast and reliable application updates.
See Also https://aws.amazon.com/codepipeline.
AWS Command Line Interface A unified downloadable and configurable tool for managing AWS services.
(AWS CLI) Control multiple AWS services from the command line and automate them
through scripts.
See Also https://aws.amazon.com/cli/.
AWS Config A fully managed service that provides an AWS resource (p. 303) inventory,
configuration history, and configuration change notifications for better security
and governance. You can create rules that automatically check the configuration
of AWS resources that AWS Config records.
See Also https://aws.amazon.com/config/.
Version 1.0
272
AWS Elemental MediaConvert A file-based video conversion service that transforms media into formats required
for traditional broadcast and for internet streaming to multi-screen devices.
See Also https://aws.amazon.com/mediaconvert.
AWS Elemental MediaLive A video service that lets you easily create live outputs for broadcast and
streaming delivery.
See Also https://aws.amazon.com/medialive.
AWS Elemental MediaPackage A just-in-time packaging and origination service that lets you format highly
secure and reliable live outputs for a variety of devices.
See Also https://aws.amazon.com/mediapackage.
AWS Elemental MediaStore A storage service optimized for media that provides the performance, consistency,
and low latency required to deliver live and on-demand video content at scale.
See Also https://aws.amazon.com/mediastore.
AWS Elemental MediaTailor A video service that lets you serve targeted ads to viewers while maintaining
broadcast quality in over-the-top (OTT) video applications.
See Also https://aws.amazon.com/mediatailor.
AWS Database Migration A web service that can help you migrate data to and from many widely used
Service commercial and open-source databases.
See Also https://aws.amazon.com/dms.
AWS Data Pipeline A web service for processing and moving data between different AWS compute
and storage services, as well as on-premises data sources, at specified intervals.
See Also https://aws.amazon.com/datapipeline.
AWS Device Farm An app testing service that allows developers to test Android, iOS, and Fire OS
devices on real, physical phones and tablets that are hosted by AWS.
See Also https://aws.amazon.com/device-farm.
AWS Direct Connect A web service that simplifies establishing a dedicated network connection
from your premises to AWS. Using AWS Direct Connect, you can establish
private connectivity between AWS and your data center, office, or colocation
environment.
See Also https://aws.amazon.com/directconnect.
AWS Directory Service A managed service for connecting your AWS resource (p. 303)s to an existing
on-premises Microsoft Active Directory or to set up and operate a new,
standalone directory in the AWS cloud.
See Also https://aws.amazon.com/directoryservice.
AWS Elastic Beanstalk A web service for deploying and managing applications in the AWS Cloud without
worrying about the infrastructure that runs those applications.
See Also https://aws.amazon.com/elasticbeanstalk.
AWS Glue A fully managed extract, transform, and load (ETL) (p. 287) service that you can
use to catalog data and load it for analytics. With AWS Glue, you can discover
your data, develop scripts to transform sources into targets, and schedule and run
ETL jobs in a serverless environment.
See Also https://aws.amazon.com/glue.
AWS GovCloud (US) An isolated AWS Region designed to host sensitive workloads in the cloud,
ensuring that this work meets the US government's regulatory and compliance
requirements. The AWS GovCloud (US) Region adheres to United States
International Traffic in Arms Regulations (ITAR), Federal Risk and Authorization
Management Program (FedRAMP) requirements, Department of Defense (DOD)
Cloud Security Requirements Guide (SRG) Levels 2 and 4, and Criminal Justice
Information Services (CJIS) Security Policy requirements.
Version 1.0
273
See Also https://aws.amazon.com/govcloud-us/.
AWS Identity and Access A web service that enables Amazon Web Services (AWS) (p. 270) customers to
Management (IAM) manage users and user permissions within AWS.
See Also https://aws.amazon.com/iam.
AWS Import/Export A service for transferring large amounts of data between AWS and portable
storage devices.
See Also https://aws.amazon.com/importexport.
AWS IoT A managed cloud platform that lets connected devices easily and securely
interact with cloud applications and other devices.
See Also https://aws.amazon.com/iot.
AWS Key Management A managed service that simplifies the creation and control of
Service (AWS KMS) encryption (p. 286) keys that are used to encrypt data.
See Also https://aws.amazon.com/kms.
AWS Lambda A web service that lets you run code without provisioning or managing servers.
You can run code for virtually any type of application or back-end service with
zero administration. You can set up your code to automatically trigger from other
AWS services or call it directly from any web or mobile app.
See Also https://aws.amazon.com/lambda/.
AWS managed key One of two types of customer master key (CMK) (p. 282)s in AWS Key
Management Service (AWS KMS) (p. 274).
AWS managed policy An IAM (p. 274) managed policy (p. 294) that is created and managed by AWS.
AWS Management Console A graphical interface to manage compute, storage, and other cloud
resource (p. 303)s.
See Also https://aws.amazon.com/console.
AWS Management Portal for A web service for managing your AWS resource (p. 303)s using VMware
vCenter vCenter. You install the portal as a vCenter plug-in within your existing
vCenter environment. Once installed, you can migrate VMware VMs to Amazon
EC2 (p. 267) and manage AWS resources from within vCenter.
See Also https://aws.amazon.com/ec2/vcenter-portal/.
AWS Marketplace A web portal where qualified partners to market and sell their software to AWS
customers. AWS Marketplace is an online software store that helps customers
find, buy, and immediately start using the software and services that run on AWS.
See Also https://aws.amazon.com/partners/aws-marketplace/.
AWS Mobile Hub An integrated console that for building, testing, and monitoring mobile apps.
See Also https://aws.amazon.com/mobile.
AWS Mobile SDK A software development kit whose libraries, code samples, and documentation
help you build high quality mobile apps for the iOS, Android, Fire OS, Unity, and
Xamarin platforms.
See Also https://aws.amazon.com/mobile/sdk.
AWS OpsWorks A configuration management service that helps you use Chef to configure and
operate groups of instances and applications. You can define the application’s
architecture and the specification of each component including package
installation, software configuration, and resource (p. 303)s such as storage. You
can automate tasks based on time, load, lifecycle events, and more.
See Also https://aws.amazon.com/opsworks/.
AWS Organizations An account management service that enables you to consolidate multiple AWS
accounts into an organization that you create and centrally manage.
Version 1.0
274
See Also https://aws.amazon.com/organizations/.
AWS SDK for C++ A software development kit for that provides C++ APIs for many AWS
services including Amazon S3 (p. 269), Amazon EC2 (p. 267), Amazon
DynamoDB (p. 266), and more. The single, downloadable package includes the
AWS C++ library, code samples, and documentation.
See Also https://aws.amazon.com/sdk-for-cpp/.
AWS SDK for Go A software development kit for integrating your Go application with the full suite
of AWS services.
See Also https://aws.amazon.com/sdk-for-go/.
AWS SDK for Java A software development kit that provides Java APIs for many AWS
services including Amazon S3 (p. 269), Amazon EC2 (p. 267), Amazon
DynamoDB (p. 266), and more. The single, downloadable package includes the
AWS Java library, code samples, and documentation.
See Also https://aws.amazon.com/sdk-for-java/.
AWS SDK for JavaScript in the A software development kit for accessing AWS services from JavaScript code
Browser running in the browser. Authenticate users through Facebook, Google, or Login
with Amazon using web identity federation. Store application data in Amazon
DynamoDB (p. 266), and save user files to Amazon S3 (p. 269).
See Also http://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/.
AWS SDK for JavaScript in A software development kit for accessing AWS services from JavaScript in
Node.js Node.js. The SDK provides JavaScript objects for AWS services, including Amazon
S3 (p. 269), Amazon EC2 (p. 267), Amazon DynamoDB (p. 266), and Amazon
Simple Workflow Service (Amazon SWF) (p. 269) . The single, downloadable
package includes the AWS JavaScript library and documentation.
See Also http://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/.
AWS SDK for .NET A software development kit that provides .NET API actions for AWS services
including Amazon S3 (p. 269), Amazon EC2 (p. 267), IAM (p. 274), and more.
You can download the SDK as multiple service-specific packages on NuGet.
See Also https://aws.amazon.com/sdk-for-net/.
AWS SDK for PHP A software development kit and open-source PHP library for integrating
your PHP application with AWS services like Amazon S3 (p. 269), Amazon
Glacier (p. 267), and Amazon DynamoDB (p. 266).
See Also https://aws.amazon.com/sdk-for-php/.
AWS SDK for Python (Boto) A software development kit for using Python to access AWS services like
Amazon EC2 (p. 267), Amazon EMR (p. 267), Auto Scaling (p. 271), Amazon
Kinesis (p. 268), AWS Lambda (p. 274), and more.
See Also http://boto.readthedocs.org/en/latest/.
AWS SDK for Ruby A software development kit for accessing AWS services from Ruby. The SDK
provides Ruby classes for many AWS services including Amazon S3 (p. 269),
Amazon EC2 (p. 267), Amazon DynamoDB (p. 266). and more. The single,
downloadable package includes the AWS Ruby Library and documentation.
See Also https://aws.amazon.com/sdk-for-ruby/.
AWS Security Token Service A web service for requesting temporary, limited-privilege credentials for AWS
(AWS STS) Identity and Access Management (IAM) (p. 274) users or for users that you
authenticate (federated users (p. 288)).
See Also https://aws.amazon.com/iam/.
AWS Service Catalog A web service that helps organizations create and manage catalogs of IT services
that are approved for use on AWS. These IT services can include everything from
Version 1.0
275
virtual machine images, servers, software, and databases to complete multitier

application architectures.
See Also https://aws.amazon.com/servicecatalog/.
AWS Step Functions A web service that coordinates the components of distributed applications as a
series of steps in a visual workflow.
See Also https://aws.amazon.com/step-functions/.
AWS Storage Gateway A web service that connects an on-premises software appliance with cloud-based
storage to provide seamless and secure integration between an organization’s on-
premises IT environment and AWS’s storage infrastructure.
See Also https://aws.amazon.com/storagegateway/.
AWS Toolkit for Eclipse An open-source plug-in for the Eclipse Java IDE that makes it easier for
developers to develop, debug, and deploy Java applications using Amazon Web
Services.
See Also https://aws.amazon.com/eclipse/.
AWS Toolkit for Visual Studio An extension for Microsoft Visual Studio that helps developers develop, debug,
and deploy .NET applications using Amazon Web Services.
See Also https://aws.amazon.com/visualstudio/.
AWS Tools for Windows A set of PowerShell cmdlets to help developers and administrators manage their
PowerShell AWS services from the Windows PowerShell scripting environment.
See Also https://aws.amazon.com/powershell/.
AWS Tools for Microsoft Provides tasks you can use in build and release definitions in VSTS to interact with
Visual Studio Team Services AWS services.
See Also https://aws.amazon.com/vsts/.
AWS Trusted Advisor A web service that inspects your AWS environment and makes recommendations
for saving money, improving system availability and performance, and helping to
close security gaps.
See Also https://aws.amazon.com/premiumsupport/trustedadvisor/.
AWS VPN CloudHub Enables secure communication between branch offices using a simple hub-and-
spoke model, with or without a VPC (p. 314).
AWS WAF A web application firewall service that controls access to content by allowing or
blocking web requests based on criteria that you specify, such as header values
or the IP addresses that the requests originate from. AWS WAF helps protect web
applications from common web exploits that could affect application availability,
compromise security, or consume excessive resources.
See Also https://aws.amazon.com/waf/.
AWS X-Ray A web service that collects data about requests that your application serves,
and provides tools you can use to view, filter, and gain insights into that data to
identify issues and opportunities for optimization.
See Also https://aws.amazon.com/xray/.
B
Z (p. 314)
basic monitoring Monitoring of AWS provided metrics derived at a 5-minute frequency.
Version 1.0
276
batch See document batch.
BGP ASN Border Gateway Protocol Autonomous System Number. A unique identifier for a
network, for use in BGP routing. Amazon EC2 (p. 267) supports all 2-byte ASN
numbers in the range of 1 – 65335, with the exception of 7224, which is reserved.
batch prediction Amazon Machine Learning: An operation that processes multiple input data
observations at one time (asynchronously). Unlike real-time predictions, batch
predictions are not available until all predictions have been processed.
See Also real-time predictions.
billing See AWS Billing and Cost Management.
binary attribute Amazon Machine Learning: An attribute for which one of two possible values is
possible. Valid positive values are 1, y, yes, t, and true answers. Valid negative
values are 0, n, no, f, and false. Amazon Machine Learning outputs 1 for positive
values and 0 for negative values.
See Also attribute.
binary classification model Amazon Machine Learning: A machine learning model that predicts the answer to
questions where the answer can be expressed as a binary variable. For example,
questions with answers of “1” or “0”, “yes” or “no”, “will click” or “will not click”
are questions that have binary answers. The result for a binary classification
model is always either a “1” (for a “true” or affirmative answers) or a “0” (for a
“false” or negative answers).
blacklist A list of IP addresses, email addresses, or domains that an internet service

provider (p. 291) suspects to be the source of spam (p. 308). The ISP blocks
incoming email from these addresses or domains.
block A data set. Amazon EMR (p. 267) breaks large amounts of data into subsets.
Each subset is called a data block. Amazon EMR assigns an ID to each block and
uses a hash table to keep track of block processing.
block device A storage device that supports reading and (optionally) writing data in fixed-size
blocks, sectors, or clusters.
block device mapping A mapping structure for every AMI (p. 268) and instance (p. 291) that specifies
the block devices attached to the instance.
blue/green deployment AWS CodeDeploy: A deployment method in which the instances in a deployment
group (the original environment) are replaced by a different set of instances (the
replacement environment).
bootstrap action A user-specified default or custom action that runs a script or an application on
all nodes of a job flow before Hadoop (p. 289) starts.
Border Gateway Protocol See BGP ASN.

Autonomous System Number
bounce A failed email delivery attempt.
breach Auto Scaling (p. 271): The condition in which a user-set threshold (upper or
lower boundary) is passed. If the duration of the breach is significant, as set by a
breach duration parameter, it can possibly start a scaling activity (p. 305).
bucket Amazon Simple Storage Service (Amazon S3) (p. 269): A container for stored
objects. Every object is contained in a bucket. For example, if the object named
photos/puppy.jpg is stored in the johnsmith bucket, then authorized users
can access the object with the URL http://johnsmith.s3.amazonaws.com/
photos/puppy.jpg.
Version 1.0
277
bucket owner The person or organization that owns a bucket (p. 277) in Amazon S3 (p. 269).
Just as Amazon is the only owner of the domain name Amazon.com, only one
person or organization can own a bucket.
bundling A commonly used term for creating an Amazon Machine Image (AMI) (p. 268). It
specifically refers to creating instance store-backed AMI (p. 291)s.
C
Z (p. 314)
cache cluster A logical cache distributed over multiple cache node (p. 278)s. A cache cluster
can be set up with a specific number of cache nodes.
cache cluster identifier Customer-supplied identifier for the cache cluster that must be unique for that
customer in an AWS Region (p. 302).
cache engine version The version of the Memcached service that is running on the cache node.
cache node A fixed-size chunk of secure, network-attached RAM. Each cache node runs an
instance of the Memcached service, and has its own DNS name and port. Multiple
types of cache nodes are supported, each with varying amounts of associated
memory.
cache node type An EC2 instance (p. 285) type used to run the cache node.
cache parameter group A container for cache engine parameter values that can be applied to one or more
cache clusters.
cache security group A group maintained by ElastiCache that combines ingress authorizations to cache
nodes for hosts belonging to Amazon EC2 (p. 267) security group (p. 306)s
specified through the console or the API or command line tools.
canned access policy A standard access control policy that you can apply to a bucket (p. 277)
or object. Options include: private, public-read, public-read-write, and
authenticated-read.
canonicalization The process of converting data into a standard format that a service such as
Amazon S3 (p. 269) can recognize.
capacity The amount of available compute size at a given time. Each Auto Scaling
group (p. 271) is defined with a minimum and maximum compute size. A scaling
activity (p. 305) increases or decreases the capacity within the defined minimum
and maximum values.
cartesian product processor A processor that calculates a cartesian product. Also known as a cartesian data
processor.
cartesian product A mathematical operation that returns a product from multiple sets.
CDN See content delivery network (CDN).
certificate A credential that some AWS products use to authenticate AWS account (p. 265)s
and users. Also known as an X.509 certificate (p. 314) . The certificate is paired
with a private key.
Version 1.0
278
chargeable resources Features or services whose use incurs fees. Although some AWS products are
free, others include charges. For example, in an AWS CloudFormation (p. 272)
stack (p. 308), AWS resource (p. 303)s that have been created incur charges.
The amount charged depends on the usage load. Use the Amazon Web Services
Simple Monthly Calculator at http://calculator.s3.amazonaws.com/calc5.html to
estimate your cost prior to creating instances, stacks, or other resources.
CIDR block Classless Inter-Domain Routing. An internet protocol address allocation and route
aggregation methodology.
See Also Classless Inter-Domain Routing in Wikipedia.
ciphertext Information that has been encrypted (p. 286), as opposed to plaintext (p. 299),
which is information that has not.
ClassicLink A feature for linking an EC2-Classic instance (p. 291) to a VPC (p. 314),
allowing your EC2-Classic instance to communicate with VPC instances using
private IP addresses.
See Also link to VPC, unlink from VPC.
classification In machine learning, a type of problem that seeks to place (classify) a data sample
into a single category or “class.” Often, classification problems are modeled to
choose one category (class) out of two. These are binary classification problems.
Problems where more than two categories (classes) are available are called
"multiclass classification" problems.
See Also binary classification model, multiclass classification model.
cloud service provider A company that provides subscribers with access to internet-hosted computing,
storage, and software services.
CloudHub See AWS VPN CloudHub.
CLI See AWS Command Line Interface (AWS CLI).
cluster A logical grouping of container instance (p. 280)s that you can place
task (p. 311)s on.
Amazon Elasticsearch Service (Amazon ES) (p. 267): A logical grouping of one or
more data nodes, optional dedicated master nodes, and storage required to run
Amazon Elasticsearch Service (Amazon ES) and operate your Amazon ES domain.
See Also data node, dedicated master node, node.
cluster compute instance A type of instance (p. 291) that provides a great amount of CPU power
coupled with increased networking performance, making it well suited for High
Performance Compute (HPC) applications and other demanding network-bound
applications.
cluster placement group A logical cluster compute instance (p. 279) grouping to provide lower latency
and high-bandwidth connectivity between the instance (p. 291)s.
cluster status Amazon Elasticsearch Service (Amazon ES) (p. 267): An indicator of the health
of a cluster. A status can be green, yellow, or red. At the shard level, green means
that all shards are allocated to nodes in a cluster, yellow means that the primary
shard is allocated but the replica shards are not, and red means that the primary
and replica shards of at least one index are not allocated. The shard status
determines the index status, and the index status determines the cluster status.
CMK See customer master key (CMK).
CNAME Canonical Name Record. A type of resource record (p. 303) in the Domain
Name System (DNS) that specifies that the domain name is an alias of another,
Version 1.0
279
canonical domain name. More simply, it is an entry in a DNS table that lets you
alias one fully qualified domain name to another.
complaint The event in which a recipient (p. 302) who does not want to receive an email
message clicks "Mark as Spam" within the email client, and the internet service
provider (p. 291) sends a notification to Amazon SES (p. 269).
compound query Amazon CloudSearch (p. 266): A search request that specifies multiple search
criteria using the Amazon CloudSearch structured search syntax.
condition IAM (p. 274): Any restriction or detail about a permission. The condition is D in
the statement "A has permission to do B to C where D applies."
AWS WAF (p. 276): A set of attributes that AWS WAF searches for in web
requests to AWS resource (p. 303)s such as Amazon CloudFront (p. 266)
distributions. Conditions can include values such as the IP addresses that web
requests originate from or values in request headers. Based on the specified
conditions, you can configure AWS WAF to allow or block web requests to AWS
resources.
conditional parameter See mapping.
configuration API Amazon CloudSearch (p. 266): The API call that you use to create, configure, and
manage search domains.
configuration template A series of key–value pairs that define parameters for various AWS products so
that AWS Elastic Beanstalk (p. 273) can provision them for an environment.
consistency model The method a service uses to achieve high availability. For example, it could
involve replicating data across multiple servers in a data center.
See Also eventual consistency.
console See AWS Management Console.
consolidated billing A feature of the AWS Organizations service for consolidating payment for
multiple AWS accounts. You create an organization that contains your AWS
accounts, and you use the master account of your organization to pay for all
member accounts. You can see a combined view of AWS costs that are incurred
by all accounts in your organization, and you can get detailed cost reports for
individual accounts.
container A Linux container that was created from a Docker image as part of a
task (p. 311).
container definition Specifies which Docker image (p. 284) to use for a container (p. 280), how
much CPU and memory the container is allocated, and more options. The
container definition is included as part of a task definition (p. 311).
container instance An EC2 instance (p. 285) that is running the Amazon Elastic Container Service
(Amazon ECS) (p. 267) agent and has been registered into a cluster (p. 279).
Amazon ECS task (p. 311)s are placed on active container instances.
container registry Stores, manages, and deploys Docker image (p. 284)s.
content delivery network A web service that speeds up distribution of your static and dynamic web content
(CDN) —such as .html, .css, .js, media files, and image files—to your users by using
a worldwide network of data centers. When a user requests your content, the
request is routed to the data center that provides the lowest latency (time delay).
If the content is already in the location with the lowest latency, the CDN delivers
it immediately. If not, the CDN retrieves it from an origin that you specify (for
Version 1.0
280
example, a web server or an Amazon S3 bucket). With some CDNs, you can help
secure your content by configuring an HTTPS connection between users and data
centers, and between data centers and your origin. Amazon CloudFront is an
example of a CDN.
continuous delivery A software development practice in which code changes are automatically built,
tested, and prepared for a release to production.
See Also https://aws.amazon.com/devops/continuous-delivery/.
continuous integration A software development practice in which developers regularly merge code
changes into a central repository, after which automated builds and tests are run.
See Also https://aws.amazon.com/devops/continuous-integration/.
cooldown period Amount of time during which Auto Scaling (p. 271) does not allow the desired
size of the Auto Scaling group (p. 271) to be changed by any other notification
from an Amazon CloudWatch (p. 266) alarm (p. 265).
core node An EC2 instance (p. 285) that runs Hadoop (p. 289) map and reduce tasks and
stores data using the Hadoop Distributed File System (HDFS). Core nodes are
managed by the master node (p. 295), which assigns Hadoop tasks to nodes and
monitors their status. The EC2 instances you assign as core nodes are capacity
that must be allotted for the entire job flow run. Because core nodes store data,
you can't remove them from a job flow. However, you can add more core nodes to
a running job flow.
Core nodes run both the DataNodes and TaskTracker Hadoop daemons.
corpus Amazon CloudSearch (p. 266): A collection of data that you want to search.
credential helper AWS CodeCommit (p. 272): A program that stores credentials for repositories
and supplies them to Git when making connections to those repositories. The
AWS CLI (p. 272) includes a credential helper that you can use with Git when
connecting to AWS CodeCommit repositories.
credentials Also called access credentials or security credentials. In authentication and

authorization, a system uses credentials to identify who is making a call and
whether to allow the requested access. In AWS, these credentials are typically the
access key ID (p. 264) and the secret access key (p. 306).
cross-account access The process of permitting limited, controlled use of resource (p. 303)s in one
AWS account (p. 265) by a user in another AWS account. For example, in AWS
CodeCommit (p. 272) and AWS CodeDeploy (p. 272) you can configure cross-
account access so that a user in AWS account A can access an AWS CodeCommit
repository created by account B. Or a pipeline in AWS CodePipeline (p. 272)
created by account A can use AWS CodeDeploy resources created by account B. In
IAM (p. 274) you use a role (p. 304) to delegate (p. 283) temporary access to
a user (p. 312) in one account to resources in another.
cross-Region replication A client-side solution for maintaining identical copies of Amazon

DynamoDB (p. 266) tables across different AWS Region (p. 302)s, in near real
time.
customer gateway A router or software application on your side of a VPN tunnel that is managed
by Amazon VPC (p. 269). The internal interfaces of the customer gateway are
attached to one or more devices in your home network. The external interface is
attached to the virtual private gateway (p. 313) across the VPN tunnel.
customer managed policy An IAM (p. 274) managed policy (p. 294) that you create and manage in your
AWS account (p. 265).
Version 1.0
281
customer master key (CMK) The fundamental resource (p. 303) that AWS Key Management Service (AWS
KMS) (p. 274) manages. CMKs can be either customer managed keys or AWS
managed keys. Use CMKs inside AWS KMS to encrypt (p. 286) or decrypt up to 4
kilobytes of data directly or to encrypt generated data keys, which are then used
to encrypt or decrypt larger amounts of data outside of the service.
D
Z (p. 314)
dashboard See service health dashboard.
data consistency A concept that describes when data is written or updated successfully and
all copies of the data are updated in all AWS Region (p. 302)s. However, it
takes time for the data to propagate to all storage locations. To support varied
application requirements, Amazon DynamoDB (p. 266) supports both eventually
consistent and strongly consistent reads.
See Also eventual consistency, eventually consistent read, strongly consistent
read.
data node Amazon Elasticsearch Service (Amazon ES) (p. 267): An Elasticsearch instance
that holds data and responds to data upload requests.
See Also dedicated master node, node.
data schema See schema.
data source The database, file, or repository that provides information required by an
application or database. For example, in AWS OpsWorks (p. 274), valid data
sources include an instance (p. 291) for a stack’s MySQL layer or a stack’s
Amazon RDS (p. 269) service layer. In Amazon Redshift (p. 269), valid data
sources include text files in an Amazon S3 (p. 269) bucket (p. 277), in an
Amazon EMR (p. 267) cluster, or on a remote host that a cluster can access
through an SSH connection.
See Also datasource.
database engine The database software and version running on the DB instance (p. 282).
database name The name of a database hosted in a DB instance (p. 282). A DB instance can host
multiple databases, but databases hosted by the same DB instance must each
have a unique name within that instance.
datasource Amazon Machine Learning (p. 268): An object that contains metadata about the
input data. Amazon ML reads the input data, computes descriptive statistics on its
attributes, and stores the statistics—along with a schema and other information
—as part of the datasource object. Amazon ML uses datasources to train and
evaluate a machine learning model and generate batch predictions.
See Also data source.
DB compute class Size of the database compute platform used to run the instance.
DB instance An isolated database environment running in the cloud. A DB instance can contain
multiple user-created databases.
DB instance identifier User-supplied identifier for the DB instance. The identifier must be unique for
that user in an AWS Region (p. 302).
Version 1.0
282
DB parameter group A container for database engine parameter values that apply to one or more DB
instance (p. 282)s.
DB security group A method that controls access to the DB instance (p. 282). By default, network
access is turned off to DB instances. After ingress is configured for a security
group (p. 306), the same rules apply to all DB instances associated with that
group.
DB snapshot A user-initiated point backup of a DB instance (p. 282).
Dedicated Host A physical server with EC2 instance (p. 285) capacity fully dedicated to a user.
Dedicated Instance An instance (p. 291) that is physically isolated at the host hardware level and
launched within a VPC (p. 314).
dedicated master node Amazon Elasticsearch Service (Amazon ES) (p. 267): An Elasticsearch instance
that performs cluster management tasks, but does not hold data or respond to
data upload requests. Amazon Elasticsearch Service (Amazon ES) uses dedicated
master nodes to increase cluster stability.
See Also data node, node.
Dedicated Reserved Instance An option that you purchase to guarantee that sufficient capacity will be available
to launch Dedicated Instance (p. 283)s into a VPC (p. 314).
delegation Within a single AWS account (p. 265): Giving AWS user (p. 312)s access to
resource (p. 303)s in your AWS account.
Between two AWS accounts: Setting up a trust between the account that owns
the resource (the trusting account), and the account that contains the users that
need to access the resource (the trusted account).
See Also trust policy.
delete marker An object with a key and version ID, but without content. Amazon S3 (p. 269)
inserts delete markers automatically into versioned bucket (p. 277)s when an
object is deleted.
deliverability The likelihood that an email message will arrive at its intended destination.
deliveries The number of email messages, sent through Amazon SES (p. 269), that
were accepted by an internet service provider (p. 291) for delivery to
recipient (p. 302)s over a period of time.
deny The result of a policy (p. 299) statement that includes deny as the effect, so
that a specific action or actions are expressly forbidden for a user, group, or role.
Explicit deny take precedence over explicit allow (p. 265).
deployment configuration AWS CodeDeploy (p. 272): A set of deployment rules and success and failure
conditions used by the service during a deployment.
deployment group AWS CodeDeploy (p. 272): A set of individually tagged instance (p. 291)s, EC2
instance (p. 285)s in Auto Scaling group (p. 271)s, or both.
detailed monitoring Monitoring of AWS provided metrics derived at a 1-minute frequency.
Description property A property added to parameters, resource (p. 303)s, resource properties,
mappings, and outputs to help you to document AWS CloudFormation (p. 272)
template elements.
dimension A name–value pair (for example, InstanceType=m1.small, or EngineName=mysql),

that contains additional information to identify a metric.
Version 1.0
283
discussion forums A place where AWS users can post technical questions and feedback to help
accelerate their development efforts and to engage with the AWS community.
The discussion forums are located at https://aws.amazon.com/forums/.
distribution A link between an origin server (such as an Amazon S3 (p. 269)

bucket (p. 277)) and a domain name, which CloudFront (p. 266) automatically
assigns. Through this link, CloudFront identifies the object you have stored in your
origin server (p. 298).
DKIM DomainKeys Identified Mail. A standard that email senders use to sign their
messages. ISPs use those signatures to verify that messages are legitimate. For
more information, see http://www.dkim.org.
DNS See Domain Name System.
Docker image A layered file system template that is the basis of a Docker container (p. 280).
Docker images can comprise specific operating systems or applications.
document Amazon CloudSearch (p. 266): An item that can be returned as a search result.
Each document has a collection of fields that contain the data that can be
searched or returned. The value of a field can be either a string or a number. Each
document must have a unique ID and at least one field.
document batch Amazon CloudSearch (p. 266): A collection of add and delete document
operations. You use the document service API to submit batches to update the
data in your search domain.
document service API Amazon CloudSearch (p. 266): The API call that you use to submit document
batches to update the data in a search domain.
document service endpoint Amazon CloudSearch (p. 266): The URL that you connect to when sending
document updates to an Amazon CloudSearch domain. Each search domain has
a unique document service endpoint that remains the same for the life of the
domain.
domain Amazon Elasticsearch Service (Amazon ES) (p. 267): The hardware, software,
and data exposed by Amazon Elasticsearch Service (Amazon ES) endpoints.
An Amazon ES domain is a service wrapper around an Elasticsearch cluster. An
Amazon ES domain encapsulates the engine instances that process Amazon ES
requests, the indexed data that you want to search, snapshots of the domain,
access policies, and metadata.
See Also cluster, Elasticsearch.
Domain Name System A service that routes internet traffic to websites by translating friendly domain
names like www.example.com into the numeric IP addresses like 192.0.2.1 that
computers use to connect to each other.
Donation button An HTML-coded button to provide an easy and secure way for US-based, IRS-
certified 501(c)3 nonprofit organizations to solicit donations.
DynamoDB stream An ordered flow of information about changes to items in anAmazon

DynamoDB (p. 266) table. When you enable a stream on a table, DynamoDB
captures information about every modification to data items in the table.
See Also Amazon DynamoDB Streams.
E
Version 1.0
284
Z (p. 314)
EBS See Amazon Elastic Block Store (Amazon EBS).
EC2 See Amazon Elastic Compute Cloud (Amazon EC2).
EC2 compute unit An AWS standard for compute CPU and memory. You can use this measure to
evaluate the CPU capacity of different EC2 instance (p. 285) types.
EC2 instance A compute instance (p. 291) in the Amazon EC2 (p. 267) service. Other AWS
services use the term EC2 instance to distinguish these instances from other types
of instances they support.
ECR See Amazon Elastic Container Registry (Amazon ECR).
ECS See Amazon Elastic Container Service (Amazon ECS).
edge location A site that CloudFront (p. 266) uses to cache copies of your content for faster
delivery to users at any location.
EFS See Amazon Elastic File System (Amazon EFS).
Elastic A company that provides open-source solutions—including Elasticsearch,

Logstash, Kibana, and Beats—that are designed to take data from any source and
search, analyze, and visualize it in real time.
Amazon Elasticsearch Service (Amazon ES) is an AWS managed service for

deploying, operating, and scaling Elasticsearch in the AWS Cloud.
See Also Amazon Elasticsearch Service (Amazon ES), Elasticsearch.
Elastic Block Store See Amazon Elastic Block Store (Amazon EBS).
Elastic IP address A fixed (static) IP address that you have allocated in Amazon EC2 (p. 267) or
Amazon VPC (p. 269) and then attached to an instance (p. 291). Elastic IP
addresses are associated with your account, not a specific instance. They are
elastic because you can easily allocate, attach, detach, and free them as your
needs change. Unlike traditional static IP addresses, Elastic IP addresses allow you
to mask instance or Availability Zone (p. 271) failures by rapidly remapping your
public IP addresses to another instance.
Elastic Load Balancing A web service that improves an application's availability by distributing incoming
traffic between two or more EC2 instance (p. 285)s.
See Also https://aws.amazon.com/elasticloadbalancing.
elastic network interface An additional network interface that can be attached to an instance (p. 291).
Elastic network interfaces include a primary private IP address, one or more
secondary private IP addresses, an elastic IP address (optional), a MAC address,
membership in specified security group (p. 306)s, a description, and a source/
destination check flag. You can create an elastic network interface, attach it to an
instance, detach it from an instance, and attach it to another instance.
Elasticsearch An open source, real-time distributed search and analytics engine used for full-
text search, structured search, and analytics. Elasticsearch was developed by the
Elastic company.
Amazon Elasticsearch Service (Amazon ES) is an AWS managed service for

deploying, operating, and scaling Elasticsearch in the AWS Cloud.
See Also Amazon Elasticsearch Service (Amazon ES), Elastic.
EMR See Amazon EMR (Amazon EMR).
Version 1.0
285
encrypt To use a mathematical algorithm to make data unintelligible to unauthorized

user (p. 312)s while allowing authorized users a method (such as a key or
password) to convert the altered data back to its original state.
encryption context A set of key–value pairs that contains additional information associated with AWS
Key Management Service (AWS KMS) (p. 274)–encrypted information.
endpoint A URL that identifies a host and port as the entry point for a web service. Every
web service request contains an endpoint. Most AWS products provide endpoints
for a Region to enable faster connectivity.
Amazon ElastiCache (p. 267): The DNS name of a cache node (p. 278).
Amazon RDS (p. 269): The DNS name of a DB instance (p. 282).
AWS CloudFormation (p. 272): The DNS name or IP address of the server that
receives an HTTP request.
endpoint port Amazon ElastiCache (p. 267): The port number used by a cache node (p. 278).
Amazon RDS (p. 269): The port number used by a DB instance (p. 282).
envelope encryption The use of a master key and a data key to algorithmically protect data. The
master key is used to encrypt and decrypt the data key and the data key is used to
encrypt and decrypt the data itself.
environment AWS Elastic Beanstalk (p. 273): A specific running instance of an

application (p. 270). The application has a CNAME and includes an application
version and a customizable configuration (which is inherited from the default
container type).
AWS CodeDeploy (p. 272): Instances in a deployment group in a blue/green

deployment. At the start of a blue/green deployment, the deployment group is
made up of instances in the original environment. At the end of the deployment,
the deployment group is made up of instances in the replacement environment.
environment configuration A collection of parameters and settings that define how an environment and its
associated resources behave.
ephemeral store See instance store.
epoch The date from which time is measured. For most Unix environments, the epoch is
January 1, 1970.
ETL See extract, transform, and load (ETL).
evaluation Amazon Machine Learning: The process of measuring the predictive performance
of a machine learning (ML) model.
Also a machine learning object that stores the details and result of an ML model
evaluation.
evaluation datasource The data that Amazon Machine Learning uses to evaluate the predictive accuracy
of a machine learning model.
eventual consistency The method through which AWS products achieve high availability, which involves
replicating data across multiple servers in Amazon's data centers. When data is
written or updated and Success is returned, all copies of the data are updated.
However, it takes time for the data to propagate to all storage locations. The data
will eventually be consistent, but an immediate read might not show the change.
Consistency is usually reached within seconds.
Version 1.0
286
See Also data consistency, eventually consistent read, strongly consistent read.
eventually consistent read A read process that returns data from only one region and might not show the
most recent write information. However, if you repeat your read request after a
short time, the response should eventually return the latest data.
See Also data consistency, eventual consistency, strongly consistent read.
eviction The deletion by CloudFront (p. 266) of an object from an edge

location (p. 285) before its expiration time. If an object in an edge location
isn't frequently requested, CloudFront might evict the object (remove the object
before its expiration date) to make room for objects that are more popular.
exbibyte A contraction of exa binary byte, an exbibyte is 2^60 or

1,152,921,504,606,846,976 bytes. An exabyte (EB) is 10^18 or
1,000,000,000,000,000,000 bytes. 1,024 EiB is a zebibyte (p. 314).
expiration For CloudFront (p. 266) caching, the time when CloudFront stops responding
to user requests with an object. If you don't use headers or CloudFront
distribution (p. 284) settings to specify how long you want objects to stay in
an edge location (p. 285), the objects expire after 24 hours. The next time a
user requests an object that has expired, CloudFront forwards the request to the
origin (p. 298).
explicit launch permission An Amazon Machine Image (AMI) (p. 268) launch permission granted to a
specific AWS account (p. 265).
exponential backoff A strategy that incrementally increases the wait between retry attempts in order
to reduce the load on the system and increase the likelihood that repeated
requests will succeed. For example, client applications might wait up to 400
milliseconds before attempting the first retry, up to 1600 milliseconds before the
second, up to 6400 milliseconds (6.4 seconds) before the third, and so on.
expression Amazon CloudSearch (p. 266): A numeric expression that you can use to control
how search hits are sorted. You can construct Amazon CloudSearch expressions
using numeric fields, other rank expressions, a document's default relevance
score, and standard numeric operators and functions. When you use the sort
option to specify an expression in a search request, the expression is evaluated for
each search hit and the hits are listed according to their expression values.
extract, transform, and load A process that is used to integrate data from multiple sources. Data is collected
(ETL) from sources (extract), converted to an appropriate format (transform), and
written to a target data store (load) for purposes of analysis and querying.
ETL tools combine these three functions to consolidate and move data from one
environment to another. AWS Glue (p. 273) is a fully managed ETL service for
discovering and organizing data, transforming it, and making it available for
search and analytics.
F
Z (p. 314)
facet Amazon CloudSearch (p. 266): An index field that represents a category that you
want to use to refine and filter search results.
Version 1.0
287
facet enabled Amazon CloudSearch (p. 266): An index field option that enables facet
information to be calculated for the field.
FBL See feedback loop.
feature transformation Amazon Machine Learning: The machine learning process of constructing more
predictive input representations or “features” from the raw input variables to
optimize a machine learning model’s ability to learn and generalize. Also known
as data transformation or feature engineering.
federated identity Allows individuals to sign in to different networks or services, using the same
management group or personal credentials to access data across all networks. With identity
federation in AWS, external identities (federated users) are granted secure access
to resource (p. 303)s in an AWS account (p. 265) without having to create IAM
user (p. 312)s. These external identities can come from a corporate identity
store (such as LDAP or Windows Active Directory) or from a third party (such as
Login with Amazon, Facebook, or Google). AWS federation also supports SAML
2.0.
federated user See federated identity management.
federation See federated identity management.
feedback loop The mechanism by which a mailbox provider (for example, an internet service
provider (p. 291)) forwards a recipient (p. 302)'s complaint (p. 280) back to
the sender (p. 306).
field weight The relative importance of a text field in a search index. Field weights control how
much matches in particular text fields affect a document's relevance score.
filter A criterion that you specify to limit the results when you list or describe your
Amazon EC2 (p. 267) resource (p. 303)s.
filter query A way to filter search results without affecting how the results are scored and
sorted. Specified with the Amazon CloudSearch (p. 266) fq parameter.
FIM See federated identity management.
Firehose See Amazon Kinesis Data Firehose.
format version See template format version.
forums See discussion forums.
function See intrinsic function.
fuzzy search A simple search query that uses approximate string matching (fuzzy matching) to
correct for typographical errors and misspellings.
G
Z (p. 314)
geospatial search A search query that uses locations specified as a latitude and longitude to
determine matches and sort the results.
Version 1.0
288
gibibyte A contraction of giga binary byte, a gibibyte is 2^30 or 1,073,741,824 bytes. A

gigabyte (GB) is 10^9 or 1,000,000,000 bytes. 1,024 GiB is a tebibyte (p. 311).
GitHub A web-based repository that uses Git for version control.
global secondary index An index with a partition key and a sort key that can be different from those on
the table. A global secondary index is considered global because queries on the
index can span all of the data in a table, across all partitions.
See Also local secondary index.
grant AWS Key Management Service (AWS KMS) (p. 274): A mechanism for giving
AWS principal (p. 300)s long-term permissions to use customer master key
(CMK) (p. 282)s.
grant token A type of identifier that allows the permissions in a grant (p. 289) to take effect
immediately.
ground truth The observations used in the machine learning (ML) model training process
that include the correct value for the target attribute. To train an ML model to
predict house sales prices, the input observations would typically include prices
of previous house sales in the area. The sale prices of these houses constitute the
ground truth.
group A collection of IAM (p. 274) user (p. 312)s. You can use IAM groups to simplify
specifying and managing permissions for multiple users.
H
Z (p. 314)
Hadoop Software that enables distributed processing for big data by using clusters
and simple programming models. For more information, see http://
hadoop.apache.org.
hard bounce A persistent email delivery failure such as "mailbox does not exist."
hardware VPN A hardware-based IPsec VPN connection over the internet.
health check A system call to check on the health status of each instance in an Auto
Scaling (p. 271) group.
high-quality email Email that recipients find valuable and want to receive. Value means different
things to different recipients and can come in the form of offers, order
confirmations, receipts, newsletters, etc.
highlights Amazon CloudSearch (p. 266): Excerpts returned with search results that show
where the search terms appear within the text of the matching documents.
highlight enabled Amazon CloudSearch (p. 266): An index field option that enables matches within
the field to be highlighted.
hit A document that matches the criteria specified in a search request. Also referred
to as a search result.
HMAC Hash-based Message Authentication Code. A specific construction for calculating

a message authentication code (MAC) involving a cryptographic hash function in
combination with a secret key. You can use it to verify both the data integrity and
Version 1.0
289
the authenticity of a message at the same time. AWS calculates the HMAC using a
standard, cryptographic hash algorithm, such as SHA-256.
hosted zone A collection of resource record (p. 303) sets that Amazon Route 53 (p. 269)
hosts. Like a traditional DNS zone file, a hosted zone represents a collection of
records that are managed together under a single domain name.
HVM virtualization Hardware Virtual Machine virtualization. Allows the guest VM to run as though it
is on a native hardware platform, except that it still uses paravirtual (PV) network
and storage drivers for improved performance.
See Also PV virtualization.
I
Z (p. 314)
IAM See AWS Identity and Access Management (IAM).
IAM group See group.
IAM policy simulator See policy simulator.
IAM role See role.
IAM user See user.
Identity and Access See AWS Identity and Access Management (IAM).
Management
identity provider (IdP) An IAM (p. 274) entity that holds metadata about external identity providers.
IdP See identity provider (IdP) .
image See Amazon Machine Image (AMI).
import/export station A machine that uploads or downloads your data to or from Amazon S3 (p. 269).
import log A report that contains details about how AWS Import/Export (p. 274) processed
your data.
in-place deployment AWS CodeDeploy: A deployment method in which the application on each
instance in the deployment group is stopped, the latest application revision is
installed, and the new version of the application is started and validated. You
can choose to use a load balancer so each instance is deregistered during its
deployment and then restored to service after the deployment is complete.
index See search index.
index field A name–value pair that is included in an Amazon CloudSearch (p. 266) domain's
index. An index field can contain text or numeric data, dates, or a location.
indexing options Configuration settings that define an Amazon CloudSearch (p. 266) domain's
index fields, how document data is mapped to those index fields, and how the
index fields can be used.
inline policy An IAM (p. 274) policy (p. 299) that is embedded in a single IAM
user (p. 312), group (p. 289), or role (p. 304).
Version 1.0
290
input data Amazon Machine Learning: The observations that you provide to Amazon
Machine Learning to train and evaluate a machine learning model and generate
predictions.
instance A copy of an Amazon Machine Image (AMI) (p. 268) running as a virtual server in
the AWS cloud.
instance family A general instance type (p. 291) grouping using either storage or CPU capacity.
instance group A Hadoop (p. 289) cluster contains one master instance group that contains
one master node (p. 295), a core instance group containing one or more core
node (p. 281) and an optional task node (p. 311) instance group, which can
contain any number of task nodes.
instance profile A container that passes IAM (p. 274) role (p. 304) information to an EC2
instance (p. 285) at launch.
instance store Disk storage that is physically attached to the host computer for an EC2
instance (p. 285), and therefore has the same lifespan as the instance. When the
instance is terminated, you lose any data in the instance store.
instance store-backed AMI A type of Amazon Machine Image (AMI) (p. 268) whose instance (p. 291)s use
an instance store (p. 291) volume (p. 313) as the root device. Compare this
with instances launched from Amazon EBS (p. 266)-backed AMIs, which use an
Amazon EBS volume as the root device.
instance type A specification that defines the memory, CPU, storage capacity, and usage
cost for an instance (p. 291). Some instance types are designed for standard
applications, whereas others are designed for CPU-intensive, memory-intensive
applications, and so on.
internet gateway Connects a network to the internet. You can route traffic for IP addresses outside
your VPC (p. 314) to the internet gateway.
internet service provider A company that provides subscribers with access to the internet. Many ISPs are
also mailbox provider (p. 294)s. Mailbox providers are sometimes referred to as
ISPs, even if they only provide mailbox services.
intrinsic function A special action in a AWS CloudFormation (p. 272) template that assigns values
to properties not available until runtime. These functions follow the format
Fn::Attribute, such as Fn::GetAtt. Arguments for intrinsic functions can be
parameters, pseudo parameters, or the output of other intrinsic functions.
IP address A numerical address (for example, 192.0.2.44) that networked devices use
to communicate with one another using the Internet Protocol (IP). All EC2
instance (p. 285)s are assigned two IP addresses at launch, which are directly
mapped to each other through network address translation (NAT (p. 296)):
a private IP address (following RFC 1918) and a public IP address. Instances
launched in a VPC (p. 269) are assigned only a private IP address. Instances
launched in your default VPC are assigned both a private IP address and a public
IP address.
IP match condition AWS WAF (p. 276): An attribute that specifies the IP addresses or IP
address ranges that web requests originate from. Based on the specified IP
addresses, you can configure AWS WAF to allow or block web requests to AWS
resource (p. 303)s such as Amazon CloudFront (p. 266) distributions.
ISP See internet service provider.
issuer The person who writes a policy (p. 299) to grant permissions to a
resource (p. 303). The issuer (by definition) is always the resource owner. AWS
Version 1.0
291
does not permit Amazon SQS (p. 269) users to create policies for resources they
don't own. If John is the resource owner, AWS authenticates John's identity when
he submits the policy he's written to grant permissions for that resource.
item A group of attributes that is uniquely identifiable among all of the other items.
Items in Amazon DynamoDB (p. 266) are similar in many ways to rows, records,
or tuples in other database systems.
J
Z (p. 314)
job flow Amazon EMR (p. 267): One or more step (p. 309)s that specify all of the
functions to be performed on the data.
job ID A five-character, alphanumeric string that uniquely identifies an AWS Import/

Export (p. 274) storage device in your shipment. AWS issues the job ID in
response to a CREATE JOB email command.
job prefix An optional string that you can add to the beginning of an AWS Import/
Export (p. 274) log file name to prevent collisions with objects of the same
name.
See Also key prefix.
JSON JavaScript Object Notation. A lightweight data interchange format. For

information about JSON, see http://www.json.org/.
junk folder The location where email messages that various filters determine to be of lesser
value are collected so that they do not arrive in the recipient (p. 302)'s inbox but
are still accessible to the recipient. This is also referred to as a spam (p. 308) or
bulk folder.
K
Z (p. 314)
key A credential that identifies an AWS account (p. 265) or user (p. 312) to AWS
(such as the AWS secret access key (p. 306)).
Amazon Simple Storage Service (Amazon S3) (p. 269), Amazon EMR (Amazon
EMR) (p. 267): The unique identifier for an object in a bucket (p. 277).
Every object in a bucket has exactly one key. Because a bucket and key
together uniquely identify each object, you can think of Amazon S3 as a
basic data map between the bucket + key, and the object itself. You can
uniquely address every object in Amazon S3 through the combination of the
web service endpoint, bucket name, and key, as in this example: http://
doc.s3.amazonaws.com/2006-03-01/AmazonS3.wsdl, where doc is the
name of the bucket, and 2006-03-01/AmazonS3.wsdl is the key.
AWS Import/Export (p. 274): The name of an object in Amazon S3. It is a

sequence of Unicode characters whose UTF-8 encoding cannot exceed 1024
Version 1.0
292
bytes. If a key, for example, logPrefix + import-log-JOBID, is longer than 1024

bytes, AWS Elastic Beanstalk (p. 273) returns an InvalidManifestField
error.
IAM (p. 274): In a policy (p. 299), a specific characteristic that is the basis for
restricting access (such as the current time, or the IP address of the requester).
Tagging resources: A general tag (p. 310) label that acts like a category for more
specific tag values. For example, you might have EC2 instance (p. 285) with the
tag key of Owner and the tag value of Jan. You can tag an AWS resource (p. 303)
with up to 10 key–value pairs. Not all AWS resources can be tagged.
key pair A set of security credentials that you use to prove your identity electronically. A
key pair consists of a private key and a public key.
key prefix A logical grouping of the objects in a bucket (p. 277). The prefix value is similar
to a directory name that enables you to store similar data under the same
directory in a bucket.
kibibyte A contraction of kilo binary byte, a kibibyte is 2^10 or 1,024 bytes. A kilobyte (KB)
is 10^3 or 1,000 bytes. 1,024 KiB is a mebibyte (p. 295).
KMS See AWS Key Management Service (AWS KMS).
L
Z (p. 314)
labeled data In machine learning, data for which you already know the target or “correct”
answer.
launch configuration A set of descriptive parameters used to create new EC2 instance (p. 285)s in an
Auto Scaling (p. 271) activity.
A template that an Auto Scaling group (p. 271) uses to launch new EC2
instances. The launch configuration contains information such as the Amazon
Machine Image (AMI) (p. 268) ID, the instance type, key pairs, security
group (p. 306)s, and block device mappings, among other configuration
settings.
launch permission An Amazon Machine Image (AMI) (p. 268) attribute that allows users to launch
an AMI.
lifecycle The lifecycle state of the EC2 instance (p. 285) contained in an Auto Scaling
group (p. 271). EC2 instances progress through several states over their lifespan;
these include Pending, InService, Terminating and Terminated.
lifecycle action An action that can be paused by Auto Scaling, such as launching or terminating
an EC2 instance.
lifecycle hook Enables you to pause Auto Scaling after it launches or terminates an EC2 instance
so that you can perform a custom action while the instance is not in service.
link to VPC The process of linking (or attaching) an EC2-Classic instance (p. 291) to a
ClassicLink-enabled VPC (p. 314).
See Also ClassicLink, unlink from VPC.
Version 1.0
293
load balancer A DNS name combined with a set of ports, which together provide a destination
for all requests intended for your application. A load balancer can distribute
traffic to multiple application instances across every Availability Zone (p. 271)
within a Region (p. 302). Load balancers can span multiple Availability Zones
within an AWS Region into which an Amazon EC2 (p. 267) instance was
launched. But load balancers cannot span multiple Regions.
local secondary index An index that has the same partition key as the table, but a different sort key. A
local secondary index is local in the sense that every partition of a local secondary
index is scoped to a table partition that has the same partition key value.
See Also local secondary index.
logical name A case-sensitive unique string within an AWS CloudFormation (p. 272) template
that identifies a resource (p. 303), mapping (p. 294), parameter, or output. In
an AWS CloudFormation template, each parameter, resource (p. 303), property,
mapping, and output must be declared with a unique logical name. You use the
logical name when dereferencing these items using the Ref function.
M
Z (p. 314)
Mail Transfer Agent (MTA) Software that transports email messages from one computer to another by using
a client-server architecture.
mailbox provider An organization that provides email mailbox hosting services. Mailbox providers
are sometimes referred to as internet service provider (p. 291)s, even if they
only provide mailbox services.
mailbox simulator A set of email addresses that you can use to test an Amazon SES (p. 269)-based
email sending application without sending messages to actual recipients. Each
email address represents a specific scenario (such as a bounce or complaint) and
generates a typical response that is specific to the scenario.
main route table The default route table (p. 304) that any new VPC (p. 314) subnet (p. 310)
uses for routing. You can associate a subnet with a different route table of your
choice. You can also change which route table is the main route table.
managed policy A standalone IAM (p. 274) policy (p. 299) that you can attach to
multiple user (p. 312)s, group (p. 289)s, and role (p. 304)s in your IAM
account (p. 265). Managed policies can either be AWS managed policies (which
are created and managed by AWS) or customer managed policies (which you
create and manage in your AWS account).
manifest When sending a create job request for an import or export operation, you describe
your job in a text file called a manifest. The manifest file is a YAML-formatted
file that specifies how to transfer data between your storage device and the AWS
cloud.
manifest file Amazon Machine Learning: The file used for describing batch predictions. The
manifest file relates each input data file with its associated batch prediction
results. It is stored in the Amazon S3 output location.
mapping A way to add conditional parameter values to an AWS CloudFormation (p. 272)
template. You specify mappings in the template's optional Mappings section and
retrieve the desired value using the FN::FindInMap function.
Version 1.0
294
marker See pagination token.
master node A process running on an Amazon Machine Image (AMI) (p. 268) that keeps track
of the work its core and task nodes complete.
maximum price The maximum price you will pay to launch one or more Spot Instance (p. 308)s.
If your maximum price exceeds the current Spot price (p. 308) and your
restrictions are met, Amazon EC2 (p. 267) launches instances on your behalf.
maximum send rate The maximum number of email messages that you can send per second using
Amazon SES (p. 269).
mebibyte A contraction of mega binary byte, a mebibyte is 2^20 or 1,048,576 bytes. A

megabyte (MB) is 10^6 or 1,000,000 bytes. 1,024 MiB is a gibibyte (p. 289).
member resources See resource.
message ID Amazon Simple Email Service (Amazon SES) (p. 269): A unique identifier that is
assigned to every email message that is sent.
Amazon Simple Queue Service (Amazon SQS) (p. 269): The identifier returned
when you send a message to a queue.
metadata Information about other data or objects. In Amazon Simple Storage Service
(Amazon S3) (p. 269) and Amazon EMR (Amazon EMR) (p. 267) metadata takes
the form of name–value pairs that describe the object. These include default
metadata such as the date last modified and standard HTTP metadata such as
Content-Type. Users can also specify custom metadata at the time they store
an object. In Amazon Elastic Compute Cloud (Amazon EC2) (p. 267) metadata
includes data about an EC2 instance (p. 285) that the instance can retrieve to
determine things about itself, such as the instance type, the IP address, and so on.
metric An element of time-series data defined by a unique combination of exactly

one namespace (p. 296), exactly one metric name, and between zero and ten
dimensions. Metrics and the statistics derived from them are the basis of Amazon
CloudWatch (p. 266).
metric name The primary identifier of a metric, used in combination with a

namespace (p. 296) and optional dimensions.
MFA See multi-factor authentication (MFA).
micro instance A type of EC2 instance (p. 285) that is more economical to use if you have
occasional bursts of high CPU activity.
MIME See Multipurpose Internet Mail Extensions (MIME).
ML model In machine learning (ML), a mathematical model that generates predictions by

finding patterns in data. Amazon Machine Learning supports three types of ML
models: binary classification, multiclass classification, and regression. Also known
as a predictive model.
See Also binary classification model, multiclass classification model, regression
model.
MTA See Mail Transfer Agent (MTA).
Multi-AZ deployment A primary DB instance (p. 282) that has a synchronous standby replica in a
different Availability Zone (p. 271). The primary DB instance is synchronously
replicated across Availability Zones to the standby replica.
Version 1.0
295
multiclass classification A machine learning model that predicts values that belong to a limited, pre-
model defined set of permissible values. For example, "Is this product a book, movie, or
clothing?"
multi-factor authentication An optional AWS account (p. 265) security feature. Once you enable AWS
(MFA) MFA, you must provide a six-digit, single-use code in addition to your sign-in
credentials whenever you access secure AWS webpages or the AWS Management
Console (p. 274). You get this single-use code from an authentication device
that you keep in your physical possession.
See Also https://aws.amazon.com/mfa/.
multi-valued attribute An attribute with more than one value.
multipart upload A feature that allows you to upload a single object as a set of parts.
Multipurpose Internet Mail An internet standard that extends the email protocol to include non-ASCII text
Extensions (MIME) and nontext elements like attachments.
Multitool A cascading application that provides a simple command-line interface for

managing large datasets.
N
Z (p. 314)
namespace An abstract container that provides context for the items (names, or technical
terms, or words) it holds, and allows disambiguation of homonym items residing
in different namespaces.
NAT Network address translation. A strategy of mapping one or more IP addresses

to another while data packets are in transit across a traffic routing device. This
is commonly used to restrict internet communication to private instances while
allowing outgoing traffic.
See Also Network Address Translation and Protocol Translation, NAT gateway,
NAT instance.
NAT gateway A NAT (p. 296) device, managed by AWS, that performs network address
translation in a private subnet (p. 310), to secure inbound internet traffic. A NAT
gateway uses both NAT and port address translation.
See Also NAT instance.
NAT instance A NAT (p. 296) device, configured by a user, that performs network address
translation in a VPC (p. 314) public subnet (p. 310) to secure inbound internet
traffic.
See Also NAT gateway.
network ACL An optional layer of security that acts as a firewall for controlling traffic in and
out of a subnet (p. 310). You can associate multiple subnets with a single
network ACL (p. 264), but a subnet can be associated with only one network ACL
at a time.
Network Address Translation (NAT (p. 296)-PT) An internet protocol standard defined in RFC 2766.
and Protocol Translation See Also NAT instance, NAT gateway.
n-gram processor A processor that performs n-gram transformations.

See Also n-gram transformation.
Version 1.0
296
n-gram transformation Amazon Machine Learning: A transformation that aids in text string analysis.
An n-gram transformation takes a text variable as input and outputs strings by
sliding a window of size n words, where n is specified by the user, over the text,
and outputting every string of words of size n and all smaller sizes. For example,
specifying the n-gram transformation with window size =2 returns all the two-
word combinations and all of the single words.
node Amazon Elasticsearch Service (Amazon ES) (p. 267): An Elasticsearch instance. A
node can be either a data instance or a dedicated master instance.
See Also dedicated master node.
NoEcho A property of AWS CloudFormation (p. 272) parameters that prevent the
otherwise default reporting of names and values of a template parameter.
Declaring the NoEcho property causes the parameter value to be masked with
asterisks in the report by the cfn-describe-stacks command.
NoSQL Nonrelational database systems that are highly available, scalable, and optimized
for high performance. Instead of the relational model, NoSQL databases (like
Amazon DynamoDB (p. 266)) use alternate models for data management, such
as key–value pairs or document storage.
null object A null object is one whose version ID is null. Amazon S3 (p. 269) adds a null
object to a bucket (p. 277) when versioning (p. 313) for that bucket is
suspended. It is possible to have only one null object for each key in a bucket.
number of passes The number of times that you allow Amazon Machine Learning to use the same
data records to train a machine learning model.
O
Z (p. 314)
object Amazon Simple Storage Service (Amazon S3) (p. 269): The fundamental entity
type stored in Amazon S3. Objects consist of object data and metadata. The data
portion is opaque to Amazon S3.
Amazon CloudFront (p. 266): Any entity that can be served either over HTTP or
a version of RTMP.
observation Amazon Machine Learning: A single instance of data that Amazon Machine
Learning (Amazon ML) uses to either train a machine learning model how to
predict or to generate a prediction. Each row in an Amazon ML input data file is
an observation.
On-Demand Instance An Amazon EC2 (p. 267) pricing option that charges you for compute capacity
by the hour with no long-term commitment.
operation An API function. Also called an action.
optimistic locking A strategy to ensure that an item that you want to update has not been modified
by others before you perform the update. For Amazon DynamoDB (p. 266),
optimistic locking support is provided by the AWS SDKs.
organization AWS Organizations (p. 274): An entity that you create to consolidate and
manage your AWS accounts. An organization has one master account along with
zero or more member accounts.
Version 1.0
297
organizational unit AWS Organizations (p. 274): A container for accounts within a root (p. 304) of
an organization. An organizational unit (OU) can contain other OUs.
origin access identity Also called OAI. When using Amazon CloudFront (p. 266) to serve content with
an Amazon S3 (p. 269) bucket (p. 277) as the origin, a virtual identity that you
use to require users to access your content through CloudFront URLs instead of
Amazon S3 URLs. Usually used with CloudFront private content (p. 300).
origin server The Amazon S3 (p. 269) bucket (p. 277) or custom origin containing
the definitive original version of the content you deliver through
CloudFront (p. 266).
original environment The instances in a deployment group at the start of an AWS CodeDeploy blue/
green deployment.
OSB transformation Orthogonal sparse bigram transformation. In machine learning, a transformation

that aids in text string analysis and that is an alternative to the n-gram
transformation. OSB transformations are generated by sliding the window of size
n words over the text, and outputting every pair of words that includes the first
word in the window.
See Also n-gram transformation.
OU See organizational unit.
output location Amazon Machine Learning: An Amazon S3 location where the results of a batch
prediction are stored.
P
Z (p. 314)
pagination The process of responding to an API request by returning a large list of records in
small separate parts. Pagination can occur in the following situations:
• The client sets the maximum number of returned records to a value below the
total number of records.
• The service has a default maximum number of returned records that is lower
than the total number of records.
When an API response is paginated, the service sends a subset of the large list
of records and a pagination token that indicates that more records are available.
The client includes this pagination token in a subsequent API request, and the
service responds with the next subset of records. This continues until the service
responds with a subset of records and no pagination token, indicating that all
records have been sent.
pagination token A marker that indicates that an API response contains a subset of a larger list of
records. The client can return this marker in a subsequent API request to retrieve
the next subset of records until the service responds with a subset of records and
no pagination token, indicating that all records have been sent.
See Also pagination.
paid AMI An Amazon Machine Image (AMI) (p. 268) that you sell to other Amazon
EC2 (p. 267) users on AWS Marketplace (p. 274).
Version 1.0
298
paravirtual virtualization See PV virtualization.
part A contiguous portion of the object's data in a multipart upload request.
partition key A simple primary key, composed of one attribute (also known as a hash attribute).
See Also partition key, sort key.
PAT Port address translation.
pebibyte A contraction of peta binary byte, a pebibyte is 2^50 or 1,125,899,906,842,624

bytes. A petabyte (PB) is 10^15 or 1,000,000,000,000,000 bytes. 1,024 PiB is an
exbibyte (p. 287).
period See sampling period.
permission A statement within a policy (p. 299) that allows or denies access to a particular
resource (p. 303). You can state any permission like this: "A has permission to do
B to C." For example, Jane (A) has permission to read messages (B) from John's
Amazon SQS (p. 269) queue (C). Whenever Jane sends a request to Amazon
SQS to use John's queue, the service checks to see if she has permission and if the
request satisfies the conditions John set forth in the permission.
persistent storage A data storage solution where the data remains intact until it is deleted. Options
within AWS (p. 270) include: Amazon S3 (p. 269), Amazon RDS (p. 269),
Amazon DynamoDB (p. 266), and other services.
physical name A unique label that AWS CloudFormation (p. 272) assigns to each
resource (p. 303) when creating a stack (p. 308). Some AWS CloudFormation
commands accept the physical name as a value with the --physical-name
parameter.
pipeline AWS CodePipeline (p. 272): A workflow construct that defines the way software
changes go through a release process.
plaintext Information that has not been encrypted (p. 286), as opposed to
ciphertext (p. 279).
policy IAM (p. 274): A document defining permissions that apply to a user, group,
or role; the permissions in turn determine what users can do in AWS. A
policy typically allow (p. 265)s access to specific actions, and can optionally
grant that the actions are allowed for specific resource (p. 303)s, like EC2
instance (p. 285)s, Amazon S3 (p. 269) bucket (p. 277)s, and so on. Policies
can also explicitly deny (p. 283) access.
Auto Scaling (p. 271): An object that stores the information needed to launch
or terminate instances for an Auto Scaling group. Executing the policy causes
instances to be launched or terminated. You can configure an alarm (p. 265) to
invoke an Auto Scaling policy.
policy generator A tool in the IAM (p. 274) AWS Management Console (p. 274) that helps you
build a policy (p. 299) by selecting elements from lists of available options.
policy simulator A tool in the IAM (p. 274) AWS Management Console (p. 274) that helps you
test and troubleshoot policies (p. 299) so you can see their effects in real-world
scenarios.
policy validator A tool in the IAM (p. 274) AWS Management Console (p. 274) that examines
your existing IAM access control policies (p. 299) to ensure that they comply
with the IAM policy grammar.
Version 1.0
299
presigned URL A web address that uses query string authentication (p. 301).
prefix See job prefix.
Premium Support A one-on-one, fast-response support channel that AWS customers can subscribe
to for support for AWS infrastructure services.
See Also https://aws.amazon.com/premiumsupport/.
primary key One or two attributes that uniquely identify each item in a Amazon
DynamoDB (p. 266) table, so that no two items can have the same key.
See Also partition key, sort key.
primary shard See shard.
principal The user (p. 312), service, or account (p. 265) that receives permissions that
are defined in a policy (p. 299). The principal is A in the statement "A has
permission to do B to C."
private content When using Amazon CloudFront (p. 266) to serve content with an Amazon
S3 (p. 269) bucket (p. 277) as the origin, a method of controlling access to
your content by requiring users to use signed URLs. Signed URLs can restrict
user access based on the current date and time and/or the IP addresses that the
requests originate from.
private IP address A private numerical address (for example, 192.0.2.44) that networked devices
use to communicate with one another using the Internet Protocol (IP). All EC2
instance (p. 285)ss are assigned two IP addresses at launch, which are directly
mapped to each other through Network Address Translation (NAT (p. 296)): a
private address (following RFC 1918) and a public address. Exception: Instances
launched in Amazon VPC (p. 269) are assigned only a private IP address.
private subnet A VPC (p. 314) subnet (p. 310) whose instances cannot be reached from the
internet.
product code An identifier provided by AWS when you submit a product to AWS
Marketplace (p. 274).
properties See resource property.
property rule A JSON (p. 292)-compliant markup standard for declaring properties, mappings,
and output values in an AWS CloudFormation (p. 272) template.
Provisioned IOPS A storage option designed to deliver fast, predictable, and consistent I/O
performance. When you specify an IOPS rate while creating a DB instance,
Amazon RDS (p. 269) provisions that IOPS rate for the lifetime of the DB
instance.
pseudo parameter A predefined setting, such as AWS:StackName that can be used in AWS
CloudFormation (p. 272) templates without having to declare them. You can use
pseudo parameters anywhere you can use a regular parameter.
public AMI An Amazon Machine Image (AMI) (p. 268) that all AWS account (p. 265)s have
permission to launch.
public data set A large collection of public information that can be seamlessly integrated into
AWS cloud-based applications. Amazon stores public data sets at no charge to the
community and, like all AWS services, users pay only for the compute and storage
they use for their own applications. These data sets currently include data from
the Human Genome Project, the U.S. Census, Wikipedia, and other sources.
See Also https://aws.amazon.com/publicdatasets.
Version 1.0
300
public IP address A pubic numerical address (for example, 192.0.2.44) that networked devices
use to communicate with one another using the Internet Protocol (IP). EC2
instance (p. 285)s are assigned two IP addresses at launch, which are directly
mapped to each other through Network Address Translation (NAT (p. 296)): a
private address (following RFC 1918) and a public address. Exception: Instances
launched in Amazon VPC (p. 269) are assigned only a private IP address.
public subnet A subnet (p. 310) whose instances can be reached from the internet.
PV virtualization Paravirtual virtualization. Allows guest VMs to run on host systems that do
not have special support extensions for full hardware and CPU virtualization.
Because PV guests run a modified operating system that does not use hardware
emulation, they cannot provide hardware-related features such as enhanced
networking or GPU support.
See Also HVM virtualization.
Q
Z (p. 314)
quartile binning Amazon Machine Learning: A process that takes two inputs, a numerical variable
transformation and a parameter called a bin number, and outputs a categorical variable. Quartile
binning transformations discover non-linearity in a variable's distribution by
enabling the machine learning model to learn separate importance values for
parts of the numeric variable’s distribution.
Query A type of web service that generally uses only the GET or POST HTTP method and
a query string with parameters in the URL.
See Also REST.
query string authentication An AWS feature that lets you place the authentication information in the HTTP
request query string instead of in the Authorization header, which enables
URL-based access to objects in a bucket (p. 277).
queue A sequence of messages or jobs that are held in temporary storage awaiting
transmission or processing.
queue URL A web address that uniquely identifies a queue.
quota Amazon RDS (p. 269): The maximum number of DB instance (p. 282)s and
available storage you can use.
Amazon ElastiCache (p. 267): The maximum number of the following items:
• The number of cache clusters for each AWS account (p. 265)
• The number of cache nodes per cache cluster
• The total number of cache nodes per AWS account across all cache clusters
created by that AWS account
R
Version 1.0
301
Z (p. 314)
range GET A request that specifies a byte range of data to get for a download. If an object is
large, you can break up a download into smaller units by sending multiple range
GET requests that each specify a different byte range to GET.
raw email A type of sendmail request with which you can specify the email headers and
MIME types.
RDS See Amazon Relational Database Service (Amazon RDS).
read replica Amazon RDS (p. 269): An active copy of another DB instance. Any updates to
the data on the source DB instance are replicated to the read replica DB instance
using the built-in replication feature of MySQL 5.1.
real-time predictions Amazon Machine Learning: Synchronously generated predictions for individual
data observations.
See Also batch prediction.
receipt handle Amazon SQS (p. 269): An identifier that you get when you receive a message
from the queue. This identifier is required to delete a message from the queue or
when changing a message's visibility timeout.
receiver The entity that consists of the network systems, software, and policies that
manage email delivery for a recipient (p. 302).
recipient Amazon Simple Email Service (Amazon SES) (p. 269): The person or entity
receiving an email message. For example, a person named in the "To" field of a
message.
Redis A fast, open source, in-memory key-value data structure store. Redis comes with
a set of versatile in-memory data structures with which you can easily create a
variety of custom applications.
reference A means of inserting a property from one AWS resource (p. 303) into another.
For example, you could insert an Amazon EC2 (p. 267) security group (p. 306)
property into an Amazon RDS (p. 269) resource.
Region A named set of AWS resource (p. 303)s in the same geographical area. A Region
comprises at least two Availability Zone (p. 271)s.
regression model Amazon Machine Learning: Preformatted instructions for common data
transformations that fine-tune machine learning model performance.
regression model A type of machine learning model that predicts a numeric value, such as the exact
purchase price of a house.
regularization A machine learning (ML) parameter that you can tune to obtain higher-quality
ML models. Regularization helps prevent ML models from memorizing training
data examples instead of learning how to generalize the patterns it sees (called
overfitting). When training data is overfitted, the ML model performs well on the
training data but does not perform well on the evaluation data or on new data.
replacement environment The instances in a deployment group after the AWS CodeDeploy blue/green
deployment.
replica shard See shard.
reply path The email address to which an email reply is sent. This is different from the return
path (p. 304).
Version 1.0
302
representational state See REST.

transfer
reputation 1. An Amazon SES (p. 269) metric, based on factors that might include
bounce (p. 277)s, complaint (p. 280)s, and other metrics, regarding whether or
not a customer is sending high-quality email.
2. A measure of confidence, as judged by an internet service provider (p. 291) or

other entity that an IP address that they are receiving email from is not the source
of spam (p. 308).
requester The person (or application) that sends a request to AWS to perform a specific
action. When AWS receives a request, it first evaluates the requester's permissions
to determine whether the requester is allowed to perform the request action (if
applicable, for the requested resource (p. 303)).
Requester Pays An Amazon S3 (p. 269) feature that allows a bucket owner (p. 278) to specify
that anyone who requests access to objects in a particular bucket (p. 277) must
pay the data transfer and request costs.
reservation A collection of EC2 instance (p. 285)s started as part of the same launch
request. Not to be confused with a Reserved Instance (p. 303).
Reserved Instance A pricing option for EC2 instance (p. 285)s that discounts the on-
demand (p. 297) usage charge for instances that meet the specified parameters.
Customers pay for the entire term of the instance, regardless of how they use it.
Reserved Instance An online exchange that matches sellers who have reserved capacity that they
Marketplace no longer need with buyers who are looking to purchase additional capacity.
Reserved Instance (p. 303)s that you purchase from third-party sellers have less
than a full standard term remaining and can be sold at different upfront prices.
The usage or reoccurring fees remain the same as the fees set when the Reserved
Instances were originally purchased. Full standard terms for Reserved Instances
available from AWS run for one year or three years.
resource An entity that users can work with in AWS, such as an EC2 instance (p. 285), an
Amazon DynamoDB (p. 266) table, an Amazon S3 (p. 269) bucket (p. 277), an
IAM (p. 274) user, an AWS OpsWorks (p. 274) stack (p. 308), and so on.
resource property A value required when including an AWS resource (p. 303) in an AWS
CloudFormation (p. 272) stack (p. 308). Each resource may have one or more
properties associated with it. For example, an AWS::EC2::Instance resource
may have a UserData property. In an AWS CloudFormation template, resources
must declare a properties section, even if the resource has no properties.
resource record Also called resource record set. The fundamental information elements in the
Domain Name System (DNS).
See Also Domain Name System in Wikipedia.
REST Representational state transfer. A simple stateless architecture that generally runs
over HTTPS/TLS. REST emphasizes that resources have unique and hierarchical
identifiers (URIs), are represented by common media types (HTML, XML,
JSON (p. 292), and so on), and that operations on the resources are either
predefined or discoverable within the media type. In practice, this generally
results in a limited number of operations.
See Also Query, WSDL, SOAP.
RESTful web service Also known as RESTful API. A web service that follows REST (p. 303)
architectural constraints. The API operations must use HTTP methods explicitly;
expose hierarchical URIs; and transfer either XML, JSON (p. 292), or both.
Version 1.0
303
HTTP-Query See Query.
return enabled Amazon CloudSearch (p. 266): An index field option that enables the field's
values to be returned in the search results.
return path The email address to which bounced email is returned. The return path is
specified in the header of the original email. This is different from the reply
path (p. 302).
revision AWS CodePipeline (p. 272): A change made to a source that is configured in a
source action, such as a pushed commit to a GitHub (p. 289) repository or an
update to a file in a versioned Amazon S3 (p. 269) bucket (p. 277).
role A tool for giving temporary access to AWS resource (p. 303)s in your AWS
account (p. 265).
rollback A return to a previous state that follows the failure to create an object, such as
AWS CloudFormation (p. 272) stack (p. 308). All resource (p. 303)s associated
with the failure are deleted during the rollback. For AWS CloudFormation, you can
override this behavior using the --disable-rollback option on the command
line.
root AWS Organizations (p. 274): A parent container for the accounts in your
organization. If you apply a service control policy (p. 306) to the root, it applies
to every organizational unit (p. 298) and account in the organization.
root credentials Authentication information associated with the AWS account (p. 265) owner.
root device volume A volume (p. 313) that contains the image used to boot the instance (p. 291)
(also known as a root device). If you launched the instance from an AMI (p. 268)
backed by instance store (p. 291), this is an instance store volume (p. 313)
created from a template stored in Amazon S3 (p. 269). If you launched the
instance from an AMI backed by Amazon EBS (p. 266), this is an Amazon EBS
volume created from an Amazon EBS snapshot.
route table A set of routing rules that controls the traffic leaving any subnet (p. 310) that is
associated with the route table. You can associate multiple subnets with a single
route table, but a subnet can be associated with only one route table at a time.
row identifier row ID.Amazon Machine Learning: An attribute in the input data that you can
include in the evaluation or prediction output to make it easier to associate a
prediction with an observation.
rule AWS WAF (p. 276): A set of conditions that AWS WAF searches for in web
requests to AWS resource (p. 303)s such as Amazon CloudFront (p. 266)
distributions. You add rules to a web ACL (p. 314), and then specify whether you
want to allow or block web requests based on each rule.
S
Z (p. 314)
S3 See Amazon Simple Storage Service (Amazon S3).
sampling period A defined duration of time, such as one minute, over which Amazon
CloudWatch (p. 266) computes a statistic (p. 309).
Version 1.0
304
sandbox A testing location where you can test the functionality of your application without
affecting production, incurring charges, or purchasing products.
Amazon SES (p. 269): An environment that is designed for developers to test
and evaluate the service. In the sandbox, you have full access to the Amazon SES
API, but you can only send messages to verified email addresses and the mailbox
simulator. To get out of the sandbox, you need to apply for production access.
Accounts in the sandbox also have lower sending limits (p. 306) than production
accounts.
scale in To remove EC2 instances from an Auto Scaling group (p. 271).
scale out To add EC2 instances to an Auto Scaling group (p. 271).
scaling policy A description of how Auto Scaling should automatically scale an Auto Scaling
group (p. 271) in response to changing demand.
See Also scale in, scale out.
scaling activity A process that changes the size, configuration, or makeup of an Auto Scaling
group (p. 271) by launching or terminating instances.
scheduler The method used for placing task (p. 311)s on container instance (p. 280)s.
schema Amazon Machine Learning: The information needed to interpret the input data
for a machine learning model, including attribute names and their assigned data
types, and the names of special attributes.
score cut-off value Amazon Machine Learning: A binary classification models output a score that
ranges from 0 to 1. To decide whether an observation should be classified as 1
or 0, you pick a classification threshold, or cut-off, and Amazon ML compares the
score against it. Observations with scores higher than the cut-off are predicted as
target equals 1, and scores lower than the cut-off are predicted as target equals 0.
SCP See service control policy.
search API Amazon CloudSearch (p. 266): The API that you use to submit search requests to
a search domain (p. 305).
search domain Amazon CloudSearch (p. 266): Encapsulates your searchable data and the
search instances that handle your search requests. You typically set up a separate
Amazon CloudSearch domain for each different collection of data that you want
to search.
search domain configuration Amazon CloudSearch (p. 266): An domain's indexing options, analysis
scheme (p. 270)s, expression (p. 287)s, suggester (p. 310)s, access policies,
and scaling and availability options.
search enabled Amazon CloudSearch (p. 266): An index field option that enables the field data
to be searched.
search endpoint Amazon CloudSearch (p. 266): The URL that you connect to when sending
search requests to a search domain. Each Amazon CloudSearch domain has a
unique search endpoint that remains the same for the life of the domain.
search index Amazon CloudSearch (p. 266): A representation of your searchable data that
facilitates fast and accurate data retrieval.
search instance Amazon CloudSearch (p. 266): A compute resource (p. 303) that indexes
your data and processes search requests. An Amazon CloudSearch domain
has one or more search instances, each with a finite amount of RAM and CPU
Version 1.0
305
resources. As your data volume grows, more search instances or larger search
instances are deployed to contain your indexed data. When necessary, your index
is automatically partitioned across multiple search instances. As your request
volume or complexity increases, each search partition is automatically replicated
to provide additional processing capacity.
search request Amazon CloudSearch (p. 266): A request that is sent to an Amazon CloudSearch
domain's search endpoint to retrieve documents from the index that match
particular search criteria.
search result Amazon CloudSearch (p. 266): A document that matches a search request. Also
referred to as a search hit.
secret access key A key that is used in conjunction with the access key ID (p. 264) to
cryptographically sign programmatic AWS requests. Signing a request identifies
the sender and prevents the request from being altered. You can generate secret
access keys for your AWS account (p. 265), individual IAM user (p. 312)s, and
temporary sessions.
security group A named set of allowed inbound network connections for an instance. (Security
groups in Amazon VPC (p. 269) also include support for outbound connections.)
Each security group consists of a list of protocols, ports, and IP address ranges. A
security group can apply to multiple instances, and multiple groups can regulate a
single instance.
sender The person or entity sending an email message.
Sender ID A Microsoft-controlled version of SPF (p. 308). An email authentication and

anti-spoofing system. For more information about Sender ID, see Sender ID in
Wikipedia.
sending limits The sending quota (p. 306) and maximum send rate (p. 295) that are
associated with every Amazon SES (p. 269) account.
sending quota The maximum number of email messages that you can send using Amazon
SES (p. 269) in a 24-hour period.
server-side encryption (SSE) The encrypting (p. 286) of data at the server level. Amazon S3 (p. 269)
supports three modes of server-side encryption: SSE-S3, in which Amazon S3
manages the keys; SSE-C, in which the customer manages the keys; and SSE-KMS,
in which AWS Key Management Service (AWS KMS) (p. 274) manages keys.
service See Amazon ECS service.
service control policy AWS Organizations (p. 274): A policy-based control that specifies the services
and actions that users and roles can use in the accounts that the service control
policy (SCP) affects.
service endpoint See endpoint.
service health dashboard A web page showing up-to-the-minute information about AWS service
availability. The dashboard is located at http://status.aws.amazon.com/.
service role An IAM (p. 274) role (p. 304) that grants permissions to an AWS service so it
can access AWS resource (p. 303)s. The policies that you attach to the service
role determine which AWS resources the service can access and what it can do
with those resources.
SES See Amazon Simple Email Service (Amazon SES).
Version 1.0
306
session The period during which the temporary security credentials provided by AWS
Security Token Service (AWS STS) (p. 275) allow access to your AWS account.
SHA Secure Hash Algorithm. SHA1 is an earlier version of the algorithm, which AWS
has deprecated in favor of SHA256.
shard Amazon Elasticsearch Service (Amazon ES) (p. 267): A partition of data in an
index. You can split an index into multiple shards, which can include primary
shards (original shards) and replica shards (copies of the primary shards). Replica
shards provide failover, which means that a replica shard is promoted to a primary
shard if a cluster node that contains a primary shard fails. Replica shards also can
handle requests.
shared AMI An Amazon Machine Image (AMI) (p. 268) that a developer builds and makes
available for others to use.
shutdown action Amazon EMR (p. 267): A predefined bootstrap action that launches a script that
executes a series of commands in parallel before terminating the job flow.
signature Refers to a digital signature, which is a mathematical way to confirm the

authenticity of a digital message. AWS uses signatures to authenticate the
requests you send to our web services. For more information, to https://
aws.amazon.com/security.
SIGNATURE file AWS Import/Export (p. 274): A file you copy to the root directory of your
storage device. The file contains a job ID, manifest file, and a signature.
Signature Version 4 Protocol for authenticating inbound API requests to AWS services in all AWS
Regions.
Simple Mail Transfer Protocol See SMTP.
Simple Object Access Protocol See SOAP.
Simple Storage Service See Amazon Simple Storage Service (Amazon S3).
Single-AZ DB instance A standard (non-Multi-AZ) DB instance (p. 282) that is deployed in one
Availability Zone (p. 271), without a standby replica in another Availability Zone.
See Also Multi-AZ deployment.
sloppy phrase search A search for a phrase that specifies how close the terms must be to one another
to be considered a match.
SMTP Simple Mail Transfer Protocol. The standard that is used to exchange email
messages between internet hosts for the purpose of routing and delivery.
snapshot Amazon Elastic Block Store (Amazon EBS) (p. 266): A backup of your
volume (p. 313)s that is stored in Amazon S3 (p. 269). You can use these
snapshots as the starting point for new Amazon EBS volumes or to protect your
data for long-term durability.
See Also DB snapshot.
SNS See Amazon Simple Notification Service (Amazon SNS).
Snowball An AWS Import/Export (p. 274) feature that uses Amazon-owned Snowball
appliances for transferring your data.
See Also https://aws.amazon.com/importexport.
SOAP Simple Object Access Protocol. An XML-based protocol that lets you exchange
information over a particular protocol (HTTP or SMTP, for example) between
applications.
Version 1.0
307
See Also REST, WSDL.
soft bounce A temporary email delivery failure such as one resulting from a full mailbox.
software VPN A software appliance-based VPN connection over the internet.
sort enabled Amazon CloudSearch (p. 266): An index field option that enables a field to be
used to sort the search results.
sort key An attribute used to sort the order of partition keys in a composite primary key
(also known as a range attribute).
See Also partition key, primary key.
source/destination checking A security measure to verify that an EC2 instance (p. 285) is the origin of all
traffic that it sends and the ultimate destination of all traffic that it receives; that
is, that the instance is not relaying traffic. Source/destination checking is enabled
by default. For instances that function as gateways, such as VPC (p. 314)
NAT (p. 296) instances, source/destination checking must be disabled.
spam Unsolicited bulk email.
spamtrap An email address that is set up by an anti-spam (p. 308) entity, not for
correspondence, but to monitor unsolicited email. This is also called a honeypot.
SPF Sender Policy Framework. A standard for authenticating email.

See Also http://www.openspf.org.
Spot Instance A type of EC2 instance (p. 285) that you can bid on to take advantage of unused
Amazon EC2 (p. 267) capacity.
Spot price The price for a Spot Instance (p. 308) at any given time. If your maximum price
exceeds the current price and your restrictions are met, Amazon EC2 (p. 267)
launches instances on your behalf.
SQL injection match condition AWS WAF (p. 276): An attribute that specifies the part of web requests, such
as a header or a query string, that AWS WAF inspects for malicious SQL code.
Based on the specified conditions, you can configure AWS WAF to allow or block
web requests to AWS resource (p. 303)s such as Amazon CloudFront (p. 266)
distributions.
SQS See Amazon Simple Queue Service (Amazon SQS).
SSE See server-side encryption (SSE).
SSL Secure Sockets Layer

See Also Transport Layer Security.
stack AWS CloudFormation (p. 272): A collection of AWS resource (p. 303)s that you
create and delete as a single unit.
AWS OpsWorks (p. 274): A set of instances that you manage collectively,
typically because they have a common purpose such as serving PHP applications.
A stack serves as a container and handles tasks that apply to the group of
instances as a whole, such as managing applications and cookbooks.
station AWS CodePipeline (p. 272): A portion of a pipeline workflow where one or more
actions are performed.
station A place at an AWS facility where your AWS Import/Export data is transferred on
to, or off of, your storage device.
Version 1.0
308
statistic One of five functions of the values submitted for a given sampling
period (p. 304). These functions are Maximum, Minimum, Sum, Average, and
SampleCount.
stem The common root or substring shared by a set of related words.
stemming The process of mapping related words to a common stem. This enables matching
on variants of a word. For example, a search for "horse" could return matches for
horses, horseback, and horsing, as well as horse. Amazon CloudSearch (p. 266)
supports both dictionary based and algorithmic stemming.
step Amazon EMR (p. 267): A single function applied to the data in a job
flow (p. 292). The sum of all steps comprises a job flow.
step type Amazon EMR (p. 267): The type of work done in a step. There are a limited
number of step types, such as moving data from Amazon S3 (p. 269) to Amazon
EC2 (p. 267) or from Amazon EC2 to Amazon S3.
sticky session A feature of the Elastic Load Balancing (p. 285) load balancer that binds a user's
session to a specific application instance so that all requests coming from the user
during the session are sent to the same application instance. By contrast, a load
balancer defaults to route each request independently to the application instance
with the smallest load.
stopping The process of filtering stop words from an index or search request.
stopword A word that is not indexed and is automatically filtered out of search requests
because it is either insignificant or so common that including it would result in
too many matches to be useful. Stop words are language-specific.
streaming Amazon EMR (Amazon EMR) (p. 267): A utility that comes with
Hadoop (p. 289) that enables you to develop MapReduce executables in
languages other than Java.
Amazon CloudFront (p. 266): The ability to use a media file in real time—as it is
transmitted in a steady stream from a server.
streaming distribution A special kind of distribution (p. 284) that serves streamed media files using a
Real Time Messaging Protocol (RTMP) connection.
Streams See Amazon Kinesis Data Streams.
string-to-sign Before you calculate an HMAC (p. 289) signature, you first assemble the required
components in a canonical order. The preencrypted string is the string-to-sign.
string match condition AWS WAF (p. 276): An attribute that specifies the strings that AWS WAF
searches for in a web request, such as a value in a header or a query string. Based
on the specified strings, you can configure AWS WAF to allow or block web
requests to AWS resource (p. 303)s such as CloudFront (p. 266) distributions.
strongly consistent read A read process that returns a response with the most up-to-date data, reflecting
the updates from all prior write operations that were successful—regardless of
the region.
See Also data consistency, eventual consistency, eventually consistent read.
structured query Search criteria specified using the Amazon CloudSearch (p. 266) structured
query language. You use the structured query language to construct compound
queries that use advanced search options and combine multiple search criteria
using Boolean operators.
STS See AWS Security Token Service (AWS STS).
Version 1.0
309
subnet A segment of the IP address range of a VPC (p. 314) that EC2
instance (p. 285)s can be attached to. You can create subnets to group instances
according to security and operational needs.
Subscription button An HTML-coded button that enables an easy way to charge customers a recurring
fee.
suggester Amazon CloudSearch (p. 266): Specifies an index field you want to use to get
autocomplete suggestions and options that can enable fuzzy matches and control
how suggestions are sorted.
suggestions Documents that contain a match for the partial search string in the field
designated by the suggester (p. 310). Amazon CloudSearch (p. 266)
suggestions include the document IDs and field values for each matching
document. To be a match, the string must match the contents of the field starting
from the beginning of the field.
supported AMI An Amazon Machine Image (AMI) (p. 268) similar to a paid AMI (p. 298), except
that the owner charges for additional software or a service that customers use
with their own AMIs.
SWF See Amazon Simple Workflow Service (Amazon SWF).
symmetric encryption Encryption (p. 286) that uses a private key only.
See Also asymmetric encryption.
synchronous bounce A type of bounce (p. 277) that occurs while the email servers of the
sender (p. 306) and receiver (p. 302) are actively communicating.
synonym A word that is the same or nearly the same as an indexed word and that should
produce the same results when specified in a search request. For example, a
search for "Rocky Four" or "Rocky 4" should return the fourth Rocky movie. This
can be done by designating that four and 4 are synonyms for IV. Synonyms are
language-specific.
T
Z (p. 314)
table A collection of data. Similar to other database systems, DynamoDB stores data in
tables.
tag Metadata that you can define and assign to AWS resource (p. 303)s, such as an
EC2 instance (p. 285). Not all AWS resources can be tagged.
tagging Tagging resources: Applying a tag (p. 310) to an AWS resource (p. 303).
Amazon SES (p. 269): Also called labeling. A way to format return path (p. 304)
email addresses so that you can specify a different return path for each
recipient of a message. Tagging enables you to support VERP (p. 313). For
example, if Andrew manages a mailing list, he can use the return paths andrew
[email protected] and [email protected] so that he can
determine which email bounced.
target attribute Amazon Machine Learning (Amazon ML ): The attribute in the input data that
contains the “correct” answers. Amazon ML uses the target attribute to learn how
Version 1.0
310
to make predictions on new data. For example, if you were building a model for
predicting the sale price of a house, the target attribute would be “target sale
price in USD.”
target revision AWS CodeDeploy (p. 272): The most recent version of the application revision
that has been uploaded to the repository and will be deployed to the instances in
a deployment group. In other words, the application revision currently targeted
for deployment. This is also the revision that will be pulled for automatic
deployments.
task An instantiation of a task definition (p. 311) that is running on a container

instance (p. 280).
task definition The blueprint for your task. Specifies the name of the task (p. 311), revisions,
container definition (p. 280)s, and volume (p. 313) information.
task node An EC2 instance (p. 285) that runs Hadoop (p. 289) map and reduce tasks,
but does not store data. Task nodes are managed by the master node (p. 295),
which assigns Hadoop tasks to nodes and monitors their status. While a job flow
is running you can increase and decrease the number of task nodes. Because they
don't store data and can be added and removed from a job flow, you can use task
nodes to manage the EC2 instance capacity your job flow uses, increasing capacity
to handle peak loads and decreasing it later.
Task nodes only run a TaskTracker Hadoop daemon.
tebibyte A contraction of tera binary byte, a tebibyte is 2^40 or 1,099,511,627,776

bytes. A terabyte (TB) is 10^12 or 1,000,000,000,000 bytes. 1,024 TiB is a
pebibyte (p. 299).
template format version The version of an AWS CloudFormation (p. 272) template design that
determines the available features. If you omit the AWSTemplateFormatVersion
section from your template, AWS CloudFormation assumes the most recent
format version.
template validation The process of confirming the use of JSON (p. 292) code in an AWS
CloudFormation (p. 272) template. You can validate any AWS CloudFormation
template using the cfn-validate-template command.
temporary security Authentication information that is provided by AWS STS (p. 275) when you
credentials call an STS API action. Includes an access key ID (p. 264), a secret access
key (p. 306), a session (p. 307) token, and an expiration time.
throttling The automatic restricting or slowing down of a process based on one or more
limits. Examples: Amazon Kinesis Data Streams (p. 268) throttles operations if
an application (or group of applications operating on the same stream) attempts
to get data from a shard at a rate faster than the shard limit. Amazon API
Gateway (p. 265) uses throttling to limit the steady-state request rates for a
single account. Amazon SES (p. 269) uses throttling to reject attempts to send
email that exceeds the sending limits (p. 306).
time series data Data provided as part of a metric. The time value is assumed to be when the value
occurred. A metric is the fundamental concept for Amazon CloudWatch (p. 266)
and represents a time-ordered set of data points. You publish metric data points
into CloudWatch and later retrieve statistics about those data points as a time-
series ordered data set.
time stamp A date/time string in ISO 8601 format.
TLS See Transport Layer Security.
Version 1.0
311
tokenization The process of splitting a stream of text into separate tokens on detectable
boundaries such as whitespace and hyphens.
topic A communication channel to send messages and subscribe to notifications. It

provides an access point for publishers and subscribers to communicate with each
other.
training datasource A datasource that contains the data that Amazon Machine Learning uses to train
the machine learning model to make predictions.
transition AWS CodePipeline (p. 272): The act of a revision in a pipeline continuing from
one stage to the next in a workflow.
Transport Layer Security A cryptographic protocol that provides security for communication over the
internet. Its predecessor is Secure Sockets Layer (SSL).
trust policy An IAM (p. 274) policy (p. 299) that is an inherent part of an IAM
role (p. 304). The trust policy specifies which principal (p. 300)s are allowed to
use the role.
trusted signers AWS account (p. 265)s that the CloudFront (p. 266) distribution owner has
given permission to create signed URLs for a distribution's content.
tuning Selecting the number and type of AMIs (p. 268) to run a Hadoop (p. 289) job
flow most efficiently.
tunnel A route for transmission of private network traffic that uses the internet to
connect nodes in the private network. The tunnel uses encryption and secure
protocols such as PPTP to prevent the traffic from being intercepted as it passes
through public routing nodes.
U
Z (p. 314)
unbounded The number of potential occurrences is not limited by a set number. This
value is often used when defining a data type that is a list (for example,
maxOccurs="unbounded"), in WSDL (p. 314).
unit Standard measurement for the values submitted to Amazon

CloudWatch (p. 266) as metric data. Units include seconds, percent, bytes, bits,
count, bytes/second, bits/second, count/second, and none.
unlink from VPC The process of unlinking (or detaching) an EC2-Classic instance (p. 291) from a
ClassicLink-enabled VPC (p. 314).
See Also ClassicLink, link to VPC.
usage report An AWS record that details your usage of a particular AWS service. You can
generate and download usage reports from https://aws.amazon.com/usage-
reports/.
user A person or application under an account (p. 265) that needs to make API calls
to AWS products. Each user has a unique name within the AWS account, and a set
of security credentials not shared with other users. These credentials are separate
from the AWS account's security credentials. Each user is associated with one and
only one AWS account.
Version 1.0
312
V
Z (p. 314)
validation See template validation.
value Instances of attributes (p. 271) for an item, such as cells in a spreadsheet. An
attribute might have multiple values.
Tagging resources: A specific tag (p. 310) label that acts as a descriptor within a
tag category (key). For example, you might have EC2 instance (p. 285) with the
tag key of Owner and the tag value of Jan. You can tag an AWS resource (p. 303)
with up to 10 key–value pairs. Not all AWS resources can be tagged.
Variable Envelope Return See VERP.

Path
verification The process of confirming that you own an email address or a domain so that you
can send email from or to it.
VERP Variable Envelope Return Path. A way in which email sending applications can
match bounce (p. 277)d email with the undeliverable address that caused
the bounce by using a different return path (p. 304) for each recipient. VERP
is typically used for mailing lists. With VERP, the recipient's email address is
embedded in the address of the return path, which is where bounced email is
returned. This makes it possible to automate the processing of bounced email
without having to open the bounce messages, which may vary in content.
versioning Every object in Amazon S3 (p. 269) has a key and a version ID. Objects with the
same key, but different version IDs can be stored in the same bucket (p. 277).
Versioning is enabled at the bucket layer using PUT Bucket versioning.
VGW See virtual private gateway.
virtualization Allows multiple guest virtual machines (VM) to run on a host operating system.
Guest VMs can run on one or more levels above the host hardware, depending on
the type of virtualization.
See Also PV virtualization, HVM virtualization.
virtual private cloud See VPC.
virtual private gateway (VGW) The Amazon side of a VPN connection (p. 314) that maintains
connectivity. The internal interfaces of the virtual private gateway connect to
your VPC (p. 314) via the VPN attachment and the external interfaces connect
to the VPN connection, which leads to the customer gateway (p. 281).
visibility timeout The period of time that a message is invisible to the rest of your application after
an application component gets it from the queue. During the visibility timeout,
the component that received the message usually processes it, and then deletes
it from the queue. This prevents multiple components from processing the same
message.
volume A fixed amount of storage on an instance (p. 291). You can share volume
data between container (p. 280)s and persist the data on the container
instance (p. 280) when the containers are no longer running.
Version 1.0
313
VPC Virtual private cloud. An elastic network populated by infrastructure, platform,

and application services that share common security and interconnection.
VPC endpoint A feature that enables you to create a private connection between your
VPC (p. 314) and an another AWS service without requiring access over the
internet, through a NAT (p. 296) instance, a VPN connection (p. 314), or AWS
Direct Connect (p. 273).
VPG See virtual private gateway.
VPN CloudHub See AWS VPN CloudHub.
VPN connection Amazon Web Services (AWS) (p. 270): The IPsec connection between a
VPC (p. 314) and some other network, such as a corporate data center, home
network, or co-location facility.
W
Z (p. 314)
WAM See Amazon WorkSpaces Application Manager (Amazon WAM).
web access control list AWS WAF (p. 276): A set of rules that defines the conditions that AWS WAF
searches for in web requests to AWS resource (p. 303)s such as Amazon
CloudFront (p. 266) distributions. A web access control list (web ACL) specifies
whether to allow, block, or count the requests.
Web Services Description See WSDL.

Language
WSDL Web Services Description Language. A language used to describe the actions
that a web service can perform, along with the syntax of action requests and
responses.
See Also REST, SOAP.
X, Y, Z
X.509 certificate An digital document that uses the X.509 public key infrastructure (PKI)
standard to verify that a public key belongs to the entity described in the
certificate (p. 278).
yobibyte A contraction of yotta binary byte, a yobibyte is 2^80 or

1,208,925,819,614,629,174,706,176 bytes. A yottabyte (YB) is 10^24 or
1,000,000,000,000,000,000,000,000 bytes.
zebibyte A contraction of zetta binary byte, a zebibyte is 2^70 or

1,180,591,620,717,411,303,424 bytes. A zettabyte (ZB) is 10^21 or
1,000,000,000,000,000,000,000 bytes. 1,024 ZiB is a yobibyte (p. 314).
zone awareness Amazon Elasticsearch Service (Amazon ES) (p. 267): A configuration that
distributes nodes in a cluster across two Availability Zone (p. 271)s in the same
Region. Zone awareness helps to prevent data loss and minimizes downtime in
the event of node and data center failure. If you enable zone awareness, you must
have an even number of data instances in the instance count, and you also must
Version 1.0
314
use the Amazon Elasticsearch Service Configuration API to replicate your data for
your Elasticsearch cluster.
Version 1.0
315

Aws General

Uploaded by

Copyright:

Available Formats

Aws General

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Aws General

Uploaded by

Copyright:

Available Formats

What is the purpose of the document?

What is the purpose of the document?

What technologies are discussed in the document?

What technologies are discussed in the document?

Amazon Web Services

Amazon Web Services: General Reference

Amazon DynamoDB Streams ..................................................................................................... 41

AWS Service Catalog ................................................................................................................. 83

ARN Format ........................................................................................................................... 121

AWS Mobile Hub ............................................................................................................ 138

Amazon CloudWatch Limits ..................................................................................................... 196

AWS Lambda Limits ................................................................................................................ 229

Links ..................................................................................................................................... 260

AWS General Reference

• AWS Regions and Endpoints (p. 2)

AWS Regions and Endpoints

• Amazon CloudWatch (p. 21)

• Amazon Kinesis Data Firehose (p. 63)

• Amazon VPC (p. 100)

Alexa for Business

US East (N. us-east-1 a4b.us-east-1.amazonaws.com HTTPS

Amazon API Gateway

US East us-east-2 apigateway.us-east-2.amazonaws.com HTTPS ZOJJZC49E0EPZ

US East (N. us-east-1 apigateway.us-east-1.amazonaws.com HTTPS Z1UJRXOUMOOFQ8

US us-west-1 apigateway.us-west-1.amazonaws.com HTTPS Z2MUQ32089INYE

US West us-west-2 apigateway.us-west-2.amazonaws.com HTTPS Z2OJLYMUO9EFXC

Asia ap- apigateway.ap-south-1.amazonaws.com HTTPS Z3VO1THU9YC4UR

Asia ap- apigateway.ap-northeast-2.amazonaws.com HTTPS Z20JF4UZKIW1U8

Asia ap- apigateway.ap-northeast-3.amazonaws.com HTTPS Z2YQB5RD63NC85

Asia ap- apigateway.ap-southeast-1.amazonaws.com HTTPS ZL327KTPIQFUL

Region Region Endpoint Protocol Amazon

Asia ap- apigateway.ap-southeast-2.amazonaws.com HTTPS Z2RPCDW04V8134

Asia ap- apigateway.ap-northeast-1.amazonaws.com HTTPS Z1YSHQZHG15GKL

Canada ca- apigateway.ca-central-1.amazonaws.com HTTPS Z19DQILCV0OWEC

China cn-north-1 apigateway.cn-north-1.amazonaws.com.cn HTTPS None

EU eu- apigateway.eu-central-1.amazonaws.com HTTPS Z1U9ULNL0V5AJ3

EU eu-west-1 apigateway.eu-west-1.amazonaws.com HTTPS ZLY8HYME6SFDD

EU eu-west-2 apigateway.eu-west-2.amazonaws.com HTTPS ZJ5UAJN8Y3Z2Q

EU (Paris) eu-west-3 apigateway.eu-west-3.amazonaws.com HTTPS Z3KY65QIEKYHQQ

South sa-east-1 apigateway.sa-east-1.amazonaws.com HTTPS ZCMLWB8V5SYIT

Application Auto Scaling

US East us-east-2 autoscaling.us-east-2.amazonaws.com HTTP and

US East (N. us-east-1 autoscaling.us-east-1.amazonaws.com HTTP and

US West (N. us-west-1 autoscaling.us-west-1.amazonaws.com HTTP and

US West us-west-2 autoscaling.us-west-2.amazonaws.com HTTP and

Region Region Endpoint Protocol

Asia Paciﬁc ap- autoscaling.ap-northeast-1.amazonaws.com HTTP and

Asia Paciﬁc ap- autoscaling.ap-northeast-2.amazonaws.com HTTP and

Asia Paciﬁc ap- autoscaling.ap-northeast-3.amazonaws.com HTTP and

Asia Paciﬁc ap-south-1 autoscaling.ap-south-1.amazonaws.com HTTP and

Asia Paciﬁc ap- autoscaling.ap-southeast-1.amazonaws.com HTTP and

Asia Paciﬁc ap- autoscaling.ap-southeast-2.amazonaws.com HTTP and

Canada ca-central-1 autoscaling.ca-central-1.amazonaws.com HTTP and

China cn-north-1 autoscaling.cn-north-1.amazonaws.com.cn HTTP and

China cn- autoscaling.cn-northwest-1.amazonaws.com.cn HTTP and

EU eu-central-1 autoscaling.eu-central-1.amazonaws.com HTTP and

EU (Ireland) eu-west-1 autoscaling.eu-west-1.amazonaws.com HTTP and

EU (London) eu-west-2 autoscaling.eu-west-2.amazonaws.com HTTP and

EU (Paris) eu-west-3 autoscaling.eu-west-3.amazonaws.com HTTP and

South sa-east-1 autoscaling.sa-east-1.amazonaws.com HTTP and