cdk-comprehend-s3olap 2.0.70 → 2.0.71

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.
@@ -436,6 +436,7 @@
436
436
  "ServerlessV2ScalingConfiguration": {
437
437
  "shape": "S2a"
438
438
  },
439
+ "NetworkType": {},
439
440
  "SourceRegion": {}
440
441
  }
441
442
  },
@@ -3016,7 +3017,8 @@
3016
3017
  },
3017
3018
  "ServerlessV2ScalingConfiguration": {
3018
3019
  "shape": "S2a"
3019
- }
3020
+ },
3021
+ "NetworkType": {}
3020
3022
  }
3021
3023
  },
3022
3024
  "output": {
@@ -3858,7 +3860,8 @@
3858
3860
  "DomainIAMRoleName": {},
3859
3861
  "ServerlessV2ScalingConfiguration": {
3860
3862
  "shape": "S2a"
3861
- }
3863
+ },
3864
+ "NetworkType": {}
3862
3865
  }
3863
3866
  },
3864
3867
  "output": {
@@ -3932,7 +3935,8 @@
3932
3935
  },
3933
3936
  "ServerlessV2ScalingConfiguration": {
3934
3937
  "shape": "S2a"
3935
- }
3938
+ },
3939
+ "NetworkType": {}
3936
3940
  }
3937
3941
  },
3938
3942
  "output": {
@@ -4006,7 +4010,8 @@
4006
4010
  },
4007
4011
  "ServerlessV2ScalingConfiguration": {
4008
4012
  "shape": "S2a"
4009
- }
4013
+ },
4014
+ "NetworkType": {}
4010
4015
  }
4011
4016
  },
4012
4017
  "output": {
@@ -5306,7 +5311,8 @@
5306
5311
  "type": "double"
5307
5312
  }
5308
5313
  }
5309
- }
5314
+ },
5315
+ "NetworkType": {}
5310
5316
  },
5311
5317
  "wrapper": true
5312
5318
  },
