aws-sdk-core 2.0.0.rc7 → 2.0.0.rc8

Sign up to get free protection for your applications and to get access to all the features.
Files changed (41) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile +1 -5
  3. data/README.md +2 -2
  4. data/apis/CloudFormation-2010-05-15.json +27 -0
  5. data/apis/CloudSearch-2013-01-01.json +16 -0
  6. data/apis/CloudWatch-2010-08-01.json +0 -185
  7. data/apis/ElastiCache-2014-03-24.json +7 -0
  8. data/apis/ElasticTranscoder-2012-09-25.json +118 -2
  9. data/apis/Glacier-2012-06-01.json +52 -0
  10. data/apis/RDS-2013-09-09.json +4 -0
  11. data/apis/S3-2006-03-01.json +490 -468
  12. data/apis/StorageGateway-2013-06-30.json +28 -0
  13. data/apis/source/cloudformation-2010-05-15.json +43 -7
  14. data/apis/source/cloudsearch-2013-01-01.json +38 -16
  15. data/apis/source/directconnect-2012-10-25.paginators.json +8 -2
  16. data/apis/source/dynamodb-2012-08-10.json +270 -269
  17. data/apis/source/ec2-2014-02-01.json +30 -30
  18. data/apis/source/elasticache-2014-03-24.paginators.json +6 -0
  19. data/apis/source/elastictranscoder-2012-09-25.json +184 -56
  20. data/apis/source/elastictranscoder-2012-09-25.paginators.json +4 -0
  21. data/apis/source/email-2010-12-01.json +1 -1
  22. data/apis/source/email-2010-12-01.waiters.json +14 -0
  23. data/apis/source/glacier-2012-06-01.json +77 -13
  24. data/apis/source/monitoring-2010-08-01.json +0 -308
  25. data/apis/source/rds-2013-01-10.json +7 -7
  26. data/apis/source/rds-2013-02-12.json +7 -7
  27. data/apis/source/rds-2013-09-09.json +76 -57
  28. data/apis/source/s3-2006-03-01.json +2213 -1209
  29. data/apis/source/s3-2006-03-01.waiters.json +5 -0
  30. data/apis/source/storagegateway-2013-06-30.json +441 -401
  31. data/apis/source/storagegateway-2013-06-30.paginators.json +6 -6
  32. data/apis/source/sts-2011-06-15.json +9 -9
  33. data/apis/source/swf-2012-01-25.json +627 -627
  34. data/doc-src/templates/default/layout/html/layout.erb +37 -0
  35. data/lib/aws/credential_provider_chain.rb +5 -7
  36. data/lib/aws/version.rb +1 -1
  37. data/spec/fixtures/operations/s3/head_object.yml +2 -2
  38. metadata +4 -5
  39. data/apis/source/cloudfront-2014-01-31.normal.json +0 -2905
  40. data/apis/source/elasticloadbalancing-2012-06-01.normal.json +0 -2107
  41. data/apis/source/kinesis-2013-12-02.normal.json +0 -761
@@ -11,9 +11,13 @@
11
11
  "result_key": "Jobs"
12
12
  },
13
13
  "ListPipelines": {
14
+ "input_token": "PageToken",
15
+ "output_token": "NextPageToken",
14
16
  "result_key": "Pipelines"
15
17
  },
16
18
  "ListPresets": {
19
+ "input_token": "PageToken",
20
+ "output_token": "NextPageToken",
17
21
  "result_key": "Presets"
18
22
  }
19
23
  }
@@ -8,7 +8,7 @@
8
8
  "service_abbreviation": "Amazon SES",
9
9
  "endpoint_prefix": "email",
10
10
  "xmlnamespace": "http://ses.amazonaws.com/doc/2010-12-01/",
