Include Global Cluster Identifier in DBCluster if the DBCluster is a Global Cluster Member.

Author: aws-sdk-dotnet-automation

generator/ServiceModels/rds/rds-2014-10-31.api.json

@@ -4182,6 +4182,7 @@
         "CrossAccountClone":{"shape":"BooleanOptional"},
         "DomainMemberships":{"shape":"DomainMembershipList"},
         "TagList":{"shape":"TagList"},
+        "GlobalClusterIdentifier":{"shape":"GlobalClusterIdentifier"},
         "GlobalWriteForwardingStatus":{"shape":"WriteForwardingStatus"},
         "GlobalWriteForwardingRequested":{"shape":"BooleanOptional"},
         "PendingModifiedValues":{"shape":"ClusterPendingModifiedValues"},

generator/ServiceModels/rds/rds-2014-10-31.docs.json

@@ -1812,7 +1812,7 @@
         {"shape":"DBInstanceNotReadyFault"},
         {"shape":"DBLogFileNotFoundFault"}
       ],
-      "documentation":"<p>Downloads all or a portion of the specified log file, up to 1 MB in size.</p> <p>This command doesn't apply to RDS Custom.</p>"
+      "documentation":"<p>Downloads all or a portion of the specified log file, up to 1 MB in size.</p> <p>This command doesn't apply to RDS Custom.</p> <note> <p>This operation uses resources on database instances. Because of this, we recommend publishing database logs to CloudWatch and then using the GetLogEvents operation. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_GetLogEvents.html\">GetLogEvents</a> in the <i>Amazon CloudWatch Logs API Reference</i>.</p> </note>"
     },
     "EnableHttpEndpoint":{
       "name":"EnableHttpEndpoint",
@@ -3750,15 +3750,15 @@
         },
         "ConnectionBorrowTimeout":{
           "shape":"IntegerOptional",
-          "documentation":"<p>The number of seconds for a proxy to wait for a connection to become available in the connection pool. This setting only applies when the proxy has opened its maximum number of connections and all connections are busy with client sessions.</p> <p>Default: <code>120</code> </p> <p>Constraints:</p> <ul> <li> <p>Must be between 0 and 3600.</p> </li> </ul>"
+          "documentation":"<p>The number of seconds for a proxy to wait for a connection to become available in the connection pool. This setting only applies when the proxy has opened its maximum number of connections and all connections are busy with client sessions.</p> <p>Default: <code>120</code> </p> <p>Constraints:</p> <ul> <li> <p>Must be between 0 and 300.</p> </li> </ul>"
         },
         "SessionPinningFilters":{
           "shape":"StringList",
           "documentation":"<p>Each item in the list represents a class of SQL operations that normally cause all later statements in a session using a proxy to be pinned to the same underlying database connection. Including an item in the list exempts that class of SQL operations from the pinning behavior.</p> <p>Default: no session pinning filters</p>"
         },
         "InitQuery":{
           "shape":"String",
-          "documentation":"<p>Add an initialization query, or modify the current one. You can specify one or more SQL statements for the proxy to run when opening each new database connection. The setting is typically used with <code>SET</code> statements to make sure that each connection has identical settings. Make sure that the query you add is valid. To include multiple variables in a single <code>SET</code> statement, use comma separators.</p> <p>For example: <code>SET variable1=value1, variable2=value2</code> </p> <p>For multiple statements, use semicolons as the separator.</p> <p>Default: no initialization query</p>"
+          "documentation":"<p>Add an initialization query, or modify the current one. You can specify one or more SQL statements for the proxy to run when opening each new database connection. The setting is typically used with <code>SET</code> statements to make sure that each connection has identical settings. Make sure the query added here is valid. This is an optional field, so you can choose to leave it empty. For including multiple variables in a single SET statement, use a comma separator.</p> <p>For example: <code>SET variable1=value1, variable2=value2</code> </p> <p>Default: no initialization query</p>"
         }
       },
       "documentation":"<p>Specifies the settings that control the size and behavior of the connection pool associated with a <code>DBProxyTargetGroup</code>.</p>"
@@ -3784,7 +3784,7 @@
         },
         "InitQuery":{
           "shape":"String",
-          "documentation":"<p>One or more SQL statements for the proxy to run when opening each new database connection. Typically used with <code>SET</code> statements to make sure that each connection has identical settings such as time zone and character set. This setting is empty by default. For multiple statements, use semicolons as the separator. You can also include multiple variables in a single <code>SET</code> statement, such as <code>SET x=1, y=2</code>.</p>"
+          "documentation":"<p>One or more SQL statements for the proxy to run when opening each new database connection. The setting is typically used with <code>SET</code> statements to make sure that each connection has identical settings. The query added here must be valid. For including multiple variables in a single SET statement, use a comma separator. This is an optional field.</p> <p>For example: <code>SET variable1=value1, variable2=value2</code> </p>"
         }
       },
       "documentation":"<p>Displays the settings that control the size and behavior of the connection pool associated with a <code>DBProxyTarget</code>.</p>"
