@aws-sdk/client-securityhub 3.536.0 → 3.547.0
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/dist-cjs/endpoint/endpointResolver.js +4 -2
- package/dist-cjs/index.js +2 -3
- package/dist-es/endpoint/endpointResolver.js +3 -1
- package/dist-es/index.js +0 -1
- package/dist-es/protocols/Aws_restJson1.js +2 -0
- package/dist-types/commands/BatchGetAutomationRulesCommand.d.ts +2 -2
- package/dist-types/commands/BatchImportFindingsCommand.d.ts +1 -0
- package/dist-types/commands/BatchUpdateAutomationRulesCommand.d.ts +2 -2
- package/dist-types/commands/CreateAutomationRuleCommand.d.ts +2 -2
- package/dist-types/commands/CreateInsightCommand.d.ts +5 -5
- package/dist-types/commands/GetFindingsCommand.d.ts +6 -5
- package/dist-types/commands/GetInsightsCommand.d.ts +5 -5
- package/dist-types/commands/UpdateFindingsCommand.d.ts +5 -5
- package/dist-types/commands/UpdateInsightCommand.d.ts +5 -5
- package/dist-types/index.d.ts +0 -1
- package/dist-types/models/models_0.d.ts +984 -120
- package/dist-types/models/models_1.d.ts +927 -113
- package/dist-types/models/models_2.d.ts +495 -56
- package/dist-types/ts3.4/index.d.ts +0 -1
- package/dist-types/ts3.4/models/models_0.d.ts +1 -1
- package/dist-types/ts3.4/models/models_2.d.ts +1 -0
- package/package.json +5 -5
|
@@ -871,9 +871,31 @@ export interface ContainerDetails {
|
|
|
871
871
|
ImageName?: string;
|
|
872
872
|
/**
|
|
873
873
|
* <p>Indicates when the container started.</p>
|
|
874
|
-
* <p>
|
|
875
|
-
*
|
|
876
|
-
*
|
|
874
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
875
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
876
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
877
|
+
* <ul>
|
|
878
|
+
* <li>
|
|
879
|
+
* <p>
|
|
880
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
881
|
+
* </li>
|
|
882
|
+
* <li>
|
|
883
|
+
* <p>
|
|
884
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
885
|
+
* </li>
|
|
886
|
+
* <li>
|
|
887
|
+
* <p>
|
|
888
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
889
|
+
* </li>
|
|
890
|
+
* <li>
|
|
891
|
+
* <p>
|
|
892
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
893
|
+
* </li>
|
|
894
|
+
* <li>
|
|
895
|
+
* <p>
|
|
896
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
897
|
+
* </li>
|
|
898
|
+
* </ul>
|
|
877
899
|
* @public
|
|
878
900
|
*/
|
|
879
901
|
LaunchedAt?: string;
|
|
@@ -1718,9 +1740,31 @@ export interface ThreatIntelIndicator {
|
|
|
1718
1740
|
/**
|
|
1719
1741
|
* <p>Indicates when the most recent instance of a threat intelligence indicator was
|
|
1720
1742
|
* observed.</p>
|
|
1721
|
-
* <p>
|
|
1722
|
-
*
|
|
1723
|
-
*
|
|
1743
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
1744
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
1745
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
1746
|
+
* <ul>
|
|
1747
|
+
* <li>
|
|
1748
|
+
* <p>
|
|
1749
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
1750
|
+
* </li>
|
|
1751
|
+
* <li>
|
|
1752
|
+
* <p>
|
|
1753
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
1754
|
+
* </li>
|
|
1755
|
+
* <li>
|
|
1756
|
+
* <p>
|
|
1757
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
1758
|
+
* </li>
|
|
1759
|
+
* <li>
|
|
1760
|
+
* <p>
|
|
1761
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
1762
|
+
* </li>
|
|
1763
|
+
* <li>
|
|
1764
|
+
* <p>
|
|
1765
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
1766
|
+
* </li>
|
|
1767
|
+
* </ul>
|
|
1724
1768
|
* @public
|
|
1725
1769
|
*/
|
|
1726
1770
|
LastObservedAt?: string;
|
|
@@ -1941,17 +1985,61 @@ export interface VulnerabilityVendor {
|
|
|
1941
1985
|
VendorSeverity?: string;
|
|
1942
1986
|
/**
|
|
1943
1987
|
* <p>Indicates when the vulnerability advisory was created.</p>
|
|
1944
|
-
* <p>
|
|
1945
|
-
*
|
|
1946
|
-
*
|
|
1988
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
1989
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
1990
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
1991
|
+
* <ul>
|
|
1992
|
+
* <li>
|
|
1993
|
+
* <p>
|
|
1994
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
1995
|
+
* </li>
|
|
1996
|
+
* <li>
|
|
1997
|
+
* <p>
|
|
1998
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
1999
|
+
* </li>
|
|
2000
|
+
* <li>
|
|
2001
|
+
* <p>
|
|
2002
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2003
|
+
* </li>
|
|
2004
|
+
* <li>
|
|
2005
|
+
* <p>
|
|
2006
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2007
|
+
* </li>
|
|
2008
|
+
* <li>
|
|
2009
|
+
* <p>
|
|
2010
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2011
|
+
* </li>
|
|
2012
|
+
* </ul>
|
|
1947
2013
|
* @public
|
|
1948
2014
|
*/
|
|
1949
2015
|
VendorCreatedAt?: string;
|
|
1950
2016
|
/**
|
|
1951
2017
|
* <p>Indicates when the vulnerability advisory was last updated.</p>
|
|
1952
|
-
* <p>
|
|
1953
|
-
*
|
|
1954
|
-
*
|
|
2018
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
2019
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
2020
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
2021
|
+
* <ul>
|
|
2022
|
+
* <li>
|
|
2023
|
+
* <p>
|
|
2024
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
2025
|
+
* </li>
|
|
2026
|
+
* <li>
|
|
2027
|
+
* <p>
|
|
2028
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
2029
|
+
* </li>
|
|
2030
|
+
* <li>
|
|
2031
|
+
* <p>
|
|
2032
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2033
|
+
* </li>
|
|
2034
|
+
* <li>
|
|
2035
|
+
* <p>
|
|
2036
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2037
|
+
* </li>
|
|
2038
|
+
* <li>
|
|
2039
|
+
* <p>
|
|
2040
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2041
|
+
* </li>
|
|
2042
|
+
* </ul>
|
|
1955
2043
|
* @public
|
|
1956
2044
|
*/
|
|
1957
2045
|
VendorUpdatedAt?: string;
|
|
@@ -2092,6 +2180,13 @@ export interface Vulnerability {
|
|
|
2092
2180
|
* @public
|
|
2093
2181
|
*/
|
|
2094
2182
|
ExploitAvailable?: VulnerabilityExploitAvailable;
|
|
2183
|
+
/**
|
|
2184
|
+
* <p>
|
|
2185
|
+
* The date and time of the last exploit associated with a finding discovered in your environment.
|
|
2186
|
+
* </p>
|
|
2187
|
+
* @public
|
|
2188
|
+
*/
|
|
2189
|
+
LastKnownExploitAt?: string;
|
|
2095
2190
|
/**
|
|
2096
2191
|
* <p>The vulnerabilities found in your Lambda function code. This field pertains to findings that
|
|
2097
2192
|
* Security Hub receives from Amazon Inspector.
|
|
@@ -2234,35 +2329,123 @@ export interface AwsSecurityFinding {
|
|
|
2234
2329
|
/**
|
|
2235
2330
|
* <p>Indicates when the security findings provider first observed the potential security
|
|
2236
2331
|
* issue that a finding captured.</p>
|
|
2237
|
-
* <p>
|
|
2238
|
-
*
|
|
2239
|
-
*
|
|
2332
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
2333
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
2334
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
2335
|
+
* <ul>
|
|
2336
|
+
* <li>
|
|
2337
|
+
* <p>
|
|
2338
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
2339
|
+
* </li>
|
|
2340
|
+
* <li>
|
|
2341
|
+
* <p>
|
|
2342
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
2343
|
+
* </li>
|
|
2344
|
+
* <li>
|
|
2345
|
+
* <p>
|
|
2346
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2347
|
+
* </li>
|
|
2348
|
+
* <li>
|
|
2349
|
+
* <p>
|
|
2350
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2351
|
+
* </li>
|
|
2352
|
+
* <li>
|
|
2353
|
+
* <p>
|
|
2354
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2355
|
+
* </li>
|
|
2356
|
+
* </ul>
|
|
2240
2357
|
* @public
|
|
2241
2358
|
*/
|
|
2242
2359
|
FirstObservedAt?: string;
|
|
2243
2360
|
/**
|
|
2244
2361
|
* <p>Indicates when the security findings provider most recently observed the potential
|
|
2245
2362
|
* security issue that a finding captured.</p>
|
|
2246
|
-
* <p>
|
|
2247
|
-
*
|
|
2248
|
-
*
|
|
2363
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
2364
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
2365
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
2366
|
+
* <ul>
|
|
2367
|
+
* <li>
|
|
2368
|
+
* <p>
|
|
2369
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
2370
|
+
* </li>
|
|
2371
|
+
* <li>
|
|
2372
|
+
* <p>
|
|
2373
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
2374
|
+
* </li>
|
|
2375
|
+
* <li>
|
|
2376
|
+
* <p>
|
|
2377
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2378
|
+
* </li>
|
|
2379
|
+
* <li>
|
|
2380
|
+
* <p>
|
|
2381
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2382
|
+
* </li>
|
|
2383
|
+
* <li>
|
|
2384
|
+
* <p>
|
|
2385
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2386
|
+
* </li>
|
|
2387
|
+
* </ul>
|
|
2249
2388
|
* @public
|
|
2250
2389
|
*/
|
|
2251
2390
|
LastObservedAt?: string;
|
|
2252
2391
|
/**
|
|
2253
2392
|
* <p>Indicates when the security findings provider created the potential security issue that
|
|
2254
2393
|
* a finding captured.</p>
|
|
2255
|
-
* <p>
|
|
2256
|
-
*
|
|
2257
|
-
*
|
|
2394
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
2395
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
2396
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
2397
|
+
* <ul>
|
|
2398
|
+
* <li>
|
|
2399
|
+
* <p>
|
|
2400
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
2401
|
+
* </li>
|
|
2402
|
+
* <li>
|
|
2403
|
+
* <p>
|
|
2404
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
2405
|
+
* </li>
|
|
2406
|
+
* <li>
|
|
2407
|
+
* <p>
|
|
2408
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2409
|
+
* </li>
|
|
2410
|
+
* <li>
|
|
2411
|
+
* <p>
|
|
2412
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2413
|
+
* </li>
|
|
2414
|
+
* <li>
|
|
2415
|
+
* <p>
|
|
2416
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2417
|
+
* </li>
|
|
2418
|
+
* </ul>
|
|
2258
2419
|
* @public
|
|
2259
2420
|
*/
|
|
2260
2421
|
CreatedAt: string | undefined;
|
|
2261
2422
|
/**
|
|
2262
2423
|
* <p>Indicates when the security findings provider last updated the finding record.</p>
|
|
2263
|
-
* <p>
|
|
2264
|
-
*
|
|
2265
|
-
*
|
|
2424
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
2425
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
2426
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
2427
|
+
* <ul>
|
|
2428
|
+
* <li>
|
|
2429
|
+
* <p>
|
|
2430
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
2431
|
+
* </li>
|
|
2432
|
+
* <li>
|
|
2433
|
+
* <p>
|
|
2434
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
2435
|
+
* </li>
|
|
2436
|
+
* <li>
|
|
2437
|
+
* <p>
|
|
2438
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2439
|
+
* </li>
|
|
2440
|
+
* <li>
|
|
2441
|
+
* <p>
|
|
2442
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2443
|
+
* </li>
|
|
2444
|
+
* <li>
|
|
2445
|
+
* <p>
|
|
2446
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2447
|
+
* </li>
|
|
2448
|
+
* </ul>
|
|
2266
2449
|
* @public
|
|
2267
2450
|
*/
|
|
2268
2451
|
UpdatedAt: string | undefined;
|
|
@@ -2439,8 +2622,32 @@ export interface AwsSecurityFinding {
|
|
|
2439
2622
|
*/
|
|
2440
2623
|
GeneratorDetails?: GeneratorDetails;
|
|
2441
2624
|
/**
|
|
2442
|
-
* <p>
|
|
2443
|
-
* <p>
|
|
2625
|
+
* <p>A imestamp that indicates when Security Hub received a finding and begins to process it.</p>
|
|
2626
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
2627
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
2628
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
2629
|
+
* <ul>
|
|
2630
|
+
* <li>
|
|
2631
|
+
* <p>
|
|
2632
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
2633
|
+
* </li>
|
|
2634
|
+
* <li>
|
|
2635
|
+
* <p>
|
|
2636
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
2637
|
+
* </li>
|
|
2638
|
+
* <li>
|
|
2639
|
+
* <p>
|
|
2640
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2641
|
+
* </li>
|
|
2642
|
+
* <li>
|
|
2643
|
+
* <p>
|
|
2644
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2645
|
+
* </li>
|
|
2646
|
+
* <li>
|
|
2647
|
+
* <p>
|
|
2648
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2649
|
+
* </li>
|
|
2650
|
+
* </ul>
|
|
2444
2651
|
* @public
|
|
2445
2652
|
*/
|
|
2446
2653
|
ProcessedAt?: string;
|
|
@@ -2527,30 +2734,126 @@ export interface AwsSecurityFindingFilters {
|
|
|
2527
2734
|
*/
|
|
2528
2735
|
Type?: StringFilter[];
|
|
2529
2736
|
/**
|
|
2530
|
-
* <p>
|
|
2737
|
+
* <p>A timestamp that indicates when the security findings provider first
|
|
2531
2738
|
* observed the potential security issue that a finding captured.</p>
|
|
2532
|
-
* <p>
|
|
2739
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
2740
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
2741
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
2742
|
+
* <ul>
|
|
2743
|
+
* <li>
|
|
2744
|
+
* <p>
|
|
2745
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
2746
|
+
* </li>
|
|
2747
|
+
* <li>
|
|
2748
|
+
* <p>
|
|
2749
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
2750
|
+
* </li>
|
|
2751
|
+
* <li>
|
|
2752
|
+
* <p>
|
|
2753
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2754
|
+
* </li>
|
|
2755
|
+
* <li>
|
|
2756
|
+
* <p>
|
|
2757
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2758
|
+
* </li>
|
|
2759
|
+
* <li>
|
|
2760
|
+
* <p>
|
|
2761
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2762
|
+
* </li>
|
|
2763
|
+
* </ul>
|
|
2533
2764
|
* @public
|
|
2534
2765
|
*/
|
|
2535
2766
|
FirstObservedAt?: DateFilter[];
|
|
2536
2767
|
/**
|
|
2537
|
-
* <p>
|
|
2768
|
+
* <p>A timestamp that indicates when the security findings provider most
|
|
2538
2769
|
* recently observed the potential security issue that a finding captured.</p>
|
|
2539
|
-
* <p>
|
|
2770
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
2771
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
2772
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
2773
|
+
* <ul>
|
|
2774
|
+
* <li>
|
|
2775
|
+
* <p>
|
|
2776
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
2777
|
+
* </li>
|
|
2778
|
+
* <li>
|
|
2779
|
+
* <p>
|
|
2780
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
2781
|
+
* </li>
|
|
2782
|
+
* <li>
|
|
2783
|
+
* <p>
|
|
2784
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2785
|
+
* </li>
|
|
2786
|
+
* <li>
|
|
2787
|
+
* <p>
|
|
2788
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2789
|
+
* </li>
|
|
2790
|
+
* <li>
|
|
2791
|
+
* <p>
|
|
2792
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2793
|
+
* </li>
|
|
2794
|
+
* </ul>
|
|
2540
2795
|
* @public
|
|
2541
2796
|
*/
|
|
2542
2797
|
LastObservedAt?: DateFilter[];
|
|
2543
2798
|
/**
|
|
2544
|
-
* <p>
|
|
2545
|
-
*
|
|
2546
|
-
* <p>
|
|
2799
|
+
* <p>A timestamp that indicates when the security findings provider
|
|
2800
|
+
* created the potential security issue that a finding reflects.</p>
|
|
2801
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
2802
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
2803
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
2804
|
+
* <ul>
|
|
2805
|
+
* <li>
|
|
2806
|
+
* <p>
|
|
2807
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
2808
|
+
* </li>
|
|
2809
|
+
* <li>
|
|
2810
|
+
* <p>
|
|
2811
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
2812
|
+
* </li>
|
|
2813
|
+
* <li>
|
|
2814
|
+
* <p>
|
|
2815
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2816
|
+
* </li>
|
|
2817
|
+
* <li>
|
|
2818
|
+
* <p>
|
|
2819
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2820
|
+
* </li>
|
|
2821
|
+
* <li>
|
|
2822
|
+
* <p>
|
|
2823
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2824
|
+
* </li>
|
|
2825
|
+
* </ul>
|
|
2547
2826
|
* @public
|
|
2548
2827
|
*/
|
|
2549
2828
|
CreatedAt?: DateFilter[];
|
|
2550
2829
|
/**
|
|
2551
|
-
* <p>
|
|
2552
|
-
* updated the finding record
|
|
2553
|
-
* <p>
|
|
2830
|
+
* <p>A timestamp that indicates when the security findings provider last
|
|
2831
|
+
* updated the finding record.</p>
|
|
2832
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
2833
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
2834
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
2835
|
+
* <ul>
|
|
2836
|
+
* <li>
|
|
2837
|
+
* <p>
|
|
2838
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
2839
|
+
* </li>
|
|
2840
|
+
* <li>
|
|
2841
|
+
* <p>
|
|
2842
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
2843
|
+
* </li>
|
|
2844
|
+
* <li>
|
|
2845
|
+
* <p>
|
|
2846
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2847
|
+
* </li>
|
|
2848
|
+
* <li>
|
|
2849
|
+
* <p>
|
|
2850
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2851
|
+
* </li>
|
|
2852
|
+
* <li>
|
|
2853
|
+
* <p>
|
|
2854
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2855
|
+
* </li>
|
|
2856
|
+
* </ul>
|
|
2554
2857
|
* @public
|
|
2555
2858
|
*/
|
|
2556
2859
|
UpdatedAt?: DateFilter[];
|
|
@@ -2731,13 +3034,61 @@ export interface AwsSecurityFindingFilters {
|
|
|
2731
3034
|
ProcessParentPid?: NumberFilter[];
|
|
2732
3035
|
/**
|
|
2733
3036
|
* <p>A timestamp that identifies when the process was launched.</p>
|
|
2734
|
-
* <p>
|
|
3037
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
3038
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
3039
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
3040
|
+
* <ul>
|
|
3041
|
+
* <li>
|
|
3042
|
+
* <p>
|
|
3043
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
3044
|
+
* </li>
|
|
3045
|
+
* <li>
|
|
3046
|
+
* <p>
|
|
3047
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
3048
|
+
* </li>
|
|
3049
|
+
* <li>
|
|
3050
|
+
* <p>
|
|
3051
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
3052
|
+
* </li>
|
|
3053
|
+
* <li>
|
|
3054
|
+
* <p>
|
|
3055
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
3056
|
+
* </li>
|
|
3057
|
+
* <li>
|
|
3058
|
+
* <p>
|
|
3059
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
3060
|
+
* </li>
|
|
3061
|
+
* </ul>
|
|
2735
3062
|
* @public
|
|
2736
3063
|
*/
|
|
2737
3064
|
ProcessLaunchedAt?: DateFilter[];
|
|
2738
3065
|
/**
|
|
2739
3066
|
* <p>A timestamp that identifies when the process was terminated.</p>
|
|
2740
|
-
* <p>
|
|
3067
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
3068
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
3069
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
3070
|
+
* <ul>
|
|
3071
|
+
* <li>
|
|
3072
|
+
* <p>
|
|
3073
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
3074
|
+
* </li>
|
|
3075
|
+
* <li>
|
|
3076
|
+
* <p>
|
|
3077
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
3078
|
+
* </li>
|
|
3079
|
+
* <li>
|
|
3080
|
+
* <p>
|
|
3081
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
3082
|
+
* </li>
|
|
3083
|
+
* <li>
|
|
3084
|
+
* <p>
|
|
3085
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
3086
|
+
* </li>
|
|
3087
|
+
* <li>
|
|
3088
|
+
* <p>
|
|
3089
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
3090
|
+
* </li>
|
|
3091
|
+
* </ul>
|
|
2741
3092
|
* @public
|
|
2742
3093
|
*/
|
|
2743
3094
|
ProcessTerminatedAt?: DateFilter[];
|
|
@@ -2896,7 +3247,31 @@ export interface AwsSecurityFindingFilters {
|
|
|
2896
3247
|
ResourceContainerImageName?: StringFilter[];
|
|
2897
3248
|
/**
|
|
2898
3249
|
* <p>A timestamp that identifies when the container was started.</p>
|
|
2899
|
-
* <p>
|
|
3250
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
3251
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
3252
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
3253
|
+
* <ul>
|
|
3254
|
+
* <li>
|
|
3255
|
+
* <p>
|
|
3256
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
3257
|
+
* </li>
|
|
3258
|
+
* <li>
|
|
3259
|
+
* <p>
|
|
3260
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
3261
|
+
* </li>
|
|
3262
|
+
* <li>
|
|
3263
|
+
* <p>
|
|
3264
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
3265
|
+
* </li>
|
|
3266
|
+
* <li>
|
|
3267
|
+
* <p>
|
|
3268
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
3269
|
+
* </li>
|
|
3270
|
+
* <li>
|
|
3271
|
+
* <p>
|
|
3272
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
3273
|
+
* </li>
|
|
3274
|
+
* </ul>
|
|
2900
3275
|
* @public
|
|
2901
3276
|
*/
|
|
2902
3277
|
ResourceContainerLaunchedAt?: DateFilter[];
|
|
@@ -6506,12 +6881,33 @@ export interface FindingHistoryRecord {
|
|
|
6506
6881
|
*/
|
|
6507
6882
|
FindingIdentifier?: AwsSecurityFindingIdentifier;
|
|
6508
6883
|
/**
|
|
6509
|
-
* <p>
|
|
6884
|
+
* <p> A timestamp that indicates when Security Hub
|
|
6510
6885
|
* processed the updated finding record.</p>
|
|
6511
|
-
* <p>
|
|
6512
|
-
*
|
|
6513
|
-
*
|
|
6514
|
-
*
|
|
6886
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
6887
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
6888
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
6889
|
+
* <ul>
|
|
6890
|
+
* <li>
|
|
6891
|
+
* <p>
|
|
6892
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
6893
|
+
* </li>
|
|
6894
|
+
* <li>
|
|
6895
|
+
* <p>
|
|
6896
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
6897
|
+
* </li>
|
|
6898
|
+
* <li>
|
|
6899
|
+
* <p>
|
|
6900
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
6901
|
+
* </li>
|
|
6902
|
+
* <li>
|
|
6903
|
+
* <p>
|
|
6904
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
6905
|
+
* </li>
|
|
6906
|
+
* <li>
|
|
6907
|
+
* <p>
|
|
6908
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
6909
|
+
* </li>
|
|
6910
|
+
* </ul>
|
|
6515
6911
|
* @public
|
|
6516
6912
|
*/
|
|
6517
6913
|
UpdateTime?: Date;
|
|
@@ -6818,11 +7214,7 @@ export interface GetFindingHistoryRequest {
|
|
|
6818
7214
|
*/
|
|
6819
7215
|
FindingIdentifier: AwsSecurityFindingIdentifier | undefined;
|
|
6820
7216
|
/**
|
|
6821
|
-
* <p>
|
|
6822
|
-
* An ISO 8601-formatted timestamp that indicates the start time of the requested finding history. A correctly formatted
|
|
6823
|
-
* example is <code>2020-05-21T20:16:34.724Z</code>. The value cannot contain spaces, and date and time should be separated
|
|
6824
|
-
* by <code>T</code>. For more information, see <a href="https://www.rfc-editor.org/rfc/rfc3339#section-5.6">RFC 3339
|
|
6825
|
-
* section 5.6, Internet Date/Time Format</a>.</p>
|
|
7217
|
+
* <p>A timestamp that indicates the start time of the requested finding history.</p>
|
|
6826
7218
|
* <p>If you provide values for both <code>StartTime</code> and <code>EndTime</code>,
|
|
6827
7219
|
* Security Hub returns finding history for the specified time period. If you
|
|
6828
7220
|
* provide a value for <code>StartTime</code> but not for <code>EndTime</code>, Security Hub returns finding history from the <code>StartTime</code> to the time at
|
|
@@ -6831,16 +7223,38 @@ export interface GetFindingHistoryRequest {
|
|
|
6831
7223
|
* provide neither <code>StartTime</code> nor <code>EndTime</code>, Security Hub
|
|
6832
7224
|
* returns finding history from the CreatedAt timestamp of the finding to the time at which
|
|
6833
7225
|
* the API is called. In all of these scenarios, the response is limited to 100 results, and the maximum time period is
|
|
6834
|
-
* limited to 90 days
|
|
7226
|
+
* limited to 90 days.</p>
|
|
7227
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
7228
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
7229
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
7230
|
+
* <ul>
|
|
7231
|
+
* <li>
|
|
7232
|
+
* <p>
|
|
7233
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
7234
|
+
* </li>
|
|
7235
|
+
* <li>
|
|
7236
|
+
* <p>
|
|
7237
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
7238
|
+
* </li>
|
|
7239
|
+
* <li>
|
|
7240
|
+
* <p>
|
|
7241
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
7242
|
+
* </li>
|
|
7243
|
+
* <li>
|
|
7244
|
+
* <p>
|
|
7245
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
7246
|
+
* </li>
|
|
7247
|
+
* <li>
|
|
7248
|
+
* <p>
|
|
7249
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
7250
|
+
* </li>
|
|
7251
|
+
* </ul>
|
|
6835
7252
|
* @public
|
|
6836
7253
|
*/
|
|
6837
7254
|
StartTime?: Date;
|
|
6838
7255
|
/**
|
|
6839
7256
|
* <p>
|
|
6840
|
-
* An ISO 8601-formatted timestamp that indicates the end time of the requested finding history
|
|
6841
|
-
* example is <code>2020-05-21T20:16:34.724Z</code>. The value cannot contain spaces, and date and time should be separated
|
|
6842
|
-
* by <code>T</code>. For more information, see <a href="https://www.rfc-editor.org/rfc/rfc3339#section-5.6">RFC 3339
|
|
6843
|
-
* section 5.6, Internet Date/Time Format</a>.</p>
|
|
7257
|
+
* An ISO 8601-formatted timestamp that indicates the end time of the requested finding history.</p>
|
|
6844
7258
|
* <p>If you provide values for both <code>StartTime</code> and <code>EndTime</code>,
|
|
6845
7259
|
* Security Hub returns finding history for the specified time period. If you
|
|
6846
7260
|
* provide a value for <code>StartTime</code> but not for <code>EndTime</code>, Security Hub returns finding history from the <code>StartTime</code> to the time at
|
|
@@ -6850,6 +7264,31 @@ export interface GetFindingHistoryRequest {
|
|
|
6850
7264
|
* returns finding history from the CreatedAt timestamp of the finding to the time at which
|
|
6851
7265
|
* the API is called. In all of these scenarios, the response is limited to 100 results, and the maximum time period is
|
|
6852
7266
|
* limited to 90 days.</p>
|
|
7267
|
+
* <p>This field accepts only the specified formats. Timestamps
|
|
7268
|
+
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
7269
|
+
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
7270
|
+
* <ul>
|
|
7271
|
+
* <li>
|
|
7272
|
+
* <p>
|
|
7273
|
+
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
7274
|
+
* </li>
|
|
7275
|
+
* <li>
|
|
7276
|
+
* <p>
|
|
7277
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
7278
|
+
* </li>
|
|
7279
|
+
* <li>
|
|
7280
|
+
* <p>
|
|
7281
|
+
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
7282
|
+
* </li>
|
|
7283
|
+
* <li>
|
|
7284
|
+
* <p>
|
|
7285
|
+
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
7286
|
+
* </li>
|
|
7287
|
+
* <li>
|
|
7288
|
+
* <p>
|
|
7289
|
+
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
7290
|
+
* </li>
|
|
7291
|
+
* </ul>
|
|
6853
7292
|
* @public
|
|
6854
7293
|
*/
|
|
6855
7294
|
EndTime?: Date;
|
|
@@ -7071,8 +7510,8 @@ export interface Insight {
|
|
|
7071
7510
|
*/
|
|
7072
7511
|
Name: string | undefined;
|
|
7073
7512
|
/**
|
|
7074
|
-
* <p>One or more attributes used to filter the findings included in the insight.
|
|
7075
|
-
*
|
|
7513
|
+
* <p>One or more attributes used to filter the findings included in the insight. You can filter by up to ten finding attributes. For each attribute, you can provide up to 20 filter values.
|
|
7514
|
+
* The insight only includes findings that match the criteria defined in the filters.</p>
|
|
7076
7515
|
* @public
|
|
7077
7516
|
*/
|
|
7078
7517
|
Filters: AwsSecurityFindingFilters | undefined;
|