11
- "documentation": "\n <fullname>Amazon Simple Email Service</fullname>\n <p>\n This is the API Reference for Amazon Simple Email Service (Amazon SES). This documentation is intended to be\n used in conjunction with the Amazon SES Developer Guide.\n </p>\n <p>\n For specific details on how to construct a service request, please consult the <a href=\"http://docs.aws.amazon.com/ses/latest/DeveloperGuide\">Amazon SES Developer Guide</a>.\n </p>\n <note>The endpoint for Amazon SES is located at:\n <code>https://email.us-east-1.amazonaws.com</code>\n </note>\n ",
11
+ "documentation": "\n <fullname>Amazon Simple Email Service</fullname>\n <p>\n This is the API Reference for Amazon Simple Email Service (Amazon SES). This documentation is intended to be\n used in conjunction with the <a href=\"http://docs.aws.amazon.com/ses/latest/DeveloperGuide/Welcome.html\">Amazon SES Developer Guide</a>.\n </p>\n <note>For a list of Amazon SES endpoints to use in service requests, see <a href=\"http://docs.aws.amazon.com/ses/latest/DeveloperGuide/regions.html\">Regions and Amazon SES</a> \n in the Amazon SES Developer Guide. \n </note>\n ",
12
12
  "operations": {
13
13
  "DeleteIdentity": {
14
14
  "name": "DeleteIdentity",
@@ -0,0 +1,14 @@
1
+ {
2
+ "waiters": {
3
+ "__default__": {
4
+ "interval": 3,
5
+ "max_attempts": 20
6
+ },
7
+ "IdentityExists": {
8
+ "operation": "GetIdentityVerificationAttributes",
9
+ "success_type": "output",
10
+ "success_path": "VerificationAttributes[].VerificationStatus",
11
+ "success_value": true
12
+ }
13
+ }
14
+ }
@@ -5,7 +5,7 @@
5
5
  "checksum_format": "sha256",
6
6
  "service_full_name": "Amazon Glacier",
7
7
  "endpoint_prefix": "glacier",
8
- "documentation": "\n <p>Amazon Glacier is a storage solution for \"cold data.\"</p>\n\n <p>Amazon Glacier is an extremely low-cost storage service that provides secure, durable and\n\t\teasy-to-use storage for data backup and archival. With Amazon Glacier, customers can store\n\t\ttheir data cost effectively for months, years, or decades. Amazon Glacier also enables\n\t\tcustomers to offload the administrative burdens of operating and scaling storage to AWS, so\n\t\tthey don't have to worry about capacity planning, hardware provisioning, data replication,\n\t\thardware failure and recovery, or time-consuming hardware migrations.</p>\n\n <p>Amazon Glacier is a great storage choice when low storage cost is paramount, your data is\n\t\trarely retrieved, and retrieval latency of several hours is acceptable. If your application\n\t\trequires fast or frequent access to your data, consider using Amazon S3. For more\n\t\tinformation, go to <a href=\"http://aws.amazon.com/s3/\">Amazon Simple Storage Service (Amazon S3)</a>.</p>\n\n <p>You can store any kind of data in any format. There is no maximum limit on the total amount\n\t\tof data you can store in Amazon Glacier. </p>\n\n <p>If you are a first-time user of Amazon Glacier, we recommend that you begin \n by reading the following sections in the <i>Amazon Glacier Developer Guide</i>:</p>\n <ul>\n <li><p><a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/introduction.html\">What is Amazon Glacier</a> - This section of the Developer Guide \n describes the underlying data model, the operations it supports, \n and the AWS SDKs that you can use to interact with the service.</p></li>\n <li><p><a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/amazon-glacier-getting-started.html\">Getting Started with Amazon Glacier</a> - The Getting \n Started section walks you through the process of creating a vault, \n uploading archives, creating jobs to download archives, \n retrieving the job output, and deleting archives.</p></li>\n </ul>\n ",
8
+ "documentation": "\n <p>Amazon Glacier is a storage solution for \"cold data.\"</p>\n\n <p>Amazon Glacier is an extremely low-cost storage service that provides secure, durable, and\n\t\teasy-to-use storage for data backup and archival. With Amazon Glacier, customers can store\n\t\ttheir data cost effectively for months, years, or decades. Amazon Glacier also enables\n\t\tcustomers to offload the administrative burdens of operating and scaling storage to AWS, so\n\t\tthey don't have to worry about capacity planning, hardware provisioning, data replication,\n\t\thardware failure and recovery, or time-consuming hardware migrations.</p>\n\n <p>Amazon Glacier is a great storage choice when low storage cost is paramount, your data is\n\t\trarely retrieved, and retrieval latency of several hours is acceptable. If your application\n\t\trequires fast or frequent access to your data, consider using Amazon S3. For more\n\t\tinformation, go to <a href=\"http://aws.amazon.com/s3/\">Amazon Simple Storage Service (Amazon S3)</a>.</p>\n\n <p>You can store any kind of data in any format. There is no maximum limit on the total amount\n\t\tof data you can store in Amazon Glacier. </p>\n\n <p>If you are a first-time user of Amazon Glacier, we recommend that you begin \n by reading the following sections in the <i>Amazon Glacier Developer Guide</i>:</p>\n <ul>\n <li><p><a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/introduction.html\">What is Amazon Glacier</a> - This section of the Developer Guide \n describes the underlying data model, the operations it supports, \n and the AWS SDKs that you can use to interact with the service.</p></li>\n <li><p><a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/amazon-glacier-getting-started.html\">Getting Started with Amazon Glacier</a> - The Getting \n Started section walks you through the process of creating a vault, \n uploading archives, creating jobs to download archives, \n retrieving the job output, and deleting archives.</p></li>\n </ul>\n ",
9
9
  "operations": {
10
10
  "AbortMultipartUpload": {
11
11
  "name": "AbortMultipartUpload",
@@ -831,7 +831,7 @@
831
831
  "JobId": {
832
832
  "shape_name": "string",
833
833
  "type": "string",
834
- "documentation": "\n <p>An opaque string that identifies an Amazon Glacier job.</p>\n \n "
834
+ "documentation": "\n <p>An opaque string that identifies an Amazon Glacier job.</p> \n "
835
835
  },
836
836
  "JobDescription": {
837
837
  "shape_name": "string",
@@ -916,6 +916,38 @@
916
916
  "shape_name": "string",
917
917
  "type": "string",
918
918
  "documentation": "\n <p>The retrieved byte range for archive retrieval jobs in the form \"<i>StartByteValue</i>-<i>EndByteValue</i>\" \n If no range was specified in the archive retrieval, then the whole archive is retrieved and \n <i>StartByteValue</i> equals 0 and <i>EndByteValue</i> equals the size of the archive minus 1. \n For inventory retrieval jobs this field is null. </p> \n "
919
+ },
920
+ "InventoryRetrievalParameters": {
921
+ "shape_name": "InventoryRetrievalJobDescription",
922
+ "type": "structure",
923
+ "members": {
924
+ "Format": {
925
+ "shape_name": "string",
926
+ "type": "string",
927
+ "documentation": "\n <p>The output format for the vault inventory list, which is set by the <b>InitiateJob</b> request \n when initiating a job to retrieve a vault inventory. Valid values are \"CSV\" and \"JSON\".</p>\n "
928
+ },
929
+ "StartDate": {
930
+ "shape_name": "DateTime",
931
+ "type": "string",
932
+ "documentation": "\n <p>The start of the date range in UTC for vault inventory retrieval that includes archives created \n on or after this date. A string representation of ISO 8601 date format, for example, 2013-03-20T17:03:43Z.</p>\n "
933
+ },
934
+ "EndDate": {
935
+ "shape_name": "DateTime",
936
+ "type": "string",
937
+ "documentation": "\n <p>The end of the date range in UTC for vault inventory retrieval that includes archives created before this date.\n A string representation of ISO 8601 date format, for example, 2013-03-20T17:03:43Z.</p>\n "
938
+ },
939
+ "Limit": {
940
+ "shape_name": "string",
941
+ "type": "string",
942
+ "documentation": "\n <p>Specifies the maximum number of inventory items returned per vault inventory retrieval request. \n This limit is set when initiating the job with the a <b>InitiateJob</b> request. </p>\n "
943
+ },
944
+ "Marker": {
945
+ "shape_name": "string",
946
+ "type": "string",
947
+ "documentation": "\n <p>An opaque string that represents where to continue pagination of the vault inventory retrieval results. \n You use the marker in a new <b>InitiateJob</b> request to obtain additional inventory items. \n If there are no more inventory items, this value is <code>null</code>. For more information, see\n <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/api-initiate-job-post.html#api-initiate-job-post-vault-inventory-list-filtering\">\n Range Inventory Retrieval</a>.</p> \n "
948
+ }
949
+ },
950
+ "documentation": "\n <p>Parameters used for range inventory retrieval.</p> \n "
919
951
  }
920
952
  },
921
953
  "documentation": "\n <p>Describes an Amazon Glacier job.</p>\n "
@@ -1349,7 +1381,7 @@
1349
1381
  "documentation": "\n <p>Returned if the service cannot complete the request.</p>\n "
1350
1382
  }
1351
1383
  ],
1352
- "documentation": "\n\t <p>This operation downloads the output of the job you initiated using <a>InitiateJob</a>. Depending on the\n\t\t\tjob type you specified when you initiated the job, the output will be either the content\n\t\t\tof an archive or a vault inventory.</p>\n\n <p>A job ID will not expire for at least 24 hours after Amazon Glacier completes the job. That is, you can download the job\n\t\t\t\toutput within the 24 hours period after Amazon Glacier completes the job.</p>\n\n\t\t<p>If the job output is large, then you can use the <code>Range</code> request header to\n\t\t\tretrieve a portion of the output. This allows you to download the entire output in smaller\n\t\t\tchunks of bytes. For example, suppose you have 1 GB of job output you want to download and\n\t\t\tyou decide to download 128 MB chunks of data at a time, which is a total of eight Get Job Output\n\t\t\trequests. You use the following process to download the job output:</p>\n\n\t\t<ol>\n\t\t\t<li>\n<p>Download a 128 MB chunk of output by specifying the appropriate byte range using the\n\t\t\t\t\t\t<code>Range</code> header.</p>\n\t\t\t</li>\n\t\t\t<li>\n<p>Along with the data, the response includes a checksum of the payload. You compute\n\t\t\t\tthe checksum of the payload on the client and compare it with the checksum you received\n\t\t\t\tin the response to ensure you received all the expected data.</p>\n\t\t\t</li>\n\t\t\t<li>\n<p>Repeat steps 1 and 2 for all the eight 128 MB chunks of output data, each time\n\t\t\t\tspecifying the appropriate byte range.</p>\n\t\t\t</li>\n\t\t\t<li>\n<p>After downloading all the parts of the job output, you have a list of eight checksum\n\t\t\t\tvalues. Compute the tree hash of these values to find the checksum of the entire output.\n\t\t\t\tUsing the Describe Job API, obtain job information of the job that provided you the\n\t\t\t\toutput. The response includes the checksum of the entire archive stored in Amazon Glacier.\n\t\t\t\tYou compare this value with the checksum you computed to ensure you have downloaded the\n\t\t\t\tentire archive content with no errors.</p>\n\t\t\t</li>\n\t\t</ol>\n\n\t\t<p>An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don't have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html\">Access Control Using AWS Identity and Access Management (IAM)</a>.</p>\n <p>For conceptual information and the underlying REST API, go to \n <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/vault-inventory.html\">Downloading a Vault Inventory</a>, \n <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/downloading-an-archive.html\">Downloading an Archive</a>, \n and \n <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/api-job-output-get.html\">Get Job Output </a> </p>\n "
1384
+ "documentation": "\n\t <p>This operation downloads the output of the job you initiated using <a>InitiateJob</a>. Depending on the\n\t\t\tjob type you specified when you initiated the job, the output will be either the content\n\t\t\tof an archive or a vault inventory.</p>\n\n <p>A job ID will not expire for at least 24 hours after Amazon Glacier completes the job. That is, you can download the job\n\t\t\t\toutput within the 24 hours period after Amazon Glacier completes the job.</p>\n\n\t\t<p>If the job output is large, then you can use the <code>Range</code> request header to\n\t\t\tretrieve a portion of the output. This allows you to download the entire output in smaller\n\t\t\tchunks of bytes. For example, suppose you have 1 GB of job output you want to download and\n\t\t\tyou decide to download 128 MB chunks of data at a time, which is a total of eight Get Job Output\n\t\t\trequests. You use the following process to download the job output:</p>\n\n\t\t<ol>\n\t\t\t<li>\n<p>Download a 128 MB chunk of output by specifying the appropriate byte range using the\n\t\t\t\t\t\t<code>Range</code> header.</p>\n\t\t\t</li>\n\t\t\t<li>\n<p>Along with the data, the response includes a checksum of the payload. You compute\n\t\t\t\tthe checksum of the payload on the client and compare it with the checksum you received\n\t\t\t\tin the response to ensure you received all the expected data.</p>\n\t\t\t</li>\n\t\t\t<li>\n<p>Repeat steps 1 and 2 for all the eight 128 MB chunks of output data, each time\n\t\t\t\tspecifying the appropriate byte range.</p>\n\t\t\t</li>\n\t\t\t<li>\n<p>After downloading all the parts of the job output, you have a list of eight checksum\n\t\t\t\tvalues. Compute the tree hash of these values to find the checksum of the entire output.\n\t\t\t\tUsing the <a>DescribeJob</a> API, obtain job information of the job that provided you the\n\t\t\t\toutput. The response includes the checksum of the entire archive stored in Amazon Glacier.\n\t\t\t\tYou compare this value with the checksum you computed to ensure you have downloaded the\n\t\t\t\tentire archive content with no errors.</p>\n\t\t\t</li>\n\t\t</ol>\n\n\t\t<p>An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don't have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html\">Access Control Using AWS Identity and Access Management (IAM)</a>.</p>\n <p>For conceptual information and the underlying REST API, go to \n <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/vault-inventory.html\">Downloading a Vault Inventory</a>, \n <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/downloading-an-archive.html\">Downloading an Archive</a>, \n and \n <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/api-job-output-get.html\">Get Job Output </a> </p>\n "
1353
1385
  },
