cdk-rds-sql 1.3.1 → 2.0.0

package/node_modules/aws-sdk/clients/devopsguru.d.ts

@@ -212,11 +212,11 @@ declare class DevOpsGuru extends Service {
    */
   removeNotificationChannel(callback?: (err: AWSError, data: DevOpsGuru.Types.RemoveNotificationChannelResponse) => void): Request<DevOpsGuru.Types.RemoveNotificationChannelResponse, AWSError>;
   /**
-   *  Returns a list of insights in your Amazon Web Services account. You can specify which insights are returned by their start time, one or more statuses (ONGOING, CLOSED, and CLOSED), one or more severities (LOW, MEDIUM, and HIGH), and type (REACTIVE or PROACTIVE).   Use the Filters parameter to specify status and severity search parameters. Use the Type parameter to specify REACTIVE or PROACTIVE in your search. 
+   *  Returns a list of insights in your Amazon Web Services account. You can specify which insights are returned by their start time, one or more statuses (ONGOING or CLOSED), one or more severities (LOW, MEDIUM, and HIGH), and type (REACTIVE or PROACTIVE).   Use the Filters parameter to specify status and severity search parameters. Use the Type parameter to specify REACTIVE or PROACTIVE in your search. 
    */
   searchInsights(params: DevOpsGuru.Types.SearchInsightsRequest, callback?: (err: AWSError, data: DevOpsGuru.Types.SearchInsightsResponse) => void): Request<DevOpsGuru.Types.SearchInsightsResponse, AWSError>;
   /**
-   *  Returns a list of insights in your Amazon Web Services account. You can specify which insights are returned by their start time, one or more statuses (ONGOING, CLOSED, and CLOSED), one or more severities (LOW, MEDIUM, and HIGH), and type (REACTIVE or PROACTIVE).   Use the Filters parameter to specify status and severity search parameters. Use the Type parameter to specify REACTIVE or PROACTIVE in your search. 
+   *  Returns a list of insights in your Amazon Web Services account. You can specify which insights are returned by their start time, one or more statuses (ONGOING or CLOSED), one or more severities (LOW, MEDIUM, and HIGH), and type (REACTIVE or PROACTIVE).   Use the Filters parameter to specify status and severity search parameters. Use the Type parameter to specify REACTIVE or PROACTIVE in your search. 
    */
   searchInsights(callback?: (err: AWSError, data: DevOpsGuru.Types.SearchInsightsResponse) => void): Request<DevOpsGuru.Types.SearchInsightsResponse, AWSError>;
   /**
@@ -301,6 +301,7 @@ declare namespace DevOpsGuru {
      */
     Status?: EventSourceOptInStatus;
   }
+  export type AnalyzedResourceCount = number;
   export interface AnomalousLogGroup {
     /**
      *  The name of the CloudWatch log group. 
@@ -419,6 +420,10 @@ declare namespace DevOpsGuru {
      *  Information about the health of the Amazon Web Services resources in your account that are specified by an Amazon Web Services CloudFormation stack, including the number of open proactive, open reactive insights, and the Mean Time to Recover (MTTR) of closed insights. 
      */
     Insight?: InsightHealth;
+    /**
+     *  Number of resources that DevOps Guru is monitoring in your account that are specified by an Amazon Web Services CloudFormation stack. 
+     */
+    AnalyzedResourceCount?: AnalyzedResourceCount;
   }
   export type CloudFormationHealths = CloudFormationHealth[];
   export type CloudWatchMetricDataStatusCode = "Complete"|"InternalError"|"PartialData"|string;
@@ -488,7 +493,7 @@ declare namespace DevOpsGuru {
      */
     CloudFormation?: CloudFormationCostEstimationResourceCollectionFilter;
     /**
-     * The Amazon Web Services tags used to filter the resource collection that is used for a cost estimate. Tags help you identify and organize your Amazon Web Services resources. Many Amazon Web Services services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you can assign the same tag to an Amazon DynamoDB table resource that you assign to an Lambda function. For more information about using tags, see the Tagging best practices whitepaper.  Each Amazon Web Services tag has two parts.    A tag key (for example, CostCenter, Environment, Project, or Secret). Tag keys are case-sensitive.   An optional field known as a tag value (for example, 111122223333, Production, or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case-sensitive.   Together these are known as key-value pairs.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be Devops-guru-deployment-application or Devops-guru-rds-application. While keys are case-sensitive, the case of key characters don't matter to DevOps Guru. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
+     * The Amazon Web Services tags used to filter the resource collection that is used for a cost estimate. Tags help you identify and organize your Amazon Web Services resources. Many Amazon Web Services services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you can assign the same tag to an Amazon DynamoDB table resource that you assign to an Lambda function. For more information about using tags, see the Tagging best practices whitepaper.  Each Amazon Web Services tag has two parts.    A tag key (for example, CostCenter, Environment, Project, or Secret). Tag keys are case-sensitive.   An optional field known as a tag value (for example, 111122223333, Production, or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case-sensitive.   Together these are known as key-value pairs.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or devops-guru-rds-application. When you create a key, the case of characters in the key can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two different keys. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
      */
     Tags?: TagCostEstimationResourceCollectionFilters;
   }
