cdk-lambda-subminute 2.0.299 → 2.0.300

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 (32) hide show
  1. package/.jsii +3 -3
  2. package/lib/cdk-lambda-subminute.js +3 -3
  3. package/node_modules/aws-sdk/CHANGELOG.md +14 -1
  4. package/node_modules/aws-sdk/README.md +1 -1
  5. package/node_modules/aws-sdk/apis/autoscaling-2011-01-01.examples.json +3 -0
  6. package/node_modules/aws-sdk/apis/autoscaling-2011-01-01.min.json +117 -94
  7. package/node_modules/aws-sdk/apis/cloudtrail-2013-11-01.min.json +37 -31
  8. package/node_modules/aws-sdk/apis/codecatalyst-2022-09-28.min.json +361 -16
  9. package/node_modules/aws-sdk/apis/codecatalyst-2022-09-28.paginators.json +12 -0
  10. package/node_modules/aws-sdk/apis/ec2-2016-11-15.min.json +423 -268
  11. package/node_modules/aws-sdk/apis/finspace-2021-03-12.min.json +15 -5
  12. package/node_modules/aws-sdk/apis/finspace-data-2020-07-13.min.json +93 -31
  13. package/node_modules/aws-sdk/apis/mwaa-2020-07-01.min.json +31 -26
  14. package/node_modules/aws-sdk/apis/redshift-2012-12-01.min.json +6 -2
  15. package/node_modules/aws-sdk/apis/s3control-2018-08-20.min.json +562 -53
  16. package/node_modules/aws-sdk/apis/s3control-2018-08-20.paginators.json +4 -0
  17. package/node_modules/aws-sdk/clients/autoscaling.d.ts +33 -4
  18. package/node_modules/aws-sdk/clients/cloudtrail.d.ts +29 -4
  19. package/node_modules/aws-sdk/clients/codecatalyst.d.ts +370 -5
  20. package/node_modules/aws-sdk/clients/ec2.d.ts +179 -1
  21. package/node_modules/aws-sdk/clients/lambda.d.ts +1 -1
  22. package/node_modules/aws-sdk/clients/mwaa.d.ts +28 -5
  23. package/node_modules/aws-sdk/clients/rds.d.ts +1 -1
  24. package/node_modules/aws-sdk/clients/redshift.d.ts +6 -2
  25. package/node_modules/aws-sdk/clients/s3control.d.ts +359 -7
  26. package/node_modules/aws-sdk/dist/aws-sdk-core-react-native.js +1 -1
  27. package/node_modules/aws-sdk/dist/aws-sdk-react-native.js +12 -12
  28. package/node_modules/aws-sdk/dist/aws-sdk.js +586 -398
  29. package/node_modules/aws-sdk/dist/aws-sdk.min.js +100 -100
  30. package/node_modules/aws-sdk/lib/core.js +1 -1
  31. package/node_modules/aws-sdk/package.json +1 -1
  32. package/package.json +2 -2
@@ -29,6 +29,10 @@
29
29
  "ListStorageLensConfigurations": {
30
30
  "input_token": "NextToken",
31
31
  "output_token": "NextToken"
32
+ },
33
+ "ListStorageLensGroups": {
34
+ "input_token": "NextToken",
35
+ "output_token": "NextToken"
32
36
  }
33
37
  }
34
38
  }
