@jjrawlins/cdk-ami-builder 0.0.66 → 0.0.67

package/node_modules/@aws-sdk/client-ecs/dist-types/commands/CreateServiceCommand.d.ts

@@ -32,7 +32,9 @@ declare const CreateServiceCommand_base: {
  * 			Amazon ECS runs another copy of the task in the specified cluster. To update an existing
  * 			service, use <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html">UpdateService</a>.</p>
  *          <note>
- *             <p>On March 21, 2024, a change was made to resolve the task definition revision before authorization. When a task definition revision is not specified, authorization will occur using the latest revision of a task definition.</p>
+ *             <p>On March 21, 2024, a change was made to resolve the task definition revision
+ * 				before authorization. When a task definition revision is not specified,
+ * 				authorization will occur using the latest revision of a task definition.</p>
  *          </note>
  *          <note>
  *             <p>Amazon Elastic Inference (EI) is no longer available to customers.</p>
@@ -40,10 +42,12 @@ declare const CreateServiceCommand_base: {
  *          <p>In addition to maintaining the desired count of tasks in your service, you can
  * 			optionally run your service behind one or more load balancers. The load balancers
  * 			distribute traffic across the tasks that are associated with the service. For more
- * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html">Service load balancing</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
- *          <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when creating or
- * 			updating a service. <code>volumeConfigurations</code> is only supported for REPLICA
- * 			service and not DAEMON service. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types">Amazon EBS volumes</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html">Service load balancing</a> in the <i>Amazon Elastic
+ * 				Container Service Developer Guide</i>.</p>
+ *          <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when
+ * 			creating or updating a service. <code>volumeConfigurations</code> is only supported for
+ * 			REPLICA service and not DAEMON service. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types">Amazon EBS volumes</a> in the <i>Amazon Elastic
+ * 				Container Service Developer Guide</i>.</p>
  *          <p>Tasks for services that don't use a load balancer are considered healthy if they're in
  * 			the <code>RUNNING</code> state. Tasks for services that use a load balancer are
  * 			considered healthy if they're in the <code>RUNNING</code> state and are reported as
@@ -52,21 +56,24 @@ declare const CreateServiceCommand_base: {
  *          <ul>
  *             <li>
  *                <p>
- *                   <code>REPLICA</code> - The replica scheduling strategy places and
- * 					maintains your desired number of tasks across your cluster. By default, the
- * 					service scheduler spreads tasks across Availability Zones. You can use task
- * 					placement strategies and constraints to customize task placement decisions. For
- * 					more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Service scheduler concepts</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ *                   <code>REPLICA</code> - The replica scheduling strategy places and maintains
+ * 					your desired number of tasks across your cluster. By default, the service
+ * 					scheduler spreads tasks across Availability Zones. You can use task placement
+ * 					strategies and constraints to customize task placement decisions. For more
+ * 					information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Service scheduler concepts</a> in the
+ * 						<i>Amazon Elastic Container Service Developer
+ * 					Guide</i>.</p>
  *             </li>
  *             <li>
  *                <p>
- *                   <code>DAEMON</code> - The daemon scheduling strategy deploys exactly one
- * 					task on each active container instance that meets all of the task placement
+ *                   <code>DAEMON</code> - The daemon scheduling strategy deploys exactly one task
+ * 					on each active container instance that meets all of the task placement
  * 					constraints that you specify in your cluster. The service scheduler also
  * 					evaluates the task placement constraints for running tasks. It also stops tasks
  * 					that don't meet the placement constraints. When using this strategy, you don't
  * 					need to specify a desired number of tasks, a task placement strategy, or use
- * 					Service Auto Scaling policies. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Amazon ECS services</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ * 					Service Auto Scaling policies. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Amazon ECS services</a> in the <i>Amazon Elastic Container
+ * 						Service Developer Guide</i>.</p>
  *             </li>
  *          </ul>
  *          <p>The deployment controller is the mechanism that determines how tasks are deployed for
@@ -74,129 +81,152 @@ declare const CreateServiceCommand_base: {
  *          <ul>
  *             <li>
  *                <p>ECS</p>
- *                <p> When you create a service which uses the <code>ECS</code> deployment controller, you can
- * 					choose between the following deployment strategies (which you can set in the
- * 						“<code>strategy</code>” field in “<code>deploymentConfiguration</code>”):
- * 					:</p>
+ *                <p> When you create a service which uses the <code>ECS</code> deployment
+ * 					controller, you can choose between the following deployment strategies (which
+ * 					you can set in the “<code>strategy</code>” field in
+ * 						“<code>deploymentConfiguration</code>”): :</p>
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <code>ROLLING</code>: When you create a service which uses the <i>rolling update</i>
- * 							(<code>ROLLING</code>) deployment strategy, the Amazon ECS service scheduler replaces the
- * 							currently running tasks with new tasks. The number of tasks that Amazon ECS adds or
- * 							removes from the service during a rolling update is controlled by the service
- * 							deployment configuration. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-ecs.html">Deploy Amazon ECS services by replacing tasks</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
- *                      <p>Rolling update deployments are best suited for the following scenarios:</p>
+ *                         <code>ROLLING</code>: When you create a service which uses the
+ * 								<i>rolling update</i> (<code>ROLLING</code>)
+ * 							deployment strategy, the Amazon ECS service scheduler replaces the
+ * 							currently running tasks with new tasks. The number of tasks that Amazon
+ * 							ECS adds or removes from the service during a rolling update is
+ * 							controlled by the service deployment configuration. For more
+ * 							information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-ecs.html">Deploy Amazon ECS services by replacing
+ * 								tasks</a> in the <i>Amazon Elastic Container Service
+ * 								Developer Guide</i>.</p>
+ *                      <p>Rolling update deployments are best suited for the following
+ * 							scenarios:</p>
  *                      <ul>
  *                         <li>
- *                            <p>Gradual service updates: You need to
- * 									update your service incrementally without taking the entire service
- * 									offline at once.</p>
+ *                            <p>Gradual service updates: You need to update your service
+ * 									incrementally without taking the entire service offline at
+ * 									once.</p>
  *                         </li>
  *                         <li>
- *                            <p>Limited resource requirements: You
- * 									want to avoid the additional resource costs of running two complete
- * 									environments simultaneously (as required by blue/green
- * 									deployments).</p>
+ *                            <p>Limited resource requirements: You want to avoid the
+ * 									additional resource costs of running two complete environments
+ * 									simultaneously (as required by blue/green deployments).</p>
  *                         </li>
  *                         <li>
- *                            <p>Acceptable deployment time: Your
- * 									application can tolerate a longer deployment process, as rolling updates
- * 									replace tasks one by one.</p>
+ *                            <p>Acceptable deployment time: Your application can tolerate a
+ * 									longer deployment process, as rolling updates replace tasks one
+ * 									by one.</p>
  *                         </li>
  *                         <li>
- *                            <p>No need for instant roll back: Your
- * 									service can tolerate a rollback process that takes minutes rather than
- * 									seconds.</p>
+ *                            <p>No need for instant roll back: Your service can tolerate a
+ * 									rollback process that takes minutes rather than seconds.</p>
  *                         </li>
  *                         <li>
- *                            <p>Simple deployment process: You prefer
- * 									a straightforward deployment approach without the complexity of managing
- * 									multiple environments, target groups, and listeners.</p>
+ *                            <p>Simple deployment process: You prefer a straightforward
+ * 									deployment approach without the complexity of managing multiple
+ * 									environments, target groups, and listeners.</p>
  *                         </li>
  *                         <li>
- *                            <p>No load balancer requirement: Your
- * 									service doesn't use or require a load balancer, Application Load Balancer, Network Load Balancer, or Service Connect (which are required
- * 									for blue/green deployments).</p>
+ *                            <p>No load balancer requirement: Your service doesn't use or
+ * 									require a load balancer, Application Load Balancer, Network Load
+ * 									Balancer, or Service Connect (which are required for blue/green
+ * 									deployments).</p>
  *                         </li>
  *                         <li>
- *                            <p>Stateful applications: Your
- * 									application maintains state that makes it difficult to run two parallel
- * 									environments.</p>
+ *                            <p>Stateful applications: Your application maintains state that
+ * 									makes it difficult to run two parallel environments.</p>
  *                         </li>
  *                         <li>
- *                            <p>Cost sensitivity: You want to
- * 									minimize deployment costs by not running duplicate environments during
- * 									deployment.</p>
+ *                            <p>Cost sensitivity: You want to minimize deployment costs by not
+ * 									running duplicate environments during deployment.</p>
  *                         </li>
  *                      </ul>
- *                      <p>Rolling updates are the default deployment strategy for services and provide a
- * 							balance between deployment safety and resource efficiency for many common
- * 							application scenarios.</p>
+ *                      <p>Rolling updates are the default deployment strategy for services and
+ * 							provide a balance between deployment safety and resource efficiency for
+ * 							many common application scenarios.</p>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <code>BLUE_GREEN</code>: A <i>blue/green</i> deployment strategy (<code>BLUE_GREEN</code>) is a release methodology that reduces downtime and
- * 							risk by running two identical production environments called blue and green.
- * 							With Amazon ECS blue/green deployments, you can validate new service revisions before
- * 							directing production traffic to them. This approach provides a safer way to
- * 							deploy changes with the ability to quickly roll back if needed. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-blue-green.html">Amazon ECS blue/green deployments</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
- *                      <p>Amazon ECS blue/green deployments are best suited for the following scenarios:</p>
+ *                         <code>BLUE_GREEN</code>: A <i>blue/green</i> deployment
+ * 							strategy (<code>BLUE_GREEN</code>) is a release methodology that reduces
+ * 							downtime and risk by running two identical production environments
+ * 							called blue and green. With Amazon ECS blue/green deployments, you can
+ * 							validate new service revisions before directing production traffic to
+ * 							them. This approach provides a safer way to deploy changes with the
+ * 							ability to quickly roll back if needed. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-blue-green.html">Amazon ECS blue/green deployments</a> in
+ * 							the <i>Amazon Elastic Container Service Developer
+ * 								Guide</i>.</p>
+ *                      <p>Amazon ECS blue/green deployments are best suited for the following
+ * 							scenarios:</p>
  *                      <ul>
  *                         <li>
- *                            <p>Service validation: When you need to
- * 									validate new service revisions before directing production traffic to
- * 									them</p>
+ *                            <p>Service validation: When you need to validate new service
+ * 									revisions before directing production traffic to them</p>
  *                         </li>
  *                         <li>
- *                            <p>Zero downtime: When your service
- * 									requires zero-downtime deployments</p>
+ *                            <p>Zero downtime: When your service requires zero-downtime
+ * 									deployments</p>
  *                         </li>
  *                         <li>
- *                            <p>Instant roll back: When you
- * 									need the ability to quickly roll back if issues are detected</p>
+ *                            <p>Instant roll back: When you need the ability to quickly roll
+ * 									back if issues are detected</p>
  *                         </li>
  *                         <li>
- *                            <p>Load balancer requirement: When your
- * 									service uses Application Load Balancer, Network Load Balancer, or Service Connect</p>
+ *                            <p>Load balancer requirement: When your service uses Application
+ * 									Load Balancer, Network Load Balancer, or Service Connect</p>
  *                         </li>
  *                      </ul>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <code>LINEAR</code>: A <i>linear</i> deployment strategy (<code>LINEAR</code>) gradually shifts traffic from the current production environment to a new environment in equal percentage increments over a specified time period. With Amazon ECS linear deployments, you can control the pace of traffic shifting and validate new service revisions with increasing amounts of production traffic.</p>
+ *                         <code>LINEAR</code>: A <i>linear</i> deployment strategy
+ * 								(<code>LINEAR</code>) gradually shifts traffic from the current
+ * 							production environment to a new environment in equal percentage
+ * 							increments. With Amazon ECS linear deployments, you can control the pace
+ * 							of traffic shifting and validate new service revisions with increasing
+ * 							amounts of production traffic.</p>
  *                      <p>Linear deployments are best suited for the following scenarios:</p>
  *                      <ul>
  *                         <li>
- *                            <p>Gradual validation: When you want to gradually validate your new service version with increasing traffic</p>
+ *                            <p>Gradual validation: When you want to gradually validate your
+ * 									new service version with increasing traffic</p>
  *                         </li>
  *                         <li>
- *                            <p>Performance monitoring: When you need time to monitor metrics and performance during the deployment</p>
+ *                            <p>Performance monitoring: When you need time to monitor metrics
+ * 									and performance during the deployment</p>
  *                         </li>
  *                         <li>
- *                            <p>Risk minimization: When you want to minimize risk by exposing the new version to production traffic incrementally</p>
+ *                            <p>Risk minimization: When you want to minimize risk by exposing
+ * 									the new version to production traffic incrementally</p>
  *                         </li>
  *                         <li>
- *                            <p>Load balancer requirement: When your service uses Application Load Balancer, Network Load Balancer, or Service Connect</p>
+ *                            <p>Load balancer requirement: When your service uses Application
+ * 									Load Balancer or Service Connect</p>
  *                         </li>
  *                      </ul>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <code>CANARY</code>: A <i>canary</i> deployment strategy (<code>CANARY</code>) shifts a small percentage of traffic to the new service revision first, then shifts the remaining traffic all at once after a specified time period. This allows you to test the new version with a subset of users before full deployment.</p>
+ *                         <code>CANARY</code>: A <i>canary</i> deployment strategy
+ * 								(<code>CANARY</code>) shifts a small percentage of traffic to the
+ * 							new service revision first, then shifts the remaining traffic all at
+ * 							once after a specified time period. This allows you to test the new
+ * 							version with a subset of users before full deployment.</p>
  *                      <p>Canary deployments are best suited for the following scenarios:</p>
  *                      <ul>
  *                         <li>
- *                            <p>Feature testing: When you want to test new features with a small subset of users before full rollout</p>
+ *                            <p>Feature testing: When you want to test new features with a
+ * 									small subset of users before full rollout</p>
  *                         </li>
  *                         <li>
- *                            <p>Production validation: When you need to validate performance and functionality with real production traffic</p>
+ *                            <p>Production validation: When you need to validate performance
+ * 									and functionality with real production traffic</p>
  *                         </li>
  *                         <li>
- *                            <p>Blast radius control: When you want to minimize blast radius if issues are discovered in the new version</p>
+ *                            <p>Blast radius control: When you want to minimize blast radius
+ * 									if issues are discovered in the new version</p>
  *                         </li>
  *                         <li>
- *                            <p>Load balancer requirement: When your service uses Application Load Balancer, Network Load Balancer, or Service Connect</p>
+ *                            <p>Load balancer requirement: When your service uses Application
+ * 									Load Balancer or Service Connect</p>
  *                         </li>
  *                      </ul>
  *                   </li>
@@ -208,19 +238,21 @@ declare const CreateServiceCommand_base: {
  *             </li>
  *             <li>
  *                <p>Blue/green deployment (powered by CodeDeploy)</p>
- *                <p>CodeDeploy installs an updated version of the application as a new replacement task
- * 					set and reroutes production traffic from the original application task set to
- * 					the replacement task set. The original task set is terminated after a successful
- * 					deployment. Use this deployment controller to verify a new deployment of a service
- * 					before sending production traffic to it.</p>
+ *                <p>CodeDeploy installs an updated version of the application as a new
+ * 					replacement task set and reroutes production traffic from the original
+ * 					application task set to the replacement task set. The original task set is
+ * 					terminated after a successful deployment. Use this deployment controller to
+ * 					verify a new deployment of a service before sending production traffic to
+ * 					it.</p>
  *             </li>
  *          </ul>
  *          <p>When creating a service that uses the <code>EXTERNAL</code> deployment controller, you
  * 			can specify only parameters that aren't controlled at the task set level. The only
- * 			required parameter is the service name. You control your services using the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateTaskSet.html">CreateTaskSet</a>. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html">Amazon ECS deployment types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ * 			required parameter is the service name. You control your services using the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateTaskSet.html">CreateTaskSet</a>. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html">Amazon ECS deployment types</a> in the <i>Amazon Elastic Container
+ * 				Service Developer Guide</i>.</p>
  *          <p>When the service scheduler launches new tasks, it determines task placement. For
- * 			information about task placement and task placement strategies, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement.html">Amazon ECS
- * 				task placement</a> in the <i>Amazon Elastic Container Service Developer Guide</i>
+ * 			information about task placement and task placement strategies, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement.html">Amazon ECS task placement</a> in the <i>Amazon Elastic Container Service
+ * 				Developer Guide</i>
  *          </p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
@@ -388,6 +420,10 @@ declare const CreateServiceCommand_base: {
  *         },
  *       ],
  *     },
+ *     accessLogConfiguration: { // ServiceConnectAccessLogConfiguration
+ *       format: "TEXT" || "JSON", // required
+ *       includeQueryParameters: "DISABLED" || "ENABLED",
+ *     },
  *   },
  *   volumeConfigurations: [ // ServiceVolumeConfigurations
  *     { // ServiceVolumeConfiguration
@@ -661,6 +697,10 @@ declare const CreateServiceCommand_base: {
  * //               },
  * //             ],
  * //           },
+ * //           accessLogConfiguration: { // ServiceConnectAccessLogConfiguration
+ * //             format: "TEXT" || "JSON", // required
+ * //             includeQueryParameters: "DISABLED" || "ENABLED",
+ * //           },
  * //         },
  * //         serviceConnectResources: [ // ServiceConnectServiceResourceList
  * //           { // ServiceConnectServiceResource
@@ -773,8 +813,8 @@ declare const CreateServiceCommand_base: {
  * @throws {@link InvalidParameterException} (client fault)
  *  <p>The specified parameter isn't valid. Review the available parameters for the API
  * 			request.</p>
- *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS service
- * 				event messages</a>. </p>
+ *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS
+ * 				service event messages</a>. </p>
  *
  * @throws {@link NamespaceNotFoundException} (client fault)
  *  <p>The specified namespace wasn't found.</p>

package/node_modules/@aws-sdk/client-ecs/dist-types/commands/CreateTaskSetCommand.d.ts

@@ -30,12 +30,15 @@ declare const CreateTaskSetCommand_base: {
  * <p>Create a task set in the specified cluster and service. This is used when a service
  * 			uses the <code>EXTERNAL</code> deployment controller type. For more information, see
  * 				<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html">Amazon ECS deployment
- * 				types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ * 				types</a> in the <i>Amazon Elastic Container Service Developer
+ * 				Guide</i>.</p>
  *          <note>
- *             <p>On March 21, 2024, a change was made to resolve the task definition revision before authorization. When a task definition revision is not specified, authorization will occur using the latest revision of a task definition.</p>
+ *             <p>On March 21, 2024, a change was made to resolve the task definition revision
+ * 				before authorization. When a task definition revision is not specified,
+ * 				authorization will occur using the latest revision of a task definition.</p>
  *          </note>
- *          <p>For information about the maximum number of task sets and other quotas, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html">Amazon ECS
- * 				service quotas</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ *          <p>For information about the maximum number of task sets and other quotas, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html">Amazon ECS service quotas</a> in the <i>Amazon Elastic Container Service
+ * 				Developer Guide</i>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -203,8 +206,8 @@ declare const CreateTaskSetCommand_base: {
  * @throws {@link InvalidParameterException} (client fault)
  *  <p>The specified parameter isn't valid. Review the available parameters for the API
  * 			request.</p>
- *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS service
- * 				event messages</a>. </p>
+ *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS
+ * 				service event messages</a>. </p>
  *
  * @throws {@link NamespaceNotFoundException} (client fault)
  *  <p>The specified namespace wasn't found.</p>

package/node_modules/@aws-sdk/client-ecs/dist-types/commands/DeleteAccountSettingCommand.d.ts

@@ -68,8 +68,8 @@ declare const DeleteAccountSettingCommand_base: {
  * @throws {@link InvalidParameterException} (client fault)
  *  <p>The specified parameter isn't valid. Review the available parameters for the API
  * 			request.</p>
- *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS service
- * 				event messages</a>. </p>
+ *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS
+ * 				service event messages</a>. </p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server issue.</p>

package/node_modules/@aws-sdk/client-ecs/dist-types/commands/DeleteAttributesCommand.d.ts

@@ -74,13 +74,13 @@ declare const DeleteAttributesCommand_base: {
  * @throws {@link InvalidParameterException} (client fault)
  *  <p>The specified parameter isn't valid. Review the available parameters for the API
  * 			request.</p>
- *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS service
- * 				event messages</a>. </p>
+ *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS
+ * 				service event messages</a>. </p>
  *
  * @throws {@link TargetNotFoundException} (client fault)
  *  <p>The specified target wasn't found. You can view your available container instances
- * 			with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListContainerInstances.html">ListContainerInstances</a>. Amazon ECS container instances are cluster-specific and
- * 			Region-specific.</p>
+ * 			with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListContainerInstances.html">ListContainerInstances</a>. Amazon ECS container instances are cluster-specific
+ * 			and Region-specific.</p>
  *
  * @throws {@link ECSServiceException}
  * <p>Base exception class for all service exceptions from ECS service.</p>

package/node_modules/@aws-sdk/client-ecs/dist-types/commands/DeleteCapacityProviderCommand.d.ts

@@ -192,8 +192,8 @@ declare const DeleteCapacityProviderCommand_base: {
  * @throws {@link InvalidParameterException} (client fault)
  *  <p>The specified parameter isn't valid. Review the available parameters for the API
  * 			request.</p>
- *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS service
- * 				event messages</a>. </p>
+ *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS
+ * 				service event messages</a>. </p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server issue.</p>

package/node_modules/@aws-sdk/client-ecs/dist-types/commands/DeleteClusterCommand.d.ts

@@ -134,7 +134,11 @@ declare const DeleteClusterCommand_base: {
  * 			action or resource. Or, it might be specifying an identifier that isn't valid.</p>
  *
  * @throws {@link ClusterContainsCapacityProviderException} (client fault)
- *  <p>The cluster contains one or more capacity providers that prevent the requested operation. This exception occurs when you try to delete a cluster that still has active capacity providers, including Amazon ECS Managed Instances capacity providers. You must first delete all capacity providers from the cluster before you can delete the cluster itself.</p>
+ *  <p>The cluster contains one or more capacity providers that prevent the requested
+ * 			operation. This exception occurs when you try to delete a cluster that still has active
+ * 			capacity providers, including Amazon ECS Managed Instances capacity providers. You must
+ * 			first delete all capacity providers from the cluster before you can delete the cluster
+ * 			itself.</p>
  *
  * @throws {@link ClusterContainsContainerInstancesException} (client fault)
  *  <p>You can't delete a cluster that has registered container instances. First, deregister
@@ -156,18 +160,18 @@ declare const DeleteClusterCommand_base: {
  * @throws {@link InvalidParameterException} (client fault)
  *  <p>The specified parameter isn't valid. Review the available parameters for the API
  * 			request.</p>
- *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS service
- * 				event messages</a>. </p>
+ *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS
+ * 				service event messages</a>. </p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server issue.</p>
  *
  * @throws {@link UpdateInProgressException} (client fault)
- *  <p>There's already a current Amazon ECS container agent update in progress on the container
- * 			instance that's specified. If the container agent becomes disconnected while it's in a
- * 			transitional stage, such as <code>PENDING</code> or <code>STAGING</code>, the update
- * 			process can get stuck in that state. However, when the agent reconnects, it resumes
- * 			where it stopped previously.</p>
+ *  <p>There's already a current Amazon ECS container agent update in progress on the
+ * 			container instance that's specified. If the container agent becomes disconnected while
+ * 			it's in a transitional stage, such as <code>PENDING</code> or <code>STAGING</code>, the
+ * 			update process can get stuck in that state. However, when the agent reconnects, it
+ * 			resumes where it stopped previously.</p>
  *
  * @throws {@link ECSServiceException}
  * <p>Base exception class for all service exceptions from ECS service.</p>

package/node_modules/@aws-sdk/client-ecs/dist-types/commands/DeleteServiceCommand.d.ts

@@ -39,8 +39,8 @@ declare const DeleteServiceCommand_base: {
  * 					<code>STOPPED</code> status, the service status moves from <code>DRAINING</code>
  * 				to <code>INACTIVE</code>. Services in the <code>DRAINING</code> or
  * 					<code>INACTIVE</code> status can still be viewed with the <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DescribeServices.html">DescribeServices</a> API operation. However, in the future,
- * 					<code>INACTIVE</code> services may be cleaned up and purged from Amazon ECS record
- * 				keeping, and <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DescribeServices.html">DescribeServices</a> calls on those services return a
+ * 					<code>INACTIVE</code> services may be cleaned up and purged from Amazon ECS
+ * 				record keeping, and <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DescribeServices.html">DescribeServices</a> calls on those services return a
  * 					<code>ServiceNotFoundException</code> error.</p>
  *          </note>
  *          <important>
@@ -296,6 +296,10 @@ declare const DeleteServiceCommand_base: {
  * //               },
  * //             ],
  * //           },
+ * //           accessLogConfiguration: { // ServiceConnectAccessLogConfiguration
+ * //             format: "TEXT" || "JSON", // required
+ * //             includeQueryParameters: "DISABLED" || "ENABLED",
+ * //           },
  * //         },
  * //         serviceConnectResources: [ // ServiceConnectServiceResourceList
  * //           { // ServiceConnectServiceResource
@@ -405,8 +409,8 @@ declare const DeleteServiceCommand_base: {
  * @throws {@link InvalidParameterException} (client fault)
  *  <p>The specified parameter isn't valid. Review the available parameters for the API
  * 			request.</p>
- *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS service
- * 				event messages</a>. </p>
+ *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS
+ * 				service event messages</a>. </p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server issue.</p>

package/node_modules/@aws-sdk/client-ecs/dist-types/commands/DeleteTaskDefinitionsCommand.d.ts

@@ -45,8 +45,8 @@ declare const DeleteTaskDefinitionsCommand_base: {
  * 			definition name is not displayed in the console and not returned in the API. If a task
  * 			definition revisions are in the <code>DELETE_IN_PROGRESS</code> state, the task
  * 			definition name is displayed in the console and returned in the API. The task definition
- * 			name is retained by Amazon ECS and the revision is incremented the next time you create a
- * 			task definition with that name.</p>
+ * 			name is retained by Amazon ECS and the revision is incremented the next time you create
+ * 			a task definition with that name.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -365,8 +365,8 @@ declare const DeleteTaskDefinitionsCommand_base: {
  * @throws {@link InvalidParameterException} (client fault)
  *  <p>The specified parameter isn't valid. Review the available parameters for the API
  * 			request.</p>
- *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS service
- * 				event messages</a>. </p>
+ *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS
+ * 				service event messages</a>. </p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server issue.</p>

package/node_modules/@aws-sdk/client-ecs/dist-types/commands/DeleteTaskSetCommand.d.ts

@@ -28,7 +28,8 @@ declare const DeleteTaskSetCommand_base: {
 };
 /**
  * <p>Deletes a specified task set within a service. This is used when a service uses the
- * 				<code>EXTERNAL</code> deployment controller type. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html">Amazon ECS deployment types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ * 				<code>EXTERNAL</code> deployment controller type. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html">Amazon ECS deployment types</a> in the <i>Amazon Elastic Container
+ * 				Service Developer Guide</i>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -143,8 +144,8 @@ declare const DeleteTaskSetCommand_base: {
  * @throws {@link InvalidParameterException} (client fault)
  *  <p>The specified parameter isn't valid. Review the available parameters for the API
  * 			request.</p>
- *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS service
- * 				event messages</a>. </p>
+ *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS
+ * 				service event messages</a>. </p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server issue.</p>

package/node_modules/@aws-sdk/client-ecs/dist-types/commands/DeregisterContainerInstanceCommand.d.ts

@@ -27,8 +27,8 @@ declare const DeregisterContainerInstanceCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Deregisters an Amazon ECS container instance from the specified cluster. This instance is
- * 			no longer available to run tasks.</p>
+ * <p>Deregisters an Amazon ECS container instance from the specified cluster. This instance
+ * 			is no longer available to run tasks.</p>
  *          <p>If you intend to use the container instance for some other purpose after
  * 			deregistration, we recommend that you stop all of the tasks running on the container
  * 			instance before deregistration. That prevents any orphaned tasks from consuming
@@ -37,9 +37,9 @@ declare const DeregisterContainerInstanceCommand_base: {
  * 			terminate the EC2 instance. If you are finished using the instance, be sure to terminate
  * 			it in the Amazon EC2 console to stop billing.</p>
  *          <note>
- *             <p>If you terminate a running container instance, Amazon ECS automatically deregisters the
- * 				instance from your cluster (stopped container instances or instances with
- * 				disconnected agents aren't automatically deregistered when terminated).</p>
+ *             <p>If you terminate a running container instance, Amazon ECS automatically
+ * 				deregisters the instance from your cluster (stopped container instances or instances
+ * 				with disconnected agents aren't automatically deregistered when terminated).</p>
  *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
@@ -158,8 +158,8 @@ declare const DeregisterContainerInstanceCommand_base: {
  * @throws {@link InvalidParameterException} (client fault)
  *  <p>The specified parameter isn't valid. Review the available parameters for the API
  * 			request.</p>
- *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS service
- * 				event messages</a>. </p>
+ *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS
+ * 				service event messages</a>. </p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server issue.</p>

package/node_modules/@aws-sdk/client-ecs/dist-types/commands/DeregisterTaskDefinitionCommand.d.ts

@@ -349,8 +349,8 @@ declare const DeregisterTaskDefinitionCommand_base: {
  * @throws {@link InvalidParameterException} (client fault)
  *  <p>The specified parameter isn't valid. Review the available parameters for the API
  * 			request.</p>
- *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS service
- * 				event messages</a>. </p>
+ *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS
+ * 				service event messages</a>. </p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server issue.</p>

package/node_modules/@aws-sdk/client-ecs/dist-types/commands/DescribeCapacityProvidersCommand.d.ts

@@ -196,8 +196,8 @@ declare const DescribeCapacityProvidersCommand_base: {
  * @throws {@link InvalidParameterException} (client fault)
  *  <p>The specified parameter isn't valid. Review the available parameters for the API
  * 			request.</p>
- *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS service
- * 				event messages</a>. </p>
+ *          <p>For more information about service event errors, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-event-messages-list.html">Amazon ECS
+ * 				service event messages</a>. </p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server issue.</p>