@aws-sdk/client-application-signals 3.616.0 → 3.620.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -6,10 +6,6 @@
6
6
 
7
7
  AWS SDK for JavaScript ApplicationSignals Client for Node.js, Browser and React Native.
8
8
 
9
- <important>
10
- <p>This is a Preview release of the Application Signals API Reference. Operations and parameters are subject to change before the general availability
11
- release.</p>
12
- </important>
13
9
  <p>Use CloudWatch Application Signals for comprehensive observability of your cloud-based applications.
14
10
  It enables real-time service health dashboards and helps you track long-term performance trends against your business goals.
15
11
  The application-centric view provides you with unified visibility across your applications, services, and
@@ -27,6 +23,8 @@ ensuring optimal customer experience.</p>
27
23
  <p>See a map of your application topology that Application Signals automatically discovers, that gives you a visual representation of your applications, dependencies, and their connectivity.</p>
28
24
  </li>
29
25
  </ul>
26
+ <p>Application Signals works with CloudWatch RUM, CloudWatch Synthetics canaries, and Amazon Web Services Service Catalog AppRegistry, to display your client pages, Synthetics canaries,
27
+ and application names within dashboards and maps.</p>
30
28
 
31
29
  ## Installing
32
30
 
@@ -292,6 +292,7 @@ const de_GetServiceCommand = async (output, context) => {
292
292
  const data = (0, smithy_client_1.expectNonNull)((0, smithy_client_1.expectObject)(await (0, core_1.parseJsonBody)(output.body, context)), "body");
293
293
  const doc = (0, smithy_client_1.take)(data, {
294
294
  EndTime: (_) => (0, smithy_client_1.expectNonNull)((0, smithy_client_1.parseEpochTimestamp)((0, smithy_client_1.expectNumber)(_))),
295
+ LogGroupReferences: smithy_client_1._json,
295
296
  Service: smithy_client_1._json,
296
297
  StartTime: (_) => (0, smithy_client_1.expectNonNull)((0, smithy_client_1.parseEpochTimestamp)((0, smithy_client_1.expectNumber)(_))),
297
298
  });
@@ -271,6 +271,7 @@ export const de_GetServiceCommand = async (output, context) => {
271
271
  const data = __expectNonNull(__expectObject(await parseBody(output.body, context)), "body");
272
272
  const doc = take(data, {
273
273
  EndTime: (_) => __expectNonNull(__parseEpochTimestamp(__expectNumber(_))),
274
+ LogGroupReferences: _json,
274
275
  Service: _json,
275
276
  StartTime: (_) => __expectNonNull(__parseEpochTimestamp(__expectNumber(_))),
276
277
  });
@@ -110,11 +110,7 @@ export interface ApplicationSignals {
110
110
  updateServiceLevelObjective(args: UpdateServiceLevelObjectiveCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateServiceLevelObjectiveCommandOutput) => void): void;
111
111
  }
112
112
  /**
113
- * <important>
114
- * <p>This is a Preview release of the Application Signals API Reference. Operations and parameters are subject to change before the general availability
115
- * release.</p>
116
- * </important>
117
- * <p>Use CloudWatch Application Signals for comprehensive observability of your cloud-based applications.
113
+ * <p>Use CloudWatch Application Signals for comprehensive observability of your cloud-based applications.
118
114
  * It enables real-time service health dashboards and helps you track long-term performance trends against your business goals.
119
115
  * The application-centric view provides you with unified visibility across your applications, services, and
120
116
  * dependencies, so you can proactively monitor and efficiently triage any issues that may arise,
@@ -131,6 +127,8 @@ export interface ApplicationSignals {
131
127
  * <p>See a map of your application topology that Application Signals automatically discovers, that gives you a visual representation of your applications, dependencies, and their connectivity.</p>
132
128
  * </li>
133
129
  * </ul>
130
+ * <p>Application Signals works with CloudWatch RUM, CloudWatch Synthetics canaries, and Amazon Web Services Service Catalog AppRegistry, to display your client pages, Synthetics canaries,
131
+ * and application names within dashboards and maps.</p>
134
132
  * @public
135
133
  */
136
134
  export declare class ApplicationSignals extends ApplicationSignalsClient implements ApplicationSignals {
@@ -166,11 +166,7 @@ export type ApplicationSignalsClientResolvedConfigType = __SmithyResolvedConfigu
166
166
  export interface ApplicationSignalsClientResolvedConfig extends ApplicationSignalsClientResolvedConfigType {
167
167
  }
168
168
  /**
169
- * <important>
170
- * <p>This is a Preview release of the Application Signals API Reference. Operations and parameters are subject to change before the general availability
171
- * release.</p>
172
- * </important>
173
- * <p>Use CloudWatch Application Signals for comprehensive observability of your cloud-based applications.
169
+ * <p>Use CloudWatch Application Signals for comprehensive observability of your cloud-based applications.
174
170
  * It enables real-time service health dashboards and helps you track long-term performance trends against your business goals.
175
171
  * The application-centric view provides you with unified visibility across your applications, services, and
176
172
  * dependencies, so you can proactively monitor and efficiently triage any issues that may arise,
@@ -187,6 +183,8 @@ export interface ApplicationSignalsClientResolvedConfig extends ApplicationSigna
187
183
  * <p>See a map of your application topology that Application Signals automatically discovers, that gives you a visual representation of your applications, dependencies, and their connectivity.</p>
188
184
  * </li>
189
185
  * </ul>
186
+ * <p>Application Signals works with CloudWatch RUM, CloudWatch Synthetics canaries, and Amazon Web Services Service Catalog AppRegistry, to display your client pages, Synthetics canaries,
187
+ * and application names within dashboards and maps.</p>
190
188
  * @public
191
189
  */
192
190
  export declare class ApplicationSignalsClient extends __Client<__HttpHandlerOptions, ServiceInputTypes, ServiceOutputTypes, ApplicationSignalsClientResolvedConfig> {
@@ -66,9 +66,19 @@ declare const GetServiceCommand_base: {
66
66
  * // MetricName: "STRING_VALUE", // required
67
67
  * // },
68
68
  * // ],
69
+ * // LogGroupReferences: [ // LogGroupReferences
70
+ * // {
71
+ * // "<keys>": "STRING_VALUE",
72
+ * // },
73
+ * // ],
69
74
  * // },
70
75
  * // StartTime: new Date("TIMESTAMP"), // required
71
76
  * // EndTime: new Date("TIMESTAMP"), // required
77
+ * // LogGroupReferences: [
78
+ * // {
79
+ * // "<keys>": "STRING_VALUE",
80
+ * // },
81
+ * // ],
72
82
  * // };
73
83
  *
74
84
  * ```
@@ -1,9 +1,5 @@
1
1
  /**
2
- * <important>
3
- * <p>This is a Preview release of the Application Signals API Reference. Operations and parameters are subject to change before the general availability
4
- * release.</p>
5
- * </important>
6
- * <p>Use CloudWatch Application Signals for comprehensive observability of your cloud-based applications.
2
+ * <p>Use CloudWatch Application Signals for comprehensive observability of your cloud-based applications.
7
3
  * It enables real-time service health dashboards and helps you track long-term performance trends against your business goals.
8
4
  * The application-centric view provides you with unified visibility across your applications, services, and
9
5
  * dependencies, so you can proactively monitor and efficiently triage any issues that may arise,
@@ -20,6 +16,8 @@
20
16
  * <p>See a map of your application topology that Application Signals automatically discovers, that gives you a visual representation of your applications, dependencies, and their connectivity.</p>
21
17
  * </li>
22
18
  * </ul>
19
+ * <p>Application Signals works with CloudWatch RUM, CloudWatch Synthetics canaries, and Amazon Web Services Service Catalog AppRegistry, to display your client pages, Synthetics canaries,
20
+ * and application names within dashboards and maps.</p>
23
21
  *
24
22
  * @packageDocumentation
25
23
  */
@@ -636,6 +636,7 @@ export interface GetServiceInput {
636
636
  * <p>The start of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as
637
637
  * be epoch time in seconds. For example: <code>1698778057</code>
638
638
  * </p>
639
+ * <p>Your requested start time will be rounded to the nearest hour.</p>
639
640
  * @public
640
641
  */
641
642
  StartTime: Date | undefined;
@@ -643,6 +644,7 @@ export interface GetServiceInput {
643
644
  * <p>The end of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as
644
645
  * be epoch time in seconds. For example: <code>1698778057</code>
645
646
  * </p>
647
+ * <p>Your requested start time will be rounded to the nearest hour.</p>
646
648
  * @public
647
649
  */
648
650
  EndTime: Date | undefined;
@@ -828,6 +830,29 @@ export interface Service {
828
830
  * @public
829
831
  */
830
832
  MetricReferences: MetricReference[] | undefined;
833
+ /**
834
+ * <p>An array of string-to-string maps that each contain information about one log group associated with this service. Each
835
+ * string-to-string map includes the following fields:</p>
836
+ * <ul>
837
+ * <li>
838
+ * <p>
839
+ * <code>"Type": "AWS::Resource"</code>
840
+ * </p>
841
+ * </li>
842
+ * <li>
843
+ * <p>
844
+ * <code>"ResourceType": "AWS::Logs::LogGroup"</code>
845
+ * </p>
846
+ * </li>
847
+ * <li>
848
+ * <p>
849
+ * <code>"Identifier": "<i>name-of-log-group</i>"</code>
850
+ * </p>
851
+ * </li>
852
+ * </ul>
853
+ * @public
854
+ */
855
+ LogGroupReferences?: Record<string, string>[];
831
856
  }
832
857
  /**
833
858
  * @public
@@ -841,15 +866,42 @@ export interface GetServiceOutput {
841
866
  /**
842
867
  * <p>The start time of the data included in the response. In a raw HTTP Query API, it is formatted as
843
868
  * be epoch time in seconds. For example: <code>1698778057</code>.</p>
869
+ * <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because
870
+ * it was rounded to the nearest hour.</p>
844
871
  * @public
845
872
  */
846
873
  StartTime: Date | undefined;
847
874
  /**
848
875
  * <p>The end time of the data included in the response. In a raw HTTP Query API, it is formatted as
849
876
  * be epoch time in seconds. For example: <code>1698778057</code>.</p>
877
+ * <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because
878
+ * it was rounded to the nearest hour.</p>
850
879
  * @public
851
880
  */
852
881
  EndTime: Date | undefined;
882
+ /**
883
+ * <p>An array of string-to-string maps that each contain information about one log group associated with this service. Each
884
+ * string-to-string map includes the following fields:</p>
885
+ * <ul>
886
+ * <li>
887
+ * <p>
888
+ * <code>"Type": "AWS::Resource"</code>
889
+ * </p>
890
+ * </li>
891
+ * <li>
892
+ * <p>
893
+ * <code>"ResourceType": "AWS::Logs::LogGroup"</code>
894
+ * </p>
895
+ * </li>
896
+ * <li>
897
+ * <p>
898
+ * <code>"Identifier": "<i>name-of-log-group</i>"</code>
899
+ * </p>
900
+ * </li>
901
+ * </ul>
902
+ * @public
903
+ */
904
+ LogGroupReferences?: Record<string, string>[];
853
905
  }
854
906
  /**
855
907
  * @public
@@ -859,6 +911,7 @@ export interface ListServiceDependenciesInput {
859
911
  * <p>The start of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as
860
912
  * be epoch time in seconds. For example: <code>1698778057</code>
861
913
  * </p>
914
+ * <p>Your requested start time will be rounded to the nearest hour.</p>
862
915
  * @public
863
916
  */
864
917
  StartTime: Date | undefined;
@@ -866,6 +919,7 @@ export interface ListServiceDependenciesInput {
866
919
  * <p>The end of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as
867
920
  * be epoch time in seconds. For example: <code>1698778057</code>
868
921
  * </p>
922
+ * <p>Your requested end time will be rounded to the nearest hour.</p>
869
923
  * @public
870
924
  */
871
925
  EndTime: Date | undefined;
@@ -979,6 +1033,8 @@ export interface ListServiceDependenciesOutput {
979
1033
  * <p>The start of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as
980
1034
  * be epoch time in seconds. For example: <code>1698778057</code>
981
1035
  * </p>
1036
+ * <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because
1037
+ * it was rounded to the nearest hour.</p>
982
1038
  * @public
983
1039
  */
984
1040
  StartTime: Date | undefined;
@@ -986,6 +1042,8 @@ export interface ListServiceDependenciesOutput {
986
1042
  * <p>The end of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as
987
1043
  * be epoch time in seconds. For example: <code>1698778057</code>
988
1044
  * </p>
1045
+ * <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because
1046
+ * it was rounded to the nearest hour.</p>
989
1047
  * @public
990
1048
  */
991
1049
  EndTime: Date | undefined;
@@ -1009,6 +1067,7 @@ export interface ListServiceDependentsInput {
1009
1067
  * <p>The start of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as
1010
1068
  * be epoch time in seconds. For example: <code>1698778057</code>
1011
1069
  * </p>
1070
+ * <p>Your requested start time will be rounded to the nearest hour.</p>
1012
1071
  * @public
1013
1072
  */
1014
1073
  StartTime: Date | undefined;
@@ -1016,6 +1075,7 @@ export interface ListServiceDependentsInput {
1016
1075
  * <p>The end of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as
1017
1076
  * be epoch time in seconds. For example: <code>1698778057</code>
1018
1077
  * </p>
1078
+ * <p>Your requested start time will be rounded to the nearest hour.</p>
1019
1079
  * @public
1020
1080
  */
1021
1081
  EndTime: Date | undefined;
@@ -1131,6 +1191,8 @@ export interface ListServiceDependentsOutput {
1131
1191
  * <p>The start of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as
1132
1192
  * be epoch time in seconds. For example: <code>1698778057</code>
1133
1193
  * </p>
1194
+ * <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because
1195
+ * it was rounded to the nearest hour.</p>
1134
1196
  * @public
1135
1197
  */
1136
1198
  StartTime: Date | undefined;
@@ -1138,6 +1200,8 @@ export interface ListServiceDependentsOutput {
1138
1200
  * <p>The end of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as
1139
1201
  * be epoch time in seconds. For example: <code>1698778057</code>
1140
1202
  * </p>
1203
+ * <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because
1204
+ * it was rounded to the nearest hour.</p>
1141
1205
  * @public
1142
1206
  */
1143
1207
  EndTime: Date | undefined;
@@ -1161,6 +1225,7 @@ export interface ListServiceOperationsInput {
1161
1225
  * <p>The start of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as
1162
1226
  * be epoch time in seconds. For example: <code>1698778057</code>
1163
1227
  * </p>
1228
+ * <p>Your requested start time will be rounded to the nearest hour.</p>
1164
1229
  * @public
1165
1230
  */
1166
1231
  StartTime: Date | undefined;
@@ -1168,6 +1233,7 @@ export interface ListServiceOperationsInput {
1168
1233
  * <p>The end of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as
1169
1234
  * be epoch time in seconds. For example: <code>1698778057</code>
1170
1235
  * </p>
1236
+ * <p>Your requested end time will be rounded to the nearest hour.</p>
1171
1237
  * @public
1172
1238
  */
1173
1239
  EndTime: Date | undefined;
@@ -1246,6 +1312,8 @@ export interface ListServiceOperationsOutput {
1246
1312
  * <p>The start of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as
1247
1313
  * be epoch time in seconds. For example: <code>1698778057</code>
1248
1314
  * </p>
1315
+ * <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because
1316
+ * it was rounded to the nearest hour.</p>
1249
1317
  * @public
1250
1318
  */
1251
1319
  StartTime: Date | undefined;
@@ -1253,6 +1321,8 @@ export interface ListServiceOperationsOutput {
1253
1321
  * <p>The end of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as
1254
1322
  * be epoch time in seconds. For example: <code>1698778057</code>
1255
1323
  * </p>
1324
+ * <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because
1325
+ * it was rounded to the nearest hour.</p>
1256
1326
  * @public
1257
1327
  */
1258
1328
  EndTime: Date | undefined;
@@ -1276,6 +1346,7 @@ export interface ListServicesInput {
1276
1346
  * <p>The start of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as
1277
1347
  * be epoch time in seconds. For example: <code>1698778057</code>
1278
1348
  * </p>
1349
+ * <p>Your requested start time will be rounded to the nearest hour.</p>
1279
1350
  * @public
1280
1351
  */
1281
1352
  StartTime: Date | undefined;
@@ -1283,6 +1354,7 @@ export interface ListServicesInput {
1283
1354
  * <p>The end of the time period to retrieve information about. When used in a raw HTTP Query API, it is formatted as
1284
1355
  * be epoch time in seconds. For example: <code>1698778057</code>
1285
1356
  * </p>
1357
+ * <p>Your requested start time will be rounded to the nearest hour.</p>
1286
1358
  * @public
1287
1359
  */
1288
1360
  EndTime: Date | undefined;
@@ -1430,6 +1502,8 @@ export interface ListServicesOutput {
1430
1502
  * <p>The start of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as
1431
1503
  * be epoch time in seconds. For example: <code>1698778057</code>
1432
1504
  * </p>
1505
+ * <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because
1506
+ * it was rounded to the nearest hour.</p>
1433
1507
  * @public
1434
1508
  */
1435
1509
  StartTime: Date | undefined;
@@ -1437,6 +1511,8 @@ export interface ListServicesOutput {
1437
1511
  * <p>The end of the time period that the returned information applies to. When used in a raw HTTP Query API, it is formatted as
1438
1512
  * be epoch time in seconds. For example: <code>1698778057</code>
1439
1513
  * </p>
1514
+ * <p>This displays the time that Application Signals used for the request. It might not match your request exactly, because
1515
+ * it was rounded to the nearest hour.</p>
1440
1516
  * @public
1441
1517
  */
1442
1518
  EndTime: Date | undefined;
@@ -1511,7 +1587,7 @@ export declare class ResourceNotFoundException extends __BaseException {
1511
1587
  */
1512
1588
  ResourceType: string | undefined;
1513
1589
  /**
1514
- * <p>Cannot find the resource id.</p>
1590
+ * <p>Can't find the resource id.</p>
1515
1591
  * @public
1516
1592
  */
1517
1593
  ResourceId: string | undefined;
@@ -196,11 +196,13 @@ export interface Service {
196
196
  KeyAttributes: Record<string, string> | undefined;
197
197
  AttributeMaps?: Record<string, string>[];
198
198
  MetricReferences: MetricReference[] | undefined;
199
+ LogGroupReferences?: Record<string, string>[];
199
200
  }
200
201
  export interface GetServiceOutput {
201
202
  Service: Service | undefined;
202
203
  StartTime: Date | undefined;
203
204
  EndTime: Date | undefined;
205
+ LogGroupReferences?: Record<string, string>[];
204
206
  }
205
207
  export interface ListServiceDependenciesInput {
206
208
  StartTime: Date | undefined;
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@aws-sdk/client-application-signals",
3
3
  "description": "AWS SDK for JavaScript Application Signals Client for Node.js, Browser and React Native",
4
- "version": "3.616.0",
4
+ "version": "3.620.1",
5
5
  "scripts": {
6
6
  "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
7
7
  "build:cjs": "tsc -p tsconfig.cjs.json",
@@ -20,40 +20,40 @@
20
20
  "dependencies": {
21
21
  "@aws-crypto/sha256-browser": "5.2.0",
22
22
  "@aws-crypto/sha256-js": "5.2.0",
23
- "@aws-sdk/client-sso-oidc": "3.616.0",
24
- "@aws-sdk/client-sts": "3.616.0",
25
- "@aws-sdk/core": "3.616.0",
26
- "@aws-sdk/credential-provider-node": "3.616.0",
27
- "@aws-sdk/middleware-host-header": "3.616.0",
23
+ "@aws-sdk/client-sso-oidc": "3.620.1",
24
+ "@aws-sdk/client-sts": "3.620.1",
25
+ "@aws-sdk/core": "3.620.1",
26
+ "@aws-sdk/credential-provider-node": "3.620.1",
27
+ "@aws-sdk/middleware-host-header": "3.620.0",
28
28
  "@aws-sdk/middleware-logger": "3.609.0",
29
- "@aws-sdk/middleware-recursion-detection": "3.616.0",
30
- "@aws-sdk/middleware-user-agent": "3.616.0",
29
+ "@aws-sdk/middleware-recursion-detection": "3.620.0",
30
+ "@aws-sdk/middleware-user-agent": "3.620.0",
31
31
  "@aws-sdk/region-config-resolver": "3.614.0",
32
32
  "@aws-sdk/types": "3.609.0",
33
33
  "@aws-sdk/util-endpoints": "3.614.0",
34
34
  "@aws-sdk/util-user-agent-browser": "3.609.0",
35
35
  "@aws-sdk/util-user-agent-node": "3.614.0",
36
36
  "@smithy/config-resolver": "^3.0.5",
37
- "@smithy/core": "^2.2.7",
38
- "@smithy/fetch-http-handler": "^3.2.2",
37
+ "@smithy/core": "^2.3.0",
38
+ "@smithy/fetch-http-handler": "^3.2.3",
39
39
  "@smithy/hash-node": "^3.0.3",
40
40
  "@smithy/invalid-dependency": "^3.0.3",
41
- "@smithy/middleware-content-length": "^3.0.4",
42
- "@smithy/middleware-endpoint": "^3.0.5",
43
- "@smithy/middleware-retry": "^3.0.10",
41
+ "@smithy/middleware-content-length": "^3.0.5",
42
+ "@smithy/middleware-endpoint": "^3.1.0",
43
+ "@smithy/middleware-retry": "^3.0.12",
44
44
  "@smithy/middleware-serde": "^3.0.3",
45
45
  "@smithy/middleware-stack": "^3.0.3",
46
46
  "@smithy/node-config-provider": "^3.1.4",
47
- "@smithy/node-http-handler": "^3.1.3",
48
- "@smithy/protocol-http": "^4.0.4",
49
- "@smithy/smithy-client": "^3.1.8",
47
+ "@smithy/node-http-handler": "^3.1.4",
48
+ "@smithy/protocol-http": "^4.1.0",
49
+ "@smithy/smithy-client": "^3.1.10",
50
50
  "@smithy/types": "^3.3.0",
51
51
  "@smithy/url-parser": "^3.0.3",
52
52
  "@smithy/util-base64": "^3.0.0",
53
53
  "@smithy/util-body-length-browser": "^3.0.0",
54
54
  "@smithy/util-body-length-node": "^3.0.0",
55
- "@smithy/util-defaults-mode-browser": "^3.0.10",
56
- "@smithy/util-defaults-mode-node": "^3.0.10",
55
+ "@smithy/util-defaults-mode-browser": "^3.0.12",
56
+ "@smithy/util-defaults-mode-node": "^3.0.12",
57
57
  "@smithy/util-endpoints": "^2.0.5",
58
58
  "@smithy/util-middleware": "^3.0.3",
59
59
  "@smithy/util-retry": "^3.0.3",