cdk-comprehend-s3olap 2.0.230 → 2.0.232

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 (46) hide show
  1. package/.jsii +4 -4
  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 +23 -1
  6. package/node_modules/aws-sdk/README.md +1 -1
  7. package/node_modules/aws-sdk/apis/amplifyuibuilder-2021-08-11.min.json +40 -9
  8. package/node_modules/aws-sdk/apis/autoscaling-2011-01-01.examples.json +73 -10
  9. package/node_modules/aws-sdk/apis/autoscaling-2011-01-01.min.json +61 -52
  10. package/node_modules/aws-sdk/apis/cleanrooms-2022-02-17.min.json +601 -85
  11. package/node_modules/aws-sdk/apis/cleanrooms-2022-02-17.paginators.json +12 -0
  12. package/node_modules/aws-sdk/apis/dms-2016-01-01.min.json +60 -16
  13. package/node_modules/aws-sdk/apis/dms-2016-01-01.paginators.json +5 -0
  14. package/node_modules/aws-sdk/apis/inspector2-2020-06-08.min.json +291 -192
  15. package/node_modules/aws-sdk/apis/internetmonitor-2021-06-03.min.json +37 -19
  16. package/node_modules/aws-sdk/apis/lookoutequipment-2020-12-15.min.json +337 -23
  17. package/node_modules/aws-sdk/apis/lookoutequipment-2020-12-15.paginators.json +5 -0
  18. package/node_modules/aws-sdk/apis/medialive-2017-10-14.min.json +12 -0
  19. package/node_modules/aws-sdk/apis/omics-2022-11-28.min.json +32 -29
  20. package/node_modules/aws-sdk/apis/rds-2014-10-31.min.json +295 -177
  21. package/node_modules/aws-sdk/apis/sagemaker-2017-07-24.min.json +571 -556
  22. package/node_modules/aws-sdk/apis/scheduler-2021-06-30.min.json +15 -12
  23. package/node_modules/aws-sdk/clients/amplifyuibuilder.d.ts +48 -4
  24. package/node_modules/aws-sdk/clients/autoscaling.d.ts +13 -2
  25. package/node_modules/aws-sdk/clients/batch.d.ts +9 -9
  26. package/node_modules/aws-sdk/clients/cleanrooms.d.ts +516 -9
  27. package/node_modules/aws-sdk/clients/codestarconnections.d.ts +10 -10
  28. package/node_modules/aws-sdk/clients/dms.d.ts +65 -1
  29. package/node_modules/aws-sdk/clients/drs.d.ts +1 -1
  30. package/node_modules/aws-sdk/clients/inspector2.d.ts +101 -2
  31. package/node_modules/aws-sdk/clients/internetmonitor.d.ts +49 -26
  32. package/node_modules/aws-sdk/clients/lookoutequipment.d.ts +522 -15
  33. package/node_modules/aws-sdk/clients/medialive.d.ts +16 -0
  34. package/node_modules/aws-sdk/clients/omics.d.ts +13 -0
  35. package/node_modules/aws-sdk/clients/polly.d.ts +2 -2
  36. package/node_modules/aws-sdk/clients/rds.d.ts +194 -8
  37. package/node_modules/aws-sdk/clients/route53.d.ts +9 -9
  38. package/node_modules/aws-sdk/clients/sagemaker.d.ts +33 -8
  39. package/node_modules/aws-sdk/clients/scheduler.d.ts +16 -3
  40. package/node_modules/aws-sdk/dist/aws-sdk-core-react-native.js +1 -1
  41. package/node_modules/aws-sdk/dist/aws-sdk-react-native.js +16 -16
  42. package/node_modules/aws-sdk/dist/aws-sdk.js +359 -232
  43. package/node_modules/aws-sdk/dist/aws-sdk.min.js +49 -49
  44. package/node_modules/aws-sdk/lib/core.js +1 -1
  45. package/node_modules/aws-sdk/package.json +1 -1
  46. package/package.json +5 -5
@@ -3549,7 +3549,7 @@ declare namespace SageMaker {
3549
3549
  */
3550
3550
  StartTimeOffset?: MonitoringTimeOffsetString;
3551
3551
  /**
3552
- * If specified, monitoring jobs substract this time from the end time. For information about using offsets for scheduling monitoring jobs, see Schedule Model Quality Monitoring Jobs.
3552
+ * If specified, monitoring jobs subtract this time from the end time. For information about using offsets for scheduling monitoring jobs, see Schedule Model Quality Monitoring Jobs.
3553
3553
  */
3554
3554
  EndTimeOffset?: MonitoringTimeOffsetString;
3555
3555
  }
