You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"description": "This release adds the task properties field to attempt details and the name field on EKS container detail."
6
+
},
7
+
{
8
+
"type": "feature",
9
+
"category": "CloudFront",
10
+
"description": "CloudFront origin access control extends support to AWS Lambda function URLs and AWS Elemental MediaPackage v2 origins."
11
+
},
12
+
{
13
+
"type": "feature",
14
+
"category": "CloudWatch",
15
+
"description": "This release adds support for Metric Characteristics for CloudWatch Anomaly Detection. Anomaly Detector now takes Metric Characteristics object with Periodic Spikes boolean field that tells Anomaly Detection that spikes that repeat at the same time every week are part of the expected pattern."
16
+
},
17
+
{
18
+
"type": "feature",
19
+
"category": "IAM",
20
+
"description": "For CreateOpenIDConnectProvider API, the ThumbprintList parameter is no longer required."
21
+
},
22
+
{
23
+
"type": "feature",
24
+
"category": "MediaLive",
25
+
"description": "AWS Elemental MediaLive introduces workflow monitor, a new feature that enables the visualization and monitoring of your media workflows. Create signal maps of your existing workflows and monitor them by creating notification and monitoring template groups."
26
+
},
27
+
{
28
+
"type": "feature",
29
+
"category": "Omics",
30
+
"description": "This release adds support for retrieval of S3 direct access metadata on sequence stores and read sets, and adds support for SHA256up and SHA512up HealthOmics ETags."
Copy file name to clipboardExpand all lines: CHANGELOG.md
+11-1
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,17 @@
1
1
# Changelog for AWS SDK for JavaScript
2
-
<!--LATEST=2.1597.0-->
2
+
<!--LATEST=2.1598.0-->
3
3
<!--ENTRYINSERT-->
4
4
5
+
## 2.1598.0
6
+
* feature: Batch: This release adds the task properties field to attempt details and the name field on EKS container detail.
7
+
* feature: CloudFront: CloudFront origin access control extends support to AWS Lambda function URLs and AWS Elemental MediaPackage v2 origins.
8
+
* feature: CloudWatch: This release adds support for Metric Characteristics for CloudWatch Anomaly Detection. Anomaly Detector now takes Metric Characteristics object with Periodic Spikes boolean field that tells Anomaly Detection that spikes that repeat at the same time every week are part of the expected pattern.
9
+
* feature: IAM: For CreateOpenIDConnectProvider API, the ThumbprintList parameter is no longer required.
10
+
* feature: MediaLive: AWS Elemental MediaLive introduces workflow monitor, a new feature that enables the visualization and monitoring of your media workflows. Create signal maps of your existing workflows and monitor them by creating notification and monitoring template groups.
11
+
* feature: Omics: This release adds support for retrieval of S3 direct access metadata on sequence stores and read sets, and adds support for SHA256up and SHA512up HealthOmics ETags.
Copy file name to clipboardExpand all lines: apis/batch-2016-08-10.normal.json
+70-6
Original file line number
Diff line number
Diff line change
@@ -655,6 +655,10 @@
655
655
"statusReason": {
656
656
"shape": "String",
657
657
"documentation": "<p>A short, human-readable string to provide additional details for the current status of the job attempt.</p>"
658
+
},
659
+
"taskProperties": {
660
+
"shape": "ListAttemptEcsTaskDetails",
661
+
"documentation": "<p>The properties for a task definition that describes the container and volume definitions of an Amazon ECS task.</p>"
658
662
}
659
663
},
660
664
"documentation": "<p>An object that represents a job attempt.</p>"
@@ -665,6 +669,50 @@
665
669
"shape": "AttemptDetail"
666
670
}
667
671
},
672
+
"AttemptEcsTaskDetails": {
673
+
"type": "structure",
674
+
"members": {
675
+
"containerInstanceArn": {
676
+
"shape": "String",
677
+
"documentation": "<p>The Amazon Resource Name (ARN) of the container instance that hosts the task.</p>"
678
+
},
679
+
"taskArn": {
680
+
"shape": "String",
681
+
"documentation": "<p>The ARN of the Amazon ECS task.</p>"
682
+
},
683
+
"containers": {
684
+
"shape": "ListAttemptTaskContainerDetails",
685
+
"documentation": "<p>A list of containers that are included in the <code>taskProperties</code> list.</p>"
686
+
}
687
+
},
688
+
"documentation": "<p>An object that represents the details of a task.</p>"
689
+
},
690
+
"AttemptTaskContainerDetails": {
691
+
"type": "structure",
692
+
"members": {
693
+
"exitCode": {
694
+
"shape": "Integer",
695
+
"documentation": "<p>The exit code for the container’s attempt. A non-zero exit code is considered failed.</p>"
696
+
},
697
+
"name": {
698
+
"shape": "String",
699
+
"documentation": "<p>The name of a container.</p>"
700
+
},
701
+
"reason": {
702
+
"shape": "String",
703
+
"documentation": "<p>A short (255 max characters) string that's easy to understand and provides additional details for a running or stopped container.</p>"
704
+
},
705
+
"logStreamName": {
706
+
"shape": "String",
707
+
"documentation": "<p>The name of the Amazon CloudWatch Logs log stream that's associated with the container. The log group for Batch jobs is <code>/aws/batch/job</code>. Each container attempt receives a log stream name when they reach the <code>RUNNING</code> status.</p>"
708
+
},
709
+
"networkInterfaces": {
710
+
"shape": "NetworkInterfaceList",
711
+
"documentation": "<p>The network interfaces that are associated with the job attempt.</p>"
712
+
}
713
+
},
714
+
"documentation": "<p>An object that represents the details of a container that's part of a job attempt.</p>"
715
+
},
668
716
"Boolean": {
669
717
"type": "boolean"
670
718
},
@@ -1893,6 +1941,10 @@
1893
1941
"EksAttemptContainerDetail": {
1894
1942
"type": "structure",
1895
1943
"members": {
1944
+
"name": {
1945
+
"shape": "String",
1946
+
"documentation": "<p>The name of a container.</p>"
1947
+
},
1896
1948
"exitCode": {
1897
1949
"shape": "Integer",
1898
1950
"documentation": "<p>The exit code returned for the job attempt. A non-zero exit code is considered failed.</p>"
@@ -2271,7 +2323,7 @@
2271
2323
},
2272
2324
"imagePullSecrets": {
2273
2325
"shape": "ImagePullSecrets",
2274
-
"documentation": "<p>References a Kubernetes secret resource. This object must start and end with an alphanumeric character, is required to be lowercase, can include periods (.) and hyphens (-), and can't contain more than 253 characters.</p> <p> <code>ImagePullSecret$name</code> is required when this object is used.</p>"
2326
+
"documentation": "<p>References a Kubernetes secret resource. It holds a list of secrets. These secrets help to gain access to pull an images from a private registry.</p> <p> <code>ImagePullSecret$name</code> is required when this object is used.</p>"
2275
2327
},
2276
2328
"containers": {
2277
2329
"shape": "EksContainers",
@@ -2313,7 +2365,7 @@
2313
2365
},
2314
2366
"imagePullSecrets": {
2315
2367
"shape": "ImagePullSecrets",
2316
-
"documentation": "<p>Displays the reference pointer to the Kubernetes secret resource.</p>"
2368
+
"documentation": "<p>Displays the reference pointer to the Kubernetes secret resource. These secrets help to gain access to pull an images from a private registry.</p>"
2317
2369
},
2318
2370
"containers": {
2319
2371
"shape": "EksContainerDetails",
@@ -2558,7 +2610,7 @@
2558
2610
"documentation": "<p>Provides a unique identifier for the <code>ImagePullSecret</code>. This object is required when <code>EksPodProperties$imagePullSecrets</code> is used.</p>"
2559
2611
}
2560
2612
},
2561
-
"documentation": "<p>References a Kubernetes configuration resource that holds a list of secrets. These secrets help to gain access to pull an image from a private registry.</p>"
2613
+
"documentation": "<p>References a Kubernetes secret resource. This name of the secret must start and end with an alphanumeric character, is required to be lowercase, can include periods (.) and hyphens (-), and can't contain more than 253 characters.</p>"
2562
2614
},
2563
2615
"ImagePullSecrets": {
2564
2616
"type": "list",
@@ -2920,15 +2972,15 @@
2920
2972
},
2921
2973
"state": {
2922
2974
"shape": "JobStateTimeLimitActionsState",
2923
-
"documentation": "<p>The state of the job needed to trigger the action. The only supported value is \"<code>RUNNABLE</code>\".</p>"
2975
+
"documentation": "<p>The state of the job needed to trigger the action. The only supported value is <code>RUNNABLE</code>.</p>"
2924
2976
},
2925
2977
"maxTimeSeconds": {
2926
2978
"shape": "Integer",
2927
2979
"documentation": "<p>The approximate amount of time, in seconds, that must pass with the job in the specified state before the action is taken. The minimum value is 600 (10 minutes) and the maximum value is 86,400 (24 hours).</p>"
2928
2980
},
2929
2981
"action": {
2930
2982
"shape": "JobStateTimeLimitActionsAction",
2931
-
"documentation": "<p>The action to take when a job is at the head of the job queue in the specified state for the specified period of time. The only supported value is \"<code>CANCEL</code>\", which will cancel the job.</p>"
2983
+
"documentation": "<p>The action to take when a job is at the head of the job queue in the specified state for the specified period of time. The only supported value is <code>CANCEL</code>, which will cancel the job.</p>"
2932
2984
}
2933
2985
},
2934
2986
"documentation": "<p>Specifies an action that Batch will take after the job has remained at the head of the queue in the specified state for longer than the specified time.</p>"
@@ -3118,6 +3170,18 @@
3118
3170
},
3119
3171
"documentation": "<p>Linux-specific modifications that are applied to the container, such as details for device mappings.</p>"
3120
3172
},
3173
+
"ListAttemptEcsTaskDetails": {
3174
+
"type": "list",
3175
+
"member": {
3176
+
"shape": "AttemptEcsTaskDetails"
3177
+
}
3178
+
},
3179
+
"ListAttemptTaskContainerDetails": {
3180
+
"type": "list",
3181
+
"member": {
3182
+
"shape": "AttemptTaskContainerDetails"
3183
+
}
3184
+
},
3121
3185
"ListEcsTaskDetails": {
3122
3186
"type": "list",
3123
3187
"member": {
@@ -4425,5 +4489,5 @@
4425
4489
}
4426
4490
}
4427
4491
},
4428
-
"documentation": "<fullname>Batch</fullname> <p>Using Batch, you can run batch computing workloads on the Amazon Web Services Cloud. Batch computing is a common means for developers, scientists, and engineers to access large amounts of compute resources. Batch uses the advantages of the batch computing to remove the undifferentiated heavy lifting of configuring and managing required infrastructure. At the same time, it also adopts a familiar batch computing software approach. You can use Batch to efficiently provision resources d, and work toward eliminating capacity constraints, reducing your overall compute costs, and delivering results more quickly.</p> <p>As a fully managed service, Batch can run batch computing workloads of any scale. Batch automatically provisions compute resources and optimizes workload distribution based on the quantity and scale of your specific workloads. With Batch, there's no need to install or manage batch computing software. This means that you can focus on analyzing results and solving your specific problems instead.</p>"
4492
+
"documentation": "<fullname>Batch</fullname> <p>Using Batch, you can run batch computing workloads on the Amazon Web Services Cloud. Batch computing is a common means for developers, scientists, and engineers to access large amounts of compute resources. Batch uses the advantages of the batch computing to remove the undifferentiated heavy lifting of configuring and managing required infrastructure. At the same time, it also adopts a familiar batch computing software approach. You can use Batch to efficiently provision resources, and work toward eliminating capacity constraints, reducing your overall compute costs, and delivering results more quickly.</p> <p>As a fully managed service, Batch can run batch computing workloads of any scale. Batch automatically provisions compute resources and optimizes workload distribution based on the quantity and scale of your specific workloads. With Batch, there's no need to install or manage batch computing software. This means that you can focus on analyzing results and solving your specific problems instead.</p>"
0 commit comments