cdk-lambda-subminute 2.0.278 → 2.0.280

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.
Files changed (37) hide show
  1. package/.gitattributes +0 -1
  2. package/.jsii +3 -3
  3. package/lib/cdk-lambda-subminute.js +3 -3
  4. package/node_modules/aws-sdk/CHANGELOG.md +17 -1
  5. package/node_modules/aws-sdk/README.md +1 -1
  6. package/node_modules/aws-sdk/apis/appstream-2016-12-01.min.json +28 -5
  7. package/node_modules/aws-sdk/apis/ec2-2016-11-15.min.json +115 -56
  8. package/node_modules/aws-sdk/apis/ec2-2016-11-15.paginators.json +6 -0
  9. package/node_modules/aws-sdk/apis/groundstation-2019-05-23.min.json +26 -25
  10. package/node_modules/aws-sdk/apis/network-firewall-2020-11-12.min.json +30 -16
  11. package/node_modules/aws-sdk/apis/opensearch-2021-01-01.min.json +184 -167
  12. package/node_modules/aws-sdk/apis/redshift-2012-12-01.min.json +168 -58
  13. package/node_modules/aws-sdk/apis/redshift-2012-12-01.paginators.json +6 -0
  14. package/node_modules/aws-sdk/apis/sagemaker-2017-07-24.min.json +877 -862
  15. package/node_modules/aws-sdk/apis/ssm-sap-2018-05-10.min.json +62 -27
  16. package/node_modules/aws-sdk/apis/transfer-2018-11-05.min.json +53 -53
  17. package/node_modules/aws-sdk/apis/transfer-2018-11-05.paginators.json +12 -24
  18. package/node_modules/aws-sdk/apis/transfer-2018-11-05.waiters2.json +33 -41
  19. package/node_modules/aws-sdk/clients/appstream.d.ts +46 -6
  20. package/node_modules/aws-sdk/clients/connectcases.d.ts +5 -5
  21. package/node_modules/aws-sdk/clients/ec2.d.ts +68 -0
  22. package/node_modules/aws-sdk/clients/groundstation.d.ts +5 -0
  23. package/node_modules/aws-sdk/clients/iam.d.ts +4 -4
  24. package/node_modules/aws-sdk/clients/networkfirewall.d.ts +31 -11
  25. package/node_modules/aws-sdk/clients/opensearch.d.ts +47 -22
  26. package/node_modules/aws-sdk/clients/redshift.d.ts +143 -0
  27. package/node_modules/aws-sdk/clients/sagemaker.d.ts +36 -14
  28. package/node_modules/aws-sdk/clients/sns.d.ts +4 -4
  29. package/node_modules/aws-sdk/clients/ssmsap.d.ts +75 -4
  30. package/node_modules/aws-sdk/clients/transfer.d.ts +3 -3
  31. package/node_modules/aws-sdk/dist/aws-sdk-core-react-native.js +1 -1
  32. package/node_modules/aws-sdk/dist/aws-sdk-react-native.js +14 -14
  33. package/node_modules/aws-sdk/dist/aws-sdk.js +298 -117
  34. package/node_modules/aws-sdk/dist/aws-sdk.min.js +68 -68
  35. package/node_modules/aws-sdk/lib/core.js +1 -1
  36. package/node_modules/aws-sdk/package.json +1 -1
  37. package/package.json +3 -4
