Release v1.44.141 (2022-11-18) (#4627)

Release v1.44.141 (2022-11-18) === ### Service Client Updates * `service/appflow`: Updates service API and documentation * `service/auditmanager`: Updates service API and documentation * `service/chime-sdk-voice`: Adds new service * `service/cloudfront`: Updates service API and documentation * CloudFront API support for staging distributions and associated traffic management policies. * `service/connect`: Updates service API and documentation * `service/dynamodb`: Updates service API, documentation, waiters, paginators, and examples * Updated minor fixes for DynamoDB documentation. * `service/ec2`: Updates service API and documentation * This release adds support for copying an Amazon Machine Image's tags when copying an AMI. * `service/glue`: Updates service API and documentation * AWSGlue Crawler - Adding support for Table and Column level Comments with database level datatypes for JDBC based crawler. * `service/iot-roborunner`: Adds new service * `service/quicksight`: Updates service API, documentation, and paginators * This release adds the following: 1) Asset management for centralized assets governance 2) QuickSight Q now supports public embedding 3) New Termination protection flag to mitigate accidental deletes 4) Athena data sources now accept a custom IAM role 5) QuickSight supports connectivity to Databricks * `service/sagemaker`: Updates service API and documentation * Added DisableProfiler flag as a new field in ProfilerConfig * `service/servicecatalog`: Updates service API and documentation * This release 1. adds support for Principal Name Sharing with Service Catalog portfolio sharing. 2. Introduces repo sourced products which are created and managed with existing SC APIs. These products are synced to external repos and auto create new product versions based on changes in the repo. * `service/ssm-sap`: Updates service API, documentation, paginators, and examples * `service/states`: Updates service API and documentation * This release adds support for using Step Functions service integrations to invoke any cross-account AWS resource, even if that service doesn't support resource-based policies or cross-account calls. See https://docs.aws.amazon.com/step-functions/latest/dg/concepts-access-cross-acct-resources.html * `service/streams.dynamodb`: Updates service documentation * `service/transfer`: Updates service API and documentation * Adds a NONE encryption algorithm type to AS2 connectors, providing support for skipping encryption of the AS2 message body when a HTTPS URL is also specified.
aws · Nov 18, 2022 · e979fb5 · e979fb5
1 parent 00f6e72
commit e979fb5
Show file tree

Hide file tree

Showing 67 changed files with 25,291 additions and 1,170 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,3 +1,33 @@
+Release v1.44.141 (2022-11-18)
+===
+
+### Service Client Updates
+* `service/appflow`: Updates service API and documentation
+* `service/auditmanager`: Updates service API and documentation
+* `service/chime-sdk-voice`: Adds new service
+* `service/cloudfront`: Updates service API and documentation
+  * CloudFront API support for staging distributions and associated traffic management policies.
+* `service/connect`: Updates service API and documentation
+* `service/dynamodb`: Updates service API, documentation, waiters, paginators, and examples
+  * Updated minor fixes for DynamoDB documentation.
+* `service/ec2`: Updates service API and documentation
+  * This release adds support for copying an Amazon Machine Image's tags when copying an AMI.
+* `service/glue`: Updates service API and documentation
+  * AWSGlue Crawler - Adding support for Table and Column level Comments with database level datatypes for JDBC based crawler.
+* `service/iot-roborunner`: Adds new service
+* `service/quicksight`: Updates service API, documentation, and paginators
+  * This release adds the following: 1) Asset management for centralized assets governance 2) QuickSight Q now supports public embedding 3) New Termination protection flag to mitigate accidental deletes 4) Athena data sources now accept a custom IAM role 5) QuickSight supports connectivity to Databricks
+* `service/sagemaker`: Updates service API and documentation
+  * Added DisableProfiler flag as a new field in ProfilerConfig
+* `service/servicecatalog`: Updates service API and documentation
+  * This release 1. adds support for Principal Name Sharing with Service Catalog portfolio sharing. 2. Introduces repo sourced products which are created and managed with existing SC APIs. These products are synced to external repos and auto create new product versions based on changes in the repo.
+* `service/ssm-sap`: Updates service API, documentation, paginators, and examples
+* `service/states`: Updates service API and documentation
+  * This release adds support for using Step Functions service integrations to invoke any cross-account AWS resource, even if that service doesn't support resource-based policies or cross-account calls. See https://docs.aws.amazon.com/step-functions/latest/dg/concepts-access-cross-acct-resources.html
+* `service/streams.dynamodb`: Updates service documentation
+* `service/transfer`: Updates service API and documentation
+  * Adds a NONE encryption algorithm type to AS2 connectors, providing support for skipping encryption of the AS2 message body when a HTTPS URL is also specified.
+
 Release v1.44.140 (2022-11-17)
 ===
 