@@ -472,11 +472,11 @@ declare class AutoScaling extends Service {
472
472
  */
473
473
  setInstanceProtection(callback?: (err: AWSError, data: AutoScaling.Types.SetInstanceProtectionAnswer) => void): Request<AutoScaling.Types.SetInstanceProtectionAnswer, AWSError>;
474
474
  /**
475
- * Starts an instance refresh. During an instance refresh, Amazon EC2 Auto Scaling performs a rolling update of instances in an Auto Scaling group. Instances are terminated first and then replaced, which temporarily reduces the capacity available within your Auto Scaling group. This operation is part of the instance refresh feature in Amazon EC2 Auto Scaling, which helps you update instances in your Auto Scaling group. This feature is helpful, for example, when you have a new AMI or a new user data script. You just need to create a new launch template that specifies the new AMI or user data script. Then start an instance refresh to immediately begin the process of updating instances in the group. If successful, the request's response contains a unique ID that you can use to track the progress of the instance refresh. To query its status, call the DescribeInstanceRefreshes API. To describe the instance refreshes that have already run, call the DescribeInstanceRefreshes API. To cancel an instance refresh that is in progress, use the CancelInstanceRefresh API. An instance refresh might fail for several reasons, such as EC2 launch failures, misconfigured health checks, or not ignoring or allowing the termination of instances that are in Standby state or protected from scale in. You can monitor for failed EC2 launches using the scaling activities. To find the scaling activities, call the DescribeScalingActivities API. If you enable auto rollback, your Auto Scaling group will be rolled back automatically when the instance refresh fails. You can enable this feature before starting an instance refresh by specifying the AutoRollback property in the instance refresh preferences. Otherwise, to roll back an instance refresh before it finishes, use the RollbackInstanceRefresh API.
475
+ * Starts an instance refresh. This operation is part of the instance refresh feature in Amazon EC2 Auto Scaling, which helps you update instances in your Auto Scaling group. This feature is helpful, for example, when you have a new AMI or a new user data script. You just need to create a new launch template that specifies the new AMI or user data script. Then start an instance refresh to immediately begin the process of updating instances in the group. If successful, the request's response contains a unique ID that you can use to track the progress of the instance refresh. To query its status, call the DescribeInstanceRefreshes API. To describe the instance refreshes that have already run, call the DescribeInstanceRefreshes API. To cancel an instance refresh that is in progress, use the CancelInstanceRefresh API. An instance refresh might fail for several reasons, such as EC2 launch failures, misconfigured health checks, or not ignoring or allowing the termination of instances that are in Standby state or protected from scale in. You can monitor for failed EC2 launches using the scaling activities. To find the scaling activities, call the DescribeScalingActivities API. If you enable auto rollback, your Auto Scaling group will be rolled back automatically when the instance refresh fails. You can enable this feature before starting an instance refresh by specifying the AutoRollback property in the instance refresh preferences. Otherwise, to roll back an instance refresh before it finishes, use the RollbackInstanceRefresh API.
476
476
  */
477
477
  startInstanceRefresh(params: AutoScaling.Types.StartInstanceRefreshType, callback?: (err: AWSError, data: AutoScaling.Types.StartInstanceRefreshAnswer) => void): Request<AutoScaling.Types.StartInstanceRefreshAnswer, AWSError>;
478
478
  /**
479
- * Starts an instance refresh. During an instance refresh, Amazon EC2 Auto Scaling performs a rolling update of instances in an Auto Scaling group. Instances are terminated first and then replaced, which temporarily reduces the capacity available within your Auto Scaling group. This operation is part of the instance refresh feature in Amazon EC2 Auto Scaling, which helps you update instances in your Auto Scaling group. This feature is helpful, for example, when you have a new AMI or a new user data script. You just need to create a new launch template that specifies the new AMI or user data script. Then start an instance refresh to immediately begin the process of updating instances in the group. If successful, the request's response contains a unique ID that you can use to track the progress of the instance refresh. To query its status, call the DescribeInstanceRefreshes API. To describe the instance refreshes that have already run, call the DescribeInstanceRefreshes API. To cancel an instance refresh that is in progress, use the CancelInstanceRefresh API. An instance refresh might fail for several reasons, such as EC2 launch failures, misconfigured health checks, or not ignoring or allowing the termination of instances that are in Standby state or protected from scale in. You can monitor for failed EC2 launches using the scaling activities. To find the scaling activities, call the DescribeScalingActivities API. If you enable auto rollback, your Auto Scaling group will be rolled back automatically when the instance refresh fails. You can enable this feature before starting an instance refresh by specifying the AutoRollback property in the instance refresh preferences. Otherwise, to roll back an instance refresh before it finishes, use the RollbackInstanceRefresh API.
479
+ * Starts an instance refresh. This operation is part of the instance refresh feature in Amazon EC2 Auto Scaling, which helps you update instances in your Auto Scaling group. This feature is helpful, for example, when you have a new AMI or a new user data script. You just need to create a new launch template that specifies the new AMI or user data script. Then start an instance refresh to immediately begin the process of updating instances in the group. If successful, the request's response contains a unique ID that you can use to track the progress of the instance refresh. To query its status, call the DescribeInstanceRefreshes API. To describe the instance refreshes that have already run, call the DescribeInstanceRefreshes API. To cancel an instance refresh that is in progress, use the CancelInstanceRefresh API. An instance refresh might fail for several reasons, such as EC2 launch failures, misconfigured health checks, or not ignoring or allowing the termination of instances that are in Standby state or protected from scale in. You can monitor for failed EC2 launches using the scaling activities. To find the scaling activities, call the DescribeScalingActivities API. If you enable auto rollback, your Auto Scaling group will be rolled back automatically when the instance refresh fails. You can enable this feature before starting an instance refresh by specifying the AutoRollback property in the instance refresh preferences. Otherwise, to roll back an instance refresh before it finishes, use the RollbackInstanceRefresh API.
480
480
  */
481
481
  startInstanceRefresh(callback?: (err: AWSError, data: AutoScaling.Types.StartInstanceRefreshAnswer) => void): Request<AutoScaling.Types.StartInstanceRefreshAnswer, AWSError>;
482
482
  /**
@@ -813,6 +813,10 @@ declare namespace AutoScaling {
813
813
  * The traffic sources associated with this Auto Scaling group.
814
814
  */
815
815
  TrafficSources?: TrafficSources;
816
+ /**
817
+ * An instance maintenance policy.
818
+ */
819
+ InstanceMaintenancePolicy?: InstanceMaintenancePolicy;
816
820
  }
