cdk-comprehend-s3olap 2.0.14 → 2.0.17

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 (33) hide show
  1. package/.jsii +3 -3
  2. package/lib/cdk-comprehend-s3olap.js +2 -2
  3. package/lib/comprehend-lambdas.js +2 -2
  4. package/lib/iam-roles.js +4 -4
  5. package/node_modules/aws-sdk/CHANGELOG.md +15 -1
  6. package/node_modules/aws-sdk/README.md +1 -1
  7. package/node_modules/aws-sdk/apis/ec2-2016-11-15.min.json +11 -4
  8. package/node_modules/aws-sdk/apis/lookoutequipment-2020-12-15.min.json +54 -5
  9. package/node_modules/aws-sdk/apis/lookoutequipment-2020-12-15.paginators.json +5 -0
  10. package/node_modules/aws-sdk/apis/mgn-2020-02-26.min.json +233 -44
  11. package/node_modules/aws-sdk/apis/mgn-2020-02-26.paginators.json +6 -0
  12. package/node_modules/aws-sdk/apis/migration-hub-refactor-spaces-2021-10-26.min.json +75 -25
  13. package/node_modules/aws-sdk/apis/pricing-2017-10-15.min.json +6 -0
  14. package/node_modules/aws-sdk/apis/sagemaker-2017-07-24.min.json +231 -182
  15. package/node_modules/aws-sdk/apis/wellarchitected-2020-03-31.min.json +39 -22
  16. package/node_modules/aws-sdk/clients/apigateway.d.ts +1 -1
  17. package/node_modules/aws-sdk/clients/ec2.d.ts +25 -5
  18. package/node_modules/aws-sdk/clients/ecs.d.ts +40 -40
  19. package/node_modules/aws-sdk/clients/lookoutequipment.d.ts +69 -1
  20. package/node_modules/aws-sdk/clients/mediaconvert.d.ts +1 -1
  21. package/node_modules/aws-sdk/clients/mgn.d.ts +218 -3
  22. package/node_modules/aws-sdk/clients/migrationhubrefactorspaces.d.ts +70 -8
  23. package/node_modules/aws-sdk/clients/pricing.d.ts +4 -4
  24. package/node_modules/aws-sdk/clients/sagemaker.d.ts +69 -8
  25. package/node_modules/aws-sdk/clients/transfer.d.ts +9 -9
  26. package/node_modules/aws-sdk/clients/wellarchitected.d.ts +28 -7
  27. package/node_modules/aws-sdk/dist/aws-sdk-core-react-native.js +1 -1
  28. package/node_modules/aws-sdk/dist/aws-sdk-react-native.js +10 -10
  29. package/node_modules/aws-sdk/dist/aws-sdk.js +20 -7
  30. package/node_modules/aws-sdk/dist/aws-sdk.min.js +60 -60
  31. package/node_modules/aws-sdk/lib/core.js +1 -1
  32. package/node_modules/aws-sdk/package.json +1 -1
  33. package/package.json +4 -4
