Merge branch 'release-1.20.31'

* release-1.20.31: Bumping version to 1.20.31 Update to latest models Update s3-object-lambda test cases Update S3 Object Lambda service name Update S3 banner endpoint and arn names Refactor S3 Banner customizations Adding S3 Banner Changes
boto · Mar 18, 2021 · ff0bcbe · ff0bcbe
2 parents 14fb527 + dbfe376
commit ff0bcbe
Show file tree

Hide file tree

Showing 15 changed files with 1,706 additions and 250 deletions.
diff --git a/.changes/1.20.31.json b/.changes/1.20.31.json
@@ -0,0 +1,27 @@
+[
+  {
+    "category": "``autoscaling``", 
+    "description": "Amazon EC2 Auto Scaling Instance Refresh now supports phased deployments.", 
+    "type": "api-change"
+  }, 
+  {
+    "category": "``s3``", 
+    "description": "S3 Object Lambda is a new S3 feature that enables users to apply their own custom code to process the output of a standard S3 GET request by automatically invoking a Lambda function with a GET request", 
+    "type": "api-change"
+  }, 
+  {
+    "category": "``redshift``", 
+    "description": "Add new fields for additional information about VPC endpoint for clusters with reallocation enabled, and a new field for total storage capacity for all clusters.", 
+    "type": "api-change"
+  }, 
+  {
+    "category": "``s3control``", 
+    "description": "S3 Object Lambda is a new S3 feature that enables users to apply their own custom code to process the output of a standard S3 GET request by automatically invoking a Lambda function with a GET request", 
+    "type": "api-change"
+  }, 
+  {
+    "category": "``securityhub``", 
+    "description": "New object for separate provider and customer values. New objects track S3 Public Access Block configuration and identify sensitive data. BatchImportFinding requests are limited to 100 findings.", 
+    "type": "api-change"
+  }
+]
diff --git a/CHANGELOG.rst b/CHANGELOG.rst
@@ -2,6 +2,16 @@
 CHANGELOG
 =========
 
+1.20.31
+=======
+
+* api-change:``autoscaling``: Amazon EC2 Auto Scaling Instance Refresh now supports phased deployments.
+* api-change:``s3``: S3 Object Lambda is a new S3 feature that enables users to apply their own custom code to process the output of a standard S3 GET request by automatically invoking a Lambda function with a GET request
+* api-change:``redshift``: Add new fields for additional information about VPC endpoint for clusters with reallocation enabled, and a new field for total storage capacity for all clusters.
+* api-change:``s3control``: S3 Object Lambda is a new S3 feature that enables users to apply their own custom code to process the output of a standard S3 GET request by automatically invoking a Lambda function with a GET request
+* api-change:``securityhub``: New object for separate provider and customer values. New objects track S3 Public Access Block configuration and identify sensitive data. BatchImportFinding requests are limited to 100 findings.
+
+
 1.20.30
 =======
 

diff --git a/botocore/__init__.py b/botocore/__init__.py
@@ -16,7 +16,7 @@
 import re
 import logging
 
-__version__ = '1.20.30'
+__version__ = '1.20.31'
 
 
 class NullHandler(logging.Handler):

diff --git a/botocore/data/autoscaling/2011-01-01/service-2.json b/botocore/data/autoscaling/2011-01-01/service-2.json
@@ -108,7 +108,7 @@
         {"shape":"ResourceContentionFault"},
         {"shape":"ActiveInstanceRefreshNotFoundFault"}
       ],
-      "documentation":"<p>Cancels an instance refresh operation in progress. Cancellation does not roll back any replacements that have already been completed, but it prevents new replacements from being started. </p> <p>For more information, see <a href=\"https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-instance-refresh.html\">Replacing Auto Scaling Instances Based on an Instance Refresh</a>.</p>"
+      "documentation":"<p>Cancels an instance refresh operation in progress. Cancellation does not roll back any replacements that have already been completed, but it prevents new replacements from being started. </p> <p>For more information, see <a href=\"https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-instance-refresh.html\">Replacing Auto Scaling instances based on an instance refresh</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p>"
     },
     "CompleteLifecycleAction":{
       "name":"CompleteLifecycleAction",
@@ -357,7 +357,7 @@
         {"shape":"InvalidNextToken"},
         {"shape":"ResourceContentionFault"}
       ],