1354
1386
  "GetVaultNotifications": {
1355
1387
  "name": "GetVaultNotifications",
@@ -1528,12 +1560,12 @@
1528
1560
  "Format": {
1529
1561
  "shape_name": "string",
1530
1562
  "type": "string",
1531
- "documentation": "\n <p>When initiating a job to retrieve a vault inventory, you can optionally add this parameter to your request to specify the output format. \n If you are initiating an inventory job and do not specify a Format field, JSON is the default format.\n Valid Values are \"CSV\" and \"JSON\". </p>\n "
1563
+ "documentation": "\n <p>When initiating a job to retrieve a vault inventory, you can optionally add this parameter to your request to specify the output format. \n If you are initiating an inventory job and do not specify a Format field, JSON is the default format.\n Valid values are \"CSV\" and \"JSON\". </p>\n "
1532
1564
  },
1533
1565
  "Type": {
1534
1566
  "shape_name": "string",
1535
1567
  "type": "string",
1536
- "documentation": "\n <p>The job type. You can initiate a job to retrieve an archive or get an inventory of a vault.\n Valid Values are \"archive-retrieval\" and \"inventory-retrieval\". </p>\n "
1568
+ "documentation": "\n <p>The job type. You can initiate a job to retrieve an archive or get an inventory of a vault. \n Valid values are \"archive-retrieval\" and \"inventory-retrieval\".</p>\n "
1537
1569
  },
1538
1570
  "ArchiveId": {
1539
1571
  "shape_name": "string",
@@ -1553,7 +1585,7 @@
1553
1585
  "RetrievalByteRange": {
1554
1586
  "shape_name": "string",
1555
1587
  "type": "string",
1556
- "documentation": "\n <p>The byte range to retrieve for an archive retrieval. in the form \"<i>StartByteValue</i>-<i>EndByteValue</i>\" \n If not specified, the whole archive is retrieved. If specified, the byte range must be megabyte \n (1024*1024) aligned which means that <i>StartByteValue</i> must be divisible by 1 MB and <i>EndByteValue</i> \n plus 1 must be divisible by 1 MB or be the end of the archive specified as the archive byte size \n value minus 1. If RetrievalByteRange is not megabyte aligned, this operation returns a 400 response.\n </p>\n <p>\n An error occurs if you specify this field for an inventory retrieval job request. </p>\n "
1588
+ "documentation": "\n <p>The byte range to retrieve for an archive retrieval. in the form \"<i>StartByteValue</i>-<i>EndByteValue</i>\" \n If not specified, the whole archive is retrieved. If specified, the byte range must be megabyte \n (1024*1024) aligned which means that <i>StartByteValue</i> must be divisible by 1 MB and <i>EndByteValue</i> \n plus 1 must be divisible by 1 MB or be the end of the archive specified as the archive byte size \n value minus 1. If RetrievalByteRange is not megabyte aligned, this operation returns a 400 response.\n </p>\n <p>An error occurs if you specify this field for an inventory retrieval job request. </p>\n "
1557
1589
  },
1558
1590
  "InventoryRetrievalParameters": {
1559
1591
  "shape_name": "InventoryRetrievalJobInput",
@@ -1562,25 +1594,25 @@
1562
1594
  "StartDate": {
1563
1595
  "shape_name": "string",
1564
1596
  "type": "string",
1565
- "documentation": null
1597
+ "documentation": "\n <p>The start of the date range in UTC for vault inventory retrieval that includes archives created \n on or after this date. A string representation of ISO 8601 date format, for example, 2013-03-20T17:03:43Z.</p>\n "
1566
1598
  },
1567
1599
  "EndDate": {
1568
1600
  "shape_name": "string",
1569
1601
  "type": "string",
1570
- "documentation": null
1602
+ "documentation": "\n <p>The end of the date range in UTC for vault inventory retrieval that includes archives created before this date.\n A string representation of ISO 8601 date format, for example, 2013-03-20T17:03:43Z.</p> \n "
1571
1603
  },
1572
1604
  "Limit": {
1573
1605
  "shape_name": "string",
1574
1606
  "type": "string",
1575
- "documentation": null
1607
+ "documentation": "\n <p>Specifies the maximum number of inventory items returned per vault inventory retrieval request.\n Valid values are greater than or equal to 1.</p>\n "
1576
1608
  },
1577
1609
  "Marker": {
1578
1610
  "shape_name": "string",
1579
1611
  "type": "string",
1580
- "documentation": null
1612
+ "documentation": "\n <p>An opaque string that represents where to continue pagination of the vault inventory retrieval results. \n You use the marker in a new <b>InitiateJob</b> request to obtain additional inventory items. \n If there are no more inventory items, this value is <code>null</code>.</p> \n "
1581
1613
  }
1582
1614
  },
1583
- "documentation": null
1615
+ "documentation": "\n <p>Input parameters used for range inventory retrieval.</p>\n "
1584
1616
  }
1585
1617
  },