diff --git a/aws/endpoints/defaults.go b/aws/endpoints/defaults.go
diff --git a/aws/version.go b/aws/version.go
@@ -5,4 +5,4 @@ package aws
 const SDKName = "aws-sdk-go"
 
 // SDKVersion is the version of this SDK
-const SDKVersion = "1.44.140"
+const SDKVersion = "1.44.141"
diff --git a/models/apis/appflow/2020-08-23/api-2.json b/models/apis/appflow/2020-08-23/api-2.json
@@ -321,6 +321,26 @@
         {"shape":"InternalServerException"}
       ]
     },
+    "UpdateConnectorRegistration":{
+      "name":"UpdateConnectorRegistration",
+      "http":{
+        "method":"POST",
+        "requestUri":"/update-connector-registration"
+      },
+      "input":{"shape":"UpdateConnectorRegistrationRequest"},
+      "output":{"shape":"UpdateConnectorRegistrationResponse"},
+      "errors":[
+        {"shape":"ValidationException"},
+        {"shape":"ConflictException"},
+        {"shape":"AccessDeniedException"},
+        {"shape":"ResourceNotFoundException"},
+        {"shape":"ServiceQuotaExceededException"},
+        {"shape":"ThrottlingException"},
+        {"shape":"InternalServerException"},
+        {"shape":"ConnectorServerException"},
+        {"shape":"ConnectorAuthenticationException"}
+      ]
+    },
     "UpdateFlow":{
       "name":"UpdateFlow",
       "http":{
@@ -3267,6 +3287,21 @@
         "connectorProfileArn":{"shape":"ConnectorProfileArn"}
       }
     },