-      "documentation":"<p>Describes one or more instance refreshes.</p> <p>You can determine the status of a request by looking at the <code>Status</code> parameter. The following are the possible statuses: </p> <ul> <li> <p> <code>Pending</code> - The request was created, but the operation has not started.</p> </li> <li> <p> <code>InProgress</code> - The operation is in progress.</p> </li> <li> <p> <code>Successful</code> - The operation completed successfully.</p> </li> <li> <p> <code>Failed</code> - The operation failed to complete. You can troubleshoot using the status reason and the scaling activities. </p> </li> <li> <p> <code>Cancelling</code> - An ongoing operation is being cancelled. Cancellation does not roll back any replacements that have already been completed, but it prevents new replacements from being started. </p> </li> <li> <p> <code>Cancelled</code> - The operation is cancelled. </p> </li> </ul> <p>For more information, see <a href=\"https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-instance-refresh.html\">Replacing Auto Scaling Instances Based on an Instance Refresh</a>.</p>"
+      "documentation":"<p>Describes one or more instance refreshes.</p> <p>You can determine the status of a request by looking at the <code>Status</code> parameter. The following are the possible statuses: </p> <ul> <li> <p> <code>Pending</code> - The request was created, but the operation has not started.</p> </li> <li> <p> <code>InProgress</code> - The operation is in progress.</p> </li> <li> <p> <code>Successful</code> - The operation completed successfully.</p> </li> <li> <p> <code>Failed</code> - The operation failed to complete. You can troubleshoot using the status reason and the scaling activities. </p> </li> <li> <p> <code>Cancelling</code> - An ongoing operation is being cancelled. Cancellation does not roll back any replacements that have already been completed, but it prevents new replacements from being started. </p> </li> <li> <p> <code>Cancelled</code> - The operation is cancelled. </p> </li> </ul> <p>For more information, see <a href=\"https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-instance-refresh.html\">Replacing Auto Scaling instances based on an instance refresh</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p>"
     },
     "DescribeLaunchConfigurations":{
       "name":"DescribeLaunchConfigurations",
@@ -837,7 +837,7 @@
         {"shape":"ResourceContentionFault"},
         {"shape":"InstanceRefreshInProgressFault"}
       ],
-      "documentation":"<p>Starts a new instance refresh operation, which triggers a rolling replacement of all previously launched instances in the Auto Scaling group with a new group of instances.</p> <p>If successful, this call creates a new instance refresh request with a unique ID that you can use to track its progress. To query its status, call the <a>DescribeInstanceRefreshes</a> API. To describe the instance refreshes that have already run, call the <a>DescribeInstanceRefreshes</a> API. To cancel an instance refresh operation in progress, use the <a>CancelInstanceRefresh</a> API. </p> <p>For more information, see <a href=\"https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-instance-refresh.html\">Replacing Auto Scaling Instances Based on an Instance Refresh</a>.</p>"
+      "documentation":"<p>Starts a new instance refresh operation, which triggers a rolling replacement of all previously launched instances in the Auto Scaling group with a new group of instances.</p> <p>If successful, this call creates a new instance refresh request with a unique ID that you can use to track its progress. To query its status, call the <a>DescribeInstanceRefreshes</a> API. To describe the instance refreshes that have already run, call the <a>DescribeInstanceRefreshes</a> API. To cancel an instance refresh operation in progress, use the <a>CancelInstanceRefresh</a> API. </p> <p>For more information, see <a href=\"https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-instance-refresh.html\">Replacing Auto Scaling instances based on an instance refresh</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p>"
     },
     "SuspendProcesses":{
       "name":"SuspendProcesses",
@@ -1469,6 +1469,15 @@
       }
     },
     "CapacityRebalanceEnabled":{"type":"boolean"},
