Updated service API models for release.

Author: AWS SDK for Ruby

CHANGELOG.md

@@ -1,6 +1,18 @@
 Unreleased Changes
 ------------------
 
+* Feature - Aws::ConfigService - Updated the API, and documentation for AWS Config.
+
+* Feature - Aws::DirectConnect - Updated the documentation for AWS Direct Connect.
+
+* Feature - Aws::FSx - Updated the API, and documentation for Amazon FSx.
+
+* Feature - Aws::Glue - Updated the API, and documentation for AWS Glue.
+
+* Feature - Aws::Lightsail - Updated the API, and documentation for Amazon Lightsail.
+
+* Feature - Aws::WorkSpaces - Updated the API, and documentation for Amazon WorkSpaces.
+
 2.11.550 (2020-07-22)
 ------------------
 

aws-sdk-core/apis/config/2014-11-12/api-2.json

@@ -385,7 +385,8 @@
       "output":{"shape":"DescribeConformancePackStatusResponse"},
       "errors":[
         {"shape":"InvalidLimitException"},
-        {"shape":"InvalidNextTokenException"}
+        {"shape":"InvalidNextTokenException"},
+        {"shape":"InvalidParameterValueException"}
       ]
     },
     "DescribeConformancePacks":{
@@ -399,7 +400,8 @@
       "errors":[
         {"shape":"NoSuchConformancePackException"},
         {"shape":"InvalidLimitException"},
-        {"shape":"InvalidNextTokenException"}
+        {"shape":"InvalidNextTokenException"},
+        {"shape":"InvalidParameterValueException"}
       ]
     },
     "DescribeDeliveryChannelStatus":{
@@ -956,7 +958,8 @@
       "input":{"shape":"PutRemediationExceptionsRequest"},
       "output":{"shape":"PutRemediationExceptionsResponse"},
       "errors":[
-        {"shape":"InvalidParameterValueException"}
+        {"shape":"InvalidParameterValueException"},
+        {"shape":"InsufficientPermissionsException"}
       ]
     },
     "PutResourceConfig":{
@@ -1528,7 +1531,8 @@
         "AccountAggregationSources":{"shape":"AccountAggregationSourceList"},
         "OrganizationAggregationSource":{"shape":"OrganizationAggregationSource"},
         "CreationTime":{"shape":"Date"},
-        "LastUpdatedTime":{"shape":"Date"}
+        "LastUpdatedTime":{"shape":"Date"},
+        "CreatedBy":{"shape":"StringWithCharLimit256"}
       }
     },
     "ConfigurationAggregatorArn":{
@@ -4010,7 +4014,10 @@
         "AWS::ServiceCatalog::Portfolio",
         "AWS::SQS::Queue",
         "AWS::KMS::Key",
-        "AWS::QLDB::Ledger"
+        "AWS::QLDB::Ledger",
+        "AWS::SecretsManager::Secret",
+        "AWS::SNS::Topic",
+        "AWS::SSM::FileData"
       ]
     },
     "ResourceTypeList":{

aws-sdk-core/apis/config/2014-11-12/docs-2.json

@@ -19,7 +19,7 @@
     "CreateConnection": "<p>Creates a connection between a customer network and a specific AWS Direct Connect location.</p> <p>A connection links your internal network to an AWS Direct Connect location over a standard Ethernet fiber-optic cable. One end of the cable is connected to your router, the other to an AWS Direct Connect router.</p> <p>To find the locations for your Region, use <a>DescribeLocations</a>.</p> <p>You can automatically add the new connection to a link aggregation group (LAG) by specifying a LAG ID in the request. This ensures that the new connection is allocated on the same AWS Direct Connect endpoint that hosts the specified LAG. If there are no available ports on the endpoint, the request fails and no connection is created.</p>",
     "CreateDirectConnectGateway": "<p>Creates a Direct Connect gateway, which is an intermediate object that enables you to connect a set of virtual interfaces and virtual private gateways. A Direct Connect gateway is global and visible in any AWS Region after it is created. The virtual interfaces and virtual private gateways that are connected through a Direct Connect gateway can be in different AWS Regions. This enables you to connect to a VPC in any Region, regardless of the Region in which the virtual interfaces are located, and pass traffic between them.</p>",
     "CreateDirectConnectGatewayAssociation": "<p>Creates an association between a Direct Connect gateway and a virtual private gateway. The virtual private gateway must be attached to a VPC and must not be associated with another Direct Connect gateway.</p>",
-    "CreateDirectConnectGatewayAssociationProposal": "<p>Creates a proposal to associate the specified virtual private gateway or transit gateway with the specified Direct Connect gateway.</p> <p>You can only associate a Direct Connect gateway and virtual private gateway or transit gateway when the account that owns the Direct Connect gateway and the account that owns the virtual private gateway or transit gateway have the same AWS Payer ID.</p>",
+    "CreateDirectConnectGatewayAssociationProposal": "<p>Creates a proposal to associate the specified virtual private gateway or transit gateway with the specified Direct Connect gateway.</p> <p>You can associate a Direct Connect gateway and virtual private gateway or transit gateway that is owned by any AWS account. </p>",
     "CreateInterconnect": "<p>Creates an interconnect between an AWS Direct Connect Partner's network and a specific AWS Direct Connect location.</p> <p>An interconnect is a connection that is capable of hosting other connections. The AWS Direct Connect partner can use an interconnect to provide AWS Direct Connect hosted connections to customers through their own network services. Like a standard connection, an interconnect links the partner's network to an AWS Direct Connect location over a standard Ethernet fiber-optic cable. One end is connected to the partner's router, the other to an AWS Direct Connect router.</p> <p>You can automatically add the new interconnect to a link aggregation group (LAG) by specifying a LAG ID in the request. This ensures that the new interconnect is allocated on the same AWS Direct Connect endpoint that hosts the specified LAG. If there are no available ports on the endpoint, the request fails and no interconnect is created.</p> <p>For each end customer, the AWS Direct Connect Partner provisions a connection on their interconnect by calling <a>AllocateHostedConnection</a>. The end customer can then connect to AWS resources by creating a virtual interface on their connection, using the VLAN assigned to them by the AWS Direct Connect Partner.</p> <note> <p>Intended for use by AWS Direct Connect Partners only.</p> </note>",
     "CreateLag": "<p>Creates a link aggregation group (LAG) with the specified number of bundled physical connections between the customer network and a specific AWS Direct Connect location. A LAG is a logical interface that uses the Link Aggregation Control Protocol (LACP) to aggregate multiple interfaces, enabling you to treat them as a single interface.</p> <p>All connections in a LAG must use the same bandwidth and must terminate at the same AWS Direct Connect endpoint.</p> <p>You can have up to 10 connections per LAG. Regardless of this limit, if you request more connections for the LAG than AWS Direct Connect can allocate on a single endpoint, no LAG is created.</p> <p>You can specify an existing physical connection or interconnect to include in the LAG (which counts towards the total number of connections). Doing so interrupts the current physical connection or hosted connections, and re-establishes them as a member of the LAG. The LAG will be created on the same AWS Direct Connect endpoint to which the connection terminates. Any virtual interfaces associated with the connection are automatically disassociated and re-associated with the LAG. The connection ID does not change.</p> <p>If the AWS account used to create a LAG is a registered AWS Direct Connect Partner, the LAG is automatically enabled to host sub-connections. For a LAG owned by a partner, any associated virtual interfaces cannot be directly configured.</p>",
     "CreatePrivateVirtualInterface": "<p>Creates a private virtual interface. A virtual interface is the VLAN that transports AWS Direct Connect traffic. A private virtual interface can be connected to either a Direct Connect gateway or a Virtual Private Gateway (VGW). Connecting the private virtual interface to a Direct Connect gateway enables the possibility for connecting to multiple VPCs, including VPCs in different AWS Regions. Connecting the private virtual interface to a VGW only provides access to a single VPC within the same Region.</p> <p>Setting the MTU of a virtual interface to 9001 (jumbo frames) can cause an update to the underlying physical connection if it wasn't updated to support jumbo frames. Updating the connection disrupts network connectivity for all virtual interfaces associated with the connection for up to 30 seconds. To check whether your connection supports jumbo frames, call <a>DescribeConnections</a>. To check whether your virtual interface supports jumbo frames, call <a>DescribeVirtualInterfaces</a>.</p>",

aws-sdk-core/apis/directconnect/2012-10-25/docs-2.json

@@ -331,6 +331,14 @@
       "min":3,
       "pattern":"^[^\\u0000\\u0085\\u2028\\u2029\\r\\n]{3,4357}$"
     },