@@ -7948,7 +7948,7 @@ declare namespace SageMaker {
7948
7948
  ProductionVariants?: ProductionVariantSummaryList;
7949
7949
  DataCaptureConfig?: DataCaptureConfigSummary;
7950
7950
  /**
7951
- * The status of the endpoint. OutOfService: Endpoint is not available to take incoming requests. Creating: CreateEndpoint is executing. Updating: UpdateEndpoint or UpdateEndpointWeightsAndCapacities is executing. SystemUpdating: Endpoint is undergoing maintenance and cannot be updated or deleted or re-scaled until it has completed. This maintenance operation does not change any customer-specified values such as VPC config, KMS encryption, model, instance type, or instance count. RollingBack: Endpoint fails to scale up or down or change its variant weight and is in the process of rolling back to its previous configuration. Once the rollback completes, endpoint returns to an InService status. This transitional status only applies to an endpoint that has autoscaling enabled and is undergoing variant weight or capacity changes as part of an UpdateEndpointWeightsAndCapacities call or when the UpdateEndpointWeightsAndCapacities operation is called explicitly. InService: Endpoint is available to process incoming requests. Deleting: DeleteEndpoint is executing. Failed: Endpoint could not be created, updated, or re-scaled. Use the FailureReason value returned by DescribeEndpoint for information about the failure. DeleteEndpoint is the only operation that can be performed on a failed endpoint.
7951
+ * The status of the endpoint. OutOfService: Endpoint is not available to take incoming requests. Creating: CreateEndpoint is executing. Updating: UpdateEndpoint or UpdateEndpointWeightsAndCapacities is executing. SystemUpdating: Endpoint is undergoing maintenance and cannot be updated or deleted or re-scaled until it has completed. This maintenance operation does not change any customer-specified values such as VPC config, KMS encryption, model, instance type, or instance count. RollingBack: Endpoint fails to scale up or down or change its variant weight and is in the process of rolling back to its previous configuration. Once the rollback completes, endpoint returns to an InService status. This transitional status only applies to an endpoint that has autoscaling enabled and is undergoing variant weight or capacity changes as part of an UpdateEndpointWeightsAndCapacities call or when the UpdateEndpointWeightsAndCapacities operation is called explicitly. InService: Endpoint is available to process incoming requests. Deleting: DeleteEndpoint is executing. Failed: Endpoint could not be created, updated, or re-scaled. Use the FailureReason value returned by DescribeEndpoint for information about the failure. DeleteEndpoint is the only operation that can be performed on a failed endpoint. UpdateRollbackFailed: Both the rolling deployment and auto-rollback failed. Your endpoint is in service with a mix of the old and new endpoint configurations. For information about how to remedy this issue and restore the endpoint's status to InService, see Rolling Deployments.
7952
7952
  */
7953
7953
  EndpointStatus: EndpointStatus;
7954
7954
  /**
@@ -11379,6 +11379,7 @@ declare namespace SageMaker {
11379
11379
  Value: MetricValue;
11380
11380
  }
11381
11381
  export type FinalMetricDataList = MetricData[];
11382
+ export type FlatInvocations = "Continue"|"Stop"|string;
11382
11383
  export type Float = number;
11383
11384
  export type FlowDefinitionArn = string;
11384
11385
  export type FlowDefinitionName = string;
@@ -16731,7 +16732,7 @@ declare namespace SageMaker {
16731
16732
  export type ModelInsightsLocation = string;
16732
16733
  export interface ModelLatencyThreshold {
16733
16734
  /**
16734
- * The model latency percentile threshold.
16735
+ * The model latency percentile threshold. For custom load tests, specify the value as P95.
16735
16736
  */
16736
16737
  Percentile?: String64;
16737
16738
  /**
@@ -17795,6 +17796,7 @@ declare namespace SageMaker {
17795
17796
  }
17796
17797
  export type NotificationTopicArn = string;
17797
17798
  export type NumberOfHumanWorkersPerDataObject = number;
17799
+ export type NumberOfSteps = number;
17798
17800
  export type ObjectiveStatus = "Succeeded"|"Pending"|"Failed"|string;
17799
17801
  export type ObjectiveStatusCounter = number;
17800
17802
  export interface ObjectiveStatusCounters {
@@ -18132,7 +18134,7 @@ declare namespace SageMaker {
18132
18134
  export type Percentage = number;
18133
18135
  export interface Phase {
18134
18136
  /**
18135
- * Specifies how many concurrent users to start with.
18137
+ * Specifies how many concurrent users to start with. The value should be between 1 and 3.
18136
18138
  */
18137
18139
  InitialNumberOfUsers?: InitialNumberOfUsers;
18138
18140
  /**
@@ -18140,7 +18142,7 @@ declare namespace SageMaker {
18140
18142
  */
18141
18143
  SpawnRate?: SpawnRate;
18142
18144
  /**
18143
- * Specifies how long traffic phase should be.
18145
+ * Specifies how long a traffic phase should be. For custom load tests, the value should be between 120 and 3600. This value should not exceed JobDurationInSeconds.
18144
18146
  */
18145
18147
  DurationInSeconds?: TrafficDurationInSeconds;
18146
18148
  }