+    "CheckpointDelay":{
+      "type":"integer",
+      "max":172800,
+      "min":0
+    },
+    "CheckpointPercentages":{
+      "type":"list",
+      "member":{"shape":"NonZeroIntPercent"}
+    },
     "ClassicLinkVPCSecurityGroups":{
       "type":"list",
       "member":{"shape":"XmlStringMaxLen255"}
@@ -3158,6 +3167,11 @@
     },
     "MonitoringEnabled":{"type":"boolean"},
     "NoDevice":{"type":"boolean"},
+    "NonZeroIntPercent":{
+      "type":"integer",
+      "max":100,
+      "min":1
+    },
     "NotificationConfiguration":{
       "type":"structure",
       "members":{
@@ -3498,9 +3512,17 @@
         "InstanceWarmup":{
           "shape":"RefreshInstanceWarmup",
           "documentation":"<p>The number of seconds until a newly launched instance is configured and ready to use. During this time, Amazon EC2 Auto Scaling does not immediately move on to the next replacement. The default is to use the value for the health check grace period defined for the group.</p>"
+        },
+        "CheckpointPercentages":{
+          "shape":"CheckpointPercentages",
+          "documentation":"<p>Threshold values for each checkpoint in ascending order. Each number must be unique. To replace all instances in the Auto Scaling group, the last number in the array must be <code>100</code>.</p> <p>For usage examples, see <a href=\"https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-adding-checkpoints-instance-refresh.html\">Adding checkpoints to an instance refresh</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p>"
+        },
+        "CheckpointDelay":{
+          "shape":"CheckpointDelay",
+          "documentation":"<p>The amount of time, in seconds, to wait after a checkpoint before continuing. This property is optional, but if you specify a value for it, you must also specify a value for <code>CheckpointPercentages</code>. If you specify a value for <code>CheckpointPercentages</code> and not for <code>CheckpointDelay</code>, the <code>CheckpointDelay</code> defaults to <code>3600</code> (1 hour). </p>"
         }
       },
-      "documentation":"<p>Describes information used to start an instance refresh. </p>"
+      "documentation":"<p>Describes information used to start an instance refresh. </p> <p>All properties are optional. However, if you specify a value for <code>CheckpointDelay</code>, you must also provide a value for <code>CheckpointPercentages</code>. </p>"
     },
     "RefreshStrategy":{
       "type":"string",

diff --git a/botocore/data/redshift/2012-12-01/service-2.json b/botocore/data/redshift/2012-12-01/service-2.json
@@ -2231,6 +2231,10 @@
         "ClusterNamespaceArn":{
           "shape":"String",
           "documentation":"<p>The namespace Amazon Resource Name (ARN) of the cluster.</p>"
+        },
+        "TotalStorageCapacityInMegaBytes":{
+          "shape":"LongOptional",
+          "documentation":"<p>The total storage capacity of the cluster in megabytes. </p>"
         }
       },
       "documentation":"<p>Describes a cluster.</p>",
@@ -2982,7 +2986,7 @@
         },
         "AutomatedSnapshotRetentionPeriod":{
           "shape":"IntegerOptional",
-          "documentation":"<p>The number of days that automated snapshots are retained. If the value is 0, automated snapshots are disabled. Even if automated snapshots are disabled, you can still create manual snapshots when you want with <a>CreateClusterSnapshot</a>. </p> <p>Default: <code>1</code> </p> <p>Constraints: Must be a value from 0 to 35.</p>"
+          "documentation":"<p>The number of days that automated snapshots are retained. If the value is 0, automated snapshots are disabled. Even if automated snapshots are disabled, you can still create manual snapshots when you want with <a>CreateClusterSnapshot</a>. </p> <p>You can't disable automated snapshots for RA3 node types. Set the automated retention period from 1-35 days.</p> <p>Default: <code>1</code> </p> <p>Constraints: Must be a value from 0 to 35.</p>"
         },
         "ManualSnapshotRetentionPeriod":{
           "shape":"IntegerOptional",
@@ -5653,7 +5657,7 @@
         },
         "AutomatedSnapshotRetentionPeriod":{
           "shape":"IntegerOptional",
-          "documentation":"<p>The number of days that automated snapshots are retained. If the value is 0, automated snapshots are disabled. Even if automated snapshots are disabled, you can still create manual snapshots when you want with <a>CreateClusterSnapshot</a>. </p> <p>If you decrease the automated snapshot retention period from its current value, existing automated snapshots that fall outside of the new retention period will be immediately deleted.</p> <p>Default: Uses existing setting.</p> <p>Constraints: Must be a value from 0 to 35.</p>"
+          "documentation":"<p>The number of days that automated snapshots are retained. If the value is 0, automated snapshots are disabled. Even if automated snapshots are disabled, you can still create manual snapshots when you want with <a>CreateClusterSnapshot</a>. </p> <p>If you decrease the automated snapshot retention period from its current value, existing automated snapshots that fall outside of the new retention period will be immediately deleted.</p> <p>You can't disable automated snapshots for RA3 node types. Set the automated retention period from 1-35 days.</p> <p>Default: Uses existing setting.</p> <p>Constraints: Must be a value from 0 to 35.</p>"
         },
         "ManualSnapshotRetentionPeriod":{
           "shape":"IntegerOptional",
@@ -5958,6 +5962,35 @@
         }
       }
     },