@@ -1,45 +1,37 @@
1
1
  {
2
- "version": 2,
3
- "waiters": {
4
- "ServerOffline": {
5
- "acceptors": [
6
- {
7
- "argument": "Server.State",
8
- "expected": "OFFLINE",
9
- "matcher": "path",
10
- "state": "success"
11
- },
12
- {
13
- "argument": "Server.State",
14
- "expected": "STOP_FAILED",
15
- "matcher": "path",
16
- "state": "failure"
17
- }
18
- ],
19
- "delay": 30,
20
- "maxAttempts": 120,
21
- "operation": "DescribeServer",
22
- "type": "api"
2
+ "version" : 2,
3
+ "waiters" : {
4
+ "ServerOffline" : {
5
+ "delay" : 30,
6
+ "maxAttempts" : 120,
7
+ "operation" : "DescribeServer",
8
+ "acceptors" : [ {
9
+ "matcher" : "path",
10
+ "argument" : "Server.State",
11
+ "state" : "success",
12
+ "expected" : "OFFLINE"
13
+ }, {
14
+ "matcher" : "path",
15
+ "argument" : "Server.State",
16
+ "state" : "failure",
17
+ "expected" : "STOP_FAILED"
18
+ } ]
23
19
  },
24
- "ServerOnline": {
25
- "acceptors": [
26
- {
27
- "argument": "Server.State",
28
- "expected": "ONLINE",
29
- "matcher": "path",
30
- "state": "success"
31
- },
32
- {
33
- "argument": "Server.State",
34
- "expected": "START_FAILED",
35
- "matcher": "path",
36
- "state": "failure"
37
- }
38
- ],
39
- "delay": 30,
40
- "maxAttempts": 120,
41
- "operation": "DescribeServer",
42
- "type": "api"
20
+ "ServerOnline" : {
21
+ "delay" : 30,
22
+ "maxAttempts" : 120,
23
+ "operation" : "DescribeServer",
24
+ "acceptors" : [ {
25
+ "matcher" : "path",
26
+ "argument" : "Server.State",
27
+ "state" : "success",
28
+ "expected" : "ONLINE"
29
+ }, {
30
+ "matcher" : "path",
31
+ "argument" : "Server.State",
32
+ "state" : "failure",
33
+ "expected" : "START_FAILED"
34
+ } ]
43
35
  }
44
36
  }
45
- }
37
+ }
@@ -986,7 +986,11 @@ declare namespace AppStream {
986
986
  /**
987
987
  * The desired number of streaming instances.
988
988
  */
989
- DesiredInstances: Integer;
989
+ DesiredInstances?: Integer;
990
+ /**
991
+ * The desired number of user sessions for a multi-session fleet. This is not allowed for single-session fleets. When you create a fleet, you must set either the DesiredSessions or DesiredInstances attribute, based on the type of fleet you create. You can’t define both attributes or leave both attributes blank.
992
+ */
993
+ DesiredSessions?: Integer;
990
994
  }
991
995
  export interface ComputeCapacityStatus {
992
996
  /**
@@ -1005,6 +1009,22 @@ declare namespace AppStream {
1005
1009
  * The number of currently available instances that can be used to stream sessions.
1006
1010
  */
1007
1011
  Available?: Integer;
1012
+ /**
1013
+ * The total number of sessions slots that are either running or pending. This represents the total number of concurrent streaming sessions your fleet can support in a steady state. DesiredUserSessionCapacity = ActualUserSessionCapacity + PendingUserSessionCapacity This only applies to multi-session fleets.
1014
+ */
1015
+ DesiredUserSessions?: Integer;
1016
+ /**
1017
+ * The number of idle session slots currently available for user sessions. AvailableUserSessionCapacity = ActualUserSessionCapacity - ActiveUserSessions This only applies to multi-session fleets.
1018
+ */
1019
+ AvailableUserSessions?: Integer;
1020
+ /**
1021
+ * The number of user sessions currently being used for streaming sessions. This only applies to multi-session fleets.
1022
+ */
1023
+ ActiveUserSessions?: Integer;
1024
+ /**
1025
+ * The total number of session slots that are available for streaming or are currently streaming. ActualUserSessionCapacity = AvailableUserSessionCapacity + ActiveUserSessions This only applies to multi-session fleets.
1026
+ */
1027
+ ActualUserSessions?: Integer;
1008
1028
  }
1009
1029
  export interface CopyImageRequest {
1010
1030
  /**
@@ -1266,7 +1286,7 @@ declare namespace AppStream {
1266
1286
  */
1267
1287
  VpcConfig?: VpcConfig;
1268
1288
  /**
1269
- * The maximum amount of time that a streaming session can remain active, in seconds. If users are still connected to a streaming instance five minutes before this limit is reached, they are prompted to save any open documents before being disconnected. After this time elapses, the instance is terminated and replaced by a new instance. Specify a value between 600 and 360000.
1289
+ * The maximum amount of time that a streaming session can remain active, in seconds. If users are still connected to a streaming instance five minutes before this limit is reached, they are prompted to save any open documents before being disconnected. After this time elapses, the instance is terminated and replaced by a new instance. Specify a value between 600 and 432000.
1270
1290
  */
1271
1291
  MaxUserDurationInSeconds?: Integer;
1272
1292
  /**
@@ -1321,6 +1341,10 @@ declare namespace AppStream {
1321
1341
  * The S3 location of the session scripts configuration zip file. This only applies to Elastic fleets.
1322
1342
  */
1323
1343
  SessionScriptS3Location?: S3Location;
1344
+ /**
1345
+ * The maximum number of user sessions on an instance. This only applies to multi-session fleets.
1346
+ */
1347
+ MaxSessionsPerInstance?: Integer;
1324
1348
  }
1325
1349
  export interface CreateFleetResult {
1326
1350
  /**
@@ -1974,11 +1998,11 @@ declare namespace AppStream {
1974
1998
  /**
1975
1999
  * The name of the stack. This value is case-sensitive.
1976
2000
  */
1977
- StackName: String;
2001
+ StackName: Name;
1978
2002
  /**
1979
2003
  * The name of the fleet. This value is case-sensitive.
1980
2004
  */
1981
- FleetName: String;
2005
+ FleetName: Name;
1982
2006
  /**
1983
2007
  * The user identifier (ID). If you specify a user ID, you must also specify the authentication type.
1984
2008
  */
@@ -1995,6 +2019,10 @@ declare namespace AppStream {
1995
2019
  * The authentication method. Specify API for a user authenticated using a streaming URL or SAML for a SAML federated user. The default is to authenticate users using a streaming URL.
1996
2020
  */
1997
2021
  AuthenticationType?: AuthenticationType;
2022
+ /**
2023
+ * The identifier for the instance hosting the session.
2024
+ */
2025
+ InstanceId?: String;
1998
2026
  }
1999
2027
  export interface DescribeSessionsResult {
2000
2028
  /**
@@ -2385,8 +2413,12 @@ declare namespace AppStream {
2385
2413
  * The S3 location of the session scripts configuration zip file. This only applies to Elastic fleets.
2386
2414
  */
2387
2415
  SessionScriptS3Location?: S3Location;
2416
+ /**
2417
+ * The maximum number of user sessions on an instance. This only applies to multi-session fleets.
2418
+ */
2419
+ MaxSessionsPerInstance?: Integer;
2388
2420
  }
2389
- export type FleetAttribute = "VPC_CONFIGURATION"|"VPC_CONFIGURATION_SECURITY_GROUP_IDS"|"DOMAIN_JOIN_INFO"|"IAM_ROLE_ARN"|"USB_DEVICE_FILTER_STRINGS"|"SESSION_SCRIPT_S3_LOCATION"|string;
2421
+ export type FleetAttribute = "VPC_CONFIGURATION"|"VPC_CONFIGURATION_SECURITY_GROUP_IDS"|"DOMAIN_JOIN_INFO"|"IAM_ROLE_ARN"|"USB_DEVICE_FILTER_STRINGS"|"SESSION_SCRIPT_S3_LOCATION"|"MAX_SESSIONS_PER_INSTANCE"|string;
2390
2422
  export type FleetAttributes = FleetAttribute[];
2391
2423
  export interface FleetError {
2392
2424
  /**
@@ -2794,6 +2826,10 @@ declare namespace AppStream {
2794
2826
  * The network details for the streaming session.
2795
2827
  */
2796
2828
  NetworkAccessConfiguration?: NetworkAccessConfiguration;
2829
+ /**
2830
+ * The identifier for the instance hosting the session.
2831
+ */
2832
+ InstanceId?: String;
2797
2833
  }
2798
2834
  export type SessionConnectionState = "CONNECTED"|"NOT_CONNECTED"|string;
2799
2835
  export type SessionList = Session[];
@@ -3151,7 +3187,7 @@ declare namespace AppStream {
3151
3187
  /**
3152
3188
  * A unique name for the fleet.
3153
3189
  */
3154
- Name?: String;
3190
+ Name?: Name;
3155
3191
  /**
3156
3192
  * The instance type to use when launching fleet instances. The following instance types are available: stream.standard.small stream.standard.medium stream.standard.large stream.standard.xlarge stream.standard.2xlarge stream.compute.large stream.compute.xlarge stream.compute.2xlarge stream.compute.4xlarge stream.compute.8xlarge stream.memory.large stream.memory.xlarge stream.memory.2xlarge stream.memory.4xlarge stream.memory.8xlarge stream.memory.z1d.large stream.memory.z1d.xlarge stream.memory.z1d.2xlarge stream.memory.z1d.3xlarge stream.memory.z1d.6xlarge stream.memory.z1d.12xlarge stream.graphics-design.large stream.graphics-design.xlarge stream.graphics-design.2xlarge stream.graphics-design.4xlarge stream.graphics-desktop.2xlarge stream.graphics.g4dn.xlarge stream.graphics.g4dn.2xlarge stream.graphics.g4dn.4xlarge stream.graphics.g4dn.8xlarge stream.graphics.g4dn.12xlarge stream.graphics.g4dn.16xlarge stream.graphics-pro.4xlarge stream.graphics-pro.8xlarge stream.graphics-pro.16xlarge The following instance types are available for Elastic fleets: stream.standard.small stream.standard.medium stream.standard.large stream.standard.xlarge stream.standard.2xlarge
3157
3193
  */
@@ -3224,6 +3260,10 @@ declare namespace AppStream {
3224
3260
  * The S3 location of the session scripts configuration zip file. This only applies to Elastic fleets.
3225
3261
  */
3226
3262
  SessionScriptS3Location?: S3Location;
3263
+ /**
3264
+ * The maximum number of user sessions on an instance. This only applies to multi-session fleets.
3265
+ */
3266
+ MaxSessionsPerInstance?: Integer;
3227
3267
  }
3228
3268
  export interface UpdateFleetResult {
3229
3269
  /**
@@ -28,11 +28,11 @@ declare class ConnectCases extends Service {
28
28
  */
29
29
  batchPutFieldOptions(callback?: (err: AWSError, data: ConnectCases.Types.BatchPutFieldOptionsResponse) => void): Request<ConnectCases.Types.BatchPutFieldOptionsResponse, AWSError>;
30
30
  /**
31
- * Creates a case in the specified Cases domain. Case system and custom fields are taken as an array id/value pairs with a declared data types. The following fields are required when creating a case: &lt;ul&gt; &lt;li&gt; &lt;p&gt; &lt;code&gt;customer_id&lt;/code&gt; - You must provide the full customer profile ARN in this format: &lt;code&gt;arn:aws:profile:your AWS Region:your AWS account ID:domains/profiles domain name/profiles/profile ID&lt;/code&gt; &lt;/p&gt; &lt;/li&gt; &lt;li&gt; &lt;p&gt; &lt;code&gt;title&lt;/code&gt; &lt;/p&gt; &lt;/li&gt; &lt;/ul&gt; &lt;/note&gt;
31
+ * Creates a case in the specified Cases domain. Case system and custom fields are taken as an array id/value pairs with a declared data types. The following fields are required when creating a case: &lt;ul&gt; &lt;li&gt; &lt;p&gt; &lt;code&gt;customer_id&lt;/code&gt; - You must provide the full customer profile ARN in this format: &lt;code&gt;arn:aws:profile:your_AWS_Region:your_AWS_account ID:domains/your_profiles_domain_name/profiles/profile_ID&lt;/code&gt; &lt;/p&gt; &lt;/li&gt; &lt;li&gt; &lt;p&gt; &lt;code&gt;title&lt;/code&gt; &lt;/p&gt; &lt;/li&gt; &lt;/ul&gt;
32
32
  */
33
33
  createCase(params: ConnectCases.Types.CreateCaseRequest, callback?: (err: AWSError, data: ConnectCases.Types.CreateCaseResponse) => void): Request<ConnectCases.Types.CreateCaseResponse, AWSError>;
34
34
  /**
35
- * Creates a case in the specified Cases domain. Case system and custom fields are taken as an array id/value pairs with a declared data types. The following fields are required when creating a case: &lt;ul&gt; &lt;li&gt; &lt;p&gt; &lt;code&gt;customer_id&lt;/code&gt; - You must provide the full customer profile ARN in this format: &lt;code&gt;arn:aws:profile:your AWS Region:your AWS account ID:domains/profiles domain name/profiles/profile ID&lt;/code&gt; &lt;/p&gt; &lt;/li&gt; &lt;li&gt; &lt;p&gt; &lt;code&gt;title&lt;/code&gt; &lt;/p&gt; &lt;/li&gt; &lt;/ul&gt; &lt;/note&gt;
35
+ * Creates a case in the specified Cases domain. Case system and custom fields are taken as an array id/value pairs with a declared data types. The following fields are required when creating a case: &lt;ul&gt; &lt;li&gt; &lt;p&gt; &lt;code&gt;customer_id&lt;/code&gt; - You must provide the full customer profile ARN in this format: &lt;code&gt;arn:aws:profile:your_AWS_Region:your_AWS_account ID:domains/your_profiles_domain_name/profiles/profile_ID&lt;/code&gt; &lt;/p&gt; &lt;/li&gt; &lt;li&gt; &lt;p&gt; &lt;code&gt;title&lt;/code&gt; &lt;/p&gt; &lt;/li&gt; &lt;/ul&gt;
36
36
  */
37
37
  createCase(callback?: (err: AWSError, data: ConnectCases.Types.CreateCaseResponse) => void): Request<ConnectCases.Types.CreateCaseResponse, AWSError>;
38
38
  /**
@@ -180,11 +180,11 @@ declare class ConnectCases extends Service {
180
180
  */
181
181
  listTemplates(callback?: (err: AWSError, data: ConnectCases.Types.ListTemplatesResponse) => void): Request<ConnectCases.Types.ListTemplatesResponse, AWSError>;
182
182
  /**
183
- * API for adding case event publishing configuration
183
+ * Adds case event publishing configuration. For a complete list of fields you can add to the event message, see Create case fields in the Amazon Connect Administrator Guide
184
184
  */
185
185
  putCaseEventConfiguration(params: ConnectCases.Types.PutCaseEventConfigurationRequest, callback?: (err: AWSError, data: ConnectCases.Types.PutCaseEventConfigurationResponse) => void): Request<ConnectCases.Types.PutCaseEventConfigurationResponse, AWSError>;
186
186
  /**
187
- * API for adding case event publishing configuration
187
+ * Adds case event publishing configuration. For a complete list of fields you can add to the event message, see Create case fields in the Amazon Connect Administrator Guide
188
188
  */
189
189
  putCaseEventConfiguration(callback?: (err: AWSError, data: ConnectCases.Types.PutCaseEventConfigurationResponse) => void): Request<ConnectCases.Types.PutCaseEventConfigurationResponse, AWSError>;
190
190
  /**
@@ -1444,7 +1444,7 @@ declare namespace ConnectCases {
1444
1444
  }
1445
1445
  export interface UpdateLayoutRequest {
1446
1446
  /**
1447
- * Information about which fields will be present in the layout, the order of the fields, and a read-only attribute of the field.
1447
+ * Information about which fields will be present in the layout, the order of the fields.
1448
1448
  */
1449
1449
  content?: LayoutContent;
1450
1450
  /**
@@ -3572,6 +3572,14 @@ declare class EC2 extends Service {
3572
3572
  * Returns a quote and exchange information for exchanging one or more specified Convertible Reserved Instances for a new Convertible Reserved Instance. If the exchange cannot be performed, the reason is returned in the response. Use AcceptReservedInstancesExchangeQuote to perform the exchange.
3573
3573
  */
3574
3574
  getReservedInstancesExchangeQuote(callback?: (err: AWSError, data: EC2.Types.GetReservedInstancesExchangeQuoteResult) => void): Request<EC2.Types.GetReservedInstancesExchangeQuoteResult, AWSError>;
3575
+ /**
3576
+ * Gets security groups that can be associated by the Amazon Web Services account making the request with network interfaces in the specified VPC.
3577
+ */
3578
+ getSecurityGroupsForVpc(params: EC2.Types.GetSecurityGroupsForVpcRequest, callback?: (err: AWSError, data: EC2.Types.GetSecurityGroupsForVpcResult) => void): Request<EC2.Types.GetSecurityGroupsForVpcResult, AWSError>;
3579
+ /**
3580
+ * Gets security groups that can be associated by the Amazon Web Services account making the request with network interfaces in the specified VPC.
3581
+ */
3582
+ getSecurityGroupsForVpc(callback?: (err: AWSError, data: EC2.Types.GetSecurityGroupsForVpcResult) => void): Request<EC2.Types.GetSecurityGroupsForVpcResult, AWSError>;
3575
3583
  /**
3576
3584
  * Retrieves the access status of your account to the EC2 serial console of all instances. By default, access to the EC2 serial console is disabled for your account. For more information, see Manage account access to the EC2 serial console in the Amazon EC2 User Guide.
3577
3585
  */
@@ -21454,6 +21462,39 @@ declare namespace EC2 {
21454
21462
  */
21455
21463
  ValidationFailureReason?: String;
21456
21464
  }
21465
+ export interface GetSecurityGroupsForVpcRequest {
21466
+ /**
21467
+ * The VPC ID where the security group can be used.
21468
+ */
21469
+ VpcId: VpcId;
21470
+ /**
21471
+ * The token returned from a previous paginated request. Pagination continues from the end of the items returned by the previous request.
21472
+ */
21473
+ NextToken?: String;
21474
+ /**
21475
+ * The maximum number of items to return for this request. To get the next page of items, make another request with the token returned in the output. For more information, see Pagination.
21476
+ */
21477
+ MaxResults?: GetSecurityGroupsForVpcRequestMaxResults;
21478
+ /**
21479
+ * The filters. If using multiple filters, the results include security groups which match all filters. group-id: The security group ID. description: The security group's description. group-name: The security group name. owner-id: The security group owner ID. primary-vpc-id: The VPC ID in which the security group was created.
21480
+ */
21481
+ Filters?: FilterList;
21482
+ /**
21483
+ * Checks whether you have the required permissions for the action, without actually making the request, and provides an error response. If you have the required permissions, the error response is DryRunOperation. Otherwise, it is UnauthorizedOperation.
21484
+ */
21485
+ DryRun?: Boolean;
21486
+ }
21487
+ export type GetSecurityGroupsForVpcRequestMaxResults = number;
21488
+ export interface GetSecurityGroupsForVpcResult {
21489
+ /**
21490
+ * The token to include in another request to get the next page of items. This value is null when there are no more items to return.
21491
+ */
21492
+ NextToken?: String;
21493
+ /**
21494
+ * The security group that can be used by interfaces in the VPC.
21495
+ */
21496
+ SecurityGroupForVpcs?: SecurityGroupForVpcList;
21497
+ }
21457
21498
  export interface GetSerialConsoleAccessStatusRequest {
21458
21499
  /**
21459
21500
  * Checks whether you have the required permissions for the action, without actually making the request, and provides an error response. If you have the required permissions, the error response is DryRunOperation. Otherwise, it is UnauthorizedOperation.
@@ -33758,6 +33799,33 @@ declare namespace EC2 {
33758
33799
  */
33759
33800
  VpcId?: String;
33760
33801
  }
33802
+ export interface SecurityGroupForVpc {
33803
+ /**
33804
+ * The security group's description.
33805
+ */
33806
+ Description?: String;
33807
+ /**
33808
+ * The security group name.
33809
+ */
33810
+ GroupName?: String;
33811
+ /**
33812
+ * The security group owner ID.
33813
+ */
33814
+ OwnerId?: String;
33815
+ /**
33816
+ * The security group ID.
33817
+ */
33818
+ GroupId?: String;
33819
+ /**
33820
+ * The security group tags.
33821
+ */
33822
+ Tags?: TagList;
33823
+ /**
33824
+ * The VPC ID in which the security group was created.
33825
+ */
33826
+ PrimaryVpcId?: String;
33827
+ }
33828
+ export type SecurityGroupForVpcList = SecurityGroupForVpc[];
33761
33829
  export type SecurityGroupId = string;
33762
33830
  export type SecurityGroupIdList = SecurityGroupId[];
33763
33831
  export type SecurityGroupIdSet = SecurityGroupId[];
@@ -1324,12 +1324,17 @@ declare namespace GroundStation {
1324
1324
  export type IpV4Address = string;
1325
1325
  export type JsonString = string;
1326
1326
  export type KeyAliasArn = string;
1327
+ export type KeyAliasName = string;
1327
1328
  export type KeyArn = string;
1328
1329
  export interface KmsKey {
1329
1330
  /**
1330
1331
  * KMS Alias Arn.
1331
1332
  */
1332
1333
  kmsAliasArn?: KeyAliasArn;
1334
+ /**
1335
+ * KMS Alias Name.
1336
+ */
1337
+ kmsAliasName?: KeyAliasName;
1333
1338
  /**
1334
1339
  * KMS Key Arn.
1335
1340
  */
@@ -413,11 +413,11 @@ declare class IAM extends Service {
413
413
  */
414
414
  generateOrganizationsAccessReport(callback?: (err: AWSError, data: IAM.Types.GenerateOrganizationsAccessReportResponse) => void): Request<IAM.Types.GenerateOrganizationsAccessReportResponse, AWSError>;
415
415
  /**
416
- * Generates a report that includes details about when an IAM resource (user, group, role, or policy) was last used in an attempt to access Amazon Web Services services. Recent activity usually appears within four hours. IAM reports activity for at least the last 400 days, or less if your Region began supporting this feature within the last year. For more information, see Regions where data is tracked. The service last accessed data includes all attempts to access an Amazon Web Services API, not just the successful ones. This includes all attempts that were made using the Amazon Web Services Management Console, the Amazon Web Services API through any of the SDKs, or any of the command line tools. An unexpected entry in the service last accessed data does not mean that your account has been compromised, because the request might have been denied. Refer to your CloudTrail logs as the authoritative source for information about all API calls and whether they were successful or denied access. For more information, see Logging IAM events with CloudTrail in the IAM User Guide. The GenerateServiceLastAccessedDetails operation returns a JobId. Use this parameter in the following operations to retrieve the following details from your report: GetServiceLastAccessedDetails – Use this operation for users, groups, roles, or policies to list every Amazon Web Services service that the resource could access using permissions policies. For each service, the response includes information about the most recent access attempt. The JobId returned by GenerateServiceLastAccessedDetail must be used by the same role within a session, or by the same user when used to call GetServiceLastAccessedDetail. GetServiceLastAccessedDetailsWithEntities – Use this operation for groups and policies to list information about the associated entities (users or roles) that attempted to access a specific Amazon Web Services service. To check the status of the GenerateServiceLastAccessedDetails request, use the JobId parameter in the same operations and test the JobStatus response parameter. For additional information about the permissions policies that allow an identity (user, group, or role) to access specific services, use the ListPoliciesGrantingServiceAccess operation. Service last accessed data does not use other policy types when determining whether a resource could access a service. These other policy types include resource-based policies, access control lists, Organizations policies, IAM permissions boundaries, and STS assume role policies. It only applies permissions policy logic. For more about the evaluation of policy types, see Evaluating policies in the IAM User Guide. For more information about service and action last accessed data, see Reducing permissions using service last accessed data in the IAM User Guide.
416
+ * Generates a report that includes details about when an IAM resource (user, group, role, or policy) was last used in an attempt to access Amazon Web Services services. Recent activity usually appears within four hours. IAM reports activity for at least the last 400 days, or less if your Region began supporting this feature within the last year. For more information, see Regions where data is tracked. For more information about services and actions for which action last accessed information is displayed, see IAM action last accessed information services and actions. The service last accessed data includes all attempts to access an Amazon Web Services API, not just the successful ones. This includes all attempts that were made using the Amazon Web Services Management Console, the Amazon Web Services API through any of the SDKs, or any of the command line tools. An unexpected entry in the service last accessed data does not mean that your account has been compromised, because the request might have been denied. Refer to your CloudTrail logs as the authoritative source for information about all API calls and whether they were successful or denied access. For more information, see Logging IAM events with CloudTrail in the IAM User Guide. The GenerateServiceLastAccessedDetails operation returns a JobId. Use this parameter in the following operations to retrieve the following details from your report: GetServiceLastAccessedDetails – Use this operation for users, groups, roles, or policies to list every Amazon Web Services service that the resource could access using permissions policies. For each service, the response includes information about the most recent access attempt. The JobId returned by GenerateServiceLastAccessedDetail must be used by the same role within a session, or by the same user when used to call GetServiceLastAccessedDetail. GetServiceLastAccessedDetailsWithEntities – Use this operation for groups and policies to list information about the associated entities (users or roles) that attempted to access a specific Amazon Web Services service. To check the status of the GenerateServiceLastAccessedDetails request, use the JobId parameter in the same operations and test the JobStatus response parameter. For additional information about the permissions policies that allow an identity (user, group, or role) to access specific services, use the ListPoliciesGrantingServiceAccess operation. Service last accessed data does not use other policy types when determining whether a resource could access a service. These other policy types include resource-based policies, access control lists, Organizations policies, IAM permissions boundaries, and STS assume role policies. It only applies permissions policy logic. For more about the evaluation of policy types, see Evaluating policies in the IAM User Guide. For more information about service and action last accessed data, see Reducing permissions using service last accessed data in the IAM User Guide.
417
417
  */
418
418
  generateServiceLastAccessedDetails(params: IAM.Types.GenerateServiceLastAccessedDetailsRequest, callback?: (err: AWSError, data: IAM.Types.GenerateServiceLastAccessedDetailsResponse) => void): Request<IAM.Types.GenerateServiceLastAccessedDetailsResponse, AWSError>;
419
419
  /**
420
- * Generates a report that includes details about when an IAM resource (user, group, role, or policy) was last used in an attempt to access Amazon Web Services services. Recent activity usually appears within four hours. IAM reports activity for at least the last 400 days, or less if your Region began supporting this feature within the last year. For more information, see Regions where data is tracked. The service last accessed data includes all attempts to access an Amazon Web Services API, not just the successful ones. This includes all attempts that were made using the Amazon Web Services Management Console, the Amazon Web Services API through any of the SDKs, or any of the command line tools. An unexpected entry in the service last accessed data does not mean that your account has been compromised, because the request might have been denied. Refer to your CloudTrail logs as the authoritative source for information about all API calls and whether they were successful or denied access. For more information, see Logging IAM events with CloudTrail in the IAM User Guide. The GenerateServiceLastAccessedDetails operation returns a JobId. Use this parameter in the following operations to retrieve the following details from your report: GetServiceLastAccessedDetails – Use this operation for users, groups, roles, or policies to list every Amazon Web Services service that the resource could access using permissions policies. For each service, the response includes information about the most recent access attempt. The JobId returned by GenerateServiceLastAccessedDetail must be used by the same role within a session, or by the same user when used to call GetServiceLastAccessedDetail. GetServiceLastAccessedDetailsWithEntities – Use this operation for groups and policies to list information about the associated entities (users or roles) that attempted to access a specific Amazon Web Services service. To check the status of the GenerateServiceLastAccessedDetails request, use the JobId parameter in the same operations and test the JobStatus response parameter. For additional information about the permissions policies that allow an identity (user, group, or role) to access specific services, use the ListPoliciesGrantingServiceAccess operation. Service last accessed data does not use other policy types when determining whether a resource could access a service. These other policy types include resource-based policies, access control lists, Organizations policies, IAM permissions boundaries, and STS assume role policies. It only applies permissions policy logic. For more about the evaluation of policy types, see Evaluating policies in the IAM User Guide. For more information about service and action last accessed data, see Reducing permissions using service last accessed data in the IAM User Guide.
420
+ * Generates a report that includes details about when an IAM resource (user, group, role, or policy) was last used in an attempt to access Amazon Web Services services. Recent activity usually appears within four hours. IAM reports activity for at least the last 400 days, or less if your Region began supporting this feature within the last year. For more information, see Regions where data is tracked. For more information about services and actions for which action last accessed information is displayed, see IAM action last accessed information services and actions. The service last accessed data includes all attempts to access an Amazon Web Services API, not just the successful ones. This includes all attempts that were made using the Amazon Web Services Management Console, the Amazon Web Services API through any of the SDKs, or any of the command line tools. An unexpected entry in the service last accessed data does not mean that your account has been compromised, because the request might have been denied. Refer to your CloudTrail logs as the authoritative source for information about all API calls and whether they were successful or denied access. For more information, see Logging IAM events with CloudTrail in the IAM User Guide. The GenerateServiceLastAccessedDetails operation returns a JobId. Use this parameter in the following operations to retrieve the following details from your report: GetServiceLastAccessedDetails – Use this operation for users, groups, roles, or policies to list every Amazon Web Services service that the resource could access using permissions policies. For each service, the response includes information about the most recent access attempt. The JobId returned by GenerateServiceLastAccessedDetail must be used by the same role within a session, or by the same user when used to call GetServiceLastAccessedDetail. GetServiceLastAccessedDetailsWithEntities – Use this operation for groups and policies to list information about the associated entities (users or roles) that attempted to access a specific Amazon Web Services service. To check the status of the GenerateServiceLastAccessedDetails request, use the JobId parameter in the same operations and test the JobStatus response parameter. For additional information about the permissions policies that allow an identity (user, group, or role) to access specific services, use the ListPoliciesGrantingServiceAccess operation. Service last accessed data does not use other policy types when determining whether a resource could access a service. These other policy types include resource-based policies, access control lists, Organizations policies, IAM permissions boundaries, and STS assume role policies. It only applies permissions policy logic. For more about the evaluation of policy types, see Evaluating policies in the IAM User Guide. For more information about service and action last accessed data, see Reducing permissions using service last accessed data in the IAM User Guide.
421
421
  */
422
422
  generateServiceLastAccessedDetails(callback?: (err: AWSError, data: IAM.Types.GenerateServiceLastAccessedDetailsResponse) => void): Request<IAM.Types.GenerateServiceLastAccessedDetailsResponse, AWSError>;
423
423
  /**
@@ -617,11 +617,11 @@ declare class IAM extends Service {
617
617
  */
618
618
  getUserPolicy(callback?: (err: AWSError, data: IAM.Types.GetUserPolicyResponse) => void): Request<IAM.Types.GetUserPolicyResponse, AWSError>;
619
619
  /**
620
- * Returns information about the access key IDs associated with the specified IAM user. If there is none, the operation returns an empty list. Although each user is limited to a small number of keys, you can still paginate the results using the MaxItems and Marker parameters. If the UserName is not specified, the user name is determined implicitly based on the Amazon Web Services access key ID used to sign the request. If a temporary access key is used, then UserName is required. If a long-term key is assigned to the user, then UserName is not required. This operation works for access keys under the Amazon Web Services account. Consequently, you can use this operation to manage Amazon Web Services account root user credentials even if the Amazon Web Services account has no associated users. To ensure the security of your Amazon Web Services account, the secret access key is accessible only during key and user creation.
620
+ * Returns information about the access key IDs associated with the specified IAM user. If there is none, the operation returns an empty list. Although each user is limited to a small number of keys, you can still paginate the results using the MaxItems and Marker parameters. If the UserName is not specified, the user name is determined implicitly based on the Amazon Web Services access key ID used to sign the request. If a temporary access key is used, then UserName is required. If a long-term key is assigned to the user, then UserName is not required. This operation works for access keys under the Amazon Web Services account. If the Amazon Web Services account has no associated users, the root user returns it's own access key IDs by running this command. To ensure the security of your Amazon Web Services account, the secret access key is accessible only during key and user creation.
621
621
  */
622
622
  listAccessKeys(params: IAM.Types.ListAccessKeysRequest, callback?: (err: AWSError, data: IAM.Types.ListAccessKeysResponse) => void): Request<IAM.Types.ListAccessKeysResponse, AWSError>;
623
623
  /**
624
- * Returns information about the access key IDs associated with the specified IAM user. If there is none, the operation returns an empty list. Although each user is limited to a small number of keys, you can still paginate the results using the MaxItems and Marker parameters. If the UserName is not specified, the user name is determined implicitly based on the Amazon Web Services access key ID used to sign the request. If a temporary access key is used, then UserName is required. If a long-term key is assigned to the user, then UserName is not required. This operation works for access keys under the Amazon Web Services account. Consequently, you can use this operation to manage Amazon Web Services account root user credentials even if the Amazon Web Services account has no associated users. To ensure the security of your Amazon Web Services account, the secret access key is accessible only during key and user creation.
624
+ * Returns information about the access key IDs associated with the specified IAM user. If there is none, the operation returns an empty list. Although each user is limited to a small number of keys, you can still paginate the results using the MaxItems and Marker parameters. If the UserName is not specified, the user name is determined implicitly based on the Amazon Web Services access key ID used to sign the request. If a temporary access key is used, then UserName is required. If a long-term key is assigned to the user, then UserName is not required. This operation works for access keys under the Amazon Web Services account. If the Amazon Web Services account has no associated users, the root user returns it's own access key IDs by running this command. To ensure the security of your Amazon Web Services account, the secret access key is accessible only during key and user creation.
625
625
  */
626
626
  listAccessKeys(callback?: (err: AWSError, data: IAM.Types.ListAccessKeysResponse) => void): Request<IAM.Types.ListAccessKeysResponse, AWSError>;
627
627
  /**
@@ -52,11 +52,11 @@ declare class NetworkFirewall extends Service {
52
52
  */
53
53
  createRuleGroup(callback?: (err: AWSError, data: NetworkFirewall.Types.CreateRuleGroupResponse) => void): Request<NetworkFirewall.Types.CreateRuleGroupResponse, AWSError>;
54
54
  /**
55
- * Creates an Network Firewall TLS inspection configuration. A TLS inspection configuration contains the Certificate Manager certificate references that Network Firewall uses to decrypt and re-encrypt inbound traffic. After you create a TLS inspection configuration, you associate it with a new firewall policy. To update the settings for a TLS inspection configuration, use UpdateTLSInspectionConfiguration. To manage a TLS inspection configuration's tags, use the standard Amazon Web Services resource tagging operations, ListTagsForResource, TagResource, and UntagResource. To retrieve information about TLS inspection configurations, use ListTLSInspectionConfigurations and DescribeTLSInspectionConfiguration. For more information about TLS inspection configurations, see Decrypting SSL/TLS traffic with TLS inspection configurations in the Network Firewall Developer Guide.
55
+ * Creates an Network Firewall TLS inspection configuration. A TLS inspection configuration contains the Certificate Manager certificate associations that Network Firewall uses to decrypt and re-encrypt traffic traveling through your firewall. After you create a TLS inspection configuration, you can associate it with a new firewall policy. To update the settings for a TLS inspection configuration, use UpdateTLSInspectionConfiguration. To manage a TLS inspection configuration's tags, use the standard Amazon Web Services resource tagging operations, ListTagsForResource, TagResource, and UntagResource. To retrieve information about TLS inspection configurations, use ListTLSInspectionConfigurations and DescribeTLSInspectionConfiguration. For more information about TLS inspection configurations, see Inspecting SSL/TLS traffic with TLS inspection configurations in the Network Firewall Developer Guide.
56
56
  */
57
57
  createTLSInspectionConfiguration(params: NetworkFirewall.Types.CreateTLSInspectionConfigurationRequest, callback?: (err: AWSError, data: NetworkFirewall.Types.CreateTLSInspectionConfigurationResponse) => void): Request<NetworkFirewall.Types.CreateTLSInspectionConfigurationResponse, AWSError>;
58
58
  /**
59
- * Creates an Network Firewall TLS inspection configuration. A TLS inspection configuration contains the Certificate Manager certificate references that Network Firewall uses to decrypt and re-encrypt inbound traffic. After you create a TLS inspection configuration, you associate it with a new firewall policy. To update the settings for a TLS inspection configuration, use UpdateTLSInspectionConfiguration. To manage a TLS inspection configuration's tags, use the standard Amazon Web Services resource tagging operations, ListTagsForResource, TagResource, and UntagResource. To retrieve information about TLS inspection configurations, use ListTLSInspectionConfigurations and DescribeTLSInspectionConfiguration. For more information about TLS inspection configurations, see Decrypting SSL/TLS traffic with TLS inspection configurations in the Network Firewall Developer Guide.
59
+ * Creates an Network Firewall TLS inspection configuration. A TLS inspection configuration contains the Certificate Manager certificate associations that Network Firewall uses to decrypt and re-encrypt traffic traveling through your firewall. After you create a TLS inspection configuration, you can associate it with a new firewall policy. To update the settings for a TLS inspection configuration, use UpdateTLSInspectionConfiguration. To manage a TLS inspection configuration's tags, use the standard Amazon Web Services resource tagging operations, ListTagsForResource, TagResource, and UntagResource. To retrieve information about TLS inspection configurations, use ListTLSInspectionConfigurations and DescribeTLSInspectionConfiguration. For more information about TLS inspection configurations, see Inspecting SSL/TLS traffic with TLS inspection configurations in the Network Firewall Developer Guide.
60
60
  */
61
61
  createTLSInspectionConfiguration(callback?: (err: AWSError, data: NetworkFirewall.Types.CreateTLSInspectionConfigurationResponse) => void): Request<NetworkFirewall.Types.CreateTLSInspectionConfigurationResponse, AWSError>;
62
62
  /**
@@ -292,11 +292,11 @@ declare class NetworkFirewall extends Service {
292
292
  */
293
293
  updateSubnetChangeProtection(callback?: (err: AWSError, data: NetworkFirewall.Types.UpdateSubnetChangeProtectionResponse) => void): Request<NetworkFirewall.Types.UpdateSubnetChangeProtectionResponse, AWSError>;
294
294
  /**
295
- * Updates the TLS inspection configuration settings for the specified TLS inspection configuration. You use a TLS inspection configuration by reference in one or more firewall policies. When you modify a TLS inspection configuration, you modify all firewall policies that use the TLS inspection configuration. To update a TLS inspection configuration, first call DescribeTLSInspectionConfiguration to retrieve the current TLSInspectionConfiguration object, update the object as needed, and then provide the updated object to this call.
295
+ * Updates the TLS inspection configuration settings for the specified TLS inspection configuration. You use a TLS inspection configuration by referencing it in one or more firewall policies. When you modify a TLS inspection configuration, you modify all firewall policies that use the TLS inspection configuration. To update a TLS inspection configuration, first call DescribeTLSInspectionConfiguration to retrieve the current TLSInspectionConfiguration object, update the object as needed, and then provide the updated object to this call.
296
296
  */
297
297
  updateTLSInspectionConfiguration(params: NetworkFirewall.Types.UpdateTLSInspectionConfigurationRequest, callback?: (err: AWSError, data: NetworkFirewall.Types.UpdateTLSInspectionConfigurationResponse) => void): Request<NetworkFirewall.Types.UpdateTLSInspectionConfigurationResponse, AWSError>;
298
298
  /**
299
- * Updates the TLS inspection configuration settings for the specified TLS inspection configuration. You use a TLS inspection configuration by reference in one or more firewall policies. When you modify a TLS inspection configuration, you modify all firewall policies that use the TLS inspection configuration. To update a TLS inspection configuration, first call DescribeTLSInspectionConfiguration to retrieve the current TLSInspectionConfiguration object, update the object as needed, and then provide the updated object to this call.
299
+ * Updates the TLS inspection configuration settings for the specified TLS inspection configuration. You use a TLS inspection configuration by referencing it in one or more firewall policies. When you modify a TLS inspection configuration, you modify all firewall policies that use the TLS inspection configuration. To update a TLS inspection configuration, first call DescribeTLSInspectionConfiguration to retrieve the current TLSInspectionConfiguration object, update the object as needed, and then provide the updated object to this call.
300
300
  */
301
301
  updateTLSInspectionConfiguration(callback?: (err: AWSError, data: NetworkFirewall.Types.UpdateTLSInspectionConfigurationResponse) => void): Request<NetworkFirewall.Types.UpdateTLSInspectionConfigurationResponse, AWSError>;
302
302
  }
@@ -433,6 +433,16 @@ declare namespace NetworkFirewall {
433
433
  CIDRs?: CIDRSummary;
434
434
  }
435
435
  export type Certificates = TlsCertificateData[];
436
+ export interface CheckCertificateRevocationStatusActions {
437
+ /**
438
+ * Configures how Network Firewall processes traffic when it determines that the certificate presented by the server in the SSL/TLS connection has a revoked status. PASS - Allow the connection to continue, and pass subsequent packets to the stateful engine for inspection. DROP - Network Firewall fails closed and drops all subsequent traffic. REJECT - Network Firewall sends a TCP reject packet back to your client so that the client can immediately establish a new session. Network Firewall then fails closed and drops all subsequent traffic. REJECT is available only for TCP traffic.
439
+ */
440
+ RevokedStatusAction?: RevocationCheckAction;
441
+ /**
442
+ * Configures how Network Firewall processes traffic when it determines that the certificate presented by the server in the SSL/TLS connection has an unknown status, or a status that cannot be determined for any other reason, including when the service is unable to connect to the OCSP and CRL endpoints for the certificate. PASS - Allow the connection to continue, and pass subsequent packets to the stateful engine for inspection. DROP - Network Firewall fails closed and drops all subsequent traffic. REJECT - Network Firewall sends a TCP reject packet back to your client so that the client can immediately establish a new session. Network Firewall then fails closed and drops all subsequent traffic. REJECT is available only for TCP traffic.
443
+ */
444
+ UnknownStatusAction?: RevocationCheckAction;
445
+ }
436
446
  export type CollectionMember_String = string;
437
447
  export type ConfigurationSyncState = "PENDING"|"IN_SYNC"|"CAPACITY_CONSTRAINED"|string;
438
448
  export interface CreateFirewallPolicyRequest {
@@ -581,7 +591,7 @@ declare namespace NetworkFirewall {
581
591
  */
582
592
  TLSInspectionConfigurationName: ResourceName;
583
593
  /**
584
- * The object that defines a TLS inspection configuration. This, along with TLSInspectionConfigurationResponse, define the TLS inspection configuration. You can retrieve all objects for a TLS inspection configuration by calling DescribeTLSInspectionConfiguration. Network Firewall uses a TLS inspection configuration to decrypt traffic. Network Firewall re-encrypts the traffic before sending it to its destination. To use a TLS inspection configuration, you add it to a new Network Firewall firewall policy, then you apply the firewall policy to a firewall. Network Firewall acts as a proxy service to decrypt and inspect inbound traffic. You can reference a TLS inspection configuration from more than one firewall policy, and you can use a firewall policy in more than one firewall. For more information about using TLS inspection configurations, see Decrypting SSL/TLS traffic with TLS inspection configurations in the Network Firewall Developer Guide.
594
+ * The object that defines a TLS inspection configuration. This, along with TLSInspectionConfigurationResponse, define the TLS inspection configuration. You can retrieve all objects for a TLS inspection configuration by calling DescribeTLSInspectionConfiguration. Network Firewall uses a TLS inspection configuration to decrypt traffic. Network Firewall re-encrypts the traffic before sending it to its destination. To use a TLS inspection configuration, you add it to a new Network Firewall firewall policy, then you apply the firewall policy to a firewall. Network Firewall acts as a proxy service to decrypt and inspect the traffic traveling through your firewalls. You can reference a TLS inspection configuration from more than one firewall policy, and you can use a firewall policy in more than one firewall. For more information about using TLS inspection configurations, see Inspecting SSL/TLS traffic with TLS inspection configurations in the Network Firewall Developer Guide.
585
595
  */
586
596
  TLSInspectionConfiguration: TLSInspectionConfiguration;
587
597
  /**
@@ -851,7 +861,7 @@ declare namespace NetworkFirewall {
851
861
  */
852
862
  UpdateToken: UpdateToken;
853
863
  /**
854
- * The object that defines a TLS inspection configuration. This, along with TLSInspectionConfigurationResponse, define the TLS inspection configuration. You can retrieve all objects for a TLS inspection configuration by calling DescribeTLSInspectionConfiguration. Network Firewall uses a TLS inspection configuration to decrypt traffic. Network Firewall re-encrypts the traffic before sending it to its destination. To use a TLS inspection configuration, you add it to a new Network Firewall firewall policy, then you apply the firewall policy to a firewall. Network Firewall acts as a proxy service to decrypt and inspect inbound traffic. You can reference a TLS inspection configuration from more than one firewall policy, and you can use a firewall policy in more than one firewall. For more information about using TLS inspection configurations, see Decrypting SSL/TLS traffic with TLS inspection configurations in the Network Firewall Developer Guide.
864
+ * The object that defines a TLS inspection configuration. This, along with TLSInspectionConfigurationResponse, define the TLS inspection configuration. You can retrieve all objects for a TLS inspection configuration by calling DescribeTLSInspectionConfiguration. Network Firewall uses a TLS inspection configuration to decrypt traffic. Network Firewall re-encrypts the traffic before sending it to its destination. To use a TLS inspection configuration, you add it to a new Network Firewall firewall policy, then you apply the firewall policy to a firewall. Network Firewall acts as a proxy service to decrypt and inspect the traffic traveling through your firewalls. You can reference a TLS inspection configuration from more than one firewall policy, and you can use a firewall policy in more than one firewall. For more information about using TLS inspection configurations, see Inspecting SSL/TLS traffic with TLS inspection configurations in the Network Firewall Developer Guide.
855
865
  */
856
866
  TLSInspectionConfiguration?: TLSInspectionConfiguration;
857
867
  /**
@@ -1393,7 +1403,8 @@ declare namespace NetworkFirewall {
1393
1403
  export type ResourceManagedStatus = "MANAGED"|"ACCOUNT"|string;
1394
1404
  export type ResourceManagedType = "AWS_MANAGED_THREAT_SIGNATURES"|"AWS_MANAGED_DOMAIN_LISTS"|string;
1395
1405
  export type ResourceName = string;
1396
- export type ResourceStatus = "ACTIVE"|"DELETING"|string;
1406
+ export type ResourceStatus = "ACTIVE"|"DELETING"|"ERROR"|string;
1407
+ export type RevocationCheckAction = "PASS"|"DROP"|"REJECT"|string;
1397
1408
  export type RuleCapacity = number;
1398
1409
  export interface RuleDefinition {
1399
1410
  /**
@@ -1552,19 +1563,27 @@ declare namespace NetworkFirewall {
1552
1563
  export type RulesString = string;
1553
1564
  export interface ServerCertificate {
1554
1565
  /**
1555
- * The Amazon Resource Name (ARN) of the Certificate Manager SSL/TLS server certificate.
1566
+ * The Amazon Resource Name (ARN) of the Certificate Manager SSL/TLS server certificate that's used for inbound SSL/TLS inspection.
1556
1567
  */
1557
1568
  ResourceArn?: ResourceArn;
1558
1569
  }
1559
1570
  export interface ServerCertificateConfiguration {
1560
1571
  /**
1561
- * The list of a server certificate configuration's Certificate Manager SSL/TLS certificates.
1572
+ * The list of a server certificate configuration's Certificate Manager certificates, used for inbound SSL/TLS inspection.
1562
1573
  */
1563
1574
  ServerCertificates?: ServerCertificates;
1564
1575
  /**
1565
- * A list of a server certificate configuration's scopes.
1576
+ * A list of scopes.
1566
1577
  */
1567
1578
  Scopes?: ServerCertificateScopes;
1579
+ /**
1580
+ * The Amazon Resource Name (ARN) of the imported certificate authority (CA) certificate configured in Certificate Manager (ACM) to use for outbound SSL/TLS inspection. The following limitations apply: You can use CA certificates that you imported into ACM, but you can't generate CA certificates with ACM. You can't use certificates issued by Private Certificate Authority. For more information about the certificate requirements for outbound inspection, see Requirements for using SSL/TLS certificates with TLS inspection configurations in the Network Firewall Developer Guide. For information about working with certificates in ACM, see Importing certificates in the Certificate Manager User Guide.
1581
+ */
1582
+ CertificateAuthorityArn?: ResourceArn;
1583
+ /**
1584
+ * When enabled, Network Firewall checks if the server certificate presented by the server in the SSL/TLS connection has a revoked or unkown status. If the certificate has an unknown or revoked status, you must specify the actions that Network Firewall takes on outbound traffic. To use this option, you must specify a CertificateAuthorityArn in ServerCertificateConfiguration.
1585
+ */
1586
+ CheckCertificateRevocationStatus?: CheckCertificateRevocationStatusActions;
1568
1587
  }
1569
1588
  export type ServerCertificateConfigurations = ServerCertificateConfiguration[];
1570
1589
  export interface ServerCertificateScope {
@@ -1788,6 +1807,7 @@ declare namespace NetworkFirewall {
1788
1807
  * A list of the certificates associated with the TLS inspection configuration.
1789
1808
  */
1790
1809
  Certificates?: Certificates;
1810
+ CertificateAuthority?: TlsCertificateData;
1791
1811
  }
1792
1812
  export type TLSInspectionConfigurations = TLSInspectionConfigurationMetadata[];
1793
1813
  export interface Tag {
@@ -2150,7 +2170,7 @@ declare namespace NetworkFirewall {
2150
2170
  */
2151
2171
  TLSInspectionConfigurationName?: ResourceName;
2152
2172
  /**
2153
- * The object that defines a TLS inspection configuration. This, along with TLSInspectionConfigurationResponse, define the TLS inspection configuration. You can retrieve all objects for a TLS inspection configuration by calling DescribeTLSInspectionConfiguration. Network Firewall uses a TLS inspection configuration to decrypt traffic. Network Firewall re-encrypts the traffic before sending it to its destination. To use a TLS inspection configuration, you add it to a new Network Firewall firewall policy, then you apply the firewall policy to a firewall. Network Firewall acts as a proxy service to decrypt and inspect inbound traffic. You can reference a TLS inspection configuration from more than one firewall policy, and you can use a firewall policy in more than one firewall. For more information about using TLS inspection configurations, see Decrypting SSL/TLS traffic with TLS inspection configurations in the Network Firewall Developer Guide.
2173
+ * The object that defines a TLS inspection configuration. This, along with TLSInspectionConfigurationResponse, define the TLS inspection configuration. You can retrieve all objects for a TLS inspection configuration by calling DescribeTLSInspectionConfiguration. Network Firewall uses a TLS inspection configuration to decrypt traffic. Network Firewall re-encrypts the traffic before sending it to its destination. To use a TLS inspection configuration, you add it to a new Network Firewall firewall policy, then you apply the firewall policy to a firewall. Network Firewall acts as a proxy service to decrypt and inspect the traffic traveling through your firewalls. You can reference a TLS inspection configuration from more than one firewall policy, and you can use a firewall policy in more than one firewall. For more information about using TLS inspection configurations, see Inspecting SSL/TLS traffic with TLS inspection configurations in the Network Firewall Developer Guide.
2154
2174
  */
2155
2175
  TLSInspectionConfiguration: TLSInspectionConfiguration;
2156
2176
  /**