@@ -534,6 +539,10 @@ declare namespace DevOpsGuru {
      * The number of Amazon DevOps Guru resource analysis hours billed to the current Amazon Web Services account in the last hour. 
      */
     ResourceHours: ResourceHours;
+    /**
+     *  Number of resources that DevOps Guru is monitoring in your Amazon Web Services account. 
+     */
+    AnalyzedResourceCount?: AnalyzedResourceCount;
   }
   export interface DescribeAccountOverviewRequest {
     /**
@@ -712,7 +721,7 @@ declare namespace DevOpsGuru {
      */
     NextToken?: UuidNextToken;
     /**
-     * Tags help you identify and organize your Amazon Web Services resources. Many Amazon Web Services services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you can assign the same tag to an Amazon DynamoDB table resource that you assign to an Lambda function. For more information about using tags, see the Tagging best practices whitepaper.  Each Amazon Web Services tag has two parts.    A tag key (for example, CostCenter, Environment, Project, or Secret). Tag keys are case-sensitive.   An optional field known as a tag value (for example, 111122223333, Production, or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case-sensitive.   Together these are known as key-value pairs.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be Devops-guru-deployment-application or Devops-guru-rds-application. While keys are case-sensitive, the case of key characters don't matter to DevOps Guru. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
+     * Tags help you identify and organize your Amazon Web Services resources. Many Amazon Web Services services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you can assign the same tag to an Amazon DynamoDB table resource that you assign to an Lambda function. For more information about using tags, see the Tagging best practices whitepaper.  Each Amazon Web Services tag has two parts.    A tag key (for example, CostCenter, Environment, Project, or Secret). Tag keys are case-sensitive.   An optional field known as a tag value (for example, 111122223333, Production, or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case-sensitive.   Together these are known as key-value pairs.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or devops-guru-rds-application. When you create a key, the case of characters in the key can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two different keys. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
      */
     Tags?: TagHealths;
   }
@@ -740,7 +749,7 @@ declare namespace DevOpsGuru {
      */
     NextToken?: UuidNextToken;
     /**
-     * The Amazon Web Services tags that are used by resources in the resource collection. Tags help you identify and organize your Amazon Web Services resources. Many Amazon Web Services services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you can assign the same tag to an Amazon DynamoDB table resource that you assign to an Lambda function. For more information about using tags, see the Tagging best practices whitepaper.  Each Amazon Web Services tag has two parts.    A tag key (for example, CostCenter, Environment, Project, or Secret). Tag keys are case-sensitive.   An optional field known as a tag value (for example, 111122223333, Production, or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case-sensitive.   Together these are known as key-value pairs.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be Devops-guru-deployment-application or Devops-guru-rds-application. While keys are case-sensitive, the case of key characters don't matter to DevOps Guru. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
+     * The Amazon Web Services tags that are used by resources in the resource collection. Tags help you identify and organize your Amazon Web Services resources. Many Amazon Web Services services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you can assign the same tag to an Amazon DynamoDB table resource that you assign to an Lambda function. For more information about using tags, see the Tagging best practices whitepaper.  Each Amazon Web Services tag has two parts.    A tag key (for example, CostCenter, Environment, Project, or Secret). Tag keys are case-sensitive.   An optional field known as a tag value (for example, 111122223333, Production, or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case-sensitive.   Together these are known as key-value pairs.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or devops-guru-rds-application. When you create a key, the case of characters in the key can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two different keys. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
      */
     Tags?: TagHealths;
   }