817
821
  export type AutoScalingGroupDesiredCapacity = number;
818
822
  export type AutoScalingGroupMaxSize = number;
@@ -1136,6 +1140,10 @@ declare namespace AutoScaling {
1136
1140
  * The list of traffic sources to attach to this Auto Scaling group. You can use any of the following as traffic sources for an Auto Scaling group: Classic Load Balancer, Application Load Balancer, Gateway Load Balancer, Network Load Balancer, and VPC Lattice.
1137
1141
  */
1138
1142
  TrafficSources?: TrafficSources;
1143
+ /**
1144
+ * An instance maintenance policy. For more information, see Set instance maintenance policy in the Amazon EC2 Auto Scaling User Guide.
1145
+ */
1146
+ InstanceMaintenancePolicy?: InstanceMaintenancePolicy;
1139
1147
  }
1140
1148
  export interface CreateLaunchConfigurationType {
1141
1149
  /**
@@ -1939,6 +1947,16 @@ declare namespace AutoScaling {
1939
1947
  export type InstanceGeneration = "current"|"previous"|string;
1940
1948
  export type InstanceGenerations = InstanceGeneration[];
1941
1949
  export type InstanceIds = XmlStringMaxLen19[];
1950
+ export interface InstanceMaintenancePolicy {
1951
+ /**
1952
+ * Specifies the lower threshold as a percentage of the desired capacity of the Auto Scaling group. It represents the minimum percentage of the group to keep in service, healthy, and ready to use to support your workload when replacing instances. Value range is 0 to 100. After it's set, a value of -1 will clear the previously set value.
1953
+ */
1954
+ MinHealthyPercentage?: IntPercentResettable;
1955
+ /**
1956
+ * Specifies the upper threshold as a percentage of the desired capacity of the Auto Scaling group. It represents the maximum percentage of the group that can be in service and healthy, or pending, to support your workload when replacing instances. Value range is 100 to 200. After it's set, a value of -1 will clear the previously set value. Both MinHealthyPercentage and MaxHealthyPercentage must be specified, and the difference between them cannot be greater than 100. A large range increases the number of instances that can be replaced at the same time.
1957
+ */
1958
+ MaxHealthyPercentage?: IntPercent100To200Resettable;
1959
+ }
1942
1960
  export type InstanceMetadataEndpointState = "disabled"|"enabled"|string;