1586
1618
  "documentation": "\n <p>Provides options for specifying job information.</p>\n ",
@@ -1700,7 +1732,7 @@
1700
1732
  "documentation": "\n <p>Returned if the service cannot complete the request.</p>\n "
1701
1733
  }
1702
1734
  ],
1703
- "documentation": "\n\t <p>This operation initiates a job of the specified type. In this release, you can initiate a\n\t\t\tjob to retrieve either an archive or a vault inventory (a list of archives in a vault). </p>\n\n\t\t<p>Retrieving data from Amazon Glacier is a two-step process: </p>\n\n\t\t<ol>\n\t\t\t<li><p>Initiate a retrieval job.</p></li>\n\t\t\t<li><p>After the job completes, download the bytes.</p></li>\n\t\t</ol>\n\n\t\t<p>The retrieval request is executed asynchronously. When you initiate a retrieval job,\n\t\t\tAmazon Glacier creates a job and returns a job ID in the response. When Amazon Glacier completes\n\t\t\tthe job, you can get the job output (archive or inventory data). For information about\n\t\t\tgetting job output, see <a>GetJobOutput</a> operation. </p>\n\n\t\t<p>The job must complete before you can get its output. To determine when a job is complete,\n\t\t\tyou have the following options:</p>\n\n\t\t<ul>\n\t\t\t<li>\n<p><b>Use Amazon SNS Notification</b> You can specify an\n\t\t\t\t\t\tAmazon Simple Notification Service (Amazon SNS) topic to which Amazon Glacier can\n\t\t\t\t\t\tpost a notification after the job is completed. You can specify an SNS topic\n\t\t\t\t\t\tper job request. The notification is sent only after Amazon Glacier completes the\n\t\t\t\t\t\tjob. In addition to specifying an SNS topic per job request, you can\n\t\t\t\t\t\tconfigure vault notifications for a vault so that job notifications are\n\t\t\t\t\t\talways sent. For more information, see <a>SetVaultNotifications</a>.</p>\n\t\t\t</li>\n\t\t\t<li>\n<p><b>Get job details</b> You can make a <a>DescribeJob</a> request\n\t\t\t\t\t\tto obtain job status information while a job is in progress. However, it is\n\t\t\t\t\t\tmore efficient to use an Amazon SNS notification to determine when a job is\n\t\t\t\t\t\tcomplete.</p>\n\t\t\t</li>\n\t\t</ul>\n\n\t\t<note><p>The information you get via notification is same that you get by calling <a>DescribeJob</a>.</p></note>\n\n\t\t<p>If for a specific event, you add both the notification configuration on the vault and also\n\t\t\tspecify an SNS topic in your initiate job request, Amazon Glacier sends both\n\t\t\tnotifications. For more information, see <a>SetVaultNotifications</a>.</p>\n\n\t\t<p>An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don't have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html\">Access Control Using AWS Identity and Access Management (IAM)</a>.</p>\n\n\t\t<p><b>About the Vault Inventory</b></p>\n\n\t\t<p>Amazon Glacier prepares an inventory for each vault periodically, every 24 hours. When you\n\t\t\t\tinitiate a job for a vault inventory, Amazon Glacier returns the last inventory for\n\t\t\t\tthe vault. The inventory data you get might be up to a day or two days old. Also,\n\t\t\t\tthe initiate inventory job might take some time to complete before you can download\n\t\t\t\tthe vault inventory. So you do not want to retrieve a vault inventory for each vault\n\t\t\t\toperation. However, in some scenarios, you might find the vault inventory useful.\n\t\t\t\tFor example, when you upload an archive, you can provide an archive description but\n\t\t\t\tnot an archive name. Amazon Glacier provides you a unique archive ID, an opaque\n\t\t\t\tstring of characters. So, you might maintain your own database that maps archive\n\t\t\t\tnames to their corresponding Amazon Glacier assigned archive IDs. You might find the\n\t\t\t\tvault inventory useful in the event you need to reconcile information in your\n\t\t\t\tdatabase with the actual vault inventory. </p>\n \n <p><b>About Ranged Archive Retrieval</b></p>\n <p>\n You can initiate an archive retrieval for the whole archive or a range of the archive. \n In the case of ranged archive retrieval, you specify a byte range to return or the whole archive. \n The range specified must be megabyte (MB) aligned, that is the range start value must be \n divisible by 1 MB and range end value plus 1 must be divisible by 1 MB or equal the end of the \n archive. If the ranged archive retrieval is not megabyte aligned, this operation returns a \n 400 response. Furthermore, to ensure you get checksum values for data you download using \n Get Job Output API, the range must be tree hash aligned. \n </p>\n\n\t\t<p>An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don't have any permissions by default. \n\t\t You must grant them explicit permission to perform specific actions. For more information, \n\t\t see <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html\">Access Control Using AWS Identity and Access Management (IAM)</a>.</p>\n <p>For conceptual information and the underlying REST API, go to \n <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/api-initiate-job-post.html\">Initiate a Job</a>\n and \n <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/vault-inventory.html\">Downloading a Vault Inventory</a> </p>\n \n "
1735
+ "documentation": "\n\t <p>This operation initiates a job of the specified type. In this release, you can initiate a\n\t\t\tjob to retrieve either an archive or a vault inventory (a list of archives in a vault). </p>\n\n\t\t<p>Retrieving data from Amazon Glacier is a two-step process: </p>\n\n\t\t<ol>\n\t\t\t<li><p>Initiate a retrieval job.</p></li>\n\t\t\t<li><p>After the job completes, download the bytes.</p></li>\n\t\t</ol>\n\n\t\t<p>The retrieval request is executed asynchronously. When you initiate a retrieval job,\n\t\t\tAmazon Glacier creates a job and returns a job ID in the response. When Amazon Glacier completes\n\t\t\tthe job, you can get the job output (archive or inventory data). For information about\n\t\t\tgetting job output, see <a>GetJobOutput</a> operation. </p>\n\n\t\t<p>The job must complete before you can get its output. To determine when a job is complete,\n\t\t\tyou have the following options:</p>\n\n\t\t<ul>\n\t\t\t<li>\n<p><b>Use Amazon SNS Notification</b> You can specify an\n\t\t\t\t\t\tAmazon Simple Notification Service (Amazon SNS) topic to which Amazon Glacier can\n\t\t\t\t\t\tpost a notification after the job is completed. You can specify an SNS topic\n\t\t\t\t\t\tper job request. The notification is sent only after Amazon Glacier completes the\n\t\t\t\t\t\tjob. In addition to specifying an SNS topic per job request, you can\n\t\t\t\t\t\tconfigure vault notifications for a vault so that job notifications are\n\t\t\t\t\t\talways sent. For more information, see <a>SetVaultNotifications</a>.</p>\n\t\t\t</li>\n\t\t\t<li>\n<p><b>Get job details</b> You can make a <a>DescribeJob</a> request\n\t\t\t\t\t\tto obtain job status information while a job is in progress. However, it is\n\t\t\t\t\t\tmore efficient to use an Amazon SNS notification to determine when a job is\n\t\t\t\t\t\tcomplete.</p>\n\t\t\t</li>\n\t\t</ul>\n\n\t\t<note><p>The information you get via notification is same that you get by calling <a>DescribeJob</a>.</p></note>\n\n\t\t<p>If for a specific event, you add both the notification configuration on the vault and also\n\t\t\tspecify an SNS topic in your initiate job request, Amazon Glacier sends both\n\t\t\tnotifications. For more information, see <a>SetVaultNotifications</a>.</p>\n\n\t\t<p>An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don't have any permissions by default. You must grant them explicit permission to perform specific actions. For more information, see <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html\">Access Control Using AWS Identity and Access Management (IAM)</a>.</p>\n\n\t\t<p><b>About the Vault Inventory</b></p>\n\n\t\t<p>Amazon Glacier prepares an inventory for each vault periodically, every 24 hours. When you\n\t\t\t\tinitiate a job for a vault inventory, Amazon Glacier returns the last inventory for\n\t\t\t\tthe vault. The inventory data you get might be up to a day or two days old. Also,\n\t\t\t\tthe initiate inventory job might take some time to complete before you can download\n\t\t\t\tthe vault inventory. So you do not want to retrieve a vault inventory for each vault\n\t\t\t\toperation. However, in some scenarios, you might find the vault inventory useful.\n\t\t\t\tFor example, when you upload an archive, you can provide an archive description but\n\t\t\t\tnot an archive name. Amazon Glacier provides you a unique archive ID, an opaque\n\t\t\t\tstring of characters. So, you might maintain your own database that maps archive\n\t\t\t\tnames to their corresponding Amazon Glacier assigned archive IDs. You might find the\n\t\t\t\tvault inventory useful in the event you need to reconcile information in your\n\t\t\t\tdatabase with the actual vault inventory. </p>\n \n <p><b>Range Inventory Retrieval</b></p>\n <p>You can limit the number of inventory items retrieved by filtering on the archive creation date \n or by setting a limit.</p>\n <p><i>Filtering by Archive Creation Date</i></p>\n <p>You can retrieve inventory items for archives created between <code>StartDate</code> and\n <code>EndDate</code> by specifying values for these parameters in the \n <b>InitiateJob</b> request. \n Archives created on or after the <code>StartDate</code> and before the <code>EndDate</code> will be returned. If\n you only provide the <code>StartDate</code> without the <code>EndDate</code>, you will retrieve the inventory for\n all archives created on or after the <code>StartDate</code>. If you only provide the <code>EndDate</code>\n without the <code>StartDate</code>, you will get back the inventory for all archives created\n before the <code>EndDate</code>.</p>\t\t\n \n <p><i>Limiting Inventory Items per Retrieval</i></p>\n <p>You can limit the number of inventory items returned by setting the <code>Limit</code>\n parameter in the <b>InitiateJob</b> request. The\n inventory job output will contain inventory items up to the specified\n <code>Limit</code>. If there are more inventory items available, the result\n is paginated. After a job is complete you can use the <a>DescribeJob</a> \n operation to get a marker that you use in a subsequent <b>InitiateJob</b> request. \n The marker will indicate the starting point to retrieve the next set of inventory items. You can page through your\n entire inventory by repeatedly making <b>InitiateJob</b> requests with the marker from the previous \n <b>DescribeJob</b> output, until you get a marker from <b>DescribeJob</b> that returns null, indicating\n that there are no more inventory items available.</p>\t\t\t\t\t\t\n <p>You can use the <code>Limit</code> parameter together with the date range parameters.</p>\t \n \n <p><b>About Ranged Archive Retrieval</b></p>\n <p>\n You can initiate an archive retrieval for the whole archive or a range of the archive. \n In the case of ranged archive retrieval, you specify a byte range to return or the whole archive. \n The range specified must be megabyte (MB) aligned, that is the range start value must be \n divisible by 1 MB and range end value plus 1 must be divisible by 1 MB or equal the end of the \n archive. If the ranged archive retrieval is not megabyte aligned, this operation returns a \n 400 response. Furthermore, to ensure you get checksum values for data you download using \n Get Job Output API, the range must be tree hash aligned. \n </p>\n\n\t\t<p>An AWS account has full permission to perform all operations (actions). However, AWS Identity and Access Management (IAM) users don't have any permissions by default. \n\t\t You must grant them explicit permission to perform specific actions. For more information, \n\t\t see <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/using-iam-with-amazon-glacier.html\">Access Control Using AWS Identity and Access Management (IAM)</a>.</p>\n <p>For conceptual information and the underlying REST API, go to \n <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/api-initiate-job-post.html\">Initiate a Job</a>\n and \n <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/vault-inventory.html\">Downloading a Vault Inventory</a> </p>\n \n "
1704
1736
  },
