cdk-comprehend-s3olap 2.0.107 → 2.0.109

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 +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 +12 -1
  6. package/node_modules/aws-sdk/README.md +1 -1
  7. package/node_modules/aws-sdk/apis/ce-2017-10-25.min.json +10 -8
  8. package/node_modules/aws-sdk/apis/iotfleetwise-2021-06-17.examples.json +5 -0
  9. package/node_modules/aws-sdk/apis/iotfleetwise-2021-06-17.min.json +1961 -0
  10. package/node_modules/aws-sdk/apis/iotfleetwise-2021-06-17.paginators.json +82 -0
  11. package/node_modules/aws-sdk/apis/iotfleetwise-2021-06-17.waiters2.json +5 -0
  12. package/node_modules/aws-sdk/apis/location-2020-11-19.min.json +64 -17
  13. package/node_modules/aws-sdk/apis/metadata.json +3 -0
  14. package/node_modules/aws-sdk/apis/ssm-2014-11-06.min.json +396 -287
  15. package/node_modules/aws-sdk/clients/all.d.ts +1 -0
  16. package/node_modules/aws-sdk/clients/all.js +2 -1
  17. package/node_modules/aws-sdk/clients/costexplorer.d.ts +15 -7
  18. package/node_modules/aws-sdk/clients/cur.d.ts +1 -1
  19. package/node_modules/aws-sdk/clients/iotfleetwise.d.ts +2549 -0
  20. package/node_modules/aws-sdk/clients/iotfleetwise.js +19 -0
  21. package/node_modules/aws-sdk/clients/kendra.d.ts +36 -36
  22. package/node_modules/aws-sdk/clients/location.d.ts +54 -4
  23. package/node_modules/aws-sdk/clients/ssm.d.ts +112 -1
  24. package/node_modules/aws-sdk/dist/aws-sdk-core-react-native.js +31 -11
  25. package/node_modules/aws-sdk/dist/aws-sdk-react-native.js +93 -23
  26. package/node_modules/aws-sdk/dist/aws-sdk.js +492 -317
  27. package/node_modules/aws-sdk/dist/aws-sdk.min.js +42 -41
  28. package/node_modules/aws-sdk/lib/config_service_placeholders.d.ts +2 -0
  29. package/node_modules/aws-sdk/lib/core.js +1 -1
  30. package/node_modules/aws-sdk/lib/event_listeners.js +1 -0
  31. package/node_modules/aws-sdk/lib/protocol/rest_json.js +15 -2
  32. package/node_modules/aws-sdk/package.json +1 -1
  33. package/package.json +7 -7
@@ -314,3 +314,4 @@ export import BackupStorage = require('./backupstorage');
314
314
  export import PrivateNetworks = require('./privatenetworks');
315
315
  export import SupportApp = require('./supportapp');
316
316
  export import ControlTower = require('./controltower');
317
+ export import IoTFleetWise = require('./iotfleetwise');
@@ -315,5 +315,6 @@ module.exports = {
315
315
  BackupStorage: require('./backupstorage'),
316
316
  PrivateNetworks: require('./privatenetworks'),
317
317
  SupportApp: require('./supportapp'),
318
- ControlTower: require('./controltower')
318
+ ControlTower: require('./controltower'),
319
+ IoTFleetWise: require('./iotfleetwise')
319
320
  };