1943
1961
  export type InstanceMetadataHttpPutResponseHopLimit = number;
1944
1962
  export type InstanceMetadataHttpTokensState = "optional"|"required"|string;
@@ -2175,6 +2193,9 @@ declare namespace AutoScaling {
2175
2193
  }
2176
2194
  export type InstancesToUpdate = number;
2177
2195
  export type IntPercent = number;
2196
+ export type IntPercent100To200 = number;
2197
+ export type IntPercent100To200Resettable = number;
2198
+ export type IntPercentResettable = number;
2178
2199
  export interface LaunchConfiguration {
2179
2200
  /**
2180
2201
  * The name of the launch configuration.
@@ -2975,7 +2996,7 @@ declare namespace AutoScaling {
2975
2996
  export type RefreshInstanceWarmup = number;
2976
2997
  export interface RefreshPreferences {
2977
2998
  /**
2978
- * The amount of capacity in the Auto Scaling group that must pass your group's health checks to allow the operation to continue. The value is expressed as a percentage of the desired capacity of the Auto Scaling group (rounded up to the nearest integer). The default is 90. Setting the minimum healthy percentage to 100 percent limits the rate of replacement to one instance at a time. In contrast, setting it to 0 percent has the effect of replacing all instances at the same time.
2999
+ * Specifies the minimum percentage of the group to keep in service, healthy, and ready to use to support your workload to allow the operation to continue. The value is expressed as a percentage of the desired capacity of the Auto Scaling group. Value range is 0 to 100. If you do not specify this property, the default is 90 percent, or the percentage set in the instance maintenance policy for the Auto Scaling group, if defined.
2979
3000
  */
2980
3001
  MinHealthyPercentage?: IntPercent;
2981
3002
  /**
@@ -3010,6 +3031,10 @@ declare namespace AutoScaling {
3010
3031
  * (Optional) The CloudWatch alarm specification. CloudWatch alarms can be used to identify any issues and fail the operation if an alarm threshold is met.
3011
3032
  */
3012
3033
  AlarmSpecification?: AlarmSpecification;
3034
+ /**
3035
+ * Specifies the maximum percentage of the group that can be in service and healthy, or pending, to support your workload when replacing instances. The value is expressed as a percentage of the desired capacity of the Auto Scaling group. Value range is 100 to 200. If you specify MaxHealthyPercentage, you must also specify MinHealthyPercentage, and the difference between them cannot be greater than 100. A larger range increases the number of instances that can be replaced at the same time. If you do not specify this property, the default is 100 percent, or the percentage set in the instance maintenance policy for the Auto Scaling group, if defined.
3036
+ */
3037
+ MaxHealthyPercentage?: IntPercent100To200;
3013
3038
  }
3014
3039
  export type RefreshStrategy = "Rolling"|string;
3015
3040
  export type ResourceName = string;