1705
1737
  "InitiateMultipartUpload": {
1706
1738
  "name": "InitiateMultipartUpload",
@@ -1918,7 +1950,7 @@
1918
1950
  "JobId": {
1919
1951
  "shape_name": "string",
1920
1952
  "type": "string",
1921
- "documentation": "\n <p>An opaque string that identifies an Amazon Glacier job.</p>\n \n "
1953
+ "documentation": "\n <p>An opaque string that identifies an Amazon Glacier job.</p> \n "
1922
1954
  },
1923
1955
  "JobDescription": {
1924
1956
  "shape_name": "string",
@@ -2003,6 +2035,38 @@
2003
2035
  "shape_name": "string",
2004
2036
  "type": "string",
2005
2037
  "documentation": "\n <p>The retrieved byte range for archive retrieval jobs in the form \"<i>StartByteValue</i>-<i>EndByteValue</i>\" \n If no range was specified in the archive retrieval, then the whole archive is retrieved and \n <i>StartByteValue</i> equals 0 and <i>EndByteValue</i> equals the size of the archive minus 1. \n For inventory retrieval jobs this field is null. </p> \n "
2038
+ },
2039
+ "InventoryRetrievalParameters": {
2040
+ "shape_name": "InventoryRetrievalJobDescription",
2041
+ "type": "structure",
2042
+ "members": {
2043
+ "Format": {
2044
+ "shape_name": "string",
2045
+ "type": "string",
2046
+ "documentation": "\n <p>The output format for the vault inventory list, which is set by the <b>InitiateJob</b> request \n when initiating a job to retrieve a vault inventory. Valid values are \"CSV\" and \"JSON\".</p>\n "
2047
+ },
2048
+ "StartDate": {
2049
+ "shape_name": "DateTime",
2050
+ "type": "string",
2051
+ "documentation": "\n <p>The start of the date range in UTC for vault inventory retrieval that includes archives created \n on or after this date. A string representation of ISO 8601 date format, for example, 2013-03-20T17:03:43Z.</p>\n "
2052
+ },
2053
+ "EndDate": {
2054
+ "shape_name": "DateTime",
2055
+ "type": "string",
2056
+ "documentation": "\n <p>The end of the date range in UTC for vault inventory retrieval that includes archives created before this date.\n A string representation of ISO 8601 date format, for example, 2013-03-20T17:03:43Z.</p>\n "
2057
+ },
2058
+ "Limit": {
2059
+ "shape_name": "string",
2060
+ "type": "string",
2061
+ "documentation": "\n <p>Specifies the maximum number of inventory items returned per vault inventory retrieval request. \n This limit is set when initiating the job with the a <b>InitiateJob</b> request. </p>\n "
2062
+ },
2063
+ "Marker": {
2064
+ "shape_name": "string",
2065
+ "type": "string",
2066
+ "documentation": "\n <p>An opaque string that represents where to continue pagination of the vault inventory retrieval results. \n You use the marker in a new <b>InitiateJob</b> request to obtain additional inventory items. \n If there are no more inventory items, this value is <code>null</code>. For more information, see\n <a href=\"http://docs.aws.amazon.com/amazonglacier/latest/dev/api-initiate-job-post.html#api-initiate-job-post-vault-inventory-list-filtering\">\n Range Inventory Retrieval</a>.</p> \n "
2067
+ }
2068
+ },
2069
+ "documentation": "\n <p>Parameters used for range inventory retrieval.</p> \n "
2006
2070
  }
2007
2071
  },