+    "NetworkInterface":{
+      "type":"structure",
+      "members":{
+        "NetworkInterfaceId":{
+          "shape":"String",
+          "documentation":"<p>The network interface identifier. </p>"
+        },
+        "SubnetId":{
+          "shape":"String",
+          "documentation":"<p>The subnet identifier. </p>"
+        },
+        "PrivateIpAddress":{
+          "shape":"String",
+          "documentation":"<p>The IPv4 address of the network interface within the subnet. </p>"
+        },
+        "AvailabilityZone":{
+          "shape":"String",
+          "documentation":"<p>The Availability Zone. </p>"
+        }
+      },
+      "documentation":"<p>Describes a network interface. </p>"
+    },
+    "NetworkInterfaceList":{
+      "type":"list",
+      "member":{
+        "shape":"NetworkInterface",
+        "locationName":"NetworkInterface"
+      }
+    },
     "NodeConfigurationOption":{
       "type":"structure",
       "members":{
@@ -6124,7 +6157,7 @@
         },
         "ParameterValue":{
           "shape":"String",
-          "documentation":"<p>The value of the parameter.</p>"
+          "documentation":"<p>The value of the parameter. If <code>ParameterName</code> is <code>wlm_json_configuration</code>, then the maximum size of <code>ParameterValue</code> is 8000 characters.</p>"
         },
         "Description":{
           "shape":"String",
@@ -6760,7 +6793,7 @@
         },
         "AutomatedSnapshotRetentionPeriod":{
           "shape":"IntegerOptional",
-          "documentation":"<p>The number of days that automated snapshots are retained. If the value is 0, automated snapshots are disabled. Even if automated snapshots are disabled, you can still create manual snapshots when you want with <a>CreateClusterSnapshot</a>. </p> <p>Default: The value selected for the cluster from which the snapshot was taken.</p> <p>Constraints: Must be a value from 0 to 35.</p>"
+          "documentation":"<p>The number of days that automated snapshots are retained. If the value is 0, automated snapshots are disabled. Even if automated snapshots are disabled, you can still create manual snapshots when you want with <a>CreateClusterSnapshot</a>. </p> <p>You can't disable automated snapshots for RA3 node types. Set the automated retention period from 1-35 days.</p> <p>Default: The value selected for the cluster from which the snapshot was taken.</p> <p>Constraints: Must be a value from 0 to 35.</p>"
         },
         "ManualSnapshotRetentionPeriod":{
           "shape":"IntegerOptional",
@@ -8280,6 +8313,14 @@
         "VpcEndpointId":{
           "shape":"String",
           "documentation":"<p>The connection endpoint ID for connecting an Amazon Redshift cluster through the proxy.</p>"
+        },
+        "VpcId":{
+          "shape":"String",
+          "documentation":"<p>The VPC identifier that the endpoint is associated. </p>"
+        },
+        "NetworkInterfaces":{
+          "shape":"NetworkInterfaceList",
+          "documentation":"<p>One or more network interfaces of the endpoint. Also known as an interface endpoint. </p>"
         }
       },
       "documentation":"<p>The connection endpoint for connecting an Amazon Redshift cluster through the proxy.</p>"