@@ -345,7 +345,7 @@ declare namespace AppMesh {
345
345
  */
346
346
  attributes?: AwsCloudMapInstanceAttributes;
347
347
  /**
348
- * The IP version to use to control traffic within the mesh.
348
+ * The preferred IP version that this virtual node uses. Setting the IP preference on the virtual node only overrides the IP preference set for the mesh on this specific node.
349
349
  */
350
350
  ipPreference?: IpPreference;
351
351
  /**
@@ -922,7 +922,7 @@ declare namespace AppMesh {
922
922
  */
923
923
  hostname: Hostname;
924
924
  /**
925
- * The IP version to use to control traffic within the mesh.
925
+ * The preferred IP version that this virtual node uses. Setting the IP preference on the virtual node only overrides the IP preference set for the mesh on this specific node.
926
926
  */
927
927
  ipPreference?: IpPreference;
928
928
  /**
@@ -951,6 +951,10 @@ declare namespace AppMesh {
951
951
  export type EgressFilterType = "ALLOW_ALL"|"DROP_ALL"|string;
952
952
  export type ExactHostName = string;
953
953
  export interface FileAccessLog {
954
+ /**
955
+ * The specified format for the logs. The format is either json_format or text_format.
956
+ */
957
+ format?: LoggingFormat;
954
958
  /**
955
959
  * The file path to write access logs to. You can use /dev/stdout to send access logs to standard out and configure your Envoy container to use a log driver, such as awslogs, to export the access logs to a log storage service such as Amazon CloudWatch Logs. You can also specify a path in the Envoy container's file system to write the files to disk. <note> <p>The Envoy process must have write permissions to the path that you specify here. Otherwise, Envoy fails to bootstrap properly.</p> </note>
956
960
  */
@@ -1062,6 +1066,10 @@ declare namespace AppMesh {
1062
1066
  }
1063
1067
  export type GatewayRouteStatusCode = "ACTIVE"|"INACTIVE"|"DELETED"|string;
1064
1068
  export interface GatewayRouteTarget {
1069
+ /**
1070
+ * The port number of the gateway route target.
1071
+ */
1072
+ port?: ListenerPort;
1065
1073
  /**
1066
1074
  * An object that represents a virtual service gateway route target.
1067
1075
  */
@@ -1102,6 +1110,10 @@ declare namespace AppMesh {
1102
1110
  * The gateway route metadata to be matched on.
1103
1111
  */
1104
1112
  metadata?: GrpcGatewayRouteMetadataList;
1113
+ /**
1114
+ * The port number to match from the request.
1115
+ */
1116
+ port?: ListenerPort;
1105
1117
  /**
1106
1118
  * The fully qualified domain name for the service to match from the request.
1107
1119
  */
@@ -1204,6 +1216,10 @@ declare namespace AppMesh {
1204
1216
  * The method name to match from the request. If you specify a name, you must also specify a serviceName.
1205
1217
  */
1206
1218
  methodName?: MethodName;
1219
+ /**
1220
+ * The port number to match on.
1221
+ */
1222
+ port?: ListenerPort;
1207
1223
  /**
1208
1224
  * The fully qualified domain name for the service to match from the request.
1209
1225
  */
@@ -1366,6 +1382,10 @@ declare namespace AppMesh {
1366
1382
  * The path to match on.
1367
1383
  */
1368
1384
  path?: HttpPathMatch;
1385
+ /**
1386
+ * The port number to match on.
1387
+ */
1388
+ port?: ListenerPort;
1369
1389
  /**
1370
1390
  * Specifies the path to match requests with. This parameter must always start with /, which by itself matches all requests to the virtual service name. You can also match for path-based routing of requests. For example, if your virtual service name is my-service.local and you want the route to match requests to my-service.local/metrics, your prefix should be /metrics.
1371
1391
  */
@@ -1502,6 +1522,10 @@ declare namespace AppMesh {
1502
1522
  * The client request path to match on.
1503
1523
  */
1504
1524
  path?: HttpPathMatch;
1525
+ /**
1526
+ * The port number to match on.
1527
+ */
1528
+ port?: ListenerPort;
1505
1529
  /**
1506
1530
  * Specifies the path to match requests with. This parameter must always start with /, which by itself matches all requests to the virtual service name. You can also match for path-based routing of requests. For example, if your virtual service name is my-service.local and you want the route to match requests to my-service.local/metrics, your prefix should be /metrics.
1507
1531
  */
@@ -1527,6 +1551,19 @@ declare namespace AppMesh {
1527
1551
  perRequest?: Duration;
1528
1552
  }
1529
1553
  export type IpPreference = "IPv6_PREFERRED"|"IPv4_PREFERRED"|"IPv4_ONLY"|"IPv6_ONLY"|string;
1554
+ export type JsonFormat = JsonFormatRef[];
1555
+ export interface JsonFormatRef {
1556
+ /**
1557
+ * The specified key for the JSON.
1558
+ */
1559
+ key: JsonKey;
1560
+ /**
1561
+ * The specified value for the JSON.
1562
+ */
1563
+ value: JsonValue;
1564
+ }
1565
+ export type JsonKey = string;
1566
+ export type JsonValue = string;
1530
1567
  export interface ListGatewayRoutesInput {
1531
1568
  /**
1532
1569
  * The maximum number of results returned by ListGatewayRoutes in paginated output. When you use this parameter, ListGatewayRoutes returns only limit results in a single page along with a nextToken response element. You can see the remaining results of the initial request by sending another ListGatewayRoutes request with the returned nextToken value. This value can be between 1 and 100. If you don't use this parameter, ListGatewayRoutes returns up to 100 results and a nextToken value if applicable.
@@ -1780,6 +1817,7 @@ declare namespace AppMesh {
1780
1817
  */
1781
1818
  tls?: ListenerTls;
1782
1819
  }
1820
+ export type ListenerPort = number;
1783
1821
  export interface ListenerTimeout {
1784
1822
  /**
1785
1823
  * An object that represents types of timeouts.
@@ -1876,6 +1914,16 @@ declare namespace AppMesh {
1876
1914
  */
1877
1915
  accessLog?: AccessLog;
1878
1916
  }
1917
+ export interface LoggingFormat {
1918
+ /**
1919
+ *
1920
+ */
1921
+ json?: JsonFormat;
1922
+ /**
1923
+ *
1924
+ */
1925
+ text?: TextFormat;
1926
+ }
1879
1927
  export type Long = number;
1880
1928
  export interface MatchRange {
1881
1929
  /**
@@ -2190,6 +2238,10 @@ declare namespace AppMesh {
2190
2238
  * The action to take if a match is determined.
2191
2239
  */
2192
2240
  action: TcpRouteAction;
2241
+ /**
2242
+ * An object that represents the criteria for determining a request match.
2243
+ */
2244
+ match?: TcpRouteMatch;
2193
2245
  /**
2194
2246
  * An object that represents types of timeouts.
2195
2247
  */
@@ -2201,16 +2253,23 @@ declare namespace AppMesh {
2201
2253
  */
2202
2254
  weightedTargets: WeightedTargets;
2203
2255
  }
2256
+ export interface TcpRouteMatch {
2257
+ /**
2258
+ * The port number to match on.
2259
+ */
2260
+ port?: ListenerPort;
2261
+ }
2204
2262
  export interface TcpTimeout {
2205
2263
  /**
2206
2264
  * An object that represents an idle timeout. An idle timeout bounds the amount of time that a connection may be idle. The default value is none.
2207
2265
  */
2208
2266
  idle?: Duration;
2209
2267
  }
2268
+ export type TextFormat = string;
2210
2269
  export type Timestamp = Date;
2211
2270
  export interface TlsValidationContext {
2212
2271
  /**
2213
- * A reference to an object that represents the SANs for a Transport Layer Security (TLS) validation context.
2272
+ * A reference to an object that represents the SANs for a Transport Layer Security (TLS) validation context. If you don't specify SANs on the terminating mesh endpoint, the Envoy proxy for that node doesn't verify the SAN on a peer client certificate. If you don't specify SANs on the originating mesh endpoint, the SAN on the certificate provided by the terminating endpoint must match the mesh endpoint service discovery configuration. Since SPIRE vended certificates have a SPIFFE ID as a name, you must set the SAN since the name doesn't match the service discovery name.
2214
2273
  */
2215
2274
  subjectAlternativeNames?: SubjectAlternativeNames;
2216
2275
  /**
@@ -2536,6 +2595,10 @@ declare namespace AppMesh {
2536
2595
  virtualGatewayName: ResourceName;
2537
2596
  }
2538
2597
  export interface VirtualGatewayFileAccessLog {
2598
+ /**
2599
+ * The specified format for the virtual gateway access logs. It can be either json_format or text_format.
2600
+ */
2601
+ format?: LoggingFormat;
2539
2602
  /**
2540
2603
  * The file path to write access logs to. You can use /dev/stdout to send access logs to standard out and configure your Envoy container to use a log driver, such as awslogs, to export the access logs to a log storage service such as Amazon CloudWatch Logs. You can also specify a path in the Envoy container's file system to write the files to disk.
2541
2604
  */
@@ -3105,6 +3168,10 @@ declare namespace AppMesh {
3105
3168
  }
3106
3169
  export type VirtualServiceStatusCode = "ACTIVE"|"INACTIVE"|"DELETED"|string;
3107
3170
  export interface WeightedTarget {
3171
+ /**
3172
+ * The targeted port of the weighted object.
3173
+ */
3174
+ port?: ListenerPort;
3108
3175
  /**
3109
3176
  * The virtual node to associate with the weighted target.
3110
3177
  */
@@ -504,7 +504,7 @@ declare namespace Kendra {
504
504
  export type AccessControlConfigurationSummaryList = AccessControlConfigurationSummary[];
505
505
  export interface AccessControlListConfiguration {
506
506
  /**
507
- * Path to the Amazon Web Services S3 bucket that contains the ACL files.
507
+ * Path to the Amazon S3 bucket that contains the ACL files.
508
508
  */
509
509
  KeyPath?: S3ObjectKey;
510
510
  }
@@ -1003,6 +1003,10 @@ declare namespace Kendra {
1003
1003
  * A list of regular expression patterns to exclude certain blog posts, pages, spaces, or attachments in your Confluence. Content that matches the patterns are excluded from the index. Content that doesn't match the patterns is included in the index. If content matches both an inclusion and exclusion pattern, the exclusion pattern takes precedence and the content isn't included in the index.
1004
1004
  */
1005
1005
  ExclusionPatterns?: DataSourceInclusionsExclusionsStrings;
1006
+ /**
1007
+ * Configuration information to connect to your Confluence URL instance via a web proxy. You can use this option for Confluence Server. You must provide the website host name and port number. For example, the host name of https://a.example.com/page1.html is "a.example.com" and the port is 443, the standard port for HTTPS. Web proxy credentials are optional and you can use them to connect to a web proxy server that requires basic authentication of user name and password. To store web proxy credentials, you use a secret in Secrets Manager. It is recommended that you follow best security practices when configuring your web proxy. This includes setting up throttling, setting up logging and monitoring, and applying security patches on a regular basis. If you use your web proxy with multiple data sources, sync jobs that occur at the same time could strain the load on your proxy. It is recommended you prepare your proxy beforehand for any security and load requirements.
1008
+ */
1009
+ ProxyConfiguration?: ProxyConfiguration;
1006
1010
  }
1007
1011
  export interface ConfluencePageConfiguration {
1008
1012
  /**
@@ -1158,7 +1162,7 @@ declare namespace Kendra {
1158
1162
  }
1159
1163
  export interface CreateDataSourceRequest {
1160
1164
  /**
1161
- * A unique name for the data source connector. A data source name can't be changed without deleting and recreating the data source connector.
1165
+ * A name for the data source connector.
1162
1166
  */
1163
1167
  Name: DataSourceName;
1164
1168
  /**
@@ -1173,6 +1177,10 @@ declare namespace Kendra {
1173
1177
  * Configuration information to connect to your data source repository. You can't specify the Configuration parameter when the Type parameter is set to CUSTOM. If you do, you receive a ValidationException exception. The Configuration parameter is required for all other data sources.
1174
1178
  */
1175
1179
  Configuration?: DataSourceConfiguration;
1180
+ /**
1181
+ * Configuration information for an Amazon Virtual Private Cloud to connect to your data source. For more information, see Configuring a VPC.
1182
+ */
1183
+ VpcConfiguration?: DataSourceVpcConfiguration;
1176
1184
  /**
1177
1185
  * A description for the data source connector.
1178
1186
  */
@@ -1488,6 +1496,10 @@ declare namespace Kendra {
1488
1496
  * Provides the configuration information to connect to Alfresco as your data source.
1489
1497
  */
1490
1498
  AlfrescoConfiguration?: AlfrescoConfiguration;
1499
+ /**
1500
+ * Provides a template for the configuration information to connect to your data source.
1501
+ */
1502
+ TemplateConfiguration?: TemplateConfiguration;
1491
1503
  }
1492
1504
  export type DataSourceDateFieldFormat = string;
1493
1505
  export type DataSourceFieldName = string;
@@ -1623,7 +1635,7 @@ declare namespace Kendra {
1623
1635
  IndexFieldName: IndexFieldName;
1624
1636
  }
1625
1637
  export type DataSourceToIndexFieldMappingList = DataSourceToIndexFieldMapping[];
1626
- export type DataSourceType = "S3"|"SHAREPOINT"|"DATABASE"|"SALESFORCE"|"ONEDRIVE"|"SERVICENOW"|"CUSTOM"|"CONFLUENCE"|"GOOGLEDRIVE"|"WEBCRAWLER"|"WORKDOCS"|"FSX"|"SLACK"|"BOX"|"QUIP"|"JIRA"|"GITHUB"|"ALFRESCO"|string;
1638
+ export type DataSourceType = "S3"|"SHAREPOINT"|"DATABASE"|"SALESFORCE"|"ONEDRIVE"|"SERVICENOW"|"CUSTOM"|"CONFLUENCE"|"GOOGLEDRIVE"|"WEBCRAWLER"|"WORKDOCS"|"FSX"|"SLACK"|"BOX"|"QUIP"|"JIRA"|"GITHUB"|"ALFRESCO"|"TEMPLATE"|string;
1627
1639
  export interface DataSourceVpcConfiguration {
1628
1640
  /**
1629
1641
  * A list of identifiers for subnets within your Amazon VPC. The subnets should be able to connect to each other in the VPC, and they should have outgoing access to the Internet through a NAT device.
@@ -1801,7 +1813,7 @@ declare namespace Kendra {
1801
1813
  */
1802
1814
  IndexId?: IndexId;
1803
1815
  /**
1804
- * The name that you gave the data source when it was created.
1816
+ * The name for the data source.
1805
1817
  */
1806
1818
  Name?: DataSourceName;
1807
1819
  /**
@@ -1812,6 +1824,10 @@ declare namespace Kendra {
1812
1824
  * Configuration details for the data source. This shows how the data source is configured. The configuration options for a data source depend on the data source provider.
1813
1825
  */
1814
1826
  Configuration?: DataSourceConfiguration;
1827
+ /**
1828
+ * Configuration information for an Amazon Virtual Private Cloud to connect to your data source. For more information, see Configuring a VPC.
1829
+ */
1830
+ VpcConfiguration?: DataSourceVpcConfiguration;
1815
1831
  /**
1816
1832
  * The Unix timestamp of when the data source was created.
1817
1833
  */
@@ -3826,7 +3842,7 @@ declare namespace Kendra {
3826
3842
  */
3827
3843
  CrawlAttachments?: Boolean;
3828
3844
  /**
3829
- * The identifiers of the Quip folders you want to index.
3845
+ * The identifiers of the Quip folders you want to index. You can find in your browser URL when you access your folder in Quip. For example, https://quip-company.com/zlLuOVNSarTL/folder-name.
3830
3846
  */
3831
3847
  FolderIds?: FolderIdList;
3832
3848
  /**
@@ -4261,6 +4277,10 @@ declare namespace Kendra {
4261
4277
  * Whether you want to connect to SharePoint using basic authentication of user name and password, or OAuth authentication of user name, password, client ID, and client secret. You can use OAuth authentication for SharePoint Online.
4262
4278
  */
4263
4279
  AuthenticationType?: SharePointOnlineAuthenticationType;
4280
+ /**
4281
+ * Configuration information to connect to your Microsoft SharePoint site URLs via instance via a web proxy. You can use this option for SharePoint Server. You must provide the website host name and port number. For example, the host name of https://a.example.com/page1.html is "a.example.com" and the port is 443, the standard port for HTTPS. Web proxy credentials are optional and you can use them to connect to a web proxy server that requires basic authentication of user name and password. To store web proxy credentials, you use a secret in Secrets Manager. It is recommended that you follow best security practices when configuring your web proxy. This includes setting up throttling, setting up logging and monitoring, and applying security patches on a regular basis. If you use your web proxy with multiple data sources, sync jobs that occur at the same time could strain the load on your proxy. It is recommended you prepare your proxy beforehand for any security and load requirements.
4282
+ */
4283
+ ProxyConfiguration?: ProxyConfiguration;
4264
4284
  }
4265
4285
  export type SharePointOnlineAuthenticationType = "HTTP_BASIC"|"OAUTH2"|string;
4266
4286
  export type SharePointUrlList = Url[];
@@ -4509,6 +4529,14 @@ declare namespace Kendra {
4509
4529
  }
4510
4530
  export type TagValue = string;
4511
4531
  export type TeamId = string;
4532
+ export interface Template {
4533
+ }
4534
+ export interface TemplateConfiguration {
4535
+ /**
4536
+ * The template schema used for the data source. The following links to the template schema for data sources where templates are supported: Zendesk template schema
4537
+ */
4538
+ Template?: Template;
4539
+ }
4512
4540
  export type TenantDomain = string;
4513
4541
  export interface TextDocumentStatistics {
4514
4542
  /**
@@ -4617,7 +4645,7 @@ declare namespace Kendra {
4617
4645
  */
4618
4646
  Id: DataSourceId;
4619
4647
  /**
4620
- * A new name for the data source connector. You must first delete the data source and re-create it to change the name of the data source.
4648
+ * A new name for the data source connector.
4621
4649
  */
4622
4650
  Name?: DataSourceName;
4623
4651
  /**
@@ -4628,6 +4656,10 @@ declare namespace Kendra {
4628
4656
  * Configuration information you want to update for the data source connector.
4629
4657
  */
4630
4658
  Configuration?: DataSourceConfiguration;
4659
+ /**
4660
+ * Configuration information for an Amazon Virtual Private Cloud to connect to your data source. For more information, see Configuring a VPC.
4661
+ */
4662
+ VpcConfiguration?: DataSourceVpcConfiguration;
4631
4663
  /**
4632
4664
  * A new description for the data source connector.
4633
4665
  */
@@ -20,6 +20,14 @@ declare class LakeFormation extends Service {
20
20
  * Attaches one or more LF-tags to an existing resource.
21
21
  */
22
22
  addLFTagsToResource(callback?: (err: AWSError, data: LakeFormation.Types.AddLFTagsToResourceResponse) => void): Request<LakeFormation.Types.AddLFTagsToResourceResponse, AWSError>;
23
+ /**
24
+ * Allows a caller to assume an IAM role decorated as the SAML user specified in the SAML assertion included in the request. This decoration allows Lake Formation to enforce access policies against the SAML users and groups. This API operation requires SAML federation setup in the caller’s account as it can only be called with valid SAML assertions. Lake Formation does not scope down the permission of the assumed role. All permissions attached to the role via the SAML federation setup will be included in the role session. This decorated role is expected to access data in Amazon S3 by getting temporary access from Lake Formation which is authorized via the virtual API GetDataAccess. Therefore, all SAML roles that can be assumed via AssumeDecoratedRoleWithSAML must at a minimum include lakeformation:GetDataAccess in their role policies. A typical IAM policy attached to such a role would look as follows:
25
+ */
26
+ assumeDecoratedRoleWithSAML(params: LakeFormation.Types.AssumeDecoratedRoleWithSAMLRequest, callback?: (err: AWSError, data: LakeFormation.Types.AssumeDecoratedRoleWithSAMLResponse) => void): Request<LakeFormation.Types.AssumeDecoratedRoleWithSAMLResponse, AWSError>;
27
+ /**
28
+ * Allows a caller to assume an IAM role decorated as the SAML user specified in the SAML assertion included in the request. This decoration allows Lake Formation to enforce access policies against the SAML users and groups. This API operation requires SAML federation setup in the caller’s account as it can only be called with valid SAML assertions. Lake Formation does not scope down the permission of the assumed role. All permissions attached to the role via the SAML federation setup will be included in the role session. This decorated role is expected to access data in Amazon S3 by getting temporary access from Lake Formation which is authorized via the virtual API GetDataAccess. Therefore, all SAML roles that can be assumed via AssumeDecoratedRoleWithSAML must at a minimum include lakeformation:GetDataAccess in their role policies. A typical IAM policy attached to such a role would look as follows:
29
+ */
30
+ assumeDecoratedRoleWithSAML(callback?: (err: AWSError, data: LakeFormation.Types.AssumeDecoratedRoleWithSAMLResponse) => void): Request<LakeFormation.Types.AssumeDecoratedRoleWithSAMLResponse, AWSError>;
23
31
  /**
24
32
  * Batch operation to grant permissions to the principal.
25
33
  */
@@ -77,11 +85,11 @@ declare class LakeFormation extends Service {
77
85
  */
78
86
  deleteDataCellsFilter(callback?: (err: AWSError, data: LakeFormation.Types.DeleteDataCellsFilterResponse) => void): Request<LakeFormation.Types.DeleteDataCellsFilterResponse, AWSError>;
79
87
  /**
80
- * Deletes the specified LF-tag key name. If the attribute key does not exist or the LF-tag does not exist, then the operation will not do anything. If the attribute key exists, then the operation checks if any resources are tagged with this attribute key, if yes, the API throws a 400 Exception with the message "Delete not allowed" as the LF-tag key is still attached with resources. You can consider untagging resources with this LF-tag key.
88
+ * Deletes the specified LF-tag given a key name. If the input parameter tag key was not found, then the operation will throw an exception. When you delete an LF-tag, the LFTagPolicy attached to the LF-tag becomes invalid. If the deleted LF-tag was still assigned to any resource, the tag policy attach to the deleted LF-tag will no longer be applied to the resource.
81
89
  */
82
90
  deleteLFTag(params: LakeFormation.Types.DeleteLFTagRequest, callback?: (err: AWSError, data: LakeFormation.Types.DeleteLFTagResponse) => void): Request<LakeFormation.Types.DeleteLFTagResponse, AWSError>;
83
91
  /**
84
- * Deletes the specified LF-tag key name. If the attribute key does not exist or the LF-tag does not exist, then the operation will not do anything. If the attribute key exists, then the operation checks if any resources are tagged with this attribute key, if yes, the API throws a 400 Exception with the message "Delete not allowed" as the LF-tag key is still attached with resources. You can consider untagging resources with this LF-tag key.
92
+ * Deletes the specified LF-tag given a key name. If the input parameter tag key was not found, then the operation will throw an exception. When you delete an LF-tag, the LFTagPolicy attached to the LF-tag becomes invalid. If the deleted LF-tag was still assigned to any resource, the tag policy attach to the deleted LF-tag will no longer be applied to the resource.
85
93
  */
86
94
  deleteLFTag(callback?: (err: AWSError, data: LakeFormation.Types.DeleteLFTagResponse) => void): Request<LakeFormation.Types.DeleteLFTagResponse, AWSError>;
87
95
  /**
@@ -407,6 +415,42 @@ declare namespace LakeFormation {
407
415
  }
408
416
  export interface AllRowsWildcard {
409
417
  }
418
+ export interface AssumeDecoratedRoleWithSAMLRequest {
419
+ /**
420
+ * A SAML assertion consisting of an assertion statement for the user who needs temporary credentials. This must match the SAML assertion that was issued to IAM. This must be Base64 encoded.
421
+ */
422
+ SAMLAssertion: SAMLAssertionString;
423
+ /**
424
+ * The role that represents an IAM principal whose scope down policy allows it to call credential vending APIs such as GetTemporaryTableCredentials. The caller must also have iam:PassRole permission on this role.
425
+ */
426
+ RoleArn: IAMRoleArn;
427
+ /**
428
+ * The Amazon Resource Name (ARN) of the SAML provider in IAM that describes the IdP.
429
+ */
430
+ PrincipalArn: IAMSAMLProviderArn;
431
+ /**
432
+ * The time period, between 900 and 43,200 seconds, for the timeout of the temporary credentials.
433
+ */
434
+ DurationSeconds?: CredentialTimeoutDurationSecondInteger;
435
+ }
436
+ export interface AssumeDecoratedRoleWithSAMLResponse {
437
+ /**
438
+ * The access key ID for the temporary credentials. (The access key consists of an access key ID and a secret key).
439
+ */
440
+ AccessKeyId?: AccessKeyIdString;
441
+ /**
442
+ * The secret key for the temporary credentials. (The access key consists of an access key ID and a secret key).
443
+ */
444
+ SecretAccessKey?: SecretAccessKeyString;
445
+ /**
446
+ * The session token for the temporary credentials.
447
+ */
448
+ SessionToken?: SessionTokenString;
449
+ /**
450
+ * The date and time when the temporary credentials expire.
451
+ */
452
+ Expiration?: ExpirationTimestamp;
453
+ }
410
454
  export interface AuditContext {
411
455
  /**
412
456
  * The filter engine can populate the 'AdditionalAuditContext' information with the request ID for you to track. This information will be displayed in CloudTrail log in your account.
@@ -1154,6 +1198,7 @@ declare namespace LakeFormation {
1154
1198
  export interface GrantPermissionsResponse {
1155
1199
  }
1156
1200
  export type IAMRoleArn = string;
1201
+ export type IAMSAMLProviderArn = string;
1157
1202
  export type Identifier = string;
1158
1203
  export type Integer = number;
1159
1204
  export interface LFTag {
@@ -1652,6 +1697,7 @@ declare namespace LakeFormation {
1652
1697
  */
1653
1698
  AllRowsWildcard?: AllRowsWildcard;
1654
1699
  }
1700
+ export type SAMLAssertionString = string;
1655
1701
  export interface SearchDatabasesByLFTagsRequest {
1656
1702
  /**
1657
1703
  * A continuation token, if this is not the first call to retrieve this list.