2008
2072
  "documentation": "\n <p>Describes an Amazon Glacier job.</p>\n "
@@ -1242,85 +1242,6 @@
1242
1242
  ],
1243
1243
  "documentation": "\n\t\t<p>\n\t\tGets statistics for the specified metric.\n\t</p>\n\t\t<p>\n\t\t\tThe maximum number of data points returned from a single\n\t\t\t<code>GetMetricStatistics</code> request is 1,440, wereas the maximum number of data points\n\t\t\tthat can be queried is 50,850. If you make a request that generates more than 1,440 data points,\n\t\t\tAmazon CloudWatch returns an error. In such a case, you can alter the request by narrowing the specified\n\t\t\ttime range or increasing the specified period. Alternatively, you can make multiple requests across adjacent time ranges.\n\t\t</p>\n\t\t<p>\n\t\t\tAmazon CloudWatch aggregates data points based on the\n\t\t\tlength of the <code>period</code> that you specify. For example, if\n\t\t\tyou request statistics with a one-minute granularity, Amazon CloudWatch aggregates data points\n\t\t\twith time stamps that fall within the same one-minute period. In such a case, the data points queried can greatly outnumber the data points returned.\n\t\t</p>\n\n\t\t<p>\n\t\tThe following examples show various statistics allowed by the data point query maximum of 50,850\n\t\twhen you call <code>GetMetricStatistics</code> on Amazon EC2 instances with\n\t\tdetailed (one-minute) monitoring enabled:\n\t\t</p>\n\t\t<ul>\n\t\t\t<li>Statistics for up to 400 instances for a span of one hour</li>\n\t\t\t<li>Statistics for up to 35 instances over a span of 24 hours</li>\n\t\t\t<li>Statistics for up to 2 instances over a span of 2 weeks</li>\n\t\t</ul>\n\t\t<p>\n\t\t\tFor information about the namespace, metric names, and dimensions that other Amazon Web Services products use to send metrics to Cloudwatch,\n\t\t\tgo to <a href=\"http://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/CW_Support_For_AWS.html\">Amazon CloudWatch Metrics, Namespaces, and Dimensions Reference</a>\n\t\t\tin the <i>Amazon CloudWatch Developer Guide</i>.\n\t\t</p>\n\t"
1244
1244
  },