+    "UpdateConnectorRegistrationRequest":{
+      "type":"structure",
+      "required":["connectorLabel"],
+      "members":{
+        "connectorLabel":{"shape":"ConnectorLabel"},
+        "description":{"shape":"Description"},
+        "connectorProvisioningConfig":{"shape":"ConnectorProvisioningConfig"}
+      }
+    },
+    "UpdateConnectorRegistrationResponse":{
+      "type":"structure",
+      "members":{
+        "connectorArn":{"shape":"ARN"}
+      }
+    },
     "UpdateFlowRequest":{
       "type":"structure",
       "required":[

diff --git a/models/apis/appflow/2020-08-23/docs-2.json b/models/apis/appflow/2020-08-23/docs-2.json
@@ -16,13 +16,14 @@
     "ListConnectors": "<p>Returns the list of all registered custom connectors in your Amazon Web Services account. This API lists only custom connectors registered in this account, not the Amazon Web Services authored connectors. </p>",
     "ListFlows": "<p> Lists all of the flows associated with your account. </p>",
     "ListTagsForResource": "<p> Retrieves the tags that are associated with a specified flow. </p>",
-    "RegisterConnector": "<p>Registers a new connector with your Amazon Web Services account. Before you can register the connector, you must deploy lambda in your account.</p>",
+    "RegisterConnector": "<p>Registers a new custom connector with your Amazon Web Services account. Before you can register the connector, you must deploy the associated AWS lambda function in your account.</p>",
     "StartFlow": "<p> Activates an existing flow. For on-demand flows, this operation runs the flow immediately. For schedule and event-triggered flows, this operation activates the flow. </p>",
     "StopFlow": "<p> Deactivates the existing flow. For on-demand flows, this operation returns an <code>unsupportedOperationException</code> error message. For schedule and event-triggered flows, this operation deactivates the flow. </p>",
     "TagResource": "<p> Applies a tag to the specified flow. </p>",
-    "UnregisterConnector": "<p>Unregisters the custom connector registered in your account that matches the connectorLabel provided in the request.</p>",
+    "UnregisterConnector": "<p>Unregisters the custom connector registered in your account that matches the connector label provided in the request.</p>",
     "UntagResource": "<p> Removes a tag from the specified flow. </p>",
     "UpdateConnectorProfile": "<p> Updates a given connector profile associated with your account. </p>",
+    "UpdateConnectorRegistration": "<p>Updates a custom connector that you've previously registered. This operation updates the connector with one of the following:</p> <ul> <li> <p>The latest version of the AWS Lambda function that's assigned to the connector</p> </li> <li> <p>A new AWS Lambda function that you specify</p> </li> </ul>",
     "UpdateFlow": "<p> Updates an existing flow. </p>"
   },
   "shapes": {
@@ -35,7 +36,8 @@
         "ListTagsForResourceRequest$resourceArn": "<p> The Amazon Resource Name (ARN) of the specified flow. </p>",
         "RegisterConnectorResponse$connectorArn": "<p>The ARN of the connector being registered.</p>",
         "TagResourceRequest$resourceArn": "<p> The Amazon Resource Name (ARN) of the flow that you want to tag. </p>",
-        "UntagResourceRequest$resourceArn": "<p> The Amazon Resource Name (ARN) of the flow that you want to untag. </p>"
+        "UntagResourceRequest$resourceArn": "<p> The Amazon Resource Name (ARN) of the flow that you want to untag. </p>",
+        "UpdateConnectorRegistrationResponse$connectorArn": "<p>The ARN of the connector being updated.</p>"
       }
     },
     "AccessDeniedException": {
@@ -414,7 +416,8 @@
         "FlowDefinition$sourceConnectorLabel": "<p>The label of the source connector in the flow.</p>",
         "FlowDefinition$destinationConnectorLabel": "<p>The label of the destination connector in the flow.</p>",
         "RegisterConnectorRequest$connectorLabel": "<p> The name of the connector. The name is unique for each <code>ConnectorRegistration</code> in your Amazon Web Services account.</p>",
-        "UnregisterConnectorRequest$connectorLabel": "<p>The label of the connector. The label is unique for each <code>ConnectorRegistration</code> in your Amazon Web Services account.</p>"
+        "UnregisterConnectorRequest$connectorLabel": "<p>The label of the connector. The label is unique for each <code>ConnectorRegistration</code> in your Amazon Web Services account.</p>",
+        "UpdateConnectorRegistrationRequest$connectorLabel": "<p>The name of the connector. The name is unique for each connector registration in your AWS account.</p>"
       }
     },
     "ConnectorList": {
@@ -540,7 +543,8 @@
       "base": "<p>Contains information about the configuration of the connector being registered.</p>",
       "refs": {
         "ConnectorConfiguration$connectorProvisioningConfig": "<p>The configuration required for registering the connector.</p>",
-        "RegisterConnectorRequest$connectorProvisioningConfig": "<p>The provisioning type of the connector. Currently the only supported value is LAMBDA.</p>"
+        "RegisterConnectorRequest$connectorProvisioningConfig": "<p>The provisioning type of the connector. Currently the only supported value is LAMBDA.</p>",
+        "UpdateConnectorRegistrationRequest$connectorProvisioningConfig": null
       }
     },
     "ConnectorProvisioningType": {
@@ -917,7 +921,8 @@
         "ConnectorEntityField$description": "<p> A description of the connector entity field. </p>",
         "ConnectorRuntimeSetting$description": "<p>A description about the connector runtime setting.</p>",
         "OAuth2CustomParameter$description": "<p>A description about the custom parameter used for OAuth 2.0 authentication.</p>",
-        "RegisterConnectorRequest$description": "<p>A description about the connector that's being registered.</p>"
+        "RegisterConnectorRequest$description": "<p>A description about the connector that's being registered.</p>",
+        "UpdateConnectorRegistrationRequest$description": "<p>A description about the update that you're applying to the connector.</p>"
       }
     },
     "DestinationConnectorProperties": {
@@ -1989,7 +1994,7 @@
       "refs": {
         "SalesforceDataTransferApiList$member": null,
         "SalesforceDestinationProperties$dataTransferApi": "<p>Specifies which Salesforce API is used by Amazon AppFlow when your flow transfers data to Salesforce.</p> <dl> <dt>AUTOMATIC</dt> <dd> <p>The default. Amazon AppFlow selects which API to use based on the number of records that your flow transfers to Salesforce. If your flow transfers fewer than 1,000 records, Amazon AppFlow uses Salesforce REST API. If your flow transfers 1,000 records or more, Amazon AppFlow uses Salesforce Bulk API 2.0.</p> <p>Each of these Salesforce APIs structures data differently. If Amazon AppFlow selects the API automatically, be aware that, for recurring flows, the data output might vary from one flow run to the next. For example, if a flow runs daily, it might use REST API on one day to transfer 900 records, and it might use Bulk API 2.0 on the next day to transfer 1,100 records. For each of these flow runs, the respective Salesforce API formats the data differently. Some of the differences include how dates are formatted and null values are represented. Also, Bulk API 2.0 doesn't transfer Salesforce compound fields.</p> <p>By choosing this option, you optimize flow performance for both small and large data transfers, but the tradeoff is inconsistent formatting in the output.</p> </dd> <dt>BULKV2</dt> <dd> <p>Amazon AppFlow uses only Salesforce Bulk API 2.0. This API runs asynchronous data transfers, and it's optimal for large sets of data. By choosing this option, you ensure that your flow writes consistent output, but you optimize performance only for large data transfers.</p> <p>Note that Bulk API 2.0 does not transfer Salesforce compound fields.</p> </dd> <dt>REST_SYNC</dt> <dd> <p>Amazon AppFlow uses only Salesforce REST API. By choosing this option, you ensure that your flow writes consistent output, but you decrease performance for large data transfers that are better suited for Bulk API 2.0. In some cases, if your flow attempts to transfer a vary large set of data, it might fail with a timed out error.</p> </dd> </dl>",
-        "SalesforceSourceProperties$dataTransferApi": "<p>Specifies which Salesforce API is used by Amazon AppFlow when your flow transfers data from Salesforce.</p> <dl> <dt>AUTOMATIC</dt> <dd> <p>The default. Amazon AppFlow selects which API to use based on the number of records that your flow transfers from Salesforce. If your flow transfers fewer than 1,000,000 records, Amazon AppFlow uses Salesforce REST API. If your flow transfers 1,000,000 records or more, Amazon AppFlow uses Salesforce Bulk API 2.0.</p> <p>Each of these Salesforce APIs structures data differently. If Amazon AppFlow selects the API automatically, be aware that, for recurring flows, the data output might vary from one flow run to the next. For example, if a flow runs daily, it might use REST API on one day to transfer 900,000 records, and it might use Bulk API 2.0 on the next day to transfer 1,100,000 records. For each of these flow runs, the respective Salesforce API formats the data differently. Some of the differences include how dates are formatted and null values are represented. Also, Bulk API 2.0 doesn't transfer Salesforce compound fields.</p> <p>By choosing this option, you optimize flow performance for both small and large data transfers, but the tradeoff is inconsistent formatting in the output.</p> </dd> <dt>BULKV2</dt> <dd> <p>Amazon AppFlow uses only Salesforce Bulk API 2.0. This API runs asynchronous data transfers, and it's optimal for large sets of data. By choosing this option, you ensure that your flow writes consistent output, but you optimize performance only for large data transfers.</p> <p>Note that Bulk API 2.0 does not transfer Salesforce compound fields.</p> </dd> <dt>REST_SYNC</dt> <dd> <p>Amazon AppFlow uses only Salesforce REST API. By choosing this option, you ensure that your flow writes consistent output, but you decrease performance for large data transfers that are better suited for Bulk API 2.0. In some cases, if your flow attempts to transfer a vary large set of data, it might fail with a timed out error.</p> </dd> </dl>"
+        "SalesforceSourceProperties$dataTransferApi": "<p>Specifies which Salesforce API is used by Amazon AppFlow when your flow transfers data from Salesforce.</p> <dl> <dt>AUTOMATIC</dt> <dd> <p>The default. Amazon AppFlow selects which API to use based on the number of records that your flow transfers from Salesforce. If your flow transfers fewer than 1,000,000 records, Amazon AppFlow uses Salesforce REST API. If your flow transfers 1,000,000 records or more, Amazon AppFlow uses Salesforce Bulk API 2.0.</p> <p>Each of these Salesforce APIs structures data differently. If Amazon AppFlow selects the API automatically, be aware that, for recurring flows, the data output might vary from one flow run to the next. For example, if a flow runs daily, it might use REST API on one day to transfer 900,000 records, and it might use Bulk API 2.0 on the next day to transfer 1,100,000 records. For each of these flow runs, the respective Salesforce API formats the data differently. Some of the differences include how dates are formatted and null values are represented. Also, Bulk API 2.0 doesn't transfer Salesforce compound fields.</p> <p>By choosing this option, you optimize flow performance for both small and large data transfers, but the tradeoff is inconsistent formatting in the output.</p> </dd> <dt>BULKV2</dt> <dd> <p>Amazon AppFlow uses only Salesforce Bulk API 2.0. This API runs asynchronous data transfers, and it's optimal for large sets of data. By choosing this option, you ensure that your flow writes consistent output, but you optimize performance only for large data transfers.</p> <p>Note that Bulk API 2.0 does not transfer Salesforce compound fields.</p> </dd> <dt>REST_SYNC</dt> <dd> <p>Amazon AppFlow uses only Salesforce REST API. By choosing this option, you ensure that your flow writes consistent output, but you decrease performance for large data transfers that are better suited for Bulk API 2.0. In some cases, if your flow attempts to transfer a vary large set of data, it might fail wituh a timed out error.</p> </dd> </dl>"
       }
     },
     "SalesforceDataTransferApiList": {
@@ -2467,6 +2472,16 @@
       "refs": {
       }
     },
+    "UpdateConnectorRegistrationRequest": {
+      "base": null,
+      "refs": {
+      }
+    },
+    "UpdateConnectorRegistrationResponse": {
+      "base": null,
+      "refs": {
+      }
+    },
     "UpdateFlowRequest": {
       "base": null,
       "refs": {