@@ -5084,7 +5084,7 @@
         },
         "ComputeRedundancy":{
           "shape":"IntegerOptional",
-          "documentation":"<p>Specifies whether to create standby DB shard groups for the DB shard group. Valid values are the following:</p> <ul> <li> <p>0 - Creates a DB shard group without a standby DB shard group. This is the default value.</p> </li> <li> <p>1 - Creates a DB shard group with a standby DB shard group in a different Availability Zone (AZ).</p> </li> <li> <p>2 - Creates a DB shard group with two standby DB shard groups in two different AZs.</p> </li> </ul>"
+          "documentation":"<p>Specifies whether to create standby standby DB data access shard for the DB shard group. Valid values are the following:</p> <ul> <li> <p>0 - Creates a DB shard group without a standby DB data access shard. This is the default value.</p> </li> <li> <p>1 - Creates a DB shard group with a standby DB data access shard in a different Availability Zone (AZ).</p> </li> <li> <p>2 - Creates a DB shard group with two standby DB data access shard in two different AZs.</p> </li> </ul>"
         },
         "MaxACU":{
           "shape":"DoubleOptional",
@@ -5678,6 +5678,10 @@
           "documentation":"<p>The Active Directory Domain membership records associated with the DB cluster.</p>"
         },
         "TagList":{"shape":"TagList"},
+        "GlobalClusterIdentifier":{
+          "shape":"GlobalClusterIdentifier",
+          "documentation":"<p>Contains a user-supplied global database cluster identifier. This identifier is the unique key that identifies a global database cluster.</p>"
+        },
         "GlobalWriteForwardingStatus":{
           "shape":"WriteForwardingStatus",
           "documentation":"<p>The status of write forwarding for a secondary cluster in an Aurora global database.</p>"
@@ -8579,7 +8583,7 @@
         },
         "Subnets":{
           "shape":"SubnetList",
-          "documentation":"<p>Contains a list of <code>Subnet</code> elements.</p>"
+          "documentation":"<p>Contains a list of <code>Subnet</code> elements. The list of subnets shown here might not reflect the current state of your VPC. For the most up-to-date information, we recommend checking your VPC configuration directly.</p>"
         },
         "DBSubnetGroupArn":{
           "shape":"String",

generator/ServiceModels/rds/rds-2014-10-31.normal.json

@@ -545,6 +545,12 @@
     <max>2048</max>
     <pattern>^arn:[A-Za-z][0-9A-Za-z-:._]*</pattern>
   </property-value-rule>
+  <property-value-rule>
+    <property>Amazon.RDS.Model.DBCluster.GlobalClusterIdentifier</property>
+    <min>1</min>
+    <max>255</max>
+    <pattern>[A-Za-z][0-9A-Za-z-:._]*</pattern>
+  </property-value-rule>
   <property-value-rule>
     <property>Amazon.RDS.Model.SwitchoverDetail.SourceMember</property>
     <min>1</min>

sdk/code-analysis/ServiceAnalysis/RDS/Generated/PropertyValueRules.xml

@@ -58,7 +58,7 @@ public partial class ConnectionPoolConfiguration
         /// </para>
         ///  <ul> <li> 
         /// <para>
-        /// Must be between 0 and 3600.
+        /// Must be between 0 and 300.
         /// </para>
         ///  </li> </ul>
         /// </summary>
@@ -80,19 +80,16 @@ internal bool IsSetConnectionBorrowTimeout()
         /// Add an initialization query, or modify the current one. You can specify one or more
         /// SQL statements for the proxy to run when opening each new database connection. The
         /// setting is typically used with <c>SET</c> statements to make sure that each connection
-        /// has identical settings. Make sure that the query you add is valid. To include multiple
-        /// variables in a single <c>SET</c> statement, use comma separators.
+        /// has identical settings. Make sure the query added here is valid. This is an optional
+        /// field, so you can choose to leave it empty. For including multiple variables in a
+        /// single SET statement, use a comma separator.
         /// </para>
         ///  
         /// <para>
         /// For example: <c>SET variable1=value1, variable2=value2</c> 
         /// </para>
         ///  
         /// <para>
-        /// For multiple statements, use semicolons as the separator.
-        /// </para>
-        ///  
-        /// <para>
         /// Default: no initialization query
         /// </para>
         /// </summary>

sdk/src/Services/RDS/Generated/Model/ConnectionPoolConfiguration.cs

@@ -65,10 +65,13 @@ internal bool IsSetConnectionBorrowTimeout()
         /// Gets and sets the property InitQuery. 
         /// <para>
         /// One or more SQL statements for the proxy to run when opening each new database connection.
-        /// Typically used with <c>SET</c> statements to make sure that each connection has identical
-        /// settings such as time zone and character set. This setting is empty by default. For
-        /// multiple statements, use semicolons as the separator. You can also include multiple
-        /// variables in a single <c>SET</c> statement, such as <c>SET x=1, y=2</c>.
+        /// The setting is typically used with <c>SET</c> statements to make sure that each connection
+        /// has identical settings. The query added here must be valid. For including multiple
+        /// variables in a single SET statement, use a comma separator. This is an optional field.
+        /// </para>
+        ///  
+        /// <para>
+        /// For example: <c>SET variable1=value1, variable2=value2</c> 
         /// </para>
         /// </summary>
         public string InitQuery

sdk/src/Services/RDS/Generated/Model/ConnectionPoolConfigurationInfo.cs

@@ -52,22 +52,23 @@ public partial class CreateDBShardGroupRequest : AmazonRDSRequest
         /// <summary>
         /// Gets and sets the property ComputeRedundancy. 
         /// <para>
-        /// Specifies whether to create standby DB shard groups for the DB shard group. Valid
-        /// values are the following:
+        /// Specifies whether to create standby standby DB data access shard for the DB shard
+        /// group. Valid values are the following:
         /// </para>
         ///  <ul> <li> 
         /// <para>
-        /// 0 - Creates a DB shard group without a standby DB shard group. This is the default
+        /// 0 - Creates a DB shard group without a standby DB data access shard. This is the default
         /// value.
         /// </para>
         ///  </li> <li> 
         /// <para>
-        /// 1 - Creates a DB shard group with a standby DB shard group in a different Availability
+        /// 1 - Creates a DB shard group with a standby DB data access shard in a different Availability
         /// Zone (AZ).
         /// </para>
         ///  </li> <li> 
         /// <para>
-        /// 2 - Creates a DB shard group with two standby DB shard groups in two different AZs.
+        /// 2 - Creates a DB shard group with two standby DB data access shard in two different
+        /// AZs.
         /// </para>
         ///  </li> </ul>
         /// </summary>

sdk/src/Services/RDS/Generated/Model/CreateDBShardGroupRequest.cs

@@ -104,6 +104,7 @@ public partial class DBCluster
         private string _engineLifecycleSupport;
         private string _engineMode;
         private string _engineVersion;
+        private string _globalClusterIdentifier;
         private bool? _globalWriteForwardingRequested;
         private WriteForwardingStatus _globalWriteForwardingStatus;
         private string _hostedZoneId;
@@ -985,6 +986,26 @@ internal bool IsSetEngineVersion()
             return this._engineVersion != null;
         }
 