@@ -465,11 +465,11 @@ declare namespace CostExplorer {
465
465
  */
466
466
  CostCategoryArn: Arn;
467
467
  /**
468
- * The effective state data of your Cost Category.
468
+ * The effective start date of your Cost Category.
469
469
  */
470
470
  EffectiveStart: ZonedDateTime;
471
471
  /**
472
- * The effective end data of your Cost Category.
472
+ * The effective end date of your Cost Category.
473
473
  */
474
474
  EffectiveEnd?: ZonedDateTime;
475
475
  Name: CostCategoryName;
@@ -716,6 +716,10 @@ declare namespace CostExplorer {
716
716
  }
717
717
  export interface CreateCostCategoryDefinitionRequest {
718
718
  Name: CostCategoryName;
719
+ /**
720
+ * The Cost Category's effective start date. It can only be a billing start date (first day of the month). If the date isn't provided, it's the first day of the current month. Dates can't be before the previous twelve months, or in the future.
721
+ */
722
+ EffectiveStart?: ZonedDateTime;
719
723
  RuleVersion: CostCategoryRuleVersion;
720
724
  /**
721
725
  * The Cost Category rules used to categorize costs. For more information, see CostCategoryRule.
@@ -737,7 +741,7 @@ declare namespace CostExplorer {
737
741
  */
738
742
  CostCategoryArn?: Arn;
739
743
  /**
740
- * The Cost Category's effective start date.
744
+ * The Cost Category's effective start date. It can only be a billing start date (first day of the month).
741
745
  */
742
746
  EffectiveStart?: ZonedDateTime;
743
747
  }
@@ -845,7 +849,7 @@ declare namespace CostExplorer {
845
849
  export type Dimension = "AZ"|"INSTANCE_TYPE"|"LINKED_ACCOUNT"|"LINKED_ACCOUNT_NAME"|"OPERATION"|"PURCHASE_TYPE"|"REGION"|"SERVICE"|"SERVICE_CODE"|"USAGE_TYPE"|"USAGE_TYPE_GROUP"|"RECORD_TYPE"|"OPERATING_SYSTEM"|"TENANCY"|"SCOPE"|"PLATFORM"|"SUBSCRIPTION_ID"|"LEGAL_ENTITY_NAME"|"DEPLOYMENT_OPTION"|"DATABASE_ENGINE"|"CACHE_ENGINE"|"INSTANCE_TYPE_FAMILY"|"BILLING_ENTITY"|"RESERVATION_ID"|"RESOURCE_ID"|"RIGHTSIZING_TYPE"|"SAVINGS_PLANS_TYPE"|"SAVINGS_PLAN_ARN"|"PAYMENT_OPTION"|"AGREEMENT_END_DATE_TIME_AFTER"|"AGREEMENT_END_DATE_TIME_BEFORE"|"INVOICING_ENTITY"|string;
846
850
  export interface DimensionValues {
847
851
  /**
848
- * The names of the metadata types that you can use to filter and group your results. For example, AZ returns a list of Availability Zones.
852
+ * The names of the metadata types that you can use to filter and group your results. For example, AZ returns a list of Availability Zones. LINK_ACCOUNT_NAME and SERVICE_CODE can only be used in CostCategoryRule.
849
853
  */
850
854
  Key?: Dimension;
851
855
  /**
@@ -1371,7 +1375,7 @@ declare namespace CostExplorer {
1371
1375
  */
1372
1376
  TimePeriod: DateInterval;
1373
1377
  /**
1374
- * The name of the dimension. Each Dimension is available for a different Context. For more information, see Context.
1378
+ * The name of the dimension. Each Dimension is available for a different Context. For more information, see Context. LINK_ACCOUNT_NAME and SERVICE_CODE can only be used in CostCategoryRule.
1375
1379
  */
1376
1380
  Dimension: Dimension;
1377
1381
  /**
@@ -1394,7 +1398,7 @@ declare namespace CostExplorer {
1394
1398
  }
1395
1399
  export interface GetDimensionValuesResponse {
1396
1400
  /**
1397
- * The filters that you used to filter your request. Some dimensions are available only for a specific context. If you set the context to COST_AND_USAGE, you can use the following dimensions for searching: AZ - The Availability Zone. An example is us-east-1a. DATABASE_ENGINE - The Amazon Relational Database Service database. Examples are Aurora or MySQL. INSTANCE_TYPE - The type of Amazon EC2 instance. An example is m4.xlarge. LEGAL_ENTITY_NAME - The name of the organization that sells you Amazon Web Services services, such as Amazon Web Services. LINKED_ACCOUNT - The description in the attribute map that includes the full name of the member account. The value field contains the Amazon Web Services ID of the member account. OPERATING_SYSTEM - The operating system. Examples are Windows or Linux. OPERATION - The action performed. Examples include RunInstance and CreateBucket. PLATFORM - The Amazon EC2 operating system. Examples are Windows or Linux. PURCHASE_TYPE - The reservation type of the purchase to which this usage is related. Examples include On-Demand Instances and Standard Reserved Instances. SERVICE - The Amazon Web Services service such as Amazon DynamoDB. USAGE_TYPE - The type of usage. An example is DataTransfer-In-Bytes. The response for the GetDimensionValues operation includes a unit attribute. Examples include GB and Hrs. USAGE_TYPE_GROUP - The grouping of common usage types. An example is Amazon EC2: CloudWatch – Alarms. The response for this operation includes a unit attribute. RECORD_TYPE - The different types of charges such as RI fees, usage costs, tax refunds, and credits. RESOURCE_ID - The unique identifier of the resource. ResourceId is an opt-in feature only available for last 14 days for EC2-Compute Service. If you set the context to RESERVATIONS, you can use the following dimensions for searching: AZ - The Availability Zone. An example is us-east-1a. CACHE_ENGINE - The Amazon ElastiCache operating system. Examples are Windows or Linux. DEPLOYMENT_OPTION - The scope of Amazon Relational Database Service deployments. Valid values are SingleAZ and MultiAZ. INSTANCE_TYPE - The type of Amazon EC2 instance. An example is m4.xlarge. LINKED_ACCOUNT - The description in the attribute map that includes the full name of the member account. The value field contains the Amazon Web Services ID of the member account. PLATFORM - The Amazon EC2 operating system. Examples are Windows or Linux. REGION - The Amazon Web Services Region. SCOPE (Utilization only) - The scope of a Reserved Instance (RI). Values are regional or a single Availability Zone. TAG (Coverage only) - The tags that are associated with a Reserved Instance (RI). TENANCY - The tenancy of a resource. Examples are shared or dedicated. If you set the context to SAVINGS_PLANS, you can use the following dimensions for searching: SAVINGS_PLANS_TYPE - Type of Savings Plans (EC2 Instance or Compute) PAYMENT_OPTION - Payment option for the given Savings Plans (for example, All Upfront) REGION - The Amazon Web Services Region. INSTANCE_TYPE_FAMILY - The family of instances (For example, m5) LINKED_ACCOUNT - The description in the attribute map that includes the full name of the member account. The value field contains the Amazon Web Services ID of the member account. SAVINGS_PLAN_ARN - The unique identifier for your Savings Plan
1401
+ * The filters that you used to filter your request. Some dimensions are available only for a specific context. If you set the context to COST_AND_USAGE, you can use the following dimensions for searching: AZ - The Availability Zone. An example is us-east-1a. DATABASE_ENGINE - The Amazon Relational Database Service database. Examples are Aurora or MySQL. INSTANCE_TYPE - The type of Amazon EC2 instance. An example is m4.xlarge. LEGAL_ENTITY_NAME - The name of the organization that sells you Amazon Web Services services, such as Amazon Web Services. LINKED_ACCOUNT - The description in the attribute map that includes the full name of the member account. The value field contains the Amazon Web Services ID of the member account. OPERATING_SYSTEM - The operating system. Examples are Windows or Linux. OPERATION - The action performed. Examples include RunInstance and CreateBucket. PLATFORM - The Amazon EC2 operating system. Examples are Windows or Linux. PURCHASE_TYPE - The reservation type of the purchase to which this usage is related. Examples include On-Demand Instances and Standard Reserved Instances. SERVICE - The Amazon Web Services service such as Amazon DynamoDB. USAGE_TYPE - The type of usage. An example is DataTransfer-In-Bytes. The response for the GetDimensionValues operation includes a unit attribute. Examples include GB and Hrs. USAGE_TYPE_GROUP - The grouping of common usage types. An example is Amazon EC2: CloudWatch – Alarms. The response for this operation includes a unit attribute. RECORD_TYPE - The different types of charges such as RI fees, usage costs, tax refunds, and credits. RESOURCE_ID - The unique identifier of the resource. ResourceId is an opt-in feature only available for last 14 days for EC2-Compute Service. You can opt-in by enabling Hourly and Resource Level Data in Cost Management Console preferences. If you set the context to RESERVATIONS, you can use the following dimensions for searching: AZ - The Availability Zone. An example is us-east-1a. CACHE_ENGINE - The Amazon ElastiCache operating system. Examples are Windows or Linux. DEPLOYMENT_OPTION - The scope of Amazon Relational Database Service deployments. Valid values are SingleAZ and MultiAZ. INSTANCE_TYPE - The type of Amazon EC2 instance. An example is m4.xlarge. LINKED_ACCOUNT - The description in the attribute map that includes the full name of the member account. The value field contains the Amazon Web Services ID of the member account. PLATFORM - The Amazon EC2 operating system. Examples are Windows or Linux. REGION - The Amazon Web Services Region. SCOPE (Utilization only) - The scope of a Reserved Instance (RI). Values are regional or a single Availability Zone. TAG (Coverage only) - The tags that are associated with a Reserved Instance (RI). TENANCY - The tenancy of a resource. Examples are shared or dedicated. If you set the context to SAVINGS_PLANS, you can use the following dimensions for searching: SAVINGS_PLANS_TYPE - Type of Savings Plans (EC2 Instance or Compute) PAYMENT_OPTION - Payment option for the given Savings Plans (for example, All Upfront) REGION - The Amazon Web Services Region. INSTANCE_TYPE_FAMILY - The family of instances (For example, m5) LINKED_ACCOUNT - The description in the attribute map that includes the full name of the member account. The value field contains the Amazon Web Services ID of the member account. SAVINGS_PLAN_ARN - The unique identifier for your Savings Plan
1398
1402
  */
1399
1403
  DimensionValues: DimensionValuesWithAttributesList;
1400
1404
  /**
@@ -3004,6 +3008,10 @@ declare namespace CostExplorer {
3004
3008
  * The unique identifier for your Cost Category.
3005
3009
  */
3006
3010
  CostCategoryArn: Arn;
3011
+ /**
3012
+ * The Cost Category's effective start date. It can only be a billing start date (first day of the month). If the date isn't provided, it's the first day of the current month. Dates can't be before the previous twelve months, or in the future.
3013
+ */
3014
+ EffectiveStart?: ZonedDateTime;
3007
3015
  RuleVersion: CostCategoryRuleVersion;
3008
3016
  /**
3009
3017
  * The Expression object used to categorize costs. For more information, see CostCategoryRule .
@@ -3021,7 +3029,7 @@ declare namespace CostExplorer {
3021
3029
  */
3022
3030
  CostCategoryArn?: Arn;
3023
3031
  /**
3024
- * The Cost Category's effective start date.
3032
+ * The Cost Category's effective start date. It can only be a billing start date (first day of the month).
3025
3033
  */
3026
3034
  EffectiveStart?: ZonedDateTime;
3027
3035
  }
@@ -45,7 +45,7 @@ declare class CUR extends Service {
45
45
  putReportDefinition(callback?: (err: AWSError, data: CUR.Types.PutReportDefinitionResponse) => void): Request<CUR.Types.PutReportDefinitionResponse, AWSError>;
46
46
  }
47
47
  declare namespace CUR {
48
- export type AWSRegion = "af-south-1"|"ap-east-1"|"ap-south-1"|"ap-southeast-1"|"ap-southeast-2"|"ap-northeast-1"|"ap-northeast-2"|"ap-northeast-3"|"ca-central-1"|"eu-central-1"|"eu-west-1"|"eu-west-2"|"eu-west-3"|"eu-north-1"|"eu-south-1"|"me-south-1"|"sa-east-1"|"us-east-1"|"us-east-2"|"us-west-1"|"us-west-2"|"cn-north-1"|"cn-northwest-1"|string;
48
+ export type AWSRegion = "af-south-1"|"ap-east-1"|"ap-south-1"|"ap-southeast-1"|"ap-southeast-2"|"ap-southeast-3"|"ap-northeast-1"|"ap-northeast-2"|"ap-northeast-3"|"ca-central-1"|"eu-central-1"|"eu-west-1"|"eu-west-2"|"eu-west-3"|"eu-north-1"|"eu-south-1"|"eu-south-2"|"me-central-1"|"me-south-1"|"sa-east-1"|"us-east-1"|"us-east-2"|"us-west-1"|"us-west-2"|"cn-north-1"|"cn-northwest-1"|string;
49
49
  export type AdditionalArtifact = "REDSHIFT"|"QUICKSIGHT"|"ATHENA"|string;
50
50
  export type AdditionalArtifactList = AdditionalArtifact[];
51
51
  export type BillingViewArn = string;