Update services based on v1.44.328 of AWS Go SDK

Reference: https://github.com/aws/aws-sdk-go/releases/tag/v1.44.328

.latest-tag-aws-sdk-go

@@ -1 +1 @@
-v1.44.327
+v1.44.328

lib/aws/generated/rds.ex

@@ -1511,23 +1511,50 @@ defmodule AWS.RDS do
   end
 
   @doc """
-  Initiates the failover process for an Aurora global database (`GlobalCluster`).
+  Promotes the specified secondary DB cluster to be the primary DB cluster in the
+  global database cluster to fail over or switch over a global database.
 
-  A failover for an Aurora global database promotes one of secondary read-only DB
-  clusters to be the primary DB cluster and demotes the primary DB cluster to
-  being a secondary (read-only) DB cluster. In other words, the role of the
-  current primary DB cluster and the selected (target) DB cluster are switched.
-  The selected secondary DB cluster assumes full read/write capabilities for the
-  Aurora global database.
+  Switchover operations were previously called "managed planned failovers."
+
+  Although this operation can be used either to fail over or to switch over a
+  global database cluster, its intended use is for global database failover. To
+  switch over a global database cluster, we recommend that you use the
+  `SwitchoverGlobalCluster` operation instead.
+
+  How you use this operation depends on whether you are failing over or switching
+  over your global database cluster:
+
+    * Failing over - Specify the `AllowDataLoss` parameter and don't
+  specify the `Switchover` parameter.
+
+    * Switching over - Specify the `Switchover` parameter or omit it,
+  but don't specify the `AllowDataLoss` parameter.
+
+  ## About failing over and switching over
+
+  While failing over and switching over a global database cluster both change the
+  primary DB cluster, you use these operations for different reasons:
+
+    * *Failing over* - Use this operation to respond to an unplanned
+  event, such as a Regional disaster in the primary Region. Failing over can
+  result in a loss of write transaction data that wasn't replicated to the chosen
+  secondary before the failover event occurred. However, the recovery process that
+  promotes a DB instance on the chosen seconday DB cluster to be the primary
+  writer DB instance guarantees that the data is in a transactionally consistent
+  state.
 
   For more information about failing over an Amazon Aurora global database, see
-  [Managed planned failover for Amazon Aurora global databases](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-disaster-recovery.html#aurora-global-database-disaster-recovery.managed-failover)
+  [Performing managed failovers for Aurora global databases](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-disaster-recovery.html#aurora-global-database-failover.managed-unplanned)
   in the *Amazon Aurora User Guide*.
 
-  This action applies to `GlobalCluster` (Aurora global databases) only. Use this
-  action only on healthy Aurora global databases with running Aurora DB clusters
-  and no Region-wide outages, to test disaster recovery scenarios or to
-  reconfigure your Aurora global database topology.
+    * *Switching over* - Use this operation on a healthy global database
+  cluster for planned events, such as Regional rotation or to fail back to the
+  original primary DB cluster after a failover operation. With this operation,
+  there is no data loss.
+
+  For more information about switching over an Amazon Aurora global database, see
+  [Performing switchovers for Aurora global databases](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-disaster-recovery.html#aurora-global-database-disaster-recovery.managed-failover)
+  in the *Amazon Aurora User Guide*.
   """
   def failover_global_cluster(%Client{} = client, input, options \\ []) do
     meta = metadata()
@@ -1887,7 +1914,7 @@ defmodule AWS.RDS do
   end
 
   @doc """
-  Modifies a setting for an Amazon Aurora global cluster.
+  Modifies a setting for an Amazon Aurora global database cluster.
 
   You can change one or more database configuration parameters by specifying these
   parameters and the new values in the request. For more information on Amazon
@@ -2470,6 +2497,33 @@ defmodule AWS.RDS do
     Request.request_post(client, meta, "SwitchoverBlueGreenDeployment", input, options)
   end
 
+  @doc """
+  Switches over the specified secondary DB cluster to be the new primary DB
+  cluster in the global database cluster.
+
+  Switchover operations were previously called "managed planned failovers."
+
+  Aurora promotes the specified secondary cluster to assume full read/write
+  capabilities and demotes the current primary cluster to a secondary (read-only)
+  cluster, maintaining the orginal replication topology. All secondary clusters
+  are synchronized with the primary at the beginning of the process so the new
+  primary continues operations for the Aurora global database without losing any
+  data. Your database is unavailable for a short time while the primary and
+  selected secondary clusters are assuming their new roles. For more information
+  about switching over an Aurora global database, see [Performing switchovers for Amazon Aurora global
+  databases](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-disaster-recovery.html#aurora-global-database-disaster-recovery.managed-failover)
+  in the *Amazon Aurora User Guide*.
+
+  This operation is intended for controlled environments, for operations such as
+  "regional rotation" or to fall back to the original primary after a global
+  database failover.
+  """
+  def switchover_global_cluster(%Client{} = client, input, options \\ []) do
+    meta = metadata()
+
+    Request.request_post(client, meta, "SwitchoverGlobalCluster", input, options)
+  end
+
   @doc """
   Switches over an Oracle standby database in an Oracle Data Guard environment,
   making it the new primary database.