cdk-docker-image-deployment 0.0.74 → 0.0.75

package/node_modules/aws-sdk/apis/xray-2016-04-12.min.json

@@ -134,6 +134,25 @@
         "members": {}
       }
     },
+    "DeleteResourcePolicy": {
+      "http": {
+        "requestUri": "/DeleteResourcePolicy"
+      },
+      "input": {
+        "type": "structure",
+        "required": [
+          "PolicyName"
+        ],
+        "members": {
+          "PolicyName": {},
+          "PolicyRevisionId": {}
+        }
+      },
+      "output": {
+        "type": "structure",
+        "members": {}
+      }
+    },
     "DeleteSamplingRule": {
       "http": {
         "requestUri": "/DeleteSamplingRule"
@@ -166,7 +185,7 @@
         "type": "structure",
         "members": {
           "EncryptionConfig": {
-            "shape": "S1f"
+            "shape": "S1j"
           }
         }
       }
@@ -245,10 +264,10 @@
               "GroupARN": {},
               "GroupName": {},
               "RootCauseServiceId": {
-                "shape": "S1t"
+                "shape": "S1x"
               },
               "Categories": {
-                "shape": "S1v"
+                "shape": "S1z"
               },
               "State": {},
               "StartTime": {
@@ -259,13 +278,13 @@
               },
               "Summary": {},
               "ClientRequestImpactStatistics": {
-                "shape": "S1z"
+                "shape": "S23"
               },
               "RootCauseServiceRequestImpactStatistics": {
-                "shape": "S1z"
+                "shape": "S23"
               },
               "TopAnomalousServices": {
-                "shape": "S21"
+                "shape": "S25"
               }
             }
           }
@@ -302,13 +321,13 @@
                   "type": "timestamp"
                 },
                 "ClientRequestImpactStatistics": {
-                  "shape": "S1z"
+                  "shape": "S23"
                 },
                 "RootCauseServiceRequestImpactStatistics": {
-                  "shape": "S1z"
+                  "shape": "S23"
                 },
                 "TopAnomalousServices": {
-                  "shape": "S21"
+                  "shape": "S25"
                 }
               }
             }
@@ -366,7 +385,7 @@
                 "Type": {},
                 "Name": {},
                 "Names": {
-                  "shape": "S1u"
+                  "shape": "S1y"
                 },
                 "AccountId": {},
                 "Edges": {
@@ -428,10 +447,10 @@
                 "GroupARN": {},
                 "GroupName": {},
                 "RootCauseServiceId": {
-                  "shape": "S1t"
+                  "shape": "S1x"
                 },
                 "Categories": {
-                  "shape": "S1v"
+                  "shape": "S1z"
                 },
                 "State": {},
                 "StartTime": {
@@ -442,13 +461,13 @@
                 },
                 "Summary": {},
                 "ClientRequestImpactStatistics": {
-                  "shape": "S1z"
+                  "shape": "S23"
                 },
                 "RootCauseServiceRequestImpactStatistics": {
-                  "shape": "S1z"
+                  "shape": "S23"
                 },
                 "TopAnomalousServices": {
-                  "shape": "S21"
+                  "shape": "S25"
                 },
                 "LastUpdateTime": {
                   "type": "timestamp"
@@ -635,7 +654,7 @@
             "type": "timestamp"
           },
           "Services": {
-            "shape": "S3a"
+            "shape": "S3e"
           },
           "ContainsOldGroupVersions": {
             "type": "boolean"
@@ -685,10 +704,10 @@
                   "type": "timestamp"
                 },
                 "EdgeSummaryStatistics": {
-                  "shape": "S3e"
+                  "shape": "S3i"
                 },
                 "ServiceSummaryStatistics": {
-                  "shape": "S3m"
+                  "shape": "S3q"
                 },
                 "ServiceForecastStatistics": {
                   "type": "structure",
@@ -702,7 +721,7 @@
                   }
                 },
                 "ResponseTimeHistogram": {
-                  "shape": "S3h"
+                  "shape": "S3l"
                 }
               }
             }
@@ -734,7 +753,7 @@
         "type": "structure",
         "members": {
           "Services": {
-            "shape": "S3a"
+            "shape": "S3e"
           },
           "NextToken": {}
         }
@@ -834,7 +853,7 @@
                           }
                         },
                         "ServiceIds": {
-                          "shape": "S49"
+                          "shape": "S4d"
                         }
                       }
                     }