@@ -3293,7 +3318,7 @@ declare namespace AutoScaling {
3293
3318
  */
3294
3319
  DesiredConfiguration?: DesiredConfiguration;
3295
3320
  /**
3296
- * Sets your preferences for the instance refresh so that it performs as expected when you start it. Includes the instance warmup time, the minimum healthy percentage, and the behaviors that you want Amazon EC2 Auto Scaling to use if instances that are in Standby state or protected from scale in are found. You can also choose to enable additional features, such as the following: Auto rollback Checkpoints CloudWatch alarms Skip matching
3321
+ * Sets your preferences for the instance refresh so that it performs as expected when you start it. Includes the instance warmup time, the minimum and maximum healthy percentages, and the behaviors that you want Amazon EC2 Auto Scaling to use if instances that are in Standby state or protected from scale in are found. You can also choose to enable additional features, such as the following: Auto rollback Checkpoints CloudWatch alarms Skip matching
3297
3322
  */
3298
3323
  Preferences?: RefreshPreferences;
3299
3324
  }
@@ -3574,6 +3599,10 @@ declare namespace AutoScaling {
3574
3599
  * The amount of time, in seconds, until a new instance is considered to have finished initializing and resource consumption to become stable after it enters the InService state. During an instance refresh, Amazon EC2 Auto Scaling waits for the warm-up period after it replaces an instance before it moves on to replacing the next instance. Amazon EC2 Auto Scaling also waits for the warm-up period before aggregating the metrics for new instances with existing instances in the Amazon CloudWatch metrics that are used for scaling, resulting in more reliable usage data. For more information, see Set the default instance warmup for an Auto Scaling group in the Amazon EC2 Auto Scaling User Guide. To manage various warm-up settings at the group level, we recommend that you set the default instance warmup, even if it is set to 0 seconds. To remove a value that you previously set, include the property but specify -1 for the value. However, we strongly recommend keeping the default instance warmup enabled by specifying a value of 0 or other nominal value.
3575
3600
  */
3576
3601
  DefaultInstanceWarmup?: DefaultInstanceWarmup;
3602
+ /**
3603
+ * An instance maintenance policy. For more information, see Set instance maintenance policy in the Amazon EC2 Auto Scaling User Guide.
3604
+ */
3605
+ InstanceMaintenancePolicy?: InstanceMaintenancePolicy;
3577
3606
  }