1245
- "ListHostInfo": {
1246
- "name": "ListHostInfo",
1247
- "input": null,
1248
- "output": {
1249
- "shape_name": "ListHostInfoOutput",
1250
- "type": "structure",
1251
- "members": {
1252
- "HostName": {
1253
- "shape_name": "HostName",
1254
- "type": "string",
1255
- "documentation": null
1256
- },
1257
- "StackName": {
1258
- "shape_name": "StackName",
1259
- "type": "string",
1260
- "documentation": null
1261
- },
1262
- "Marketplace": {
1263
- "shape_name": "Marketplace",
1264
- "type": "string",
1265
- "documentation": null
1266
- },
1267
- "Region": {
1268
- "shape_name": "Region",
1269
- "type": "string",
1270
- "documentation": null
1271
- },
1272
- "SdbDatastoreEndpoints": {
1273
- "shape_name": "SdbDatastoreEndpoints",
1274
- "type": "list",
1275
- "members": {
1276
- "shape_name": "SdbDatastoreEndpoint",
1277
- "type": "string",
1278
- "documentation": null
1279
- },
1280
- "documentation": null
1281
- },
1282
- "DatastoreEndpoints": {
1283
- "shape_name": "DatastoreEndpoints",
1284
- "type": "list",
1285
- "members": {
1286
- "shape_name": "DatastoreEndpoint",
1287
- "type": "string",
1288
- "documentation": null
1289
- },
1290
- "documentation": null
1291
- },
1292
- "AmpQueues": {
1293
- "shape_name": "AmpQueues",
1294
- "type": "list",
1295
- "members": {
1296
- "shape_name": "AmpQueue",
1297
- "type": "string",
1298
- "documentation": null
1299
- },
1300
- "documentation": null
1301
- }
1302
- },
1303
- "documentation": null
1304
- },
1305
- "errors": [
1306
- {
1307
- "shape_name": "InternalServiceFault",
1308
- "type": "structure",
1309
- "members": {
1310
- "Message": {
1311
- "shape_name": "FaultDescription",
1312
- "type": "string",
1313
- "documentation": "\n\t\t<p></p>\n\t"
1314
- }
1315
- },
1316
- "member_order": [
1317
- "Message"
1318
- ],
1319
- "documentation": "\n\t\t<p>\n\t\tIndicates that the request processing has\n\t\tfailed due to some unknown error, exception, or failure.\n\t\t</p>\n\t"
1320
- }
1321
- ],
1322
- "documentation": null
1323
- },
1324
1245
  "ListMetrics": {
1325
1246
  "name": "ListMetrics",
1326
1247
  "input": {
@@ -1909,235 +1830,6 @@
1909
1830
  ],
1910
1831
  "documentation": "\n\t\t<p>\n\t\tPublishes metric data points to Amazon CloudWatch. Amazon Cloudwatch\n\t\tassociates the data points with the specified metric. If the specified metric does not exist,\n\t\tAmazon CloudWatch creates the metric. It can take up to fifteen minutes for a new metric to appear\n\t\tin calls to the <a>ListMetrics</a> action.</p>\n\n\t\t<p>\n\t\t\tThe size of a <function>PutMetricData</function> request is limited to 8 KB\n\t\t\tfor HTTP GET requests and 40 KB for HTTP POST requests.\n\t\t</p>\n\t\t<important>\n\t\t\tAlthough the <code>Value</code> parameter accepts numbers of type <code>Double</code>,\n\t\t\tAmazon CloudWatch truncates values with very large exponents.\n\t\t\tValues with base-10 exponents greater than 126 (1 x 10^126) are truncated.\n\t\t\tLikewise, values with base-10 exponents less than -130 (1 x 10^-130) are also truncated.\n\t\t</important>\n\t\t\n\t\t<p>Data that is timestamped 24 hours or more in the past may take in excess of 48 hours to become\n\t\t\tavailable from submission time using <code>GetMetricStatistics</code>.</p>\n\n\t\t<examples>\n\t\t\t<queryrequest>\nThe following example puts data for a single metric containing one dimension:\n\nhttps://monitoring.amazonaws.com/doc/2010-08-01/\n?Action=PutMetricData\n&Version=2010-08-01\n&Namespace=TestNamespace\n&MetricData.member.1.MetricName=buffers\n&MetricData.member.1.Unit=Bytes\n&MetricData.member.1.Value=231434333\n&MetricData.member.1.Dimensions.member.1.Name=InstanceType\n&MetricData.member.1.Dimensions.member.1.Value=m1.small\n&AUTHPARAMS\n\n\nThe following example puts data for a single metric containing two dimensions:\n\nhttps://monitoring.amazonaws.com/doc/2010-08-01/\n?Action=PutMetricData\n&Version=2010-08-01\n&Namespace=TestNamespace\n&MetricData.member.1.MetricName=buffers\n&MetricData.member.1.Unit=Bytes\n&MetricData.member.1.Value=231434333\n&MetricData.member.1.Dimensions.member.1.Name=InstanceID\n&MetricData.member.1.Dimensions.member.1.Value=i-aaba32d4\n&MetricData.member.1.Dimensions.member.2.Name=InstanceType\n&MetricData.member.1.Dimensions.member.2.Value=m1.small\n&AUTHPARAMS\n\n\nThe following example puts data for two metrics, each with two dimensions:\n\nhttps://monitoring.amazonaws.com/doc/2010-08-01/\n?Action=PutMetricData\n&Version=2010-08-01\n&Namespace=TestNamespace\n&MetricData.member.1.MetricName=buffers\n&MetricData.member.1.Unit=Bytes\n&MetricData.member.1.Value=231434333\n&MetricData.member.1.Dimensions.member.1.Name=InstanceID\n&MetricData.member.1.Dimensions.member.1.Value=i-aaba32d4\n&MetricData.member.1.Dimensions.member.2.Name=InstanceType\n&MetricData.member.1.Dimensions.member.2.Value=m1.small\n&MetricData.member.2.MetricName=latency\n&MetricData.member.2.Unit=Milliseconds\n&MetricData.member.2.Value=23\n&MetricData.member.2.Dimensions.member.1.Name=InstanceID\n&MetricData.member.2.Dimensions.member.1.Value=i-aaba32d4\n&MetricData.member.2.Dimensions.member.2.Name=InstanceType\n&MetricData.member.2.Dimensions.member.2.Value=m1.small\n&AUTHPARAMS\n\t\t\t</queryrequest>\n\t\t\t<queryresponse>\n<PutMetricDataResponse xmlns=\"http://monitoring.amazonaws.com/doc/2010-08-01/\">\n <ResponseMetadata>\n <RequestId>e16fc4d3-9a04-11e0-9362-093a1cae5385</RequestId>\n </ResponseMetadata>\n</PutMetricDataResponse> \n\t\t\t</queryresponse>\n\t\t</examples>\n\t\t\n\t"
1911
1832
  },