+    "AutoImportPolicyType":{
+      "type":"string",
+      "enum":[
+        "NONE",
+        "NEW",
+        "NEW_CHANGED"
+      ]
+    },
     "AutomaticBackupRetentionDays":{
       "type":"integer",
       "max":35,
@@ -533,6 +541,7 @@
         "ExportPath":{"shape":"ArchivePath"},
         "ImportedFileChunkSize":{"shape":"Megabytes"},
         "DeploymentType":{"shape":"LustreDeploymentType"},
+        "AutoImportPolicy":{"shape":"AutoImportPolicyType"},
         "PerUnitStorageThroughput":{"shape":"PerUnitStorageThroughput"},
         "DailyAutomaticBackupStartTime":{"shape":"DailyTime"},
         "AutomaticBackupRetentionDays":{"shape":"AutomaticBackupRetentionDays"},
@@ -599,11 +608,30 @@
     "DataRepositoryConfiguration":{
       "type":"structure",
       "members":{
+        "Lifecycle":{"shape":"DataRepositoryLifecycle"},
         "ImportPath":{"shape":"ArchivePath"},
         "ExportPath":{"shape":"ArchivePath"},
-        "ImportedFileChunkSize":{"shape":"Megabytes"}
+        "ImportedFileChunkSize":{"shape":"Megabytes"},
+        "AutoImportPolicy":{"shape":"AutoImportPolicyType"},
+        "FailureDetails":{"shape":"DataRepositoryFailureDetails"}
+      }
+    },
+    "DataRepositoryFailureDetails":{
+      "type":"structure",
+      "members":{
+        "Message":{"shape":"ErrorMessage"}
       }
     },
+    "DataRepositoryLifecycle":{
+      "type":"string",
+      "enum":[
+        "CREATING",
+        "AVAILABLE",
+        "MISCONFIGURED",
+        "UPDATING",
+        "DELETING"
+      ]
+    },
     "DataRepositoryTask":{
       "type":"structure",
       "required":[
@@ -1298,6 +1326,10 @@
     "SucceededCount":{"type":"long"},
     "Tag":{
       "type":"structure",
+      "required":[
+        "Key",
+        "Value"
+      ],
       "members":{
         "Key":{"shape":"TagKey"},
         "Value":{"shape":"TagValue"}
@@ -1383,7 +1415,8 @@
       "members":{
         "WeeklyMaintenanceStartTime":{"shape":"WeeklyTime"},
         "DailyAutomaticBackupStartTime":{"shape":"DailyTime"},
-        "AutomaticBackupRetentionDays":{"shape":"AutomaticBackupRetentionDays"}
+        "AutomaticBackupRetentionDays":{"shape":"AutomaticBackupRetentionDays"},
+        "AutoImportPolicy":{"shape":"AutoImportPolicyType"}
       }
     },
     "UpdateFileSystemRequest":{

aws-sdk-core/apis/fsx/2018-03-01/api-2.json

@@ -83,6 +83,14 @@
         "DataRepositoryConfiguration$ExportPath": "<p>The export path to the Amazon S3 bucket (and prefix) that you are using to store new and changed Lustre file system files in S3.</p>"
       }
     },
+    "AutoImportPolicyType": {
+      "base": null,
+      "refs": {
+        "CreateFileSystemLustreConfiguration$AutoImportPolicy": "<p>Use this property to turn the Autoimport feature on and off. AutoImport enables your FSx for Lustre file system to automatically update its contents with changes that have been made to its linked Amazon S3 data repository. You can set the policy to have one the following values:</p> <ul> <li> <p> <code>NONE</code> - (Default) Autoimport is turned off. Changes to your S3 repository will not be reflected on the FSx file system.</p> </li> <li> <p> <code>NEW</code> - Autoimport is turned on; only new files in the linked S3 repository will be imported to the FSx file system. Updates to existing files and deleted files will not be imported to the FSx file system.</p> </li> <li> <p> <code>NEW_CHANGED</code> - Autoimport is turned on; new files and changes to existing files in the linked S3 repository will be imported to the FSx file system. Files deleted in S3 are not deleted in the FSx file system.</p> </li> <li> <p> <code>NEW_CHANGED_DELETED</code> - Autoimport is turned on; new files, changes to existing files, and deleted files in the linked S3 repository will be imported to the FSx file system. </p> </li> </ul>",
+        "DataRepositoryConfiguration$AutoImportPolicy": "<p>Describes the data repository's <code>AutoImportPolicy</code>. AutoImport enables your FSx for Lustre file system to automatically update its contents with changes that have been made to its linked Amazon S3 data repository. The policy can have the following values:</p> <ul> <li> <p> <code>NONE</code> - (Default) Autoimport is turned off, Changes to your S3 repository will not be reflected on the FSx file system.</p> </li> <li> <p> <code>NEW</code> - Autoimport is turned on; only new files in the linked S3 repository will be imported to the FSx file system. Updates to existing files and deleted files will not be imported to the FSx file system.</p> </li> <li> <p> <code>NEW_CHANGED</code> - Autoimport is turned on; new files and changes to existing files in the linked S3 repository will be imported to the FSx file system. Files deleted in S3 are not deleted in the FSx file system.</p> </li> <li> <p> <code>NEW_CHANGED_DELETED</code> - Autoimport is turned on; new files, changes to existing files, and deleted files in the linked S3 repository will be imported to the FSx file system. </p> </li> </ul>",
+        "UpdateFileSystemLustreConfiguration$AutoImportPolicy": "<p>Use this property to turn the Autoimport feature on and off. AutoImport enables your FSx for Lustre file system to automatically update its contents with changes that have been made to its linked Amazon S3 data repository. You can set the policy to have one the following values:</p> <ul> <li> <p> <code>NONE</code> - (Default) Autoimport is turned off. Changes to your S3 repository will not be reflected on the FSx file system.</p> </li> <li> <p> <code>NEW</code> - Autoimport is turned on; only new files in the linked S3 repository will be imported to the FSx file system. Updates to existing files and deleted files will not be imported to the FSx file system.</p> </li> <li> <p> <code>NEW_CHANGED</code> - Autoimport is turned on; new files and changes to existing files in the linked S3 repository will be imported to the FSx file system. Files deleted in S3 are not deleted in the FSx file system.</p> </li> <li> <p> <code>NEW_CHANGED_DELETED</code> - Autoimport is turned on; new files, changes to existing files, and deleted files in the linked S3 repository will be imported to the FSx file system. </p> </li> </ul>"
+      }
+    },
     "AutomaticBackupRetentionDays": {
       "base": "<p>The number of days to retain automatic backups. Setting this to 0 disables automatic backups. You can retain automatic backups for a maximum of 35 days. The default is 0.</p>",
       "refs": {
@@ -279,6 +287,18 @@
         "LustreFileSystemConfiguration$DataRepositoryConfiguration": null
       }
     },
+    "DataRepositoryFailureDetails": {
+      "base": "<p>Provides detailed information about the data respository if its <code>Lifecycle</code> is set to <code>MISCONFIGURED</code>.</p>",
+      "refs": {
+        "DataRepositoryConfiguration$FailureDetails": null
+      }
+    },
+    "DataRepositoryLifecycle": {
+      "base": null,
+      "refs": {
+        "DataRepositoryConfiguration$Lifecycle": "<p>Describes the state of the file system's S3 durable data repository, if it is configured with an S3 repository. The lifecycle can have the following values:</p> <ul> <li> <p> <code>CREATING</code> - Amazon FSx is creating the new data repository.</p> </li> <li> <p> <code>AVAILABLE</code> - The data repository is available for use.</p> </li> <li> <p> <code>MISCONFIGURED</code> - The data repository is in a failed but recoverable state.</p> </li> <li> <p> <code>UPDATING</code> - The data repository is undergoing a customer initiated update.</p> </li> </ul>"
+      }
+    },
     "DataRepositoryTask": {
       "base": "<p>A description of the data repository task. You use data repository tasks to perform bulk transfer operations between your Amazon FSx file system and its linked data repository.</p>",
       "refs": {
@@ -498,6 +518,7 @@
         "BackupNotFound$Message": null,
         "BackupRestoring$Message": null,
         "BadRequest$Message": null,
+        "DataRepositoryFailureDetails$Message": null,
         "DataRepositoryTaskEnded$Message": null,
         "DataRepositoryTaskExecuting$Message": null,
         "DataRepositoryTaskFailureDetails$Message": null,

aws-sdk-core/apis/fsx/2018-03-01/docs-2.json

@@ -2743,7 +2743,10 @@
         "SKIP_CUSTOM_JDBC_CERT_VALIDATION",
         "CUSTOM_JDBC_CERT_STRING",
         "CONNECTION_URL",
-        "KAFKA_BOOTSTRAP_SERVERS"
+        "KAFKA_BOOTSTRAP_SERVERS",
+        "KAFKA_SSL_ENABLED",
+        "KAFKA_CUSTOM_CERT",
+        "KAFKA_SKIP_CUSTOM_CERT_VALIDATION"
       ]
     },
     "ConnectionType":{