3578
3607
  export interface VCpuCountRequest {
3579
3608
  /**
@@ -364,11 +364,11 @@ declare class CloudTrail extends Service {
364
364
  */
365
365
  updateChannel(callback?: (err: AWSError, data: CloudTrail.Types.UpdateChannelResponse) => void): Request<CloudTrail.Types.UpdateChannelResponse, AWSError>;
366
366
  /**
367
- * Updates an event data store. The required EventDataStore value is an ARN or the ID portion of the ARN. Other parameters are optional, but at least one optional parameter must be specified, or CloudTrail throws an error. RetentionPeriod is in days, and valid values are integers between 90 and 2557. By default, TerminationProtection is enabled. For event data stores for CloudTrail events, AdvancedEventSelectors includes or excludes management, data, or Insights events in your event data store. For more information about AdvancedEventSelectors, see AdvancedEventSelectors. For event data stores for Config configuration items, Audit Manager evidence, or non-Amazon Web Services events, AdvancedEventSelectors includes events of that type in your event data store.
367
+ * Updates an event data store. The required EventDataStore value is an ARN or the ID portion of the ARN. Other parameters are optional, but at least one optional parameter must be specified, or CloudTrail throws an error. RetentionPeriod is in days, and valid values are integers between 7 and 3653 if the BillingMode is set to EXTENDABLE_RETENTION_PRICING, or between 7 and 2557 if BillingMode is set to FIXED_RETENTION_PRICING. By default, TerminationProtection is enabled. For event data stores for CloudTrail events, AdvancedEventSelectors includes or excludes management, data, or Insights events in your event data store. For more information about AdvancedEventSelectors, see AdvancedEventSelectors. For event data stores for Config configuration items, Audit Manager evidence, or non-Amazon Web Services events, AdvancedEventSelectors includes events of that type in your event data store.
368
368
  */
369
369
  updateEventDataStore(params: CloudTrail.Types.UpdateEventDataStoreRequest, callback?: (err: AWSError, data: CloudTrail.Types.UpdateEventDataStoreResponse) => void): Request<CloudTrail.Types.UpdateEventDataStoreResponse, AWSError>;
370
370
  /**
371
- * Updates an event data store. The required EventDataStore value is an ARN or the ID portion of the ARN. Other parameters are optional, but at least one optional parameter must be specified, or CloudTrail throws an error. RetentionPeriod is in days, and valid values are integers between 90 and 2557. By default, TerminationProtection is enabled. For event data stores for CloudTrail events, AdvancedEventSelectors includes or excludes management, data, or Insights events in your event data store. For more information about AdvancedEventSelectors, see AdvancedEventSelectors. For event data stores for Config configuration items, Audit Manager evidence, or non-Amazon Web Services events, AdvancedEventSelectors includes events of that type in your event data store.
371
+ * Updates an event data store. The required EventDataStore value is an ARN or the ID portion of the ARN. Other parameters are optional, but at least one optional parameter must be specified, or CloudTrail throws an error. RetentionPeriod is in days, and valid values are integers between 7 and 3653 if the BillingMode is set to EXTENDABLE_RETENTION_PRICING, or between 7 and 2557 if BillingMode is set to FIXED_RETENTION_PRICING. By default, TerminationProtection is enabled. For event data stores for CloudTrail events, AdvancedEventSelectors includes or excludes management, data, or Insights events in your event data store. For more information about AdvancedEventSelectors, see AdvancedEventSelectors. For event data stores for Config configuration items, Audit Manager evidence, or non-Amazon Web Services events, AdvancedEventSelectors includes events of that type in your event data store.
372
372
  */
373
373
  updateEventDataStore(callback?: (err: AWSError, data: CloudTrail.Types.UpdateEventDataStoreResponse) => void): Request<CloudTrail.Types.UpdateEventDataStoreResponse, AWSError>;
374
374
  /**
@@ -436,6 +436,7 @@ declare namespace CloudTrail {
436
436
  NotEndsWith?: Operator;
437
437
  }
438
438
  export type AdvancedFieldSelectors = AdvancedFieldSelector[];
439
+ export type BillingMode = "EXTENDABLE_RETENTION_PRICING"|"FIXED_RETENTION_PRICING"|string;
439
440
  export type Boolean = boolean;
440
441
  export type ByteBuffer = Buffer|Uint8Array|Blob|string;
441
442
  export interface CancelQueryRequest {
@@ -523,7 +524,7 @@ declare namespace CloudTrail {
523
524
  */
524
525
  OrganizationEnabled?: Boolean;
525
526
  /**
526
- * The retention period of the event data store, in days. You can set a retention period of up to 2557 days, the equivalent of seven years. CloudTrail Lake determines whether to retain an event by checking if the eventTime of the event is within the specified retention period. For example, if you set a retention period of 90 days, CloudTrail will remove events when the eventTime is older than 90 days. If you plan to copy trail events to this event data store, we recommend that you consider both the age of the events that you want to copy as well as how long you want to keep the copied events in your event data store. For example, if you copy trail events that are 5 years old and specify a retention period of 7 years, the event data store will retain those events for two years.
527
+ * The retention period of the event data store, in days. If BillingMode is set to EXTENDABLE_RETENTION_PRICING, you can set a retention period of up to 3653 days, the equivalent of 10 years. If BillingMode is set to FIXED_RETENTION_PRICING, you can set a retention period of up to 2557 days, the equivalent of seven years. CloudTrail Lake determines whether to retain an event by checking if the eventTime of the event is within the specified retention period. For example, if you set a retention period of 90 days, CloudTrail will remove events when the eventTime is older than 90 days. If you plan to copy trail events to this event data store, we recommend that you consider both the age of the events that you want to copy as well as how long you want to keep the copied events in your event data store. For example, if you copy trail events that are 5 years old and specify a retention period of 7 years, the event data store will retain those events for two years.
527
528
  */
528
529
  RetentionPeriod?: RetentionPeriod;
529
530
  /**
@@ -539,6 +540,10 @@ declare namespace CloudTrail {
539
540
  * Specifies whether the event data store should start ingesting live events. The default is true.
540
541
  */
541
542
  StartIngestion?: Boolean;
543
+ /**
544
+ * The billing mode for the event data store determines the cost for ingesting events and the default and maximum retention period for the event data store. The following are the possible values: EXTENDABLE_RETENTION_PRICING - This billing mode is generally recommended if you want a flexible retention period of up to 3653 days (about 10 years). The default retention period for this billing mode is 366 days. FIXED_RETENTION_PRICING - This billing mode is recommended if you expect to ingest more than 25 TB of event data per month and need a retention period of up to 2557 days (about 7 years). The default retention period for this billing mode is 2557 days. The default value is EXTENDABLE_RETENTION_PRICING. For more information about CloudTrail pricing, see CloudTrail Pricing and Managing CloudTrail Lake costs.
545
+ */
546
+ BillingMode?: BillingMode;
542
547
  }
