cdk-comprehend-s3olap 2.0.76 → 2.0.79
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/.jsii +3 -3
- package/lib/cdk-comprehend-s3olap.js +2 -2
- package/lib/comprehend-lambdas.js +2 -2
- package/lib/iam-roles.js +4 -4
- package/node_modules/aws-sdk/CHANGELOG.md +15 -1
- package/node_modules/aws-sdk/README.md +1 -1
- package/node_modules/aws-sdk/apis/cloudfront-2020-05-31.min.json +350 -82
- package/node_modules/aws-sdk/apis/config-2014-11-12.min.json +107 -91
- package/node_modules/aws-sdk/apis/iotwireless-2020-11-22.min.json +123 -79
- package/node_modules/aws-sdk/apis/panorama-2019-07-24.min.json +47 -10
- package/node_modules/aws-sdk/apis/quicksight-2018-04-01.min.json +64 -29
- package/node_modules/aws-sdk/apis/rds-2014-10-31.min.json +23 -0
- package/node_modules/aws-sdk/apis/sso-oidc-2019-06-10.min.json +1 -2
- package/node_modules/aws-sdk/clients/cloudfront.d.ts +246 -4
- package/node_modules/aws-sdk/clients/configservice.d.ts +27 -7
- package/node_modules/aws-sdk/clients/elbv2.d.ts +1 -1
- package/node_modules/aws-sdk/clients/gamelift.d.ts +1 -1
- package/node_modules/aws-sdk/clients/iam.d.ts +6 -6
- package/node_modules/aws-sdk/clients/iotwireless.d.ts +60 -11
- package/node_modules/aws-sdk/clients/ivs.d.ts +3 -3
- package/node_modules/aws-sdk/clients/panorama.d.ts +62 -0
- package/node_modules/aws-sdk/clients/quicksight.d.ts +38 -4
- package/node_modules/aws-sdk/clients/rds.d.ts +21 -0
- package/node_modules/aws-sdk/clients/ssoadmin.d.ts +6 -6
- package/node_modules/aws-sdk/clients/ssooidc.d.ts +12 -12
- package/node_modules/aws-sdk/clients/transfer.d.ts +20 -20
- package/node_modules/aws-sdk/dist/aws-sdk-core-react-native.js +1 -1
- package/node_modules/aws-sdk/dist/aws-sdk-react-native.js +8 -8
- package/node_modules/aws-sdk/dist/aws-sdk.js +483 -176
- package/node_modules/aws-sdk/dist/aws-sdk.min.js +85 -85
- package/node_modules/aws-sdk/lib/core.js +1 -1
- package/node_modules/aws-sdk/package.json +1 -1
- package/package.json +6 -6
@@ -461,15 +461,15 @@ declare namespace Transfer {
|
|
461
461
|
export type Arn = string;
|
462
462
|
export interface As2ConnectorConfig {
|
463
463
|
/**
|
464
|
-
* A unique identifier for the AS2
|
464
|
+
* A unique identifier for the AS2 local profile.
|
465
465
|
*/
|
466
466
|
LocalProfileId?: ProfileId;
|
467
467
|
/**
|
468
|
-
* A unique identifier for the partner for the connector.
|
468
|
+
* A unique identifier for the partner profile for the connector.
|
469
469
|
*/
|
470
470
|
PartnerProfileId?: ProfileId;
|
471
471
|
/**
|
472
|
-
*
|
472
|
+
* Used as the Subject HTTP header attribute in AS2 messages that are being sent with the connector.
|
473
473
|
*/
|
474
474
|
MessageSubject?: MessageSubject;
|
475
475
|
/**
|
@@ -481,11 +481,11 @@ declare namespace Transfer {
|
|
481
481
|
*/
|
482
482
|
EncryptionAlgorithm?: EncryptionAlg;
|
483
483
|
/**
|
484
|
-
* The algorithm that is used to sign the AS2
|
484
|
+
* The algorithm that is used to sign the AS2 messages sent with the connector.
|
485
485
|
*/
|
486
486
|
SigningAlgorithm?: SigningAlg;
|
487
487
|
/**
|
488
|
-
* The signing algorithm for the MDN response.
|
488
|
+
* The signing algorithm for the MDN response. If set to DEFAULT (or not set at all), the value for SigningAlogorithm is used.
|
489
489
|
*/
|
490
490
|
MdnSigningAlgorithm?: MdnSigningAlg;
|
491
491
|
/**
|
@@ -590,7 +590,7 @@ declare namespace Transfer {
|
|
590
590
|
*/
|
591
591
|
BaseDirectory: HomeDirectory;
|
592
592
|
/**
|
593
|
-
*
|
593
|
+
* With AS2, you can send files by calling StartFileTransfer and specifying the file paths in the request parameter, SendFilePaths. We use the file’s parent directory (for example, for --send-file-paths /bucket/dir/file.txt, parent directory is /bucket/dir/) to temporarily store a processed AS2 message file, store the MDN when we receive them from the partner, and write a final JSON file containing relevant metadata of the transmission. So, the AccessRole needs to provide read and write access to the parent directory of the file location used in the StartFileTransfer request. Additionally, you need to provide read and write access to the parent directory of the files that you intend to send with StartFileTransfer.
|
594
594
|
*/
|
595
595
|
AccessRole: Role;
|
596
596
|
/**
|
@@ -638,7 +638,7 @@ declare namespace Transfer {
|
|
638
638
|
}
|
639
639
|
export interface CreateProfileRequest {
|
640
640
|
/**
|
641
|
-
* The As2Id is the AS2-name, as defined in the
|
641
|
+
* The As2Id is the AS2-name, as defined in the RFC 4130. For inbound transfers, this is the AS2-From header for the AS2 messages sent from the partner. For outbound connectors, this is the AS2-To header for the AS2 messages sent to the partner using the StartFileTransfer API operation. This ID cannot include spaces.
|
642
642
|
*/
|
643
643
|
As2Id: As2Id;
|
644
644
|
/**
|
@@ -1107,11 +1107,11 @@ declare namespace Transfer {
|
|
1107
1107
|
*/
|
1108
1108
|
ServerId?: ServerId;
|
1109
1109
|
/**
|
1110
|
-
* A unique identifier for the AS2
|
1110
|
+
* A unique identifier for the AS2 local profile.
|
1111
1111
|
*/
|
1112
1112
|
LocalProfileId?: ProfileId;
|
1113
1113
|
/**
|
1114
|
-
* A unique identifier for the partner in the agreement.
|
1114
|
+
* A unique identifier for the partner profile used in the agreement.
|
1115
1115
|
*/
|
1116
1116
|
PartnerProfileId?: ProfileId;
|
1117
1117
|
/**
|
@@ -1119,7 +1119,7 @@ declare namespace Transfer {
|
|
1119
1119
|
*/
|
1120
1120
|
BaseDirectory?: HomeDirectory;
|
1121
1121
|
/**
|
1122
|
-
*
|
1122
|
+
* With AS2, you can send files by calling StartFileTransfer and specifying the file paths in the request parameter, SendFilePaths. We use the file’s parent directory (for example, for --send-file-paths /bucket/dir/file.txt, parent directory is /bucket/dir/) to temporarily store a processed AS2 message file, store the MDN when we receive them from the partner, and write a final JSON file containing relevant metadata of the transmission. So, the AccessRole needs to provide read and write access to the parent directory of the file location used in the StartFileTransfer request. Additionally, you need to provide read and write access to the parent directory of the files that you intend to send with StartFileTransfer.
|
1123
1123
|
*/
|
1124
1124
|
AccessRole?: Role;
|
1125
1125
|
/**
|
@@ -1260,7 +1260,7 @@ declare namespace Transfer {
|
|
1260
1260
|
*/
|
1261
1261
|
ProfileType?: ProfileType;
|
1262
1262
|
/**
|
1263
|
-
* The
|
1263
|
+
* The As2Id is the AS2-name, as defined in the RFC 4130. For inbound transfers, this is the AS2-From header for the AS2 messages sent from the partner. For outbound connectors, this is the AS2-To header for the AS2 messages sent to the partner using the StartFileTransfer API operation. This ID cannot include spaces.
|
1264
1264
|
*/
|
1265
1265
|
As2Id?: As2Id;
|
1266
1266
|
/**
|
@@ -1308,7 +1308,7 @@ declare namespace Transfer {
|
|
1308
1308
|
*/
|
1309
1309
|
Certificate?: Certificate;
|
1310
1310
|
/**
|
1311
|
-
*
|
1311
|
+
* The protocol settings that are configured for your server. To indicate passive mode (for FTP and FTPS protocols), use the PassiveIp parameter. Enter a single dotted-quad IPv4 address, such as the external IP address of a firewall, router, or load balancer. To ignore the error that is generated when the client attempts to use the SETSTAT command on a file that you are uploading to an Amazon S3 bucket, use the SetStatOption parameter. To have the Transfer Family server ignore the SETSTAT command and upload files without needing to make any changes to your SFTP client, set the value to ENABLE_NO_OP. If you set the SetStatOption parameter to ENABLE_NO_OP, Transfer Family generates a log entry to Amazon CloudWatch Logs, so that you can determine when the client is making a SETSTAT call. To determine whether your Transfer Family server resumes recent, negotiated sessions through a unique session ID, use the TlsSessionResumptionMode parameter. As2Transports indicates the transport method for the AS2 messages. Currently, only HTTP is supported.
|
1312
1312
|
*/
|
1313
1313
|
ProtocolDetails?: ProtocolDetails;
|
1314
1314
|
/**
|
@@ -1348,7 +1348,7 @@ declare namespace Transfer {
|
|
1348
1348
|
*/
|
1349
1349
|
PreAuthenticationLoginBanner?: PreAuthenticationLoginBanner;
|
1350
1350
|
/**
|
1351
|
-
* Specifies the file transfer protocol or protocols over which your file transfer protocol client can connect to your server's endpoint. The available protocols are: SFTP (Secure Shell (SSH) File Transfer Protocol): File transfer over SSH FTPS (File Transfer Protocol Secure): File transfer with TLS encryption FTP (File Transfer Protocol): Unencrypted file transfer
|
1351
|
+
* Specifies the file transfer protocol or protocols over which your file transfer protocol client can connect to your server's endpoint. The available protocols are: SFTP (Secure Shell (SSH) File Transfer Protocol): File transfer over SSH FTPS (File Transfer Protocol Secure): File transfer with TLS encryption FTP (File Transfer Protocol): Unencrypted file transfer AS2 (Applicability Statement 2): used for transporting structured business-to-business data If you select FTPS, you must choose a certificate stored in Certificate Manager (ACM) which is used to identify your server when clients connect to it over FTPS. If Protocol includes either FTP or FTPS, then the EndpointType must be VPC and the IdentityProviderType must be AWS_DIRECTORY_SERVICE or API_GATEWAY. If Protocol includes FTP, then AddressAllocationIds cannot be associated. If Protocol is set only to SFTP, the EndpointType can be set to PUBLIC and the IdentityProviderType can be set to SERVICE_MANAGED. If Protocol includes AS2, then the EndpointType must be VPC, and domain must be Amazon S3.
|
1352
1352
|
*/
|
1353
1353
|
Protocols?: Protocols;
|
1354
1354
|
/**
|
@@ -1950,11 +1950,11 @@ declare namespace Transfer {
|
|
1950
1950
|
*/
|
1951
1951
|
ServerId?: ServerId;
|
1952
1952
|
/**
|
1953
|
-
* A unique identifier for the AS2
|
1953
|
+
* A unique identifier for the AS2 local profile.
|
1954
1954
|
*/
|
1955
1955
|
LocalProfileId?: ProfileId;
|
1956
1956
|
/**
|
1957
|
-
* A unique identifier for the partner
|
1957
|
+
* A unique identifier for the partner profile.
|
1958
1958
|
*/
|
1959
1959
|
PartnerProfileId?: ProfileId;
|
1960
1960
|
}
|
@@ -2038,7 +2038,7 @@ declare namespace Transfer {
|
|
2038
2038
|
*/
|
2039
2039
|
ProfileId?: ProfileId;
|
2040
2040
|
/**
|
2041
|
-
* The
|
2041
|
+
* The As2Id is the AS2-name, as defined in the RFC 4130. For inbound transfers, this is the AS2-From header for the AS2 messages sent from the partner. For outbound connectors, this is the AS2-To header for the AS2 messages sent to the partner using the StartFileTransfer API operation. This ID cannot include spaces.
|
2042
2042
|
*/
|
2043
2043
|
As2Id?: As2Id;
|
2044
2044
|
/**
|
@@ -2474,11 +2474,11 @@ declare namespace Transfer {
|
|
2474
2474
|
*/
|
2475
2475
|
Status?: AgreementStatusType;
|
2476
2476
|
/**
|
2477
|
-
* To change the local profile identifier, provide a new value here.
|
2477
|
+
* A unique identifier for the AS2 local profile. To change the local profile identifier, provide a new value here.
|
2478
2478
|
*/
|
2479
2479
|
LocalProfileId?: ProfileId;
|
2480
2480
|
/**
|
2481
|
-
* To change the partner profile identifier, provide a new value here.
|
2481
|
+
* A unique identifier for the partner profile. To change the partner profile identifier, provide a new value here.
|
2482
2482
|
*/
|
2483
2483
|
PartnerProfileId?: ProfileId;
|
2484
2484
|
/**
|
@@ -2486,7 +2486,7 @@ declare namespace Transfer {
|
|
2486
2486
|
*/
|
2487
2487
|
BaseDirectory?: HomeDirectory;
|
2488
2488
|
/**
|
2489
|
-
*
|
2489
|
+
* With AS2, you can send files by calling StartFileTransfer and specifying the file paths in the request parameter, SendFilePaths. We use the file’s parent directory (for example, for --send-file-paths /bucket/dir/file.txt, parent directory is /bucket/dir/) to temporarily store a processed AS2 message file, store the MDN when we receive them from the partner, and write a final JSON file containing relevant metadata of the transmission. So, the AccessRole needs to provide read and write access to the parent directory of the file location used in the StartFileTransfer request. Additionally, you need to provide read and write access to the parent directory of the files that you intend to send with StartFileTransfer.
|
2490
2490
|
*/
|
2491
2491
|
AccessRole?: Role;
|
2492
2492
|
}
|
@@ -2602,7 +2602,7 @@ declare namespace Transfer {
|
|
2602
2602
|
*/
|
2603
2603
|
PreAuthenticationLoginBanner?: PreAuthenticationLoginBanner;
|
2604
2604
|
/**
|
2605
|
-
* Specifies the file transfer protocol or protocols over which your file transfer protocol client can connect to your server's endpoint. The available protocols are:
|
2605
|
+
* Specifies the file transfer protocol or protocols over which your file transfer protocol client can connect to your server's endpoint. The available protocols are: SFTP (Secure Shell (SSH) File Transfer Protocol): File transfer over SSH FTPS (File Transfer Protocol Secure): File transfer with TLS encryption FTP (File Transfer Protocol): Unencrypted file transfer AS2 (Applicability Statement 2): used for transporting structured business-to-business data If you select FTPS, you must choose a certificate stored in Certificate Manager (ACM) which is used to identify your server when clients connect to it over FTPS. If Protocol includes either FTP or FTPS, then the EndpointType must be VPC and the IdentityProviderType must be AWS_DIRECTORY_SERVICE or API_GATEWAY. If Protocol includes FTP, then AddressAllocationIds cannot be associated. If Protocol is set only to SFTP, the EndpointType can be set to PUBLIC and the IdentityProviderType can be set to SERVICE_MANAGED. If Protocol includes AS2, then the EndpointType must be VPC, and domain must be Amazon S3.
|
2606
2606
|
*/
|
2607
2607
|
Protocols?: Protocols;
|
2608
2608
|
/**
|