Release v1.50.36 (2024-03-11) (#5193)

Release v1.50.36 (2024-03-11) === ### Service Client Updates * `service/codestar-connections`: Updates service API and documentation * `service/elasticache`: Updates service documentation * Revisions to API text that are now to be carried over to SDK text, changing usages of "SFO" in code examples to "us-west-1", and some other typos. * `service/mediapackagev2`: Updates service API and documentation
aws · Mar 11, 2024 · 5406152 · 5406152
1 parent b965d61
commit 5406152
Show file tree

Hide file tree

Showing 10 changed files with 331 additions and 27 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,3 +1,12 @@
+Release v1.50.36 (2024-03-11)
+===
+
+### Service Client Updates
+* `service/codestar-connections`: Updates service API and documentation
+* `service/elasticache`: Updates service documentation
+  * Revisions to API text that are now to be carried over to SDK text, changing usages of "SFO" in code examples to "us-west-1", and some other typos.
+* `service/mediapackagev2`: Updates service API and documentation
+
 Release v1.50.35 (2024-03-08)
 ===
 

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.50.35"
+const SDKVersion = "1.50.36"
diff --git a/models/apis/codestar-connections/2019-12-01/api-2.json b/models/apis/codestar-connections/2019-12-01/api-2.json
@@ -591,7 +591,9 @@
         "RepositoryLinkId":{"shape":"RepositoryLinkId"},
         "ResourceName":{"shape":"ResourceName"},
         "RoleArn":{"shape":"IamRoleArn"},
-        "SyncType":{"shape":"SyncConfigurationType"}
+        "SyncType":{"shape":"SyncConfigurationType"},
+        "PublishDeploymentStatus":{"shape":"PublishDeploymentStatus"},
+        "TriggerResourceUpdateOn":{"shape":"TriggerResourceUpdateOn"}
       }
     },
     "CreateSyncConfigurationOutput":{
@@ -985,6 +987,13 @@
         "GitLabSelfManaged"
       ]
     },
+    "PublishDeploymentStatus":{
+      "type":"string",
+      "enum":[
+        "ENABLED",
+        "DISABLED"
+      ]
+    },
     "RepositoryLinkArn":{
       "type":"string",
       "pattern":"^arn:aws(?:-[a-z]+)*:codestar-connections:[a-z\\-0-9]+:\\d{12}:repository-link\\/[a-zA-Z0-9\\-:/]+"
@@ -1296,7 +1305,9 @@
         "RepositoryName":{"shape":"RepositoryName"},
         "ResourceName":{"shape":"ResourceName"},
         "RoleArn":{"shape":"IamRoleArn"},
-        "SyncType":{"shape":"SyncConfigurationType"}
+        "SyncType":{"shape":"SyncConfigurationType"},
+        "PublishDeploymentStatus":{"shape":"PublishDeploymentStatus"},
+        "TriggerResourceUpdateOn":{"shape":"TriggerResourceUpdateOn"}
       }
     },
     "SyncConfigurationList":{
@@ -1380,6 +1391,13 @@
       "min":1,
       "pattern":"[\\s\\S]*"
     },
+    "TriggerResourceUpdateOn":{
+      "type":"string",
+      "enum":[
+        "ANY_CHANGE",
+        "FILE_CHANGE"
+      ]
+    },
     "Type":{"type":"string"},
     "UnsupportedOperationException":{
       "type":"structure",
@@ -1487,7 +1505,9 @@
         "RepositoryLinkId":{"shape":"RepositoryLinkId"},
         "ResourceName":{"shape":"ResourceName"},
         "RoleArn":{"shape":"IamRoleArn"},
-        "SyncType":{"shape":"SyncConfigurationType"}
+        "SyncType":{"shape":"SyncConfigurationType"},
+        "PublishDeploymentStatus":{"shape":"PublishDeploymentStatus"},
+        "TriggerResourceUpdateOn":{"shape":"TriggerResourceUpdateOn"}
       }
     },
     "UpdateSyncConfigurationOutput":{

diff --git a/models/apis/codestar-connections/2019-12-01/docs-2.json b/models/apis/codestar-connections/2019-12-01/docs-2.json
@@ -530,6 +530,14 @@
         "SyncConfiguration$ProviderType": "<p>The connection provider type associated with a specific sync configuration, such as GitHub.</p>"
       }
     },