@@ -19340,7 +19342,7 @@ declare namespace SageMaker {
19340
19342
  */
19341
19343
  ModelPackageVersionArn?: ModelPackageArn;
19342
19344
  /**
19343
- * Specifies the maximum duration of the job, in seconds.>
19345
+ * Specifies the maximum duration of the job, in seconds. The maximum value is 7200.
19344
19346
  */
19345
19347
  JobDurationInSeconds?: JobDurationInSeconds;
19346
19348
  /**
@@ -19417,6 +19419,10 @@ declare namespace SageMaker {
19417
19419
  * The interval of time taken by a model to respond as viewed from SageMaker. The interval includes the local communication time taken to send the request and to fetch the response from the container of a model and the time taken to complete the inference in the container.
19418
19420
  */
19419
19421
  ModelLatencyThresholds?: ModelLatencyThresholds;
19422
+ /**
19423
+ * Stops a load test when the number of invocations (TPS) peaks and flattens, which means that the instance has reached capacity. The default value is Stop. If you want the load test to continue after invocations have flattened, set the value to Continue.
19424
+ */
19425
+ FlatInvocations?: FlatInvocations;
19420
19426
  }
19421
19427
  export type RecommendationJobSupportedContentTypes = String[];
19422
19428
  export type RecommendationJobSupportedEndpointType = "RealTime"|"Serverless"|string;