@@ -847,13 +866,13 @@
                     "members": {
                       "UserName": {},
                       "ServiceIds": {
-                        "shape": "S49"
+                        "shape": "S4d"
                       }
                     }
                   }
                 },
                 "ServiceIds": {
-                  "shape": "S49"
+                  "shape": "S4d"
                 },
                 "ResourceARNs": {
                   "type": "list",
@@ -883,7 +902,7 @@
                   }
                 },
                 "EntryPoint": {
-                  "shape": "S1t"
+                  "shape": "S1x"
                 },
                 "FaultRootCauses": {
                   "type": "list",
@@ -897,7 +916,7 @@
                           "members": {
                             "Name": {},
                             "Names": {
-                              "shape": "S1u"
+                              "shape": "S1y"
                             },
                             "Type": {},
                             "AccountId": {},
@@ -908,7 +927,7 @@
                                 "members": {
                                   "Name": {},
                                   "Exceptions": {
-                                    "shape": "S4o"
+                                    "shape": "S4s"
                                   },
                                   "Remote": {
                                     "type": "boolean"
@@ -940,7 +959,7 @@
                           "members": {
                             "Name": {},
                             "Names": {
-                              "shape": "S1u"
+                              "shape": "S1y"
                             },
                             "Type": {},
                             "AccountId": {},
@@ -951,7 +970,7 @@
                                 "members": {
                                   "Name": {},
                                   "Exceptions": {
-                                    "shape": "S4o"
+                                    "shape": "S4s"
                                   },
                                   "Remote": {
                                     "type": "boolean"
@@ -983,7 +1002,7 @@
                           "members": {
                             "Name": {},
                             "Names": {
-                              "shape": "S1u"
+                              "shape": "S1y"
                             },
                             "Type": {},
                             "AccountId": {},
@@ -1033,6 +1052,29 @@
         }
       }
     },
+    "ListResourcePolicies": {
+      "http": {
+        "requestUri": "/ListResourcePolicies"
+      },
+      "input": {
+        "type": "structure",
+        "members": {
+          "NextToken": {}
+        }
+      },
+      "output": {
+        "type": "structure",
+        "members": {
+          "ResourcePolicies": {
+            "type": "list",
+            "member": {
+              "shape": "S5a"
+            }
+          },
+          "NextToken": {}
+        }
+      }
+    },
     "ListTagsForResource": {
       "http": {
         "requestUri": "/ListTagsForResource"
@@ -1075,7 +1117,35 @@
         "type": "structure",
         "members": {
           "EncryptionConfig": {
-            "shape": "S1f"
+            "shape": "S1j"
+          }
+        }
+      }
+    },
+    "PutResourcePolicy": {
+      "http": {
+        "requestUri": "/PutResourcePolicy"
+      },
+      "input": {
+        "type": "structure",
+        "required": [
+          "PolicyName",
+          "PolicyDocument"
+        ],
+        "members": {
+          "PolicyName": {},
+          "PolicyDocument": {},
+          "PolicyRevisionId": {},
+          "BypassPolicyLockoutCheck": {
+            "type": "boolean"
+          }
+        }
+      },
+      "output": {
+        "type": "structure",
+        "members": {
+          "ResourcePolicy": {
+            "shape": "S5a"
           }
         }
       }
@@ -1398,7 +1468,7 @@
         }
       }
     },
-    "S1f": {
+    "S1j": {
       "type": "structure",
       "members": {
         "KeyId": {},
@@ -1406,26 +1476,26 @@
         "Type": {}
       }
     },
-    "S1t": {
+    "S1x": {
       "type": "structure",
       "members": {
         "Name": {},
         "Names": {
-          "shape": "S1u"
+          "shape": "S1y"
         },
         "AccountId": {},
         "Type": {}
       }
     },
-    "S1u": {
+    "S1y": {
       "type": "list",
       "member": {}
     },
-    "S1v": {
+    "S1z": {
       "type": "list",
       "member": {}
     },
-    "S1z": {
+    "S23": {
       "type": "structure",
       "members": {
         "FaultCount": {
@@ -1439,18 +1509,18 @@
         }
       }
     },
-    "S21": {
+    "S25": {
       "type": "list",
       "member": {
         "type": "structure",
         "members": {
           "ServiceId": {
-            "shape": "S1t"
+            "shape": "S1x"
           }
         }
       }
     },
-    "S3a": {
+    "S3e": {
       "type": "list",
       "member": {
         "type": "structure",
@@ -1460,7 +1530,7 @@
           },
           "Name": {},
           "Names": {
-            "shape": "S1u"
+            "shape": "S1y"
           },
           "Root": {
             "type": "boolean"
@@ -1489,10 +1559,10 @@
                   "type": "timestamp"
                 },
                 "SummaryStatistics": {
-                  "shape": "S3e"
+                  "shape": "S3i"
                 },
                 "ResponseTimeHistogram": {
-                  "shape": "S3h"
+                  "shape": "S3l"
                 },
                 "Aliases": {
                   "type": "list",
@@ -1510,34 +1580,34 @@
                 },
                 "EdgeType": {},
                 "ReceivedEventAgeHistogram": {
-                  "shape": "S3h"
+                  "shape": "S3l"
                 }
               }
             }
           },
           "SummaryStatistics": {
-            "shape": "S3m"
+            "shape": "S3q"
           },
           "DurationHistogram": {
-            "shape": "S3h"
+            "shape": "S3l"
           },
           "ResponseTimeHistogram": {
-            "shape": "S3h"
+            "shape": "S3l"
           }
         }
       }
     },
-    "S3e": {
+    "S3i": {
       "type": "structure",
       "members": {
         "OkCount": {
           "type": "long"
         },
         "ErrorStatistics": {
-          "shape": "S3f"
+          "shape": "S3j"
         },
         "FaultStatistics": {
-          "shape": "S3g"
+          "shape": "S3k"
         },
         "TotalCount": {
           "type": "long"
@@ -1547,7 +1617,7 @@
         }
       }
     },
-    "S3f": {
+    "S3j": {
       "type": "structure",
       "members": {
         "ThrottleCount": {
@@ -1561,7 +1631,7 @@
         }
       }
     },
-    "S3g": {
+    "S3k": {
       "type": "structure",
       "members": {
         "OtherCount": {
@@ -1572,7 +1642,7 @@
         }
       }
     },
-    "S3h": {
+    "S3l": {
       "type": "list",
       "member": {
         "type": "structure",
@@ -1586,17 +1656,17 @@
         }
       }
     },
-    "S3m": {
+    "S3q": {
       "type": "structure",
       "members": {
         "OkCount": {
           "type": "long"
         },
         "ErrorStatistics": {
-          "shape": "S3f"
+          "shape": "S3j"
         },
         "FaultStatistics": {
-          "shape": "S3g"
+          "shape": "S3k"
         },
         "TotalCount": {
           "type": "long"
@@ -1606,13 +1676,13 @@
         }
       }
     },
-    "S49": {
+    "S4d": {
       "type": "list",
       "member": {
-        "shape": "S1t"
+        "shape": "S1x"
       }
     },
-    "S4o": {
+    "S4s": {
       "type": "list",
       "member": {
         "type": "structure",
@@ -1621,6 +1691,17 @@
           "Message": {}
         }
       }
+    },
+    "S5a": {
+      "type": "structure",
+      "members": {
+        "PolicyName": {},
+        "PolicyDocument": {},
+        "PolicyRevisionId": {},
+        "LastUpdatedTime": {
+          "type": "timestamp"
+        }
+      }
     }
   }
 }

package/node_modules/aws-sdk/apis/xray-2016-04-12.paginators.json

@@ -2,6 +2,9 @@
   "pagination": {
     "BatchGetTraces": {
       "input_token": "NextToken",
+      "non_aggregate_keys": [
+        "UnprocessedTraceIds"
+      ],
       "output_token": "NextToken",
       "result_key": "Traces"
     },
@@ -32,11 +35,19 @@
     },
     "GetServiceGraph": {
       "input_token": "NextToken",
+      "non_aggregate_keys": [
+        "StartTime",
+        "EndTime",
+        "ContainsOldGroupVersions"
+      ],
       "output_token": "NextToken",
       "result_key": "Services"
     },
     "GetTimeSeriesServiceStatistics": {
       "input_token": "NextToken",
+      "non_aggregate_keys": [
+        "ContainsOldGroupVersions"
+      ],
       "output_token": "NextToken",
       "result_key": "TimeSeriesServiceStatistics"
     },
@@ -47,8 +58,22 @@
     },
     "GetTraceSummaries": {
       "input_token": "NextToken",
+      "non_aggregate_keys": [
+        "TracesProcessedCount",
+        "ApproximateTime"
+      ],
       "output_token": "NextToken",
       "result_key": "TraceSummaries"
+    },
+    "ListResourcePolicies": {
+      "input_token": "NextToken",
+      "output_token": "NextToken",
+      "result_key": "ResourcePolicies"
+    },
+    "ListTagsForResource": {
+      "input_token": "NextToken",
+      "output_token": "NextToken",
+      "result_key": "Tags"
     }
   }
 }

package/node_modules/aws-sdk/clients/batch.d.ts

@@ -20,11 +20,11 @@ declare class Batch extends Service {
    */
   cancelJob(callback?: (err: AWSError, data: Batch.Types.CancelJobResponse) => void): Request<Batch.Types.CancelJobResponse, AWSError>;
   /**
-   * Creates an Batch compute environment. You can create MANAGED or UNMANAGED compute environments. MANAGED compute environments can use Amazon EC2 or Fargate resources. UNMANAGED compute environments can only use EC2 resources. In a managed compute environment, Batch manages the capacity and instance types of the compute resources within the environment. This is based on the compute resource specification that you define or the launch template that you specify when you create the compute environment. Either, you can choose to use EC2 On-Demand Instances and EC2 Spot Instances. Or, you can use Fargate and Fargate Spot capacity in your managed compute environment. You can optionally set a maximum price so that Spot Instances only launch when the Spot Instance price is less than a specified percentage of the On-Demand price.  Multi-node parallel jobs aren't supported on Spot Instances.  In an unmanaged compute environment, you can manage your own EC2 compute resources and have flexibility with how you configure your compute resources. For example, you can use custom AMIs. However, you must verify that each of your AMIs meet the Amazon ECS container instance AMI specification. For more information, see container instance AMIs in the Amazon Elastic Container Service Developer Guide. After you created your unmanaged compute environment, you can use the DescribeComputeEnvironments operation to find the Amazon ECS cluster that's associated with it. Then, launch your container instances into that Amazon ECS cluster. For more information, see Launching an Amazon ECS container instance in the Amazon Elastic Container Service Developer Guide.  Batch doesn't automatically upgrade the AMIs in a compute environment after it's created. For example, it also doesn't update the AMIs in your compute environment when a newer version of the Amazon ECS optimized AMI is available. You're responsible for the management of the guest operating system. This includes any updates and security patches. You're also responsible for any additional application software or utilities that you install on the compute resources. There are two ways to use a new AMI for your Batch jobs. The original method is to complete these steps:   Create a new compute environment with the new AMI.   Add the compute environment to an existing job queue.   Remove the earlier compute environment from your job queue.   Delete the earlier compute environment.   In April 2022, Batch added enhanced support for updating compute environments. For more information, see Updating compute environments. To use the enhanced updating of compute environments to update AMIs, follow these rules:   Either don't set the service role (serviceRole) parameter or set it to the AWSBatchServiceRole service-linked role.   Set the allocation strategy (allocationStrategy) parameter to BEST_FIT_PROGRESSIVE or SPOT_CAPACITY_OPTIMIZED.   Set the update to latest image version (updateToLatestImageVersion) parameter to true.   Don't specify an AMI ID in imageId, imageIdOverride (in  ec2Configuration ), or in the launch template (launchTemplate). In that case, Batch selects the latest Amazon ECS optimized AMI that's supported by Batch at the time the infrastructure update is initiated. Alternatively, you can specify the AMI ID in the imageId or imageIdOverride parameters, or the launch template identified by the LaunchTemplate properties. Changing any of these properties starts an infrastructure update. If the AMI ID is specified in the launch template, it can't be replaced by specifying an AMI ID in either the imageId or imageIdOverride parameters. It can only be replaced by specifying a different launch template, or if the launch template version is set to $Default or $Latest, by setting either a new default version for the launch template (if $Default) or by adding a new version to the launch template (if $Latest).   If these rules are followed, any update that starts an infrastructure update causes the AMI ID to be re-selected. If the version setting in the launch template (launchTemplate) is set to $Latest or $Default, the latest or default version of the launch template is evaluated up at the time of the infrastructure update, even if the launchTemplate wasn't updated. 
+   * Creates an Batch compute environment. You can create MANAGED or UNMANAGED compute environments. MANAGED compute environments can use Amazon EC2 or Fargate resources. UNMANAGED compute environments can only use EC2 resources. In a managed compute environment, Batch manages the capacity and instance types of the compute resources within the environment. This is based on the compute resource specification that you define or the launch template that you specify when you create the compute environment. Either, you can choose to use EC2 On-Demand Instances and EC2 Spot Instances. Or, you can use Fargate and Fargate Spot capacity in your managed compute environment. You can optionally set a maximum price so that Spot Instances only launch when the Spot Instance price is less than a specified percentage of the On-Demand price.  Multi-node parallel jobs aren't supported on Spot Instances.  In an unmanaged compute environment, you can manage your own EC2 compute resources and have flexibility with how you configure your compute resources. For example, you can use custom AMIs. However, you must verify that each of your AMIs meet the Amazon ECS container instance AMI specification. For more information, see container instance AMIs in the Amazon Elastic Container Service Developer Guide. After you created your unmanaged compute environment, you can use the DescribeComputeEnvironments operation to find the Amazon ECS cluster that's associated with it. Then, launch your container instances into that Amazon ECS cluster. For more information, see Launching an Amazon ECS container instance in the Amazon Elastic Container Service Developer Guide.  To create a compute environment that uses EKS resources, the caller must have permissions to call eks:DescribeCluster.   Batch doesn't automatically upgrade the AMIs in a compute environment after it's created. For example, it also doesn't update the AMIs in your compute environment when a newer version of the Amazon ECS optimized AMI is available. You're responsible for the management of the guest operating system. This includes any updates and security patches. You're also responsible for any additional application software or utilities that you install on the compute resources. There are two ways to use a new AMI for your Batch jobs. The original method is to complete these steps:   Create a new compute environment with the new AMI.   Add the compute environment to an existing job queue.   Remove the earlier compute environment from your job queue.   Delete the earlier compute environment.   In April 2022, Batch added enhanced support for updating compute environments. For more information, see Updating compute environments. To use the enhanced updating of compute environments to update AMIs, follow these rules:   Either don't set the service role (serviceRole) parameter or set it to the AWSBatchServiceRole service-linked role.   Set the allocation strategy (allocationStrategy) parameter to BEST_FIT_PROGRESSIVE or SPOT_CAPACITY_OPTIMIZED.   Set the update to latest image version (updateToLatestImageVersion) parameter to true.   Don't specify an AMI ID in imageId, imageIdOverride (in  ec2Configuration ), or in the launch template (launchTemplate). In that case, Batch selects the latest Amazon ECS optimized AMI that's supported by Batch at the time the infrastructure update is initiated. Alternatively, you can specify the AMI ID in the imageId or imageIdOverride parameters, or the launch template identified by the LaunchTemplate properties. Changing any of these properties starts an infrastructure update. If the AMI ID is specified in the launch template, it can't be replaced by specifying an AMI ID in either the imageId or imageIdOverride parameters. It can only be replaced by specifying a different launch template, or if the launch template version is set to $Default or $Latest, by setting either a new default version for the launch template (if $Default) or by adding a new version to the launch template (if $Latest).   If these rules are followed, any update that starts an infrastructure update causes the AMI ID to be re-selected. If the version setting in the launch template (launchTemplate) is set to $Latest or $Default, the latest or default version of the launch template is evaluated up at the time of the infrastructure update, even if the launchTemplate wasn't updated. 
    */
   createComputeEnvironment(params: Batch.Types.CreateComputeEnvironmentRequest, callback?: (err: AWSError, data: Batch.Types.CreateComputeEnvironmentResponse) => void): Request<Batch.Types.CreateComputeEnvironmentResponse, AWSError>;
   /**
-   * Creates an Batch compute environment. You can create MANAGED or UNMANAGED compute environments. MANAGED compute environments can use Amazon EC2 or Fargate resources. UNMANAGED compute environments can only use EC2 resources. In a managed compute environment, Batch manages the capacity and instance types of the compute resources within the environment. This is based on the compute resource specification that you define or the launch template that you specify when you create the compute environment. Either, you can choose to use EC2 On-Demand Instances and EC2 Spot Instances. Or, you can use Fargate and Fargate Spot capacity in your managed compute environment. You can optionally set a maximum price so that Spot Instances only launch when the Spot Instance price is less than a specified percentage of the On-Demand price.  Multi-node parallel jobs aren't supported on Spot Instances.  In an unmanaged compute environment, you can manage your own EC2 compute resources and have flexibility with how you configure your compute resources. For example, you can use custom AMIs. However, you must verify that each of your AMIs meet the Amazon ECS container instance AMI specification. For more information, see container instance AMIs in the Amazon Elastic Container Service Developer Guide. After you created your unmanaged compute environment, you can use the DescribeComputeEnvironments operation to find the Amazon ECS cluster that's associated with it. Then, launch your container instances into that Amazon ECS cluster. For more information, see Launching an Amazon ECS container instance in the Amazon Elastic Container Service Developer Guide.  Batch doesn't automatically upgrade the AMIs in a compute environment after it's created. For example, it also doesn't update the AMIs in your compute environment when a newer version of the Amazon ECS optimized AMI is available. You're responsible for the management of the guest operating system. This includes any updates and security patches. You're also responsible for any additional application software or utilities that you install on the compute resources. There are two ways to use a new AMI for your Batch jobs. The original method is to complete these steps:   Create a new compute environment with the new AMI.   Add the compute environment to an existing job queue.   Remove the earlier compute environment from your job queue.   Delete the earlier compute environment.   In April 2022, Batch added enhanced support for updating compute environments. For more information, see Updating compute environments. To use the enhanced updating of compute environments to update AMIs, follow these rules:   Either don't set the service role (serviceRole) parameter or set it to the AWSBatchServiceRole service-linked role.   Set the allocation strategy (allocationStrategy) parameter to BEST_FIT_PROGRESSIVE or SPOT_CAPACITY_OPTIMIZED.   Set the update to latest image version (updateToLatestImageVersion) parameter to true.   Don't specify an AMI ID in imageId, imageIdOverride (in  ec2Configuration ), or in the launch template (launchTemplate). In that case, Batch selects the latest Amazon ECS optimized AMI that's supported by Batch at the time the infrastructure update is initiated. Alternatively, you can specify the AMI ID in the imageId or imageIdOverride parameters, or the launch template identified by the LaunchTemplate properties. Changing any of these properties starts an infrastructure update. If the AMI ID is specified in the launch template, it can't be replaced by specifying an AMI ID in either the imageId or imageIdOverride parameters. It can only be replaced by specifying a different launch template, or if the launch template version is set to $Default or $Latest, by setting either a new default version for the launch template (if $Default) or by adding a new version to the launch template (if $Latest).   If these rules are followed, any update that starts an infrastructure update causes the AMI ID to be re-selected. If the version setting in the launch template (launchTemplate) is set to $Latest or $Default, the latest or default version of the launch template is evaluated up at the time of the infrastructure update, even if the launchTemplate wasn't updated. 
+   * Creates an Batch compute environment. You can create MANAGED or UNMANAGED compute environments. MANAGED compute environments can use Amazon EC2 or Fargate resources. UNMANAGED compute environments can only use EC2 resources. In a managed compute environment, Batch manages the capacity and instance types of the compute resources within the environment. This is based on the compute resource specification that you define or the launch template that you specify when you create the compute environment. Either, you can choose to use EC2 On-Demand Instances and EC2 Spot Instances. Or, you can use Fargate and Fargate Spot capacity in your managed compute environment. You can optionally set a maximum price so that Spot Instances only launch when the Spot Instance price is less than a specified percentage of the On-Demand price.  Multi-node parallel jobs aren't supported on Spot Instances.  In an unmanaged compute environment, you can manage your own EC2 compute resources and have flexibility with how you configure your compute resources. For example, you can use custom AMIs. However, you must verify that each of your AMIs meet the Amazon ECS container instance AMI specification. For more information, see container instance AMIs in the Amazon Elastic Container Service Developer Guide. After you created your unmanaged compute environment, you can use the DescribeComputeEnvironments operation to find the Amazon ECS cluster that's associated with it. Then, launch your container instances into that Amazon ECS cluster. For more information, see Launching an Amazon ECS container instance in the Amazon Elastic Container Service Developer Guide.  To create a compute environment that uses EKS resources, the caller must have permissions to call eks:DescribeCluster.   Batch doesn't automatically upgrade the AMIs in a compute environment after it's created. For example, it also doesn't update the AMIs in your compute environment when a newer version of the Amazon ECS optimized AMI is available. You're responsible for the management of the guest operating system. This includes any updates and security patches. You're also responsible for any additional application software or utilities that you install on the compute resources. There are two ways to use a new AMI for your Batch jobs. The original method is to complete these steps:   Create a new compute environment with the new AMI.   Add the compute environment to an existing job queue.   Remove the earlier compute environment from your job queue.   Delete the earlier compute environment.   In April 2022, Batch added enhanced support for updating compute environments. For more information, see Updating compute environments. To use the enhanced updating of compute environments to update AMIs, follow these rules:   Either don't set the service role (serviceRole) parameter or set it to the AWSBatchServiceRole service-linked role.   Set the allocation strategy (allocationStrategy) parameter to BEST_FIT_PROGRESSIVE or SPOT_CAPACITY_OPTIMIZED.   Set the update to latest image version (updateToLatestImageVersion) parameter to true.   Don't specify an AMI ID in imageId, imageIdOverride (in  ec2Configuration ), or in the launch template (launchTemplate). In that case, Batch selects the latest Amazon ECS optimized AMI that's supported by Batch at the time the infrastructure update is initiated. Alternatively, you can specify the AMI ID in the imageId or imageIdOverride parameters, or the launch template identified by the LaunchTemplate properties. Changing any of these properties starts an infrastructure update. If the AMI ID is specified in the launch template, it can't be replaced by specifying an AMI ID in either the imageId or imageIdOverride parameters. It can only be replaced by specifying a different launch template, or if the launch template version is set to $Default or $Latest, by setting either a new default version for the launch template (if $Default) or by adding a new version to the launch template (if $Latest).   If these rules are followed, any update that starts an infrastructure update causes the AMI ID to be re-selected. If the version setting in the launch template (launchTemplate) is set to $Latest or $Default, the latest or default version of the launch template is evaluated up at the time of the infrastructure update, even if the launchTemplate wasn't updated. 
    */
   createComputeEnvironment(callback?: (err: AWSError, data: Batch.Types.CreateComputeEnvironmentResponse) => void): Request<Batch.Types.CreateComputeEnvironmentResponse, AWSError>;
   /**
@@ -456,7 +456,7 @@ declare namespace Batch {
      */
     maxvCpus?: Integer;
     /**
-     * The desired number of Amazon EC2 vCPUS in the compute environment. Batch modifies this value between the minimum and maximum values based on job queue demand.  This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it. 
+     * The desired number of Amazon EC2 vCPUS in the compute environment. Batch modifies this value between the minimum and maximum values based on job queue demand.  This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.   Batch doesn't support changing the desired number of vCPUs of an existing compute environment. Don't specify this parameter for compute environments using Amazon EKS clusters. 
      */
     desiredvCpus?: Integer;
     /**
@@ -1288,7 +1288,7 @@ declare namespace Batch {
      */
     hostNetwork?: Boolean;
     /**
-     * The DNS policy for the pod. The default value is ClusterFirst. If the hostNetwork parameter is not specified, the default is ClusterFirstWithHostNet. ClusterFirst indicates that any DNS query that does not match the configured cluster domain suffix is forwarded to the upstream nameserver inherited from the node. For more information, see Pod's DNS policy in the Kubernetes documentation. Valid values: Default | ClusterFirst | ClusterFirstWithHostNet | None 
+     * The DNS policy for the pod. The default value is ClusterFirst. If the hostNetwork parameter is not specified, the default is ClusterFirstWithHostNet. ClusterFirst indicates that any DNS query that does not match the configured cluster domain suffix is forwarded to the upstream nameserver inherited from the node. For more information, see Pod's DNS policy in the Kubernetes documentation. Valid values: Default | ClusterFirst | ClusterFirstWithHostNet 
      */
     dnsPolicy?: String;
     /**
@@ -1310,7 +1310,7 @@ declare namespace Batch {
      */
     hostNetwork?: Boolean;
     /**
-     * The DNS policy for the pod. The default value is ClusterFirst. If the hostNetwork parameter is not specified, the default is ClusterFirstWithHostNet. ClusterFirst indicates that any DNS query that does not match the configured cluster domain suffix is forwarded to the upstream nameserver inherited from the node. For more information, see Pod's DNS policy in the Kubernetes documentation. Valid values: Default | ClusterFirst | ClusterFirstWithHostNet | None 
+     * The DNS policy for the pod. The default value is ClusterFirst. If the hostNetwork parameter is not specified, the default is ClusterFirstWithHostNet. ClusterFirst indicates that any DNS query that does not match the configured cluster domain suffix is forwarded to the upstream nameserver inherited from the node. If no value was specified for dnsPolicy in the RegisterJobDefinition API operation, then no value will be returned for dnsPolicy by either of DescribeJobDefinitions or DescribeJobs API operations. The pod spec setting will contain either ClusterFirst or ClusterFirstWithHostNet, depending on the value of the hostNetwork parameter. For more information, see Pod's DNS policy in the Kubernetes documentation. Valid values: Default | ClusterFirst | ClusterFirstWithHostNet 
      */
     dnsPolicy?: String;
     /**
@@ -2048,7 +2048,7 @@ declare namespace Batch {
   }
   export interface ResourceRequirement {
     /**
-     * The quantity of the specified resource to reserve for the container. The values vary based on the type specified.  type="GPU"  The number of physical GPUs to reserve for the container. Make sure that the number of GPUs reserved for all containers in a job doesn't exceed the number of available GPUs on the compute resource that the job is launched on.  GPUs aren't available for jobs that are running on Fargate resources.   type="MEMORY"  The memory hard limit (in MiB) present to the container. This parameter is supported for jobs that are running on EC2 resources. If your container attempts to exceed the memory specified, the container is terminated. This parameter maps to Memory in the Create a container section of the Docker Remote API and the --memory option to docker run. You must specify at least 4 MiB of memory for a job. This is required but can be specified in several places for multi-node parallel (MNP) jobs. It must be specified for each node at least once. This parameter maps to Memory in the Create a container section of the Docker Remote API and the --memory option to docker run.  If you're trying to maximize your resource utilization by providing your jobs as much memory as possible for a particular instance type, see Memory management in the Batch User Guide.  For jobs that are running on Fargate resources, then value is the hard limit (in MiB), and must match one of the supported values and the VCPU values must be one of the values supported for that memory value.  value = 512   VCPU = 0.25  value = 1024   VCPU = 0.25 or 0.5  value = 2048   VCPU = 0.25, 0.5, or 1  value = 3072   VCPU = 0.5, or 1  value = 4096   VCPU = 0.5, 1, or 2  value = 5120, 6144, or 7168   VCPU = 1 or 2  value = 8192   VCPU = 1, 2, or 4  value = 9216, 10240, 11264, 12288, 13312, 14336, 15360, or 16384   VCPU = 2 or 4  value = 17408, 18432, 19456, 20480, 21504, 22528, 23552, 24576, 25600, 26624, 27648, 28672, 29696, or 30720   VCPU = 4    type="VCPU"  The number of vCPUs reserved for the container. This parameter maps to CpuShares in the Create a container section of the Docker Remote API and the --cpu-shares option to docker run. Each vCPU is equivalent to 1,024 CPU shares. For EC2 resources, you must specify at least one vCPU. This is required but can be specified in several places; it must be specified for each node at least once. For jobs that are running on Fargate resources, then value must match one of the supported values and the MEMORY values must be one of the values supported for that VCPU value. The supported values are 0.25, 0.5, 1, 2, and 4  value = 0.25   MEMORY = 512, 1024, or 2048  value = 0.5   MEMORY = 1024, 2048, 3072, or 4096  value = 1   MEMORY = 2048, 3072, 4096, 5120, 6144, 7168, or 8192  value = 2   MEMORY = 4096, 5120, 6144, 7168, 8192, 9216, 10240, 11264, 12288, 13312, 14336, 15360, or 16384  value = 4   MEMORY = 8192, 9216, 10240, 11264, 12288, 13312, 14336, 15360, 16384, 17408, 18432, 19456, 20480, 21504, 22528, 23552, 24576, 25600, 26624, 27648, 28672, 29696, or 30720    
+     * The quantity of the specified resource to reserve for the container. The values vary based on the type specified.  type="GPU"  The number of physical GPUs to reserve for the container. Make sure that the number of GPUs reserved for all containers in a job doesn't exceed the number of available GPUs on the compute resource that the job is launched on.  GPUs aren't available for jobs that are running on Fargate resources.   type="MEMORY"  The memory hard limit (in MiB) present to the container. This parameter is supported for jobs that are running on EC2 resources. If your container attempts to exceed the memory specified, the container is terminated. This parameter maps to Memory in the Create a container section of the Docker Remote API and the --memory option to docker run. You must specify at least 4 MiB of memory for a job. This is required but can be specified in several places for multi-node parallel (MNP) jobs. It must be specified for each node at least once. This parameter maps to Memory in the Create a container section of the Docker Remote API and the --memory option to docker run.  If you're trying to maximize your resource utilization by providing your jobs as much memory as possible for a particular instance type, see Memory management in the Batch User Guide.  For jobs that are running on Fargate resources, then value is the hard limit (in MiB), and must match one of the supported values and the VCPU values must be one of the values supported for that memory value.  value = 512   VCPU = 0.25  value = 1024   VCPU = 0.25 or 0.5  value = 2048   VCPU = 0.25, 0.5, or 1  value = 3072   VCPU = 0.5, or 1  value = 4096   VCPU = 0.5, 1, or 2  value = 5120, 6144, or 7168   VCPU = 1 or 2  value = 8192   VCPU = 1, 2, 4, or 8  value = 9216, 10240, 11264, 12288, 13312, 14336, or 15360   VCPU = 2 or 4  value = 16384   VCPU = 2, 4, or 8  value = 17408, 18432, 19456, 21504, 22528, 23552, 25600, 26624, 27648, 29696, or 30720   VCPU = 4  value = 20480, 24576, or 28672   VCPU = 4 or 8  value = 36864, 45056, 53248, or 61440   VCPU = 8  value = 32768, 40960, 49152, or 57344   VCPU = 8 or 16  value = 65536, 73728, 81920, 90112, 98304, 106496, 114688, or 122880   VCPU = 16    type="VCPU"  The number of vCPUs reserved for the container. This parameter maps to CpuShares in the Create a container section of the Docker Remote API and the --cpu-shares option to docker run. Each vCPU is equivalent to 1,024 CPU shares. For EC2 resources, you must specify at least one vCPU. This is required but can be specified in several places; it must be specified for each node at least once. The default for the Fargate On-Demand vCPU resource count quota is 6 vCPUs. For more information about Fargate quotas, see Fargate quotas in the Amazon Web Services General Reference. For jobs that are running on Fargate resources, then value must match one of the supported values and the MEMORY values must be one of the values supported for that VCPU value. The supported values are 0.25, 0.5, 1, 2, 4, 8, and 16  value = 0.25   MEMORY = 512, 1024, or 2048  value = 0.5   MEMORY = 1024, 2048, 3072, or 4096  value = 1   MEMORY = 2048, 3072, 4096, 5120, 6144, 7168, or 8192  value = 2   MEMORY = 4096, 5120, 6144, 7168, 8192, 9216, 10240, 11264, 12288, 13312, 14336, 15360, or 16384  value = 4   MEMORY = 8192, 9216, 10240, 11264, 12288, 13312, 14336, 15360, 16384, 17408, 18432, 19456, 20480, 21504, 22528, 23552, 24576, 25600, 26624, 27648, 28672, 29696, or 30720  value = 8   MEMORY = 16384, 20480, 24576, 28672, 32768, 36864, 40960, 45056, 49152, 53248, 57344, or 61440   value = 16   MEMORY = 32768, 40960, 49152, 57344, 65536, 73728, 81920, 90112, 98304, 106496, 114688, or 122880     
      */
     value: String;
     /**