+    "PublishDeploymentStatus": {
+      "base": null,
+      "refs": {
+        "CreateSyncConfigurationInput$PublishDeploymentStatus": "<p>Whether to enable or disable publishing of deployment status to source providers.</p>",
+        "SyncConfiguration$PublishDeploymentStatus": "<p>Whether to enable or disable publishing of deployment status to source providers.</p>",
+        "UpdateSyncConfigurationInput$PublishDeploymentStatus": "<p>Whether to enable or disable publishing of deployment status to source providers.</p>"
+      }
+    },
     "RepositoryLinkArn": {
       "base": null,
       "refs": {
@@ -882,6 +890,14 @@
         "VpcConfiguration$TlsCertificate": "<p>The value of the Transport Layer Security (TLS) certificate associated with the infrastructure where your provider type is installed.</p>"
       }
     },
+    "TriggerResourceUpdateOn": {
+      "base": null,
+      "refs": {
+        "CreateSyncConfigurationInput$TriggerResourceUpdateOn": "<p>When to trigger Git sync to begin the stack update.</p>",
+        "SyncConfiguration$TriggerResourceUpdateOn": "<p>When to trigger Git sync to begin the stack update.</p>",
+        "UpdateSyncConfigurationInput$TriggerResourceUpdateOn": "<p>When to trigger Git sync to begin the stack update.</p>"
+      }
+    },
     "Type": {
       "base": null,
       "refs": {

diff --git a/models/apis/elasticache/2015-02-02/docs-2.json b/models/apis/elasticache/2015-02-02/docs-2.json
@@ -14,7 +14,7 @@
     "CreateCacheSecurityGroup": "<p>Creates a new cache security group. Use a cache security group to control access to one or more clusters.</p> <p>Cache security groups are only used when you are creating a cluster outside of an Amazon Virtual Private Cloud (Amazon VPC). If you are creating a cluster inside of a VPC, use a cache subnet group instead. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonElastiCache/latest/APIReference/API_CreateCacheSubnetGroup.html\">CreateCacheSubnetGroup</a>.</p>",
     "CreateCacheSubnetGroup": "<p>Creates a new cache subnet group.</p> <p>Use this parameter only when you are creating a cluster in an Amazon Virtual Private Cloud (Amazon VPC).</p>",
     "CreateGlobalReplicationGroup": "<p>Global Datastore for Redis offers fully managed, fast, reliable and secure cross-region replication. Using Global Datastore for Redis, you can create cross-region read replica clusters for ElastiCache for Redis to enable low-latency reads and disaster recovery across regions. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/Redis-Global-Datastore.html\">Replication Across Regions Using Global Datastore</a>. </p> <ul> <li> <p>The <b>GlobalReplicationGroupIdSuffix</b> is the name of the Global datastore.</p> </li> <li> <p>The <b>PrimaryReplicationGroupId</b> represents the name of the primary cluster that accepts writes and will replicate updates to the secondary cluster.</p> </li> </ul>",
-    "CreateReplicationGroup": "<p>Creates a Redis (cluster mode disabled) or a Redis (cluster mode enabled) replication group.</p> <p>This API can be used to create a standalone regional replication group or a secondary replication group associated with a Global datastore.</p> <p>A Redis (cluster mode disabled) replication group is a collection of clusters, where one of the clusters is a read/write primary and the others are read-only replicas. Writes to the primary are asynchronously propagated to the replicas.</p> <p>A Redis cluster-mode enabled cluster is comprised of from 1 to 90 shards (API/CLI: node groups). Each shard has a primary node and up to 5 read-only replica nodes. The configuration can range from 90 shards and 0 replicas to 15 shards and 5 replicas, which is the maximum number or replicas allowed. </p> <p>The node or shard limit can be increased to a maximum of 500 per cluster if the Redis engine version is 5.0.6 or higher. For example, you can choose to configure a 500 node cluster that ranges between 83 shards (one primary and 5 replicas per shard) and 500 shards (single primary and no replicas). Make sure there are enough available IP addresses to accommodate the increase. Common pitfalls include the subnets in the subnet group have too small a CIDR range or the subnets are shared and heavily used by other clusters. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/SubnetGroups.Creating.html\">Creating a Subnet Group</a>. For versions below 5.0.6, the limit is 250 per cluster.</p> <p>To request a limit increase, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html\">Amazon Service Limits</a> and choose the limit type <b>Nodes per cluster per instance type</b>. </p> <p>When a Redis (cluster mode disabled) replication group has been successfully created, you can add one or more read replicas to it, up to a total of 5 read replicas. If you need to increase or decrease the number of node groups (console: shards), you can avail yourself of ElastiCache for Redis' scaling. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/Scaling.html\">Scaling ElastiCache for Redis Clusters</a> in the <i>ElastiCache User Guide</i>.</p> <note> <p>This operation is valid for Redis only.</p> </note>",
+    "CreateReplicationGroup": "<p>Creates a Redis (cluster mode disabled) or a Redis (cluster mode enabled) replication group.</p> <p>This API can be used to create a standalone regional replication group or a secondary replication group associated with a Global datastore.</p> <p>A Redis (cluster mode disabled) replication group is a collection of nodes, where one of the nodes is a read/write primary and the others are read-only replicas. Writes to the primary are asynchronously propagated to the replicas.</p> <p>A Redis cluster-mode enabled cluster is comprised of from 1 to 90 shards (API/CLI: node groups). Each shard has a primary node and up to 5 read-only replica nodes. The configuration can range from 90 shards and 0 replicas to 15 shards and 5 replicas, which is the maximum number or replicas allowed. </p> <p>The node or shard limit can be increased to a maximum of 500 per cluster if the Redis engine version is 5.0.6 or higher. For example, you can choose to configure a 500 node cluster that ranges between 83 shards (one primary and 5 replicas per shard) and 500 shards (single primary and no replicas). Make sure there are enough available IP addresses to accommodate the increase. Common pitfalls include the subnets in the subnet group have too small a CIDR range or the subnets are shared and heavily used by other clusters. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/SubnetGroups.Creating.html\">Creating a Subnet Group</a>. For versions below 5.0.6, the limit is 250 per cluster.</p> <p>To request a limit increase, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html\">Amazon Service Limits</a> and choose the limit type <b>Nodes per cluster per instance type</b>. </p> <p>When a Redis (cluster mode disabled) replication group has been successfully created, you can add one or more read replicas to it, up to a total of 5 read replicas. If you need to increase or decrease the number of node groups (console: shards), you can avail yourself of ElastiCache for Redis' scaling. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/Scaling.html\">Scaling ElastiCache for Redis Clusters</a> in the <i>ElastiCache User Guide</i>.</p> <note> <p>This operation is valid for Redis only.</p> </note>",
     "CreateServerlessCache": "<p>Creates a serverless cache.</p>",
     "CreateServerlessCacheSnapshot": "<p>This API creates a copy of an entire ServerlessCache at a specific moment in time. Available for Redis only.</p>",
     "CreateSnapshot": "<p>Creates a copy of an entire cluster or replication group at a specific moment in time.</p> <note> <p>This operation is valid for Redis only.</p> </note>",
@@ -1059,12 +1059,12 @@
       }
     },
     "Endpoint": {
-      "base": "<p>Represents the information required for client programs to connect to a cache node.</p>",
+      "base": "<p>Represents the information required for client programs to connect to a cache node. This value is read-only.</p>",
       "refs": {
         "CacheCluster$ConfigurationEndpoint": "<p>Represents a Memcached cluster endpoint which can be used by an application to connect to any node in the cluster. The configuration endpoint will always have <code>.cfg</code> in it.</p> <p>Example: <code>mem-3.9dvc4r<u>.cfg</u>.usw2.cache.amazonaws.com:11211</code> </p>",
         "CacheNode$Endpoint": "<p>The hostname for connecting to this cache node.</p>",
         "NodeGroup$PrimaryEndpoint": "<p>The endpoint of the primary node in this node group (shard).</p>",
-        "NodeGroup$ReaderEndpoint": "<p>The endpoint of the replica nodes in this node group (shard).</p>",
+        "NodeGroup$ReaderEndpoint": "<p>The endpoint of the replica nodes in this node group (shard). This value is read-only.</p>",
         "NodeGroupMember$ReadEndpoint": "<p>The information required for client programs to connect to a node for read operations. The read endpoint is only applicable on Redis (cluster mode disabled) clusters.</p>",
         "ReplicationGroup$ConfigurationEndpoint": "<p>The configuration endpoint for this replication group. Use the configuration endpoint to connect to this replication group.</p>",
         "ServerlessCache$Endpoint": null,
@@ -2383,7 +2383,7 @@
         "CreateReplicationGroupMessage$CacheParameterGroupName": "<p>The name of the parameter group to associate with this replication group. If this argument is omitted, the default cache parameter group for the specified engine is used.</p> <p>If you are running Redis version 3.2.4 or later, only one node group (shard), and want to use a default parameter group, we recommend that you specify the parameter group by name. </p> <ul> <li> <p>To create a Redis (cluster mode disabled) replication group, use <code>CacheParameterGroupName=default.redis3.2</code>.</p> </li> <li> <p>To create a Redis (cluster mode enabled) replication group, use <code>CacheParameterGroupName=default.redis3.2.cluster.on</code>.</p> </li> </ul>",
         "CreateReplicationGroupMessage$CacheSubnetGroupName": "<p>The name of the cache subnet group to be used for the replication group.</p> <important> <p>If you're going to launch your cluster in an Amazon VPC, you need to create a subnet group before you start creating a cluster. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/SubnetGroups.html\">Subnets and Subnet Groups</a>.</p> </important>",
         "CreateReplicationGroupMessage$SnapshotName": "<p>The name of a snapshot from which to restore data into the new replication group. The snapshot status changes to <code>restoring</code> while the new replication group is being created.</p>",
-        "CreateReplicationGroupMessage$PreferredMaintenanceWindow": "<p>Specifies the weekly time range during which maintenance on the cluster is performed. It is specified as a range in the format ddd:hh24:mi-ddd:hh24:mi (24H Clock UTC). The minimum maintenance window is a 60 minute period. Valid values for <code>ddd</code> are:</p> <p>Specifies the weekly time range during which maintenance on the cluster is performed. It is specified as a range in the format ddd:hh24:mi-ddd:hh24:mi (24H Clock UTC). The minimum maintenance window is a 60 minute period.</p> <p>Valid values for <code>ddd</code> are:</p> <ul> <li> <p> <code>sun</code> </p> </li> <li> <p> <code>mon</code> </p> </li> <li> <p> <code>tue</code> </p> </li> <li> <p> <code>wed</code> </p> </li> <li> <p> <code>thu</code> </p> </li> <li> <p> <code>fri</code> </p> </li> <li> <p> <code>sat</code> </p> </li> </ul> <p>Example: <code>sun:23:00-mon:01:30</code> </p>",
+        "CreateReplicationGroupMessage$PreferredMaintenanceWindow": "<p>Specifies the weekly time range during which maintenance on the cluster is performed. It is specified as a range in the format ddd:hh24:mi-ddd:hh24:mi (24H Clock UTC). The minimum maintenance window is a 60 minute period.</p> <p>Valid values for <code>ddd</code> are:</p> <ul> <li> <p> <code>sun</code> </p> </li> <li> <p> <code>mon</code> </p> </li> <li> <p> <code>tue</code> </p> </li> <li> <p> <code>wed</code> </p> </li> <li> <p> <code>thu</code> </p> </li> <li> <p> <code>fri</code> </p> </li> <li> <p> <code>sat</code> </p> </li> </ul> <p>Example: <code>sun:23:00-mon:01:30</code> </p>",
         "CreateReplicationGroupMessage$NotificationTopicArn": "<p>The Amazon Resource Name (ARN) of the Amazon Simple Notification Service (SNS) topic to which notifications are sent.</p> <note> <p>The Amazon SNS topic owner must be the same as the cluster owner.</p> </note>",
         "CreateReplicationGroupMessage$SnapshotWindow": "<p>The daily time range (in UTC) during which ElastiCache begins taking a daily snapshot of your node group (shard).</p> <p>Example: <code>05:00-09:00</code> </p> <p>If you do not specify this parameter, ElastiCache automatically chooses an appropriate time range.</p>",
         "CreateReplicationGroupMessage$AuthToken": "<p> <b>Reserved parameter.</b> The password used to access a password protected server.</p> <p> <code>AuthToken</code> can be specified only on replication groups where <code>TransitEncryptionEnabled</code> is <code>true</code>.</p> <important> <p>For HIPAA compliance, you must specify <code>TransitEncryptionEnabled</code> as <code>true</code>, an <code>AuthToken</code>, and a <code>CacheSubnetGroup</code>.</p> </important> <p>Password constraints:</p> <ul> <li> <p>Must be only printable ASCII characters.</p> </li> <li> <p>Must be at least 16 characters and no more than 128 characters in length.</p> </li> <li> <p>The only permitted printable special characters are !, &amp;, #, $, ^, &lt;, &gt;, and -. Other printable special characters cannot be used in the AUTH token.</p> </li> </ul> <p>For more information, see <a href=\"http://redis.io/commands/AUTH\">AUTH password</a> at http://redis.io/commands/AUTH.</p>",
@@ -2735,7 +2735,7 @@
       "base": null,
       "refs": {
         "CreateServerlessCacheRequest$SubnetIds": "<p>A list of the identifiers of the subnets where the VPC endpoint for the serverless cache will be deployed. All the subnetIds must belong to the same VPC.</p>",
-        "ServerlessCache$SubnetIds": "<p>If no subnet IDs are given and your VPC is in SFO, then ElastiCache will select 2 default subnets across AZs in your VPC. For all other Regions, if no subnet IDs are given then ElastiCache will select 3 default subnets across AZs in your default VPC.</p>"
+        "ServerlessCache$SubnetIds": "<p>If no subnet IDs are given and your VPC is in us-west-1, then ElastiCache will select 2 default subnets across AZs in your VPC. For all other Regions, if no subnet IDs are given then ElastiCache will select 3 default subnets across AZs in your default VPC.</p>"
       }
     },
     "SubnetInUse": {