@@ -20146,6 +20152,20 @@ declare namespace SageMaker {
20146
20152
  export type SpawnRate = number;
20147
20153
  export type SplitType = "None"|"Line"|"RecordIO"|"TFRecord"|string;
20148
20154
  export type StageStatus = "CREATING"|"READYTODEPLOY"|"STARTING"|"INPROGRESS"|"DEPLOYED"|"FAILED"|"STOPPING"|"STOPPED"|string;
20155
+ export interface Stairs {
20156
+ /**
20157
+ * Defines how long each traffic step should be.
20158
+ */
20159
+ DurationInSeconds?: TrafficDurationInSeconds;
20160
+ /**
20161
+ * Specifies how many steps to perform during traffic.
20162
+ */
20163
+ NumberOfSteps?: NumberOfSteps;
20164
+ /**
20165
+ * Specifies how many new users to spawn in each step.
20166
+ */
20167
+ UsersPerStep?: UsersPerStep;
20168
+ }
20149
20169
  export interface StartEdgeDeploymentStageRequest {
20150
20170
  /**
20151
20171
  * The name of the edge deployment plan to start.
@@ -20611,13 +20631,17 @@ declare namespace SageMaker {
20611
20631
  export type TrafficDurationInSeconds = number;
20612
20632
  export interface TrafficPattern {
20613
20633
  /**
20614
- * Defines the traffic patterns.
20634
+ * Defines the traffic patterns. Choose either PHASES or STAIRS.
20615
20635
  */
20616
20636
  TrafficType?: TrafficType;
20617
20637
  /**
20618
20638
  * Defines the phases traffic specification.
20619
20639
  */
20620
20640
  Phases?: Phases;
20641
+ /**
20642
+ * Defines the stairs traffic pattern.
20643
+ */
20644
+ Stairs?: Stairs;
20621
20645
  }
20622
20646
  export interface TrafficRoutingConfig {
20623
20647
  /**
@@ -20638,7 +20662,7 @@ declare namespace SageMaker {
20638
20662
  LinearStepSize?: CapacitySize;
20639
20663
  }
20640
20664
  export type TrafficRoutingConfigType = "ALL_AT_ONCE"|"CANARY"|"LINEAR"|string;
20641
- export type TrafficType = "PHASES"|string;
20665
+ export type TrafficType = "PHASES"|"STAIRS"|string;
20642
20666
  export type TrainingContainerArgument = string;
20643
20667
  export type TrainingContainerArguments = TrainingContainerArgument[];
20644
20668
  export type TrainingContainerEntrypoint = TrainingContainerEntrypointString[];
@@ -22473,6 +22497,7 @@ declare namespace SageMaker {
22473
22497
  */
22474
22498
  CanvasAppSettings?: CanvasAppSettings;
22475
22499
  }
22500
+ export type UsersPerStep = number;
22476
22501
  export type UtilizationMetric = number;
22477
22502
  export type ValidationFraction = number;
22478
22503
  export type VariantName = string;
@@ -109,6 +109,7 @@ declare class Scheduler extends Service {
109
109
  updateSchedule(callback?: (err: AWSError, data: Scheduler.Types.UpdateScheduleOutput) => void): Request<Scheduler.Types.UpdateScheduleOutput, AWSError>;
110
110
  }
111
111
  declare namespace Scheduler {
112
+ export type ActionAfterCompletion = "NONE"|"DELETE"|string;
112
113
  export type AssignPublicIp = "ENABLED"|"DISABLED"|string;
113
114
  export interface AwsVpcConfiguration {
114
115
  /**
@@ -164,6 +165,10 @@ declare namespace Scheduler {
164
165
  ScheduleGroupArn: ScheduleGroupArn;
165
166
  }
166
167
  export interface CreateScheduleInput {
168
+ /**
169
+ * Specifies the action that EventBridge Scheduler applies to the schedule after the schedule completes invoking the target.
170
+ */
171
+ ActionAfterCompletion?: ActionAfterCompletion;
167
172
  /**
168
173
  * Unique, case-sensitive identifier you provide to ensure the idempotency of the request. If you do not specify a client token, EventBridge Scheduler uses a randomly generated token for the request to ensure idempotency.
169
174
  */
@@ -193,7 +198,7 @@ declare namespace Scheduler {
193
198
  */
194
199
  Name: Name;
195
200
  /**
196
- * The expression that defines when the schedule runs. The following formats are supported. at expression - at(yyyy-mm-ddThh:mm:ss) rate expression - rate(unit value) cron expression - cron(fields) You can use at expressions to create one-time schedules that invoke a target once, at the time and in the time zone, that you specify. You can use rate and cron expressions to create recurring schedules. Rate-based schedules are useful when you want to invoke a target at regular intervals, such as every 15 minutes or every five days. Cron-based schedules are useful when you want to invoke a target periodically at a specific time, such as at 8:00 am (UTC+0) every 1st day of the month. A cron expression consists of six fields separated by white spaces: (minutes hours day_of_month month day_of_week year). A rate expression consists of a value as a positive integer, and a unit with the following options: minute | minutes | hour | hours | day | days For more information and examples, see Schedule types on EventBridge Scheduler in the EventBridge Scheduler User Guide.
201
+ * The expression that defines when the schedule runs. The following formats are supported. at expression - at(yyyy-mm-ddThh:mm:ss) rate expression - rate(value unit) cron expression - cron(fields) You can use at expressions to create one-time schedules that invoke a target once, at the time and in the time zone, that you specify. You can use rate and cron expressions to create recurring schedules. Rate-based schedules are useful when you want to invoke a target at regular intervals, such as every 15 minutes or every five days. Cron-based schedules are useful when you want to invoke a target periodically at a specific time, such as at 8:00 am (UTC+0) every 1st day of the month. A cron expression consists of six fields separated by white spaces: (minutes hours day_of_month month day_of_week year). A rate expression consists of a value as a positive integer, and a unit with the following options: minute | minutes | hour | hours | day | days For more information and examples, see Schedule types on EventBridge Scheduler in the EventBridge Scheduler User Guide.
197
202
  */
198
203
  ScheduleExpression: ScheduleExpression;
199
204
  /**
@@ -378,6 +383,10 @@ declare namespace Scheduler {
378
383
  Name: Name;
379
384
  }
380
385
  export interface GetScheduleOutput {
386
+ /**
387
+ * Indicates the action that EventBridge Scheduler applies to the schedule after the schedule completes invoking the target.
388
+ */
389
+ ActionAfterCompletion?: ActionAfterCompletion;
381
390
  /**
382
391
  * The Amazon Resource Name (ARN) of the schedule.
383
392
  */
@@ -415,7 +424,7 @@ declare namespace Scheduler {
415
424
  */
416
425
  Name?: Name;
417
426
  /**
418
- * The expression that defines when the schedule runs. The following formats are supported. at expression - at(yyyy-mm-ddThh:mm:ss) rate expression - rate(unit value) cron expression - cron(fields) You can use at expressions to create one-time schedules that invoke a target once, at the time and in the time zone, that you specify. You can use rate and cron expressions to create recurring schedules. Rate-based schedules are useful when you want to invoke a target at regular intervals, such as every 15 minutes or every five days. Cron-based schedules are useful when you want to invoke a target periodically at a specific time, such as at 8:00 am (UTC+0) every 1st day of the month. A cron expression consists of six fields separated by white spaces: (minutes hours day_of_month month day_of_week year). A rate expression consists of a value as a positive integer, and a unit with the following options: minute | minutes | hour | hours | day | days For more information and examples, see Schedule types on EventBridge Scheduler in the EventBridge Scheduler User Guide.
427
+ * The expression that defines when the schedule runs. The following formats are supported. at expression - at(yyyy-mm-ddThh:mm:ss) rate expression - rate(value unit) cron expression - cron(fields) You can use at expressions to create one-time schedules that invoke a target once, at the time and in the time zone, that you specify. You can use rate and cron expressions to create recurring schedules. Rate-based schedules are useful when you want to invoke a target at regular intervals, such as every 15 minutes or every five days. Cron-based schedules are useful when you want to invoke a target periodically at a specific time, such as at 8:00 am (UTC+0) every 1st day of the month. A cron expression consists of six fields separated by white spaces: (minutes hours day_of_month month day_of_week year). A rate expression consists of a value as a positive integer, and a unit with the following options: minute | minutes | hour | hours | day | days For more information and examples, see Schedule types on EventBridge Scheduler in the EventBridge Scheduler User Guide.
419
428
  */
420
429
  ScheduleExpression?: ScheduleExpression;
421
430
  /**
@@ -755,6 +764,10 @@ declare namespace Scheduler {
755
764
  export interface UntagResourceOutput {
756
765
  }
757
766
  export interface UpdateScheduleInput {
767
+ /**
768
+ * Specifies the action that EventBridge Scheduler applies to the schedule after the schedule completes invoking the target.
769
+ */
770
+ ActionAfterCompletion?: ActionAfterCompletion;
758
771
  /**
759
772
  * Unique, case-sensitive identifier you provide to ensure the idempotency of the request. If you do not specify a client token, EventBridge Scheduler uses a randomly generated token for the request to ensure idempotency.
760
773
  */
@@ -784,7 +797,7 @@ declare namespace Scheduler {
784
797
  */
785
798
  Name: Name;
786
799
  /**
787
- * The expression that defines when the schedule runs. The following formats are supported. at expression - at(yyyy-mm-ddThh:mm:ss) rate expression - rate(unit value) cron expression - cron(fields) You can use at expressions to create one-time schedules that invoke a target once, at the time and in the time zone, that you specify. You can use rate and cron expressions to create recurring schedules. Rate-based schedules are useful when you want to invoke a target at regular intervals, such as every 15 minutes or every five days. Cron-based schedules are useful when you want to invoke a target periodically at a specific time, such as at 8:00 am (UTC+0) every 1st day of the month. A cron expression consists of six fields separated by white spaces: (minutes hours day_of_month month day_of_week year). A rate expression consists of a value as a positive integer, and a unit with the following options: minute | minutes | hour | hours | day | days For more information and examples, see Schedule types on EventBridge Scheduler in the EventBridge Scheduler User Guide.
800
+ * The expression that defines when the schedule runs. The following formats are supported. at expression - at(yyyy-mm-ddThh:mm:ss) rate expression - rate(value unit) cron expression - cron(fields) You can use at expressions to create one-time schedules that invoke a target once, at the time and in the time zone, that you specify. You can use rate and cron expressions to create recurring schedules. Rate-based schedules are useful when you want to invoke a target at regular intervals, such as every 15 minutes or every five days. Cron-based schedules are useful when you want to invoke a target periodically at a specific time, such as at 8:00 am (UTC+0) every 1st day of the month. A cron expression consists of six fields separated by white spaces: (minutes hours day_of_month month day_of_week year). A rate expression consists of a value as a positive integer, and a unit with the following options: minute | minutes | hour | hours | day | days For more information and examples, see Schedule types on EventBridge Scheduler in the EventBridge Scheduler User Guide.
788
801
  */
789
802
  ScheduleExpression: ScheduleExpression;
790
803
  /**
@@ -83,7 +83,7 @@ return /******/ (function(modules) { // webpackBootstrap
83
83
  /**
84
84
  * @constant
85
85
  */
86
- VERSION: '2.1425.0',
86
+ VERSION: '2.1427.0',
87
87
 
88
88
  /**
89
89
  * @api private