@@ -1131,7 +1140,7 @@ declare namespace DevOpsGuru {
     /**
      *  Filters to determine which monitored resources you want to retrieve. You can filter by resource type or resource permission status. 
      */
-    Filters: ListMonitoredResourcesFilters;
+    Filters?: ListMonitoredResourcesFilters;
     /**
      * The maximum number of results to return with a single call. To retrieve the remaining results, make another call with the returned nextToken value.
      */
@@ -1299,6 +1308,11 @@ declare namespace DevOpsGuru {
      *  The permission status of a resource. 
      */
     ResourcePermission?: ResourcePermission;
+    /**
+     *  The time at which DevOps Guru last updated this resource. 
+     */
+    LastUpdated?: Timestamp;
+    ResourceCollection?: ResourceCollection;
   }
   export type MonitoredResourceIdentifiers = MonitoredResourceIdentifier[];
   export type MonitoredResourceName = string;
@@ -1317,8 +1331,24 @@ declare namespace DevOpsGuru {
      *  Information about a notification channel configured in DevOps Guru to send notifications when insights are created.  If you use an Amazon SNS topic in another account, you must attach a policy to it that grants DevOps Guru permission to it notifications. DevOps Guru adds the required policy on your behalf to send notifications using Amazon SNS in your account. DevOps Guru only supports standard SNS topics. For more information, see Permissions for cross account Amazon SNS topics. If you use an Amazon SNS topic in another account, you must attach a policy to it that grants DevOps Guru permission to it notifications. DevOps Guru adds the required policy on your behalf to send notifications using Amazon SNS in your account. For more information, see Permissions for cross account Amazon SNS topics. If you use an Amazon SNS topic that is encrypted by an Amazon Web Services Key Management Service customer-managed key (CMK), then you must add permissions to the CMK. For more information, see Permissions for Amazon Web Services KMS–encrypted Amazon SNS topics.
      */
     Sns: SnsChannelConfig;
+    /**
+     *  The filter configurations for the Amazon SNS notification topic you use with DevOps Guru. If you do not provide filter configurations, the default configurations are to receive notifications for all message types of High or Medium severity. 
+     */
+    Filters?: NotificationFilterConfig;
   }
   export type NotificationChannelId = string;
+  export interface NotificationFilterConfig {
+    /**
+     *  The severity levels that you want to receive notifications for. For example, you can choose to receive notifications only for insights with HIGH and MEDIUM severity levels. For more information, see Understanding insight severities. 
+     */
+    Severities?: InsightSeverities;
+    /**
+     *  The events that you want to receive notifications for. For example, you can choose to receive notifications only when the severity level is upgraded or a new insight is created. 
+     */
+    MessageTypes?: NotificationMessageTypes;
+  }
+  export type NotificationMessageType = "NEW_INSIGHT"|"CLOSED_INSIGHT"|"NEW_ASSOCIATION"|"SEVERITY_UPGRADED"|"NEW_RECOMMENDATION"|string;
+  export type NotificationMessageTypes = NotificationMessageType[];
   export type NumMetricsAnalyzed = number;
   export type NumOpenProactiveInsights = number;
   export type NumOpenReactiveInsights = number;
@@ -1962,7 +1992,7 @@ declare namespace DevOpsGuru {
      */
     CloudFormation?: CloudFormationCollection;
     /**
-     * The Amazon Web Services tags that are used by resources in the resource collection. Tags help you identify and organize your Amazon Web Services resources. Many Amazon Web Services services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you can assign the same tag to an Amazon DynamoDB table resource that you assign to an Lambda function. For more information about using tags, see the Tagging best practices whitepaper.  Each Amazon Web Services tag has two parts.    A tag key (for example, CostCenter, Environment, Project, or Secret). Tag keys are case-sensitive.   An optional field known as a tag value (for example, 111122223333, Production, or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case-sensitive.   Together these are known as key-value pairs.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be Devops-guru-deployment-application or Devops-guru-rds-application. While keys are case-sensitive, the case of key characters don't matter to DevOps Guru. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
+     * The Amazon Web Services tags that are used by resources in the resource collection. Tags help you identify and organize your Amazon Web Services resources. Many Amazon Web Services services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you can assign the same tag to an Amazon DynamoDB table resource that you assign to an Lambda function. For more information about using tags, see the Tagging best practices whitepaper.  Each Amazon Web Services tag has two parts.    A tag key (for example, CostCenter, Environment, Project, or Secret). Tag keys are case-sensitive.   An optional field known as a tag value (for example, 111122223333, Production, or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case-sensitive.   Together these are known as key-value pairs.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or devops-guru-rds-application. When you create a key, the case of characters in the key can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two different keys. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
      */
     Tags?: TagCollections;
   }
@@ -1972,7 +2002,7 @@ declare namespace DevOpsGuru {
      */
     CloudFormation?: CloudFormationCollectionFilter;
     /**
-     * The Amazon Web Services tags used to filter the resources in the resource collection. Tags help you identify and organize your Amazon Web Services resources. Many Amazon Web Services services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you can assign the same tag to an Amazon DynamoDB table resource that you assign to an Lambda function. For more information about using tags, see the Tagging best practices whitepaper.  Each Amazon Web Services tag has two parts.    A tag key (for example, CostCenter, Environment, Project, or Secret). Tag keys are case-sensitive.   An optional field known as a tag value (for example, 111122223333, Production, or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case-sensitive.   Together these are known as key-value pairs.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be Devops-guru-deployment-application or Devops-guru-rds-application. While keys are case-sensitive, the case of key characters don't matter to DevOps Guru. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
+     * The Amazon Web Services tags used to filter the resources in the resource collection. Tags help you identify and organize your Amazon Web Services resources. Many Amazon Web Services services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you can assign the same tag to an Amazon DynamoDB table resource that you assign to an Lambda function. For more information about using tags, see the Tagging best practices whitepaper.  Each Amazon Web Services tag has two parts.    A tag key (for example, CostCenter, Environment, Project, or Secret). Tag keys are case-sensitive.   An optional field known as a tag value (for example, 111122223333, Production, or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case-sensitive.   Together these are known as key-value pairs.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or devops-guru-rds-application. When you create a key, the case of characters in the key can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two different keys. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
      */
     Tags?: TagCollectionFilters;
   }
@@ -1981,7 +2011,7 @@ declare namespace DevOpsGuru {
   export type ResourceName = string;
   export type ResourcePermission = "FULL_PERMISSION"|"MISSING_PERMISSION"|string;
   export type ResourceType = string;
-  export type ResourceTypeFilter = "LOG_GROUPS"|string;
+  export type ResourceTypeFilter = "LOG_GROUPS"|"CLOUDFRONT_DISTRIBUTION"|"DYNAMODB_TABLE"|"EC2_NAT_GATEWAY"|"ECS_CLUSTER"|"ECS_SERVICE"|"EKS_CLUSTER"|"ELASTIC_BEANSTALK_ENVIRONMENT"|"ELASTIC_LOAD_BALANCER_LOAD_BALANCER"|"ELASTIC_LOAD_BALANCING_V2_LOAD_BALANCER"|"ELASTIC_LOAD_BALANCING_V2_TARGET_GROUP"|"ELASTICACHE_CACHE_CLUSTER"|"ELASTICSEARCH_DOMAIN"|"KINESIS_STREAM"|"LAMBDA_FUNCTION"|"OPEN_SEARCH_SERVICE_DOMAIN"|"RDS_DB_INSTANCE"|"RDS_DB_CLUSTER"|"REDSHIFT_CLUSTER"|"ROUTE53_HOSTED_ZONE"|"ROUTE53_HEALTH_CHECK"|"S3_BUCKET"|"SAGEMAKER_ENDPOINT"|"SNS_TOPIC"|"SQS_QUEUE"|"STEP_FUNCTIONS_ACTIVITY"|"STEP_FUNCTIONS_STATE_MACHINE"|string;
   export type ResourceTypeFilters = ResourceTypeFilter[];
   export type SearchInsightsAccountIdList = AwsAccountId[];
   export interface SearchInsightsFilters {
@@ -2101,6 +2131,10 @@ declare namespace DevOpsGuru {
      * Represents the health of an Amazon Web Services service. This is a ServiceInsightHealth that contains the number of open proactive and reactive insights for this service.
      */
     Insight?: ServiceInsightHealth;
+    /**
+     *  Number of resources that DevOps Guru is monitoring in an analyzed Amazon Web Services service. 
+     */
+    AnalyzedResourceCount?: AnalyzedResourceCount;
   }
   export type ServiceHealths = ServiceHealth[];
   export interface ServiceInsightHealth {
@@ -2181,7 +2215,7 @@ declare namespace DevOpsGuru {
   }
   export interface TagCollection {
     /**
-     * An Amazon Web Services tag key that is used to identify the Amazon Web Services resources that DevOps Guru analyzes. All Amazon Web Services resources in your account and Region tagged with this key make up your DevOps Guru application and analysis boundary.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be Devops-guru-deployment-application or Devops-guru-rds-application. While keys are case-sensitive, the case of key characters don't matter to DevOps Guru. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
+     * An Amazon Web Services tag key that is used to identify the Amazon Web Services resources that DevOps Guru analyzes. All Amazon Web Services resources in your account and Region tagged with this key make up your DevOps Guru application and analysis boundary.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or devops-guru-rds-application. When you create a key, the case of characters in the key can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two different keys. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
      */
     AppBoundaryKey: AppBoundaryKey;
     /**
@@ -2191,7 +2225,7 @@ declare namespace DevOpsGuru {
   }
   export interface TagCollectionFilter {
     /**
-     * An Amazon Web Services tag key that is used to identify the Amazon Web Services resources that DevOps Guru analyzes. All Amazon Web Services resources in your account and Region tagged with this key make up your DevOps Guru application and analysis boundary.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be Devops-guru-deployment-application or Devops-guru-rds-application. While keys are case-sensitive, the case of key characters don't matter to DevOps Guru. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
+     * An Amazon Web Services tag key that is used to identify the Amazon Web Services resources that DevOps Guru analyzes. All Amazon Web Services resources in your account and Region tagged with this key make up your DevOps Guru application and analysis boundary.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or devops-guru-rds-application. When you create a key, the case of characters in the key can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two different keys. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
      */
     AppBoundaryKey: AppBoundaryKey;
     /**
@@ -2203,7 +2237,7 @@ declare namespace DevOpsGuru {
   export type TagCollections = TagCollection[];
   export interface TagCostEstimationResourceCollectionFilter {
     /**
-     * An Amazon Web Services tag key that is used to identify the Amazon Web Services resources that DevOps Guru analyzes. All Amazon Web Services resources in your account and Region tagged with this key make up your DevOps Guru application and analysis boundary.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be Devops-guru-deployment-application or Devops-guru-rds-application. While keys are case-sensitive, the case of key characters don't matter to DevOps Guru. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
+     * An Amazon Web Services tag key that is used to identify the Amazon Web Services resources that DevOps Guru analyzes. All Amazon Web Services resources in your account and Region tagged with this key make up your DevOps Guru application and analysis boundary.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or devops-guru-rds-application. When you create a key, the case of characters in the key can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two different keys. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
      */
     AppBoundaryKey: AppBoundaryKey;
     /**
@@ -2214,7 +2248,7 @@ declare namespace DevOpsGuru {
   export type TagCostEstimationResourceCollectionFilters = TagCostEstimationResourceCollectionFilter[];
   export interface TagHealth {
     /**
-     * An Amazon Web Services tag key that is used to identify the Amazon Web Services resources that DevOps Guru analyzes. All Amazon Web Services resources in your account and Region tagged with this key make up your DevOps Guru application and analysis boundary.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be Devops-guru-deployment-application or Devops-guru-rds-application. While keys are case-sensitive, the case of key characters don't matter to DevOps Guru. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
+     * An Amazon Web Services tag key that is used to identify the Amazon Web Services resources that DevOps Guru analyzes. All Amazon Web Services resources in your account and Region tagged with this key make up your DevOps Guru application and analysis boundary.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or devops-guru-rds-application. When you create a key, the case of characters in the key can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two different keys. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
      */
     AppBoundaryKey?: AppBoundaryKey;
     /**
@@ -2225,6 +2259,10 @@ declare namespace DevOpsGuru {
      * Information about the health of the Amazon Web Services resources in your account that are specified by an Amazon Web Services tag, including the number of open proactive, open reactive insights, and the Mean Time to Recover (MTTR) of closed insights. 
      */
     Insight?: InsightHealth;
+    /**
+     *  Number of resources that DevOps Guru is monitoring in your account that are specified by an Amazon Web Services tag. 
+     */
+    AnalyzedResourceCount?: AnalyzedResourceCount;
   }
   export type TagHealths = TagHealth[];
   export type TagValue = string;
@@ -2263,7 +2301,7 @@ declare namespace DevOpsGuru {
      */
     CloudFormation?: UpdateCloudFormationCollectionFilter;
     /**
-     * The updated Amazon Web Services tags used to filter the resources in the resource collection. Tags help you identify and organize your Amazon Web Services resources. Many Amazon Web Services services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you can assign the same tag to an Amazon DynamoDB table resource that you assign to an Lambda function. For more information about using tags, see the Tagging best practices whitepaper.  Each Amazon Web Services tag has two parts.    A tag key (for example, CostCenter, Environment, Project, or Secret). Tag keys are case-sensitive.   An optional field known as a tag value (for example, 111122223333, Production, or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case-sensitive.   Together these are known as key-value pairs.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be Devops-guru-deployment-application or Devops-guru-rds-application. While keys are case-sensitive, the case of key characters don't matter to DevOps Guru. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
+     * The updated Amazon Web Services tags used to filter the resources in the resource collection. Tags help you identify and organize your Amazon Web Services resources. Many Amazon Web Services services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you can assign the same tag to an Amazon DynamoDB table resource that you assign to an Lambda function. For more information about using tags, see the Tagging best practices whitepaper.  Each Amazon Web Services tag has two parts.    A tag key (for example, CostCenter, Environment, Project, or Secret). Tag keys are case-sensitive.   An optional field known as a tag value (for example, 111122223333, Production, or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case-sensitive.   Together these are known as key-value pairs.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or devops-guru-rds-application. When you create a key, the case of characters in the key can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two different keys. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
      */
     Tags?: UpdateTagCollectionFilters;
   }
@@ -2294,7 +2332,7 @@ declare namespace DevOpsGuru {
   export type UpdateStackNames = StackName[];
   export interface UpdateTagCollectionFilter {
     /**
-     * An Amazon Web Services tag key that is used to identify the Amazon Web Services resources that DevOps Guru analyzes. All Amazon Web Services resources in your account and Region tagged with this key make up your DevOps Guru application and analysis boundary.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be Devops-guru-deployment-application or Devops-guru-rds-application. While keys are case-sensitive, the case of key characters don't matter to DevOps Guru. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
+     * An Amazon Web Services tag key that is used to identify the Amazon Web Services resources that DevOps Guru analyzes. All Amazon Web Services resources in your account and Region tagged with this key make up your DevOps Guru application and analysis boundary.  The string used for a key in a tag that you use to define your resource coverage must begin with the prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or devops-guru-rds-application. When you create a key, the case of characters in the key can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two different keys. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers. 
      */
     AppBoundaryKey: AppBoundaryKey;
     /**

package/node_modules/aws-sdk/clients/directoryservice.d.ts

@@ -275,6 +275,14 @@ declare class DirectoryService extends Service {
    * Obtains information about the trust relationships for this account. If no input parameters are provided, such as DirectoryId or TrustIds, this request describes all the trust relationships belonging to the account.
    */
   describeTrusts(callback?: (err: AWSError, data: DirectoryService.Types.DescribeTrustsResult) => void): Request<DirectoryService.Types.DescribeTrustsResult, AWSError>;
+  /**
+   *  Describes the updates of a directory for a particular update type. 
+   */
+  describeUpdateDirectory(params: DirectoryService.Types.DescribeUpdateDirectoryRequest, callback?: (err: AWSError, data: DirectoryService.Types.DescribeUpdateDirectoryResult) => void): Request<DirectoryService.Types.DescribeUpdateDirectoryResult, AWSError>;
+  /**
+   *  Describes the updates of a directory for a particular update type. 
+   */
+  describeUpdateDirectory(callback?: (err: AWSError, data: DirectoryService.Types.DescribeUpdateDirectoryResult) => void): Request<DirectoryService.Types.DescribeUpdateDirectoryResult, AWSError>;
   /**
    * Disables alternative client authentication methods for the specified directory. 
    */
@@ -491,6 +499,14 @@ declare class DirectoryService extends Service {
    * Updates a conditional forwarder that has been set up for your Amazon Web Services directory.
    */
   updateConditionalForwarder(callback?: (err: AWSError, data: DirectoryService.Types.UpdateConditionalForwarderResult) => void): Request<DirectoryService.Types.UpdateConditionalForwarderResult, AWSError>;
+  /**
+   *  Updates the directory for a particular update type. 
+   */
+  updateDirectorySetup(params: DirectoryService.Types.UpdateDirectorySetupRequest, callback?: (err: AWSError, data: DirectoryService.Types.UpdateDirectorySetupResult) => void): Request<DirectoryService.Types.UpdateDirectorySetupResult, AWSError>;
+  /**
+   *  Updates the directory for a particular update type. 
+   */
+  updateDirectorySetup(callback?: (err: AWSError, data: DirectoryService.Types.UpdateDirectorySetupResult) => void): Request<DirectoryService.Types.UpdateDirectorySetupResult, AWSError>;
   /**
    * Adds or removes domain controllers to or from the directory. Based on the difference between current value and new value (provided through this API call), domain controllers will be added or removed. It may take up to 45 minutes for any new domain controllers to become fully active once the requested number of domain controllers is updated. During this time, you cannot make another update request.
    */
@@ -926,6 +942,7 @@ declare namespace DirectoryService {
     DirectoryId?: DirectoryId;
   }
   export type CreateSnapshotBeforeSchemaExtension = boolean;
+  export type CreateSnapshotBeforeUpdate = boolean;
   export interface CreateSnapshotRequest {
     /**
      * The identifier of the directory of which to take a snapshot.
@@ -1358,6 +1375,34 @@ declare namespace DirectoryService {
      */
     NextToken?: NextToken;
   }
+  export interface DescribeUpdateDirectoryRequest {
+    /**
+     *  The unique identifier of the directory. 
+     */
+    DirectoryId: DirectoryId;
+    /**
+     *  The type of updates you want to describe for the directory. 
+     */
+    UpdateType: UpdateType;
+    /**
+     *  The name of the Region. 
+     */
+    RegionName?: RegionName;
+    /**
+     *  The DescribeUpdateDirectoryResult. NextToken value from a previous call to DescribeUpdateDirectory. Pass null if this is the first call. 
+     */
+    NextToken?: NextToken;
+  }
+  export interface DescribeUpdateDirectoryResult {
+    /**
+     *  The list of update activities on a directory for the requested update type. 
+     */
+    UpdateActivities?: UpdateActivities;
+    /**
+     *  If not null, more results are available. Pass this value for the NextToken parameter. 
+     */
+    NextToken?: NextToken;
+  }
   export type Description = string;
   export type DesiredNumberOfDomainControllers = number;
   export type DirectoryConfigurationSettingAllowedValues = string;
@@ -1514,6 +1559,10 @@ declare namespace DirectoryService {
      * Lists the Regions where the directory has replicated.
      */
     RegionsInfo?: RegionsInfo;
+    /**
+     * The operating system (OS) version of the directory.
+     */
+    OsVersion?: OSVersion;
   }
   export type DirectoryDescriptions = DirectoryDescription[];
   export type DirectoryEdition = "Enterprise"|"Standard"|string;
@@ -1782,6 +1831,7 @@ declare namespace DirectoryService {
      */
     SnapshotLimits?: SnapshotLimits;
   }
+  export type InitiatedBy = string;
   export type IpAddr = string;
   export type IpAddrs = IpAddr[];
   export interface IpRoute {
@@ -1986,6 +2036,13 @@ declare namespace DirectoryService {
   export type NextToken = string;
   export type Notes = string;
   export type OCSPUrl = string;
+  export interface OSUpdateSettings {
+    /**
+     *  OS version that the directory needs to be updated to. 
+     */
+    OSVersion?: OSVersion;
+  }
+  export type OSVersion = "SERVER_2012"|"SERVER_2019"|string;
   export type OrganizationalUnitDN = string;
   export interface OwnerDirectoryDescription {
     /**
@@ -2559,6 +2616,7 @@ declare namespace DirectoryService {
      */
     Type: TargetType;
   }
+  export type UpdateActivities = UpdateInfoEntry[];
   export interface UpdateConditionalForwarderRequest {
     /**
      * The directory ID of the Amazon Web Services directory for which to update the conditional forwarder.
@@ -2575,6 +2633,60 @@ declare namespace DirectoryService {
   }
   export interface UpdateConditionalForwarderResult {
   }
+  export interface UpdateDirectorySetupRequest {
+    /**
+     *  The identifier of the directory on which you want to perform the update. 
+     */
+    DirectoryId: DirectoryId;
+    /**
+     *  The type of update that needs to be performed on the directory. For example, OS. 
+     */
+    UpdateType: UpdateType;
+    /**
+     *  The settings for the OS update that needs to be performed on the directory. 
+     */
+    OSUpdateSettings?: OSUpdateSettings;
+    /**
+     *  The boolean that specifies if a snapshot for the directory needs to be taken before updating the directory. 
+     */
+    CreateSnapshotBeforeUpdate?: CreateSnapshotBeforeUpdate;
+  }
+  export interface UpdateDirectorySetupResult {
+  }
+  export interface UpdateInfoEntry {
+    /**
+     *  The name of the Region. 
+     */
+    Region?: RegionName;
+    /**
+     *  The status of the update performed on the directory. 
+     */
+    Status?: UpdateStatus;
+    /**
+     *  The reason for the current status of the update type activity. 
+     */
+    StatusReason?: UpdateStatusReason;
+    /**
+     *  This specifies if the update was initiated by the customer or by the service team. 
+     */
+    InitiatedBy?: InitiatedBy;
+    /**
+     *  The new value of the target setting. 
+     */
+    NewValue?: UpdateValue;
+    /**
+     *  The old value of the target setting. 
+     */
+    PreviousValue?: UpdateValue;
+    /**
+     *  The start time of the UpdateDirectorySetup for the particular type. 
+     */
+    StartTime?: StartDateTime;
+    /**
+     *  The last updated date and time of a particular directory setting. 
+     */
+    LastUpdatedDateTime?: LastUpdatedDateTime;
+  }
   export interface UpdateNumberOfDomainControllersRequest {
     /**
      * Identifier of the directory to which the domain controllers will be added or removed.
@@ -2616,6 +2728,8 @@ declare namespace DirectoryService {
      */
     DirectoryId?: DirectoryId;
   }
+  export type UpdateStatus = "Updated"|"Updating"|"UpdateFailed"|string;
+  export type UpdateStatusReason = string;
   export interface UpdateTrustRequest {
     /**
      * Identifier of the trust relationship.
@@ -2633,6 +2747,13 @@ declare namespace DirectoryService {
      */
     TrustId?: TrustId;
   }
+  export type UpdateType = "OS"|string;
+  export interface UpdateValue {
+    /**
+     *  The OS update related settings. 
+     */
+    OSUpdateSettings?: OSUpdateSettings;
+  }
   export type UseSameUsername = boolean;
   export type UserName = string;
   export type UserPassword = string;

package/node_modules/aws-sdk/clients/dlm.d.ts

@@ -20,11 +20,11 @@ declare class DLM extends Service {
    */
   createLifecyclePolicy(callback?: (err: AWSError, data: DLM.Types.CreateLifecyclePolicyResponse) => void): Request<DLM.Types.CreateLifecyclePolicyResponse, AWSError>;
   /**
-   * Deletes the specified lifecycle policy and halts the automated operations that the policy specified.
+   * Deletes the specified lifecycle policy and halts the automated operations that the policy specified. For more information about deleting a policy, see Delete lifecycle policies.
    */
   deleteLifecyclePolicy(params: DLM.Types.DeleteLifecyclePolicyRequest, callback?: (err: AWSError, data: DLM.Types.DeleteLifecyclePolicyResponse) => void): Request<DLM.Types.DeleteLifecyclePolicyResponse, AWSError>;
   /**
-   * Deletes the specified lifecycle policy and halts the automated operations that the policy specified.
+   * Deletes the specified lifecycle policy and halts the automated operations that the policy specified. For more information about deleting a policy, see Delete lifecycle policies.
    */
   deleteLifecyclePolicy(callback?: (err: AWSError, data: DLM.Types.DeleteLifecyclePolicyResponse) => void): Request<DLM.Types.DeleteLifecyclePolicyResponse, AWSError>;
   /**
@@ -68,11 +68,11 @@ declare class DLM extends Service {
    */
   untagResource(callback?: (err: AWSError, data: DLM.Types.UntagResourceResponse) => void): Request<DLM.Types.UntagResourceResponse, AWSError>;
   /**
-   * Updates the specified lifecycle policy.
+   * Updates the specified lifecycle policy. For more information about updating a policy, see Modify lifecycle policies.
    */
   updateLifecyclePolicy(params: DLM.Types.UpdateLifecyclePolicyRequest, callback?: (err: AWSError, data: DLM.Types.UpdateLifecyclePolicyResponse) => void): Request<DLM.Types.UpdateLifecyclePolicyResponse, AWSError>;
   /**
-   * Updates the specified lifecycle policy.
+   * Updates the specified lifecycle policy. For more information about updating a policy, see Modify lifecycle policies.
    */
   updateLifecyclePolicy(callback?: (err: AWSError, data: DLM.Types.UpdateLifecyclePolicyResponse) => void): Request<DLM.Types.UpdateLifecyclePolicyResponse, AWSError>;
 }
@@ -89,6 +89,18 @@ declare namespace DLM {
   }
   export type ActionList = Action[];
   export type ActionName = string;
+  export interface ArchiveRetainRule {
+    /**
+     * Information about retention period in the Amazon EBS Snapshots Archive. For more information, see Archive Amazon EBS snapshots.
+     */
+    RetentionArchiveTier: RetentionArchiveTier;
+  }
+  export interface ArchiveRule {
+    /**
+     * Information about the retention period for the snapshot archiving rule.
+     */
+    RetainRule: ArchiveRetainRule;
+  }
   export type AvailabilityZone = string;
   export type AvailabilityZoneList = AvailabilityZone[];
   export type AwsAccountId = string;
@@ -138,7 +150,7 @@ declare namespace DLM {
      */
     IntervalUnit?: IntervalUnitValues;
     /**
-     * The time, in UTC, to start the operation. The supported format is hh:mm. The operation occurs within a one-hour window following the specified time. If you do not specify a time, Amazon DLM selects a time within the next 24 hours.
+     * The time, in UTC, to start the operation. The supported format is hh:mm. The operation occurs within a one-hour window following the specified time. If you do not specify a time, Amazon Data Lifecycle Manager selects a time within the next 24 hours.
      */
     Times?: TimesList;
     /**
@@ -472,15 +484,29 @@ declare namespace DLM {
   export type ResourceTypeValuesList = ResourceTypeValues[];
   export interface RetainRule {
     /**
-     * The number of snapshots to retain for each volume, up to a maximum of 1000.
+     * The number of snapshots to retain for each volume, up to a maximum of 1000. For example if you want to retain a maximum of three snapshots, specify 3. When the fourth snapshot is created, the oldest retained snapshot is deleted, or it is moved to the archive tier if you have specified an ArchiveRule.
      */
-    Count?: Count;
+    Count?: StandardTierRetainRuleCount;
     /**
      * The amount of time to retain each snapshot. The maximum is 100 years. This is equivalent to 1200 months, 5200 weeks, or 36500 days.
      */
+    Interval?: StandardTierRetainRuleInterval;
+    /**
+     * The unit of time for time-based retention. For example, to retain snapshots for 3 months, specify Interval=3 and IntervalUnit=MONTHS. Once the snapshot has been retained for 3 months, it is deleted, or it is moved to the archive tier if you have specified an ArchiveRule.
+     */
+    IntervalUnit?: RetentionIntervalUnitValues;
+  }
+  export interface RetentionArchiveTier {
+    /**
+     * The maximum number of snapshots to retain in the archive storage tier for each volume. The count must ensure that each snapshot remains in the archive tier for at least 90 days. For example, if the schedule creates snapshots every 30 days, you must specify a count of 3 or more to ensure that each snapshot is archived for at least 90 days.
+     */
+    Count?: Count;
+    /**
+     * Specifies the period of time to retain snapshots in the archive tier. After this period expires, the snapshot is permanently deleted.
+     */
     Interval?: Interval;
     /**
-     * The unit of time for time-based retention.
+     * The unit of time in which to measure the Interval. For example, to retain a snapshots in the archive tier for 6 months, specify Interval=6 and IntervalUnit=MONTHS.
      */
     IntervalUnit?: RetentionIntervalUnitValues;
   }
@@ -526,6 +552,10 @@ declare namespace DLM {
      *  [AMI policies only] The AMI deprecation rule for the schedule.
      */
     DeprecateRule?: DeprecateRule;
+    /**
+     *  [Snapshot policies that target volumes only] The snapshot archiving rule for the schedule. When you specify an archiving rule, snapshots are automatically moved from the standard tier to the archive tier once the schedule's retention threshold is met. Snapshots are then retained in the archive tier for the archive retention period that you specify.  For more information about using snapshot archiving, see Considerations for snapshot lifecycle policies.
+     */
+    ArchiveRule?: ArchiveRule;
   }
   export type ScheduleList = Schedule[];
   export type ScheduleName = string;
@@ -547,6 +577,8 @@ declare namespace DLM {
   export type ShareRules = ShareRule[];
   export type ShareTargetAccountList = AwsAccountId[];
   export type SnapshotOwnerList = AwsAccountId[];
+  export type StandardTierRetainRuleCount = number;
+  export type StandardTierRetainRuleInterval = number;
   export type StatusMessage = string;
   export type String = string;
   export interface Tag {