+        /// <summary>
+        /// Gets and sets the property GlobalClusterIdentifier. 
+        /// <para>
+        /// Contains a user-supplied global database cluster identifier. This identifier is the
+        /// unique key that identifies a global database cluster.
+        /// </para>
+        /// </summary>
+        [AWSProperty(Min=1, Max=255)]
+        public string GlobalClusterIdentifier
+        {
+            get { return this._globalClusterIdentifier; }
+            set { this._globalClusterIdentifier = value; }
+        }
+
+        // Check to see if GlobalClusterIdentifier property is set
+        internal bool IsSetGlobalClusterIdentifier()
+        {
+            return this._globalClusterIdentifier != null;
+        }
+
         /// <summary>
         /// Gets and sets the property GlobalWriteForwardingRequested. 
         /// <para>

sdk/src/Services/RDS/Generated/Model/DBCluster.cs

@@ -123,7 +123,9 @@ internal bool IsSetSubnetGroupStatus()
         /// <summary>
         /// Gets and sets the property Subnets. 
         /// <para>
-        /// Contains a list of <c>Subnet</c> elements.
+        /// Contains a list of <c>Subnet</c> elements. The list of subnets shown here might not
+        /// reflect the current state of your VPC. For the most up-to-date information, we recommend
+        /// checking your VPC configuration directly.
         /// </para>
         /// </summary>
         public List<Subnet> Subnets

sdk/src/Services/RDS/Generated/Model/DBSubnetGroup.cs

@@ -37,6 +37,14 @@ namespace Amazon.RDS.Model
     /// <para>
     /// This command doesn't apply to RDS Custom.
     /// </para>
+    ///  <note> 
+    /// <para>
+    /// This operation uses resources on database instances. Because of this, we recommend
+    /// publishing database logs to CloudWatch and then using the GetLogEvents operation.
+    /// For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_GetLogEvents.html">GetLogEvents</a>
+    /// in the <i>Amazon CloudWatch Logs API Reference</i>.
+    /// </para>
+    ///  </note>
     /// </summary>
     public partial class DownloadDBLogFilePortionRequest : AmazonRDSRequest
     {