1912
- "PutMetricDataBatch": {
1913
- "name": "PutMetricDataBatch",
1914
- "input": {
1915
- "shape_name": "PutMetricDataBatchInput",
1916
- "type": "structure",
1917
- "members": {
1918
- "MetricDataBatches": {
1919
- "shape_name": "MetricDataBatches",
1920
- "type": "list",
1921
- "members": {
1922
- "shape_name": "MetricDataBatch",
1923
- "type": "structure",
1924
- "members": {
1925
- "AccountId": {
1926
- "shape_name": "AccountId",
1927
- "type": "string",
1928
- "min_length": 1,
1929
- "max_length": 255,
1930
- "documentation": null,
1931
- "required": true
1932
- },
1933
- "Namespace": {
1934
- "shape_name": "Namespace",
1935
- "type": "string",
1936
- "pattern": "[^:].*",
1937
- "min_length": 1,
1938
- "max_length": 255,
1939
- "documentation": null,
1940
- "required": true
1941
- },
1942
- "MetricData": {
1943
- "shape_name": "MetricData",
1944
- "type": "list",
1945
- "members": {
1946
- "shape_name": "MetricDatum",
1947
- "type": "structure",
1948
- "members": {
1949
- "MetricName": {
1950
- "shape_name": "MetricName",
1951
- "type": "string",
1952
- "min_length": 1,
1953
- "max_length": 255,
1954
- "documentation": "\n\t\t<p>\n\t\t\tThe name of the metric.\n\t\t</p>\n\t",
1955
- "required": true
1956
- },
1957
- "Dimensions": {
1958
- "shape_name": "Dimensions",
1959
- "type": "list",
1960
- "members": {
1961
- "shape_name": "Dimension",
1962
- "type": "structure",
1963
- "members": {
1964
- "Name": {
1965
- "shape_name": "DimensionName",
1966
- "type": "string",
1967
- "min_length": 1,
1968
- "max_length": 255,
1969
- "documentation": "\n\t\t<p>\n\t\tThe name of the dimension.\n\t\t</p>\n\t",
1970
- "required": true
1971
- },
1972
- "Value": {
1973
- "shape_name": "DimensionValue",
1974
- "type": "string",
1975
- "min_length": 1,
1976
- "max_length": 255,
1977
- "documentation": "\n\t\t<p>\n\t\tThe value representing the dimension measurement\n\t\t</p>\n\t",
1978
- "required": true
1979
- }
1980
- },
1981
- "member_order": [
1982
- "Name",
1983
- "Value"
1984
- ],
1985
- "documentation": "\n\t\t<p>\n\t\tThe <code>Dimension</code> data type further expands on the\n\t\tidentity of a metric using a Name, Value pair.\n\t\t</p>\n\t\t<p>For examples that use one or more dimensions, see <a>PutMetricData</a>.</p>\n\n\t"
1986
- },
1987
- "max_length": 10,
1988
- "documentation": "\n\t\t<p>\n\t\t\tA list of dimensions associated with the metric. Note, when using the Dimensions value in a query, you need to append .member.N to it (e.g., Dimensions.member.N).\n\t\t</p>\n\t"
1989
- },
1990
- "Timestamp": {
1991
- "shape_name": "Timestamp",
1992
- "type": "timestamp",
1993
- "documentation": "\n\t\t<p>\n\t\t\tThe time stamp used for the metric. If not specified, the default value is set to the time the metric data was received. Amazon CloudWatch uses Coordinated Universal Time (UTC) when returning time stamps, which do not accommodate seasonal adjustments such as daylight savings time. For more information, see <a href=\"http://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/cloudwatch_concepts.html#about_timestamp\">Time stamps</a> in the <i>Amazon CloudWatch Developer Guide</i>.\n\t\t</p>\n\t"
1994
- },
1995
- "Value": {
1996
- "shape_name": "DatapointValue",
1997
- "type": "double",
1998
- "documentation": "\n\t\t<p>\n\t\t\tThe value for the metric.\n\t\t</p>\n\t\t<important>Although the <code>Value</code> parameter accepts numbers of type <code>Double</code>,\n\t\t\tAmazon CloudWatch truncates values with very large exponents.\n\t\t\tValues with base-10 exponents greater than 126 (1 x 10^126) are truncated.\n\t\t\tLikewise, values with base-10 exponents less than -130 (1 x 10^-130) are also truncated.\n\t\t</important>\n\t"
1999
- },
2000
- "StatisticValues": {
2001
- "shape_name": "StatisticSet",
2002
- "type": "structure",
2003
- "members": {
2004
- "SampleCount": {
2005
- "shape_name": "DatapointValue",
2006
- "type": "double",
2007
- "documentation": "\n\t\t<p>\n\t\t\tThe number of samples used for the statistic set.\n\t\t</p>\n\t",
2008
- "required": true
2009
- },
2010
- "Sum": {
2011
- "shape_name": "DatapointValue",
2012
- "type": "double",
2013
- "documentation": "\n\t\t<p>\n\t\t\tThe sum of values for the sample set.\n\t\t</p>\n\t",
2014
- "required": true
2015
- },
2016
- "Minimum": {
2017
- "shape_name": "DatapointValue",
2018
- "type": "double",
2019
- "documentation": "\n\t\t<p>\n\t\t\tThe minimum value of the sample set.\n\t\t</p>\n\t",
2020
- "required": true
2021
- },
2022
- "Maximum": {
2023
- "shape_name": "DatapointValue",
2024
- "type": "double",
2025
- "documentation": "\n\t\t<p>\n\t\t\tThe maximum value of the sample set.\n\t\t</p>\n\t",
2026
- "required": true
2027
- }
2028
- },
2029
- "documentation": "\n\t\t<p>\n\t\t\tA set of statistical values describing the metric.\n\t\t</p>\n\t"
2030
- },
2031
- "Unit": {
2032
- "shape_name": "StandardUnit",
2033
- "type": "string",
2034
- "enum": [
2035
- "Seconds",
2036
- "Microseconds",
2037
- "Milliseconds",
2038
- "Bytes",
2039
- "Kilobytes",
2040
- "Megabytes",
2041
- "Gigabytes",
2042
- "Terabytes",
2043
- "Bits",
2044
- "Kilobits",
2045
- "Megabits",
2046
- "Gigabits",
2047
- "Terabits",
2048
- "Percent",
2049
- "Count",
2050
- "Bytes/Second",
2051
- "Kilobytes/Second",
2052
- "Megabytes/Second",
2053
- "Gigabytes/Second",
2054
- "Terabytes/Second",
2055
- "Bits/Second",
2056
- "Kilobits/Second",
2057
- "Megabits/Second",
2058
- "Gigabits/Second",
2059
- "Terabits/Second",
2060
- "Count/Second",
2061
- "None"
2062
- ],
2063
- "documentation": "\n\t\t<p>\n\t\t\tThe unit of the metric.\n\t\t</p>\n\t"
2064
- }
2065
- },
2066
- "documentation": "\n\t\t<p>\n\t\t\tThe <code>MetricDatum</code> data type encapsulates the information\n\t\t\tsent with <a>PutMetricData</a> to either create a new metric or\n\t\t\tadd new values to be aggregated into an existing metric.\n\t\t</p>\n\t"
2067
- },
2068
- "documentation": null,
2069
- "required": true
2070
- },
2071
- "AutoDecompose": {
2072
- "shape_name": "AutoDecompose",
2073
- "type": "boolean",
2074
- "documentation": null
2075
- }
2076
- },
2077
- "documentation": null
2078
- },
2079
- "documentation": null,
2080
- "required": true
2081
- }
2082
- },
2083
- "documentation": null
2084
- },
2085
- "output": null,
2086
- "errors": [
2087
- {
2088
- "shape_name": "InvalidParameterValueException",
2089
- "type": "structure",
2090
- "members": {
2091
- "message": {
2092
- "shape_name": "AwsQueryErrorMessage",
2093
- "type": "string",
2094
- "documentation": "\n\t\t<p></p>\n\t"
2095
- }
2096
- },
2097
- "documentation": "\n\t\t<p>\n\t\tBad or out-of-range value was supplied for the input\n\t\tparameter.\n\t\t</p>\n\t"
2098
- },
2099
- {
2100
- "shape_name": "MissingRequiredParameterException",
2101
- "type": "structure",
2102
- "members": {
2103
- "message": {
2104
- "shape_name": "AwsQueryErrorMessage",
2105
- "type": "string",
2106
- "documentation": "\n\t\t<p></p>\n\t"
2107
- }
2108
- },
2109
- "documentation": "\n\t\t<p>\n\t\tAn input parameter that is mandatory for processing\n\t\tthe request is not supplied.\n\t\t</p>\n\t"
2110
- },
2111
- {
2112
- "shape_name": "InvalidParameterCombinationException",
2113
- "type": "structure",
2114
- "members": {
2115
- "message": {
2116
- "shape_name": "AwsQueryErrorMessage",
2117
- "type": "string",
2118
- "documentation": "\n\t\t<p></p>\n\t"
2119
- }
2120
- },
2121
- "documentation": "\n\t\t<p>\n\t\tParameters that must not be used together were\n\t\tused together.\n\t\t</p>\n\t"
2122
- },
2123
- {
2124
- "shape_name": "InternalServiceFault",
2125
- "type": "structure",
2126
- "members": {
2127
- "Message": {
2128
- "shape_name": "FaultDescription",
2129
- "type": "string",
2130
- "documentation": "\n\t\t<p></p>\n\t"
2131
- }
2132
- },
2133
- "member_order": [
2134
- "Message"
2135
- ],
2136
- "documentation": "\n\t\t<p>\n\t\tIndicates that the request processing has\n\t\tfailed due to some unknown error, exception, or failure.\n\t\t</p>\n\t"
2137
- }
2138
- ],
2139
- "documentation": null
2140
- },
2141
1833
  "SetAlarmState": {
2142
1834
  "name": "SetAlarmState",
2143
1835
  "input": {