@@ -237,11 +237,11 @@ declare class SageMaker extends Service {
237
237
  */
238
238
  createLabelingJob(callback?: (err: AWSError, data: SageMaker.Types.CreateLabelingJobResponse) => void): Request<SageMaker.Types.CreateLabelingJobResponse, AWSError>;
239
239
  /**
240
- * Creates a model in SageMaker. In the request, you name the model and describe a primary container. For the primary container, you specify the Docker image that contains inference code, artifacts (from prior training), and a custom environment map that the inference code uses when you deploy the model for predictions. Use this API to create a model if you want to use SageMaker hosting services or run a batch transform job. To host your model, you create an endpoint configuration with the CreateEndpointConfig API, and then create an endpoint with the CreateEndpoint API. SageMaker then deploys all of the containers that you defined for the model in the hosting environment. For an example that calls this method when deploying a model to SageMaker hosting services, see Deploy the Model to Amazon SageMaker Hosting Services (Amazon Web Services SDK for Python (Boto 3)). To run a batch transform using your model, you start a job with the CreateTransformJob API. SageMaker uses your model and your dataset to get inferences which are then saved to a specified S3 location. In the request, you also provide an IAM role that SageMaker can assume to access model artifacts and docker image for deployment on ML compute hosting instances or for batch transform jobs. In addition, you also use the IAM role to manage permissions the inference code needs. For example, if the inference code access any other Amazon Web Services resources, you grant necessary permissions via this role.
240
+ * Creates a model in SageMaker. In the request, you name the model and describe a primary container. For the primary container, you specify the Docker image that contains inference code, artifacts (from prior training), and a custom environment map that the inference code uses when you deploy the model for predictions. Use this API to create a model if you want to use SageMaker hosting services or run a batch transform job. To host your model, you create an endpoint configuration with the CreateEndpointConfig API, and then create an endpoint with the CreateEndpoint API. SageMaker then deploys all of the containers that you defined for the model in the hosting environment. For an example that calls this method when deploying a model to SageMaker hosting services, see Create a Model (Amazon Web Services SDK for Python (Boto 3)). To run a batch transform using your model, you start a job with the CreateTransformJob API. SageMaker uses your model and your dataset to get inferences which are then saved to a specified S3 location. In the request, you also provide an IAM role that SageMaker can assume to access model artifacts and docker image for deployment on ML compute hosting instances or for batch transform jobs. In addition, you also use the IAM role to manage permissions the inference code needs. For example, if the inference code access any other Amazon Web Services resources, you grant necessary permissions via this role.
241
241
  */
242
242
  createModel(params: SageMaker.Types.CreateModelInput, callback?: (err: AWSError, data: SageMaker.Types.CreateModelOutput) => void): Request<SageMaker.Types.CreateModelOutput, AWSError>;
243
243
  /**
244
- * Creates a model in SageMaker. In the request, you name the model and describe a primary container. For the primary container, you specify the Docker image that contains inference code, artifacts (from prior training), and a custom environment map that the inference code uses when you deploy the model for predictions. Use this API to create a model if you want to use SageMaker hosting services or run a batch transform job. To host your model, you create an endpoint configuration with the CreateEndpointConfig API, and then create an endpoint with the CreateEndpoint API. SageMaker then deploys all of the containers that you defined for the model in the hosting environment. For an example that calls this method when deploying a model to SageMaker hosting services, see Deploy the Model to Amazon SageMaker Hosting Services (Amazon Web Services SDK for Python (Boto 3)). To run a batch transform using your model, you start a job with the CreateTransformJob API. SageMaker uses your model and your dataset to get inferences which are then saved to a specified S3 location. In the request, you also provide an IAM role that SageMaker can assume to access model artifacts and docker image for deployment on ML compute hosting instances or for batch transform jobs. In addition, you also use the IAM role to manage permissions the inference code needs. For example, if the inference code access any other Amazon Web Services resources, you grant necessary permissions via this role.
244
+ * Creates a model in SageMaker. In the request, you name the model and describe a primary container. For the primary container, you specify the Docker image that contains inference code, artifacts (from prior training), and a custom environment map that the inference code uses when you deploy the model for predictions. Use this API to create a model if you want to use SageMaker hosting services or run a batch transform job. To host your model, you create an endpoint configuration with the CreateEndpointConfig API, and then create an endpoint with the CreateEndpoint API. SageMaker then deploys all of the containers that you defined for the model in the hosting environment. For an example that calls this method when deploying a model to SageMaker hosting services, see Create a Model (Amazon Web Services SDK for Python (Boto 3)). To run a batch transform using your model, you start a job with the CreateTransformJob API. SageMaker uses your model and your dataset to get inferences which are then saved to a specified S3 location. In the request, you also provide an IAM role that SageMaker can assume to access model artifacts and docker image for deployment on ML compute hosting instances or for batch transform jobs. In addition, you also use the IAM role to manage permissions the inference code needs. For example, if the inference code access any other Amazon Web Services resources, you grant necessary permissions via this role.
245
245
  */
246
246
  createModel(callback?: (err: AWSError, data: SageMaker.Types.CreateModelOutput) => void): Request<SageMaker.Types.CreateModelOutput, AWSError>;
247
247
  /**
@@ -2005,11 +2005,11 @@ declare class SageMaker extends Service {
2005
2005
  */
2006
2006
  updateUserProfile(callback?: (err: AWSError, data: SageMaker.Types.UpdateUserProfileResponse) => void): Request<SageMaker.Types.UpdateUserProfileResponse, AWSError>;
2007
2007
  /**
2008
- * Use this operation to update your workforce. You can use this operation to require that workers use specific IP addresses to work on tasks and to update your OpenID Connect (OIDC) Identity Provider (IdP) workforce configuration. Use SourceIpConfig to restrict worker access to tasks to a specific range of IP addresses. You specify allowed IP addresses by creating a list of up to ten CIDRs. By default, a workforce isn't restricted to specific IP addresses. If you specify a range of IP addresses, workers who attempt to access tasks using any IP address outside the specified range are denied and get a Not Found error message on the worker portal. Use OidcConfig to update the configuration of a workforce created using your own OIDC IdP. You can only update your OIDC IdP configuration when there are no work teams associated with your workforce. You can delete work teams using the operation. After restricting access to a range of IP addresses or updating your OIDC IdP configuration with this operation, you can view details about your update workforce using the operation. This operation only applies to private workforces.
2008
+ * Use this operation to update your workforce. You can use this operation to require that workers use specific IP addresses to work on tasks and to update your OpenID Connect (OIDC) Identity Provider (IdP) workforce configuration. The worker portal is now supported in VPC and public internet. Use SourceIpConfig to restrict worker access to tasks to a specific range of IP addresses. You specify allowed IP addresses by creating a list of up to ten CIDRs. By default, a workforce isn't restricted to specific IP addresses. If you specify a range of IP addresses, workers who attempt to access tasks using any IP address outside the specified range are denied and get a Not Found error message on the worker portal. To restrict access to all the workers in public internet, add the SourceIpConfig CIDR value as "0.0.0.0/0". Amazon SageMaker does not support Source Ip restriction for worker portals in VPC. Use OidcConfig to update the configuration of a workforce created using your own OIDC IdP. You can only update your OIDC IdP configuration when there are no work teams associated with your workforce. You can delete work teams using the operation. After restricting access to a range of IP addresses or updating your OIDC IdP configuration with this operation, you can view details about your update workforce using the operation. This operation only applies to private workforces.
2009
2009
  */
2010
2010
  updateWorkforce(params: SageMaker.Types.UpdateWorkforceRequest, callback?: (err: AWSError, data: SageMaker.Types.UpdateWorkforceResponse) => void): Request<SageMaker.Types.UpdateWorkforceResponse, AWSError>;
2011
2011
  /**
2012
- * Use this operation to update your workforce. You can use this operation to require that workers use specific IP addresses to work on tasks and to update your OpenID Connect (OIDC) Identity Provider (IdP) workforce configuration. Use SourceIpConfig to restrict worker access to tasks to a specific range of IP addresses. You specify allowed IP addresses by creating a list of up to ten CIDRs. By default, a workforce isn't restricted to specific IP addresses. If you specify a range of IP addresses, workers who attempt to access tasks using any IP address outside the specified range are denied and get a Not Found error message on the worker portal. Use OidcConfig to update the configuration of a workforce created using your own OIDC IdP. You can only update your OIDC IdP configuration when there are no work teams associated with your workforce. You can delete work teams using the operation. After restricting access to a range of IP addresses or updating your OIDC IdP configuration with this operation, you can view details about your update workforce using the operation. This operation only applies to private workforces.
2012
+ * Use this operation to update your workforce. You can use this operation to require that workers use specific IP addresses to work on tasks and to update your OpenID Connect (OIDC) Identity Provider (IdP) workforce configuration. The worker portal is now supported in VPC and public internet. Use SourceIpConfig to restrict worker access to tasks to a specific range of IP addresses. You specify allowed IP addresses by creating a list of up to ten CIDRs. By default, a workforce isn't restricted to specific IP addresses. If you specify a range of IP addresses, workers who attempt to access tasks using any IP address outside the specified range are denied and get a Not Found error message on the worker portal. To restrict access to all the workers in public internet, add the SourceIpConfig CIDR value as "0.0.0.0/0". Amazon SageMaker does not support Source Ip restriction for worker portals in VPC. Use OidcConfig to update the configuration of a workforce created using your own OIDC IdP. You can only update your OIDC IdP configuration when there are no work teams associated with your workforce. You can delete work teams using the operation. After restricting access to a range of IP addresses or updating your OIDC IdP configuration with this operation, you can view details about your update workforce using the operation. This operation only applies to private workforces.
2013
2013
  */
2014
2014
  updateWorkforce(callback?: (err: AWSError, data: SageMaker.Types.UpdateWorkforceResponse) => void): Request<SageMaker.Types.UpdateWorkforceResponse, AWSError>;
2015
2015
  /**
@@ -2726,7 +2726,7 @@ declare namespace SageMaker {
2726
2726
  export type AutoMLContainerDefinitions = AutoMLContainerDefinition[];
2727
2727
  export interface AutoMLDataSource {
2728
2728
  /**
2729
- * The Amazon S3 location of the input data. The input data must be in CSV format and contain at least 500 rows.
2729
+ * The Amazon S3 location of the input data.
2730
2730
  */
2731
2731
  S3DataSource: AutoMLS3DataSource;
2732
2732
  }