543
548
  export interface CreateEventDataStoreResponse {
544
549
  /**
@@ -586,6 +591,10 @@ declare namespace CloudTrail {
586
591
  * Specifies the KMS key ID that encrypts the events delivered by CloudTrail. The value is a fully specified ARN to a KMS key in the following format. arn:aws:kms:us-east-2:123456789012:key/12345678-1234-1234-1234-123456789012
587
592
  */
588
593
  KmsKeyId?: EventDataStoreKmsKeyId;
594
+ /**
595
+ * The billing mode for the event data store.
596
+ */
597
+ BillingMode?: BillingMode;
589
598
  }
590
599
  export interface CreateTrailRequest {
591
600
  /**
@@ -1006,6 +1015,10 @@ declare namespace CloudTrail {
1006
1015
  * Specifies the KMS key ID that encrypts the events delivered by CloudTrail. The value is a fully specified ARN to a KMS key in the following format. arn:aws:kms:us-east-2:123456789012:key/12345678-1234-1234-1234-123456789012
1007
1016
  */
1008
1017
  KmsKeyId?: EventDataStoreKmsKeyId;
1018
+ /**
1019
+ * The billing mode for the event data store.
1020
+ */
1021
+ BillingMode?: BillingMode;
1009
1022
  }
1010
1023
  export interface GetEventSelectorsRequest {
1011
1024
  /**
@@ -1859,6 +1872,10 @@ declare namespace CloudTrail {
1859
1872
  * Specifies the KMS key ID that encrypts the events delivered by CloudTrail. The value is a fully specified ARN to a KMS key in the following format. arn:aws:kms:us-east-2:123456789012:key/12345678-1234-1234-1234-123456789012
1860
1873
  */
1861
1874
  KmsKeyId?: EventDataStoreKmsKeyId;
1875
+ /**
1876
+ * The billing mode for the event data store.
1877
+ */
1878
+ BillingMode?: BillingMode;
1862
1879
  }
1863
1880
  export type RetentionPeriod = number;