@@ -2853,7 +2853,7 @@ declare namespace SageMaker {
2853
2853
  export type AutoMLPartialFailureReasons = AutoMLPartialFailureReason[];
2854
2854
  export interface AutoMLS3DataSource {
2855
2855
  /**
2856
- * The data type.
2856
+ * The data type. A ManifestFile should have the format shown below: [ {"prefix": "s3://DOC-EXAMPLE-BUCKET/DOC-EXAMPLE-FOLDER/DOC-EXAMPLE-PREFIX/"}, "DOC-EXAMPLE-RELATIVE-PATH/DOC-EXAMPLE-FOLDER/DATA-1", "DOC-EXAMPLE-RELATIVE-PATH/DOC-EXAMPLE-FOLDER/DATA-2", ... "DOC-EXAMPLE-RELATIVE-PATH/DOC-EXAMPLE-FOLDER/DATA-N" ] An S3Prefix should have the following format: s3://DOC-EXAMPLE-BUCKET/DOC-EXAMPLE-FOLDER-OR-FILE
2857
2857
  */
2858
2858
  S3DataType: AutoMLS3DataType;
2859
2859
  /**
@@ -3557,7 +3557,7 @@ declare namespace SageMaker {
3557
3557
  */
3558
3558
  Tags?: TagList;
3559
3559
  /**
3560
- * The instance type and the Amazon Resource Name (ARN) of the SageMaker image created on the instance.
3560
+ * The instance type and the Amazon Resource Name (ARN) of the SageMaker image created on the instance. The value of InstanceType passed as part of the ResourceSpec in the CreateApp call overrides the value passed as part of the ResourceSpec configured for the user profile or the domain. If InstanceType is not specified in any of those three ResourceSpec values for a KernelGateway app, the CreateApp call fails with a request validation error.
3561
3561
  */
3562
3562
  ResourceSpec?: ResourceSpec;
3563
3563
  }
@@ -5042,6 +5042,10 @@ declare namespace SageMaker {
5042
5042
  * An array of key-value pairs that contain metadata to help you categorize and organize our workforce. Each tag consists of a key and a value, both of which you define.
5043
5043
  */
5044
5044
  Tags?: TagList;
5045
+ /**
5046
+ * Use this parameter to configure a workforce using VPC.
5047
+ */
5048
+ WorkforceVpcConfig?: WorkforceVpcConfigRequest;
5045
5049
  }
5046
5050
  export interface CreateWorkforceResponse {
5047
5051
  /**
@@ -10162,6 +10166,7 @@ declare namespace SageMaker {
10162
10166
  * The Amazon Web Services Key Management Service (Amazon Web Services KMS) key that Amazon SageMaker uses to encrypt data on the storage volume attached to the ML compute instance(s) that run the training and inference jobs used for automated data labeling. You can only specify a VolumeKmsKeyId when you create a labeling job with automated data labeling enabled using the API operation CreateLabelingJob. You cannot specify an Amazon Web Services KMS key to encrypt the storage volume used for automated data labeling model training and inference when you create a labeling job using the console. To learn more, see Output Data and Storage Volume Encryption. The VolumeKmsKeyId can be any of the following formats: KMS Key ID "1234abcd-12ab-34cd-56ef-1234567890ab" Amazon Resource Name (ARN) of a KMS Key "arn:aws:kms:us-west-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab"
10163
10167
  */
10164
10168
  VolumeKmsKeyId?: KmsKeyId;
10169
+ VpcConfig?: VpcConfig;
10165
10170
  }
10166
10171
  export interface LabelingJobS3DataSource {
10167
10172
  /**
@@ -15479,7 +15484,7 @@ declare namespace SageMaker {
15479
15484
  */
15480
15485
  SageMakerImageVersionArn?: ImageVersionArn;
15481
15486
  /**
15482
- * The instance type that the image version runs on. JupyterServer Apps only support the system value. KernelGateway Apps do not support the system value, but support all other values for available instance types.
15487
+ * The instance type that the image version runs on. JupyterServer apps only support the system value. For KernelGateway apps, the system value is translated to ml.t3.medium. KernelGateway apps also support all other values for available instance types.
15483
15488
  */
15484
15489
  InstanceType?: AppInstanceType;
15485
15490
  /**
@@ -17563,6 +17568,10 @@ declare namespace SageMaker {
17563
17568
  * Use this parameter to update your OIDC Identity Provider (IdP) configuration for a workforce made using your own IdP.
17564
17569
  */
17565
17570
  OidcConfig?: OidcConfig;
17571
+ /**
17572
+ * Use this parameter to update your VPC configuration for a workforce.
17573
+ */
17574
+ WorkforceVpcConfig?: WorkforceVpcConfigRequest;
17566
17575
  }
17567
17576
  export interface UpdateWorkforceResponse {
17568
17577
  /**
@@ -17747,9 +17756,61 @@ declare namespace SageMaker {
17747
17756
  * The date that the workforce is created.
17748
17757
  */
17749
17758
  CreateDate?: Timestamp;
17759
+ /**
17760
+ * The configuration of a VPC workforce.
17761
+ */
17762
+ WorkforceVpcConfig?: WorkforceVpcConfigResponse;
17763
+ /**
17764
+ * The status of your workforce.
17765
+ */
17766
+ Status?: WorkforceStatus;
17767
+ /**
17768
+ * The reason your workforce failed.
17769
+ */
17770
+ FailureReason?: WorkforceFailureReason;
17750
17771
  }
17751
17772
  export type WorkforceArn = string;
17773
+ export type WorkforceFailureReason = string;
17752
17774
  export type WorkforceName = string;
17775
+ export type WorkforceSecurityGroupId = string;
17776
+ export type WorkforceSecurityGroupIds = WorkforceSecurityGroupId[];
17777
+ export type WorkforceStatus = "Initializing"|"Updating"|"Deleting"|"Failed"|"Active"|string;
17778
+ export type WorkforceSubnetId = string;
17779
+ export type WorkforceSubnets = WorkforceSubnetId[];
17780
+ export interface WorkforceVpcConfigRequest {
17781
+ /**
17782
+ * The ID of the VPC that the workforce uses for communication.
17783
+ */
17784
+ VpcId?: WorkforceVpcId;
17785
+ /**
17786
+ * The VPC security group IDs, in the form sg-xxxxxxxx. The security groups must be for the same VPC as specified in the subnet.
17787
+ */
17788
+ SecurityGroupIds?: WorkforceSecurityGroupIds;
17789
+ /**
17790
+ * The ID of the subnets in the VPC that you want to connect.
17791
+ */
17792
+ Subnets?: WorkforceSubnets;
17793
+ }
17794
+ export interface WorkforceVpcConfigResponse {
17795
+ /**
17796
+ * The ID of the VPC that the workforce uses for communication.
17797
+ */
17798
+ VpcId: WorkforceVpcId;
17799
+ /**
17800
+ * The VPC security group IDs, in the form sg-xxxxxxxx. The security groups must be for the same VPC as specified in the subnet.
17801
+ */
17802
+ SecurityGroupIds: WorkforceSecurityGroupIds;
17803
+ /**
17804
+ * The ID of the subnets in the VPC that you want to connect.
17805
+ */
17806
+ Subnets: WorkforceSubnets;
17807
+ /**
17808
+ * The IDs for the VPC service endpoints of your VPC workforce when it is created and updated.
17809
+ */
17810
+ VpcEndpointId?: WorkforceVpcEndpointId;
17811
+ }
17812
+ export type WorkforceVpcEndpointId = string;
17813
+ export type WorkforceVpcId = string;
17753
17814
  export type Workforces = Workforce[];
17754
17815
  export interface Workteam {
17755
17816
  /**
@@ -368,7 +368,7 @@ declare namespace Transfer {
368
368
  */
369
369
  EndpointType?: EndpointType;
370
370
  /**
371
- * The RSA private key as generated by the ssh-keygen -N "" -m PEM -f my-new-server-key command. If you aren't planning to migrate existing users from an existing SFTP-enabled server to a new server, don't update the host key. Accidentally changing a server's host key can be disruptive. For more information, see Change the host key for your SFTP-enabled server in the Amazon Web Services Transfer Family User Guide.
371
+ * The RSA, ECDSA, or ED25519 private key to use for your server. Use the following command to generate an RSA 2048 bit key with no passphrase: ssh-keygen -t rsa -b 2048 -N "" -m PEM -f my-new-server-key. Use a minimum value of 2048 for the -b option: you can create a stronger key using 3072 or 4096. Use the following command to generate an ECDSA 256 bit key with no passphrase: ssh-keygen -t ecdsa -b 256 -N "" -m PEM -f my-new-server-key. Valid values for the -b option for ECDSA are 256, 384, and 521. Use the following command to generate an ED25519 key with no passphrase: ssh-keygen -t ed25519 -N "" -f my-new-server-key. For all of these commands, you can replace my-new-server-key with a string of your choice. If you aren't planning to migrate existing users from an existing SFTP-enabled server to a new server, don't update the host key. Accidentally changing a server's host key can be disruptive. For more information, see Change the host key for your SFTP-enabled server in the Amazon Web Services Transfer Family User Guide.
372
372
  */
373
373
  HostKey?: HostKey;
374
374
  /**
@@ -448,7 +448,7 @@ declare namespace Transfer {
448
448
  */
449
449
  ServerId: ServerId;
450
450
  /**
451
- * The public portion of the Secure Shell (SSH) key used to authenticate the user to the server. Currently, Transfer Family does not accept elliptical curve keys (keys beginning with ecdsa).
451
+ * The public portion of the Secure Shell (SSH) key used to authenticate the user to the server. Transfer Family accepts RSA, ECDSA, and ED25519 keys.
452
452
  */
453
453
  SshPublicKeyBody?: SshPublicKeyBody;
454
454
  /**
@@ -762,7 +762,7 @@ declare namespace Transfer {
762
762
  */
763
763
  Certificate?: Certificate;
764
764
  /**
765
- * The protocol settings that are configured for your server. Use the PassiveIp parameter to indicate passive mode. Enter a single dotted-quad IPv4 address, such as the external IP address of a firewall, router, or load balancer.
765
+ * The protocol settings that are configured for your server. Use the PassiveIp parameter to indicate passive mode. Enter a single IPv4 address, such as the public IP address of a firewall, router, or load balancer.
766
766
  */
767
767
  ProtocolDetails?: ProtocolDetails;
768
768
  /**
@@ -1027,7 +1027,7 @@ declare namespace Transfer {
1027
1027
  */
1028
1028
  ServerId: ServerId;
1029
1029
  /**
1030
- * The public key portion of an SSH key pair.
1030
+ * The public key portion of an SSH key pair. Transfer Family accepts RSA, ECDSA, and ED25519 keys.
1031
1031
  */
1032
1032
  SshPublicKeyBody: SshPublicKeyBody;
1033
1033
  /**
@@ -1387,15 +1387,15 @@ declare namespace Transfer {
1387
1387
  export type Protocol = "SFTP"|"FTP"|"FTPS"|string;
1388
1388
  export interface ProtocolDetails {
1389
1389
  /**
1390
- * Indicates passive mode, for FTP and FTPS protocols. Enter a single dotted-quad IPv4 address, such as the external IP address of a firewall, router, or load balancer. For example: aws transfer update-server --protocol-details PassiveIp=0.0.0.0 Replace 0.0.0.0 in the example above with the actual IP address you want to use. If you change the PassiveIp value, you must stop and then restart your Transfer server for the change to take effect. For details on using Passive IP (PASV) in a NAT environment, see Configuring your FTPS server behind a firewall or NAT with Amazon Web Services Transfer Family.
1390
+ * Indicates passive mode, for FTP and FTPS protocols. Enter a single IPv4 address, such as the public IP address of a firewall, router, or load balancer. For example: aws transfer update-server --protocol-details PassiveIp=0.0.0.0 Replace 0.0.0.0 in the example above with the actual IP address you want to use. If you change the PassiveIp value, you must stop and then restart your Transfer Family server for the change to take effect. For details on using passive mode (PASV) in a NAT environment, see Configuring your FTPS server behind a firewall or NAT with Transfer Family.
1391
1391
  */
1392
1392
  PassiveIp?: PassiveIp;
1393
1393
  /**
1394
- * A property used with Transfer servers that use the FTPS protocol. TLS Session Resumption provides a mechanism to resume or share a negotiated secret key between the control and data connection for an FTPS session. TlsSessionResumptionMode determines whether or not the server resumes recent, negotiated sessions through a unique session ID. This property is available during CreateServer and UpdateServer calls. If a TlsSessionResumptionMode value is not specified during CreateServer, it is set to ENFORCED by default. DISABLED: the server does not process TLS session resumption client requests and creates a new TLS session for each request. ENABLED: the server processes and accepts clients that are performing TLS session resumption. The server doesn't reject client data connections that do not perform the TLS session resumption client processing. ENFORCED: the server processes and accepts clients that are performing TLS session resumption. The server rejects client data connections that do not perform the TLS session resumption client processing. Before you set the value to ENFORCED, test your clients. Not all FTPS clients perform TLS session resumption. So, if you choose to enforce TLS session resumption, you prevent any connections from FTPS clients that don't perform the protocol negotiation. To determine whether or not you can use the ENFORCED value, you need to test your clients.
1394
+ * A property used with Transfer Family servers that use the FTPS protocol. TLS Session Resumption provides a mechanism to resume or share a negotiated secret key between the control and data connection for an FTPS session. TlsSessionResumptionMode determines whether or not the server resumes recent, negotiated sessions through a unique session ID. This property is available during CreateServer and UpdateServer calls. If a TlsSessionResumptionMode value is not specified during CreateServer, it is set to ENFORCED by default. DISABLED: the server does not process TLS session resumption client requests and creates a new TLS session for each request. ENABLED: the server processes and accepts clients that are performing TLS session resumption. The server doesn't reject client data connections that do not perform the TLS session resumption client processing. ENFORCED: the server processes and accepts clients that are performing TLS session resumption. The server rejects client data connections that do not perform the TLS session resumption client processing. Before you set the value to ENFORCED, test your clients. Not all FTPS clients perform TLS session resumption. So, if you choose to enforce TLS session resumption, you prevent any connections from FTPS clients that don't perform the protocol negotiation. To determine whether or not you can use the ENFORCED value, you need to test your clients.
1395
1395
  */
1396
1396
  TlsSessionResumptionMode?: TlsSessionResumptionMode;
1397
1397
  /**
1398
- * Use the SetStatOption to ignore the error that is generated when the client attempts to use SETSTAT on a file you are uploading to an S3 bucket. Some SFTP file transfer clients can attempt to change the attributes of remote files, including timestamp and permissions, using commands, such as SETSTAT when uploading the file. However, these commands are not compatible with object storage systems, such as Amazon S3. Due to this incompatibility, file uploads from these clients can result in errors even when the file is otherwise successfully uploaded. Set the value to ENABLE_NO_OP to have the Transfer Family server ignore the SETSTAT command, and upload files without needing to make any changes to your SFTP client. While the SetStatOption ENABLE_NO_OP setting ignores the error, it does generate a log entry in CloudWatch Logs, so you can determine when the client is making a SETSTAT call. If you want to preserve the original timestamp for your file, and modify other file attributes using SETSTAT, you can use Amazon EFS as backend storage with Transfer Family.
1398
+ * Use the SetStatOption to ignore the error that is generated when the client attempts to use SETSTAT on a file you are uploading to an S3 bucket. Some SFTP file transfer clients can attempt to change the attributes of remote files, including timestamp and permissions, using commands, such as SETSTAT when uploading the file. However, these commands are not compatible with object storage systems, such as Amazon S3. Due to this incompatibility, file uploads from these clients can result in errors even when the file is otherwise successfully uploaded. Set the value to ENABLE_NO_OP to have the Transfer Family server ignore the SETSTAT command, and upload files without needing to make any changes to your SFTP client. While the SetStatOption ENABLE_NO_OP setting ignores the error, it does generate a log entry in Amazon CloudWatch Logs, so you can determine when the client is making a SETSTAT call. If you want to preserve the original timestamp for your file, and modify other file attributes using SETSTAT, you can use Amazon EFS as backend storage with Transfer Family.
1399
1399
  */
1400
1400
  SetStatOption?: SetStatOption;
1401
1401
  }
@@ -1491,7 +1491,7 @@ declare namespace Transfer {
1491
1491
  */
1492
1492
  DateImported: DateImported;
1493
1493
  /**
1494
- * Specifies the content of the SSH public key as specified by the PublicKeyId.
1494
+ * Specifies the content of the SSH public key as specified by the PublicKeyId. Transfer Family accepts RSA, ECDSA, and ED25519 keys.
1495
1495
  */
1496
1496
  SshPublicKeyBody: SshPublicKeyBody;
1497
1497
  /**
@@ -1668,7 +1668,7 @@ declare namespace Transfer {
1668
1668
  */
1669
1669
  EndpointType?: EndpointType;
1670
1670
  /**
1671
- * The RSA private key as generated by ssh-keygen -N "" -m PEM -f my-new-server-key. If you aren't planning to migrate existing users from an existing server to a new server, don't update the host key. Accidentally changing a server's host key can be disruptive. For more information, see Change the host key for your SFTP-enabled server in the Amazon Web ServicesTransfer Family User Guide.
1671
+ * The RSA, ECDSA, or ED25519 private key to use for your server. Use the following command to generate an RSA 2048 bit key with no passphrase: ssh-keygen -t rsa -b 2048 -N "" -m PEM -f my-new-server-key. Use a minimum value of 2048 for the -b option: you can create a stronger key using 3072 or 4096. Use the following command to generate an ECDSA 256 bit key with no passphrase: ssh-keygen -t ecdsa -b 256 -N "" -m PEM -f my-new-server-key. Valid values for the -b option for ECDSA are 256, 384, and 521. Use the following command to generate an ED25519 key with no passphrase: ssh-keygen -t ed25519 -N "" -f my-new-server-key. For all of these commands, you can replace my-new-server-key with a string of your choice. If you aren't planning to migrate existing users from an existing SFTP-enabled server to a new server, don't update the host key. Accidentally changing a server's host key can be disruptive. For more information, see Change the host key for your SFTP-enabled server in the Amazon Web Services Transfer Family User Guide.
1672
1672
  */
1673
1673
  HostKey?: HostKey;
1674
1674
  /**
@@ -236,11 +236,11 @@ declare class WellArchitected extends Service {
236
236
  */
237
237
  listShareInvitations(callback?: (err: AWSError, data: WellArchitected.Types.ListShareInvitationsOutput) => void): Request<WellArchitected.Types.ListShareInvitationsOutput, AWSError>;
238
238
  /**
239
- * List the tags for a resource.
239
+ * List the tags for a resource. The WorkloadArn parameter can be either a workload ARN or a custom lens ARN.
240
240
  */
241
241
  listTagsForResource(params: WellArchitected.Types.ListTagsForResourceInput, callback?: (err: AWSError, data: WellArchitected.Types.ListTagsForResourceOutput) => void): Request<WellArchitected.Types.ListTagsForResourceOutput, AWSError>;
242
242
  /**
243
- * List the tags for a resource.
243
+ * List the tags for a resource. The WorkloadArn parameter can be either a workload ARN or a custom lens ARN.
244
244
  */
245
245
  listTagsForResource(callback?: (err: AWSError, data: WellArchitected.Types.ListTagsForResourceOutput) => void): Request<WellArchitected.Types.ListTagsForResourceOutput, AWSError>;
246
246
  /**
@@ -260,19 +260,19 @@ declare class WellArchitected extends Service {
260
260
  */
261
261
  listWorkloads(callback?: (err: AWSError, data: WellArchitected.Types.ListWorkloadsOutput) => void): Request<WellArchitected.Types.ListWorkloadsOutput, AWSError>;
262
262
  /**
263
- * Adds one or more tags to the specified resource.
263
+ * Adds one or more tags to the specified resource. The WorkloadArn parameter can be either a workload ARN or a custom lens ARN.
264
264
  */
265
265
  tagResource(params: WellArchitected.Types.TagResourceInput, callback?: (err: AWSError, data: WellArchitected.Types.TagResourceOutput) => void): Request<WellArchitected.Types.TagResourceOutput, AWSError>;
266
266
  /**
267
- * Adds one or more tags to the specified resource.
267
+ * Adds one or more tags to the specified resource. The WorkloadArn parameter can be either a workload ARN or a custom lens ARN.
268
268
  */
269
269
  tagResource(callback?: (err: AWSError, data: WellArchitected.Types.TagResourceOutput) => void): Request<WellArchitected.Types.TagResourceOutput, AWSError>;
270
270
  /**
271
- * Deletes specified tags from a resource. To specify multiple tags, use separate tagKeys parameters, for example: DELETE /tags/WorkloadArn?tagKeys=key1&amp;tagKeys=key2
271
+ * Deletes specified tags from a resource. The WorkloadArn parameter can be either a workload ARN or a custom lens ARN. To specify multiple tags, use separate tagKeys parameters, for example: DELETE /tags/WorkloadArn?tagKeys=key1&amp;tagKeys=key2
272
272
  */
273
273
  untagResource(params: WellArchitected.Types.UntagResourceInput, callback?: (err: AWSError, data: WellArchitected.Types.UntagResourceOutput) => void): Request<WellArchitected.Types.UntagResourceOutput, AWSError>;
274
274
  /**
275
- * Deletes specified tags from a resource. To specify multiple tags, use separate tagKeys parameters, for example: DELETE /tags/WorkloadArn?tagKeys=key1&amp;tagKeys=key2
275
+ * Deletes specified tags from a resource. The WorkloadArn parameter can be either a workload ARN or a custom lens ARN. To specify multiple tags, use separate tagKeys parameters, for example: DELETE /tags/WorkloadArn?tagKeys=key1&amp;tagKeys=key2
276
276
  */
277
277
  untagResource(callback?: (err: AWSError, data: WellArchitected.Types.UntagResourceOutput) => void): Request<WellArchitected.Types.UntagResourceOutput, AWSError>;
278
278
  /**
@@ -325,6 +325,18 @@ declare class WellArchitected extends Service {
325
325
  upgradeLensReview(callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
326
326
  }
327
327
  declare namespace WellArchitected {
328
+ export type AdditionalResourceType = "HELPFUL_RESOURCE"|"IMPROVEMENT_PLAN"|string;
329
+ export interface AdditionalResources {
330
+ /**
331
+ * Type of additional resource.
332
+ */
333
+ Type?: AdditionalResourceType;
334
+ /**
335
+ * The URLs for additional resources, either helpful resources or improvement plans. Up to five additional URLs can be specified.
336
+ */
337
+ Content?: Urls;
338
+ }
339
+ export type AdditionalResourcesList = AdditionalResources[];
328
340
  export interface Answer {
329
341
  QuestionId?: QuestionId;
330
342
  PillarId?: PillarId;
@@ -388,6 +400,10 @@ declare namespace WellArchitected {
388
400
  * The choice level improvement plan.
389
401
  */
390
402
  ImprovementPlan?: ChoiceContent;
403
+ /**
404
+ * The additional resources for a choice. A choice can have up to two additional resources: one of type HELPFUL_RESOURCE, one of type IMPROVEMENT_PLAN, or both.
405
+ */
406
+ AdditionalResources?: AdditionalResourcesList;
391
407
  }
392
408
  export interface ChoiceAnswer {
393
409
  ChoiceId?: ChoiceId;
@@ -510,7 +526,7 @@ declare namespace WellArchitected {
510
526
  NonAwsRegions?: WorkloadNonAwsRegions;
511
527
  PillarPriorities?: WorkloadPillarPriorities;
512
528
  ArchitecturalDesign?: WorkloadArchitecturalDesign;
513
- ReviewOwner: WorkloadReviewOwner;
529
+ ReviewOwner?: WorkloadReviewOwner;
514
530
  IndustryType?: WorkloadIndustryType;
515
531
  Industry?: WorkloadIndustry;
516
532
  Lenses: WorkloadLenses;
@@ -729,6 +745,10 @@ declare namespace WellArchitected {
729
745
  * The ID assigned to the share invitation.
730
746
  */
731
747
  ShareInvitationId?: ShareInvitationId;
748
+ /**
749
+ * The tags assigned to the lens.
750
+ */
751
+ Tags?: TagMap;
732
752
  }
733
753
  export type LensAlias = string;
734
754
  export type LensAliases = LensAlias[];
@@ -1244,6 +1264,7 @@ declare namespace WellArchitected {
1244
1264
  MilestoneName: MilestoneName;
1245
1265
  ClientRequestToken?: ClientRequestToken;
1246
1266
  }
1267
+ export type Urls = ChoiceContent[];
1247
1268
  export interface VersionDifferences {
1248
1269
  /**
1249
1270
  * The differences between the base and latest versions of the lens.
@@ -83,7 +83,7 @@ return /******/ (function(modules) { // webpackBootstrap
83
83
  /**
84
84
  * @constant
85
85
  */
86
- VERSION: '2.1158.0',
86
+ VERSION: '2.1161.0',
87
87
 
88
88
  /**
89
89
  * @api private