1864
1881
  export interface S3ImportSource {
@@ -2197,7 +2214,7 @@ declare namespace CloudTrail {
2197
2214
  */
2198
2215
  OrganizationEnabled?: Boolean;
2199
2216
  /**
2200
- * The retention period of the event data store, in days. You can set a retention period of up to 2557 days, the equivalent of seven years. CloudTrail Lake determines whether to retain an event by checking if the eventTime of the event is within the specified retention period. For example, if you set a retention period of 90 days, CloudTrail will remove events when the eventTime is older than 90 days. If you decrease the retention period of an event data store, CloudTrail will remove any events with an eventTime older than the new retention period. For example, if the previous retention period was 365 days and you decrease it to 100 days, CloudTrail will remove events with an eventTime older than 100 days.
2217
+ * The retention period of the event data store, in days. If BillingMode is set to EXTENDABLE_RETENTION_PRICING, you can set a retention period of up to 3653 days, the equivalent of 10 years. If BillingMode is set to FIXED_RETENTION_PRICING, you can set a retention period of up to 2557 days, the equivalent of seven years. CloudTrail Lake determines whether to retain an event by checking if the eventTime of the event is within the specified retention period. For example, if you set a retention period of 90 days, CloudTrail will remove events when the eventTime is older than 90 days. If you decrease the retention period of an event data store, CloudTrail will remove any events with an eventTime older than the new retention period. For example, if the previous retention period was 365 days and you decrease it to 100 days, CloudTrail will remove events with an eventTime older than 100 days.
2201
2218
  */
2202
2219
  RetentionPeriod?: RetentionPeriod;
2203
2220
  /**
@@ -2208,6 +2225,10 @@ declare namespace CloudTrail {
2208
2225
  * Specifies the KMS key ID to use to encrypt the events delivered by CloudTrail. The value can be an alias name prefixed by alias/, a fully specified ARN to an alias, a fully specified ARN to a key, or a globally unique identifier. Disabling or deleting the KMS key, or removing CloudTrail permissions on the key, prevents CloudTrail from logging events to the event data store, and prevents users from querying the data in the event data store that was encrypted with the key. After you associate an event data store with a KMS key, the KMS key cannot be removed or changed. Before you disable or delete a KMS key that you are using with an event data store, delete or back up your event data store. CloudTrail also supports KMS multi-Region keys. For more information about multi-Region keys, see Using multi-Region keys in the Key Management Service Developer Guide. Examples: alias/MyAliasName arn:aws:kms:us-east-2:123456789012:alias/MyAliasName arn:aws:kms:us-east-2:123456789012:key/12345678-1234-1234-1234-123456789012 12345678-1234-1234-1234-123456789012
2209
2226
  */
2210
2227
  KmsKeyId?: EventDataStoreKmsKeyId;
2228
+ /**
2229
+ * You can't change the billing mode from EXTENDABLE_RETENTION_PRICING to FIXED_RETENTION_PRICING. If BillingMode is set to EXTENDABLE_RETENTION_PRICING and you want to use FIXED_RETENTION_PRICING instead, you'll need to stop ingestion on the event data store and create a new event data store that uses FIXED_RETENTION_PRICING. The billing mode for the event data store determines the cost for ingesting events and the default and maximum retention period for the event data store. The following are the possible values: EXTENDABLE_RETENTION_PRICING - This billing mode is generally recommended if you want a flexible retention period of up to 3653 days (about 10 years). The default retention period for this billing mode is 366 days. FIXED_RETENTION_PRICING - This billing mode is recommended if you expect to ingest more than 25 TB of event data per month and need a retention period of up to 2557 days (about 7 years). The default retention period for this billing mode is 2557 days. For more information about CloudTrail pricing, see CloudTrail Pricing and Managing CloudTrail Lake costs.
2230
+ */
2231
+ BillingMode?: BillingMode;
2211
2232
  }
2212
2233
  export interface UpdateEventDataStoreResponse {
2213
2234
  /**
@@ -2254,6 +2275,10 @@ declare namespace CloudTrail {
2254
2275
  * Specifies the KMS key ID that encrypts the events delivered by CloudTrail. The value is a fully specified ARN to a KMS key in the following format. arn:aws:kms:us-east-2:123456789012:key/12345678-1234-1234-1234-123456789012
2255
2276
  */
2256
2277
  KmsKeyId?: EventDataStoreKmsKeyId;
2278
+ /**
2279
+ * The billing mode for the event data store.
2280
+ */
2281
+ BillingMode?: BillingMode;
2257
2282
  }
2258
2283
  export interface UpdateTrailRequest {
2259
2284
  /**