@epilot360/icons 0.0.2 → 1.0.0

package/iac/node_modules/aws-cdk-lib/aws-backup/README.md

@@ -1,210 +0,0 @@
-# AWS Backup Construct Library
-
-
-AWS Backup is a fully managed backup service that makes it easy to centralize and automate the
-backup of data across AWS services in the cloud and on premises. Using AWS Backup, you can
-configure backup policies and monitor backup activity for your AWS resources in one place.
-
-## Backup plan and selection
-
-In AWS Backup, a *backup plan* is a policy expression that defines when and how you want to back up
- your AWS resources, such as Amazon DynamoDB tables or Amazon Elastic File System (Amazon EFS) file
- systems. You can assign resources to backup plans, and AWS Backup automatically backs up and retains
- backups for those resources according to the backup plan. You can create multiple backup plans if you
- have workloads with different backup requirements.
-
-This module provides ready-made backup plans (similar to the console experience):
-
-```ts
-// Daily, weekly and monthly with 5 year retention
-const plan = backup.BackupPlan.dailyWeeklyMonthly5YearRetention(this, 'Plan');
-```
-
-Assigning resources to a plan can be done with `addSelection()`:
-
-```ts
-declare const plan: backup.BackupPlan;
-declare const vpc: ec2.Vpc;
-const myTable = dynamodb.Table.fromTableName(this, 'Table', 'myTableName');
-const myDatabaseInstance = new rds.DatabaseInstance(this, 'DatabaseInstance', {
-  engine: rds.DatabaseInstanceEngine.mysql({ version: rds.MysqlEngineVersion.VER_8_0_26 }),
-  vpc,
-});
-const myDatabaseCluster = new rds.DatabaseCluster(this, 'DatabaseCluster', {
-  engine: rds.DatabaseClusterEngine.auroraMysql({ version: rds.AuroraMysqlEngineVersion.VER_2_08_1 }),
-  credentials: rds.Credentials.fromGeneratedSecret('clusteradmin'),
-  instanceProps: {
-    vpc,
-  },
-});
-const myServerlessCluster = new rds.ServerlessCluster(this, 'ServerlessCluster', {
-  engine: rds.DatabaseClusterEngine.AURORA_POSTGRESQL,
-  parameterGroup: rds.ParameterGroup.fromParameterGroupName(this, 'ParameterGroup', 'default.aurora-postgresql10'),
-  vpc,
-});
-const myCoolConstruct = new Construct(this, 'MyCoolConstruct');
-
-plan.addSelection('Selection', {
-  resources: [
-    backup.BackupResource.fromDynamoDbTable(myTable), // A DynamoDB table
-    backup.BackupResource.fromRdsDatabaseInstance(myDatabaseInstance), // A RDS instance
-    backup.BackupResource.fromRdsDatabaseCluster(myDatabaseCluster), // A RDS database cluster
-    backup.BackupResource.fromRdsServerlessCluster(myServerlessCluster), // An Aurora Serverless cluster
-    backup.BackupResource.fromTag('stage', 'prod'), // All resources that are tagged stage=prod in the region/account
-    backup.BackupResource.fromConstruct(myCoolConstruct), // All backupable resources in `myCoolConstruct`
-  ]
-})
-```
-
-If not specified, a new IAM role with a managed policy for backup will be
-created for the selection. The `BackupSelection` implements `IGrantable`.
-
-To add rules to a plan, use `addRule()`:
-
-```ts
-declare const plan: backup.BackupPlan;
-plan.addRule(new backup.BackupPlanRule({
-  completionWindow: Duration.hours(2),
-  startWindow: Duration.hours(1),
-  scheduleExpression: events.Schedule.cron({ // Only cron expressions are supported
-    day: '15',
-    hour: '3',
-    minute: '30',
-  }),
-  moveToColdStorageAfter: Duration.days(30),
-}));
-```
-
-Continuous backup and point-in-time restores (PITR) can be configured.
-Property `deleteAfter` defines the retention period for the backup. It is mandatory if PITR is enabled.
-If no value is specified, the retention period is set to 35 days which is the maximum retention period supported by PITR.
-Property `moveToColdStorageAfter` must not be specified because PITR does not support this option.
-This example defines an AWS Backup rule with PITR and a retention period set to 14 days:
-
-```ts
-declare const plan: backup.BackupPlan;
-plan.addRule(new backup.BackupPlanRule({
-  enableContinuousBackup: true,
-  deleteAfter: Duration.days(14),
-}));
-```
-
-Ready-made rules are also available:
-
-```ts
-declare const plan: backup.BackupPlan;
-plan.addRule(backup.BackupPlanRule.daily());
-plan.addRule(backup.BackupPlanRule.weekly());
-```
-
-By default a new [vault](#Backup-vault) is created when creating a plan.
-It is also possible to specify a vault either at the plan level or at the
-rule level.
-
-```ts
-const myVault = backup.BackupVault.fromBackupVaultName(this, 'Vault1', 'myVault');
-const otherVault = backup.BackupVault.fromBackupVaultName(this, 'Vault2', 'otherVault');
-
-const plan = backup.BackupPlan.daily35DayRetention(this, 'Plan', myVault); // Use `myVault` for all plan rules
-plan.addRule(backup.BackupPlanRule.monthly1Year(otherVault)); // Use `otherVault` for this specific rule
-```
-
-You can [backup](https://docs.aws.amazon.com/aws-backup/latest/devguide/windows-backups.html)
-VSS-enabled Windows applications running on Amazon EC2 instances by setting the `windowsVss`
-parameter to `true`. If the application has VSS writer registered with Windows VSS,
-then AWS Backup creates a snapshot that will be consistent for that application.
-
-```ts
-const plan = new backup.BackupPlan(this, 'Plan', {
-  windowsVss: true,
-});
-```
-
-## Backup vault
-
-In AWS Backup, a *backup vault* is a container that you organize your backups in. You can use backup
-vaults to set the AWS Key Management Service (AWS KMS) encryption key that is used to encrypt backups
-in the backup vault and to control access to the backups in the backup vault. If you require different
-encryption keys or access policies for different groups of backups, you can optionally create multiple
-backup vaults.
-
-```ts
-const myKey = kms.Key.fromKeyArn(this, 'MyKey', 'aaa');
-const myTopic = sns.Topic.fromTopicArn(this, 'MyTopic', 'bbb');
-
-const vault = new backup.BackupVault(this, 'Vault', {
-  encryptionKey: myKey, // Custom encryption key
-  notificationTopic: myTopic, // Send all vault events to this SNS topic
-});
-```
-
-A vault has a default `RemovalPolicy` set to `RETAIN`. Note that removing a vault
-that contains recovery points will fail.
-
-You can assign policies to backup vaults and the resources they contain. Assigning policies allows
-you to do things like grant access to users to create backup plans and on-demand backups, but limit
-their ability to delete recovery points after they're created.
-
-Use the `accessPolicy` property to create a backup vault policy:
-
-```ts
-const vault = new backup.BackupVault(this, 'Vault', {
-  accessPolicy: new iam.PolicyDocument({
-    statements: [
-      new iam.PolicyStatement({
-        effect: iam.Effect.DENY,
-        principals: [new iam.AnyPrincipal()],
-        actions: ['backup:DeleteRecoveryPoint'],
-        resources: ['*'],
-        conditions: {
-          StringNotLike: {
-            'aws:userId': [
-              'user1',
-              'user2',
-            ],
-          },
-        },
-      }),
-    ],
-  }),
-})
-```
-
-Alternativately statements can be added to the vault policy using `addToAccessPolicy()`.
-
-Use the `blockRecoveryPointDeletion` property or the `blockRecoveryPointDeletion()` method to add
-a statement to the vault access policy that prevents recovery point deletions in your vault:
-
-```ts
-new backup.BackupVault(this, 'Vault', {
-  blockRecoveryPointDeletion: true,
-});
-
-declare const backupVault: backup.BackupVault;
-backupVault.blockRecoveryPointDeletion();
-```
-
-By default access is not restricted.
-
-Use the `lockConfiguration` property to enable [AWS Backup Vault Lock](https://docs.aws.amazon.com/aws-backup/latest/devguide/vault-lock.html):
-
-```ts
-new BackupVault(stack, 'Vault', {
-  lockConfiguration: {
-    minRetention: Duration.days(30),
-  },
-});
-```
-
-## Importing existing backup vault
-
-To import an existing backup vault into your CDK application, use the `BackupVault.fromBackupVaultArn` or `BackupVault.fromBackupVaultName`
-static method. Here is an example of giving an IAM Role permission to start a backup job:
-
-```ts
-const importedVault = backup.BackupVault.fromBackupVaultName(this, 'Vault', 'myVaultName');
-
-const role = new iam.Role(this, 'Access Role', { assumedBy: new iam.ServicePrincipal('lambda.amazonaws.com') });
-
-importedVault.grant(role, 'backup:StartBackupJob');
-```

package/iac/node_modules/aws-cdk-lib/aws-batch/README.md

@@ -1,32 +0,0 @@
-# AWS Batch Construct Library
-
-
-This module is part of the [AWS Cloud Development Kit](https://github.com/aws/aws-cdk) project.
-
-```ts nofixture
-import * as batch from 'aws-cdk-lib/aws-batch';
-```
-
-<!--BEGIN CFNONLY DISCLAIMER-->
-
-There are no official hand-written ([L2](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_lib)) constructs for this service yet. Here are some suggestions on how to proceed:
-
-- Search [Construct Hub for Batch construct libraries](https://constructs.dev/search?q=batch)
-- Use the automatically generated [L1](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_l1_using) constructs, in the same way you would use [the CloudFormation AWS::Batch resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_Batch.html) directly.
-
-
-> An experimental construct library for this service is available in preview. Since it is not stable yet, it is distributed
-> as a separate package so that you can pin its version independently of the rest of the CDK. See the package:
->
-> <span class="package-reference">@aws-cdk/aws-batch-alpha</span>
-
-<!--BEGIN CFNONLY DISCLAIMER-->
-
-There are no hand-written ([L2](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_lib)) constructs for this service yet. 
-However, you can still use the automatically generated [L1](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_l1_using) constructs, and use this service exactly as you would using CloudFormation directly.
-
-For more information on the resources and properties available for this service, see the [CloudFormation documentation for AWS::Batch](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_Batch.html).
-
-(Read the [CDK Contributing Guide](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and submit an RFC if you are interested in contributing to this construct library.)
-
-<!--END CFNONLY DISCLAIMER-->

package/iac/node_modules/aws-cdk-lib/aws-billingconductor/README.md

@@ -1,27 +0,0 @@
-# AWS::BillingConductor Construct Library
-
-
-This module is part of the [AWS Cloud Development Kit](https://github.com/aws/aws-cdk) project.
-
-```ts nofixture
-import * as billingconductor from 'aws-cdk-lib/aws-billingconductor';
-```
-
-<!--BEGIN CFNONLY DISCLAIMER-->
-
-There are no official hand-written ([L2](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_lib)) constructs for this service yet. Here are some suggestions on how to proceed:
-
-- Search [Construct Hub for BillingConductor construct libraries](https://constructs.dev/search?q=billingconductor)
-- Use the automatically generated [L1](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_l1_using) constructs, in the same way you would use [the CloudFormation AWS::BillingConductor resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_BillingConductor.html) directly.
-
-
-<!--BEGIN CFNONLY DISCLAIMER-->
-
-There are no hand-written ([L2](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_lib)) constructs for this service yet. 
-However, you can still use the automatically generated [L1](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_l1_using) constructs, and use this service exactly as you would using CloudFormation directly.
-
-For more information on the resources and properties available for this service, see the [CloudFormation documentation for AWS::BillingConductor](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_BillingConductor.html).
-
-(Read the [CDK Contributing Guide](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and submit an RFC if you are interested in contributing to this construct library.)
-
-<!--END CFNONLY DISCLAIMER-->

package/iac/node_modules/aws-cdk-lib/aws-budgets/README.md

@@ -1,27 +0,0 @@
-# AWS Budgets Construct Library
-
-
-This module is part of the [AWS Cloud Development Kit](https://github.com/aws/aws-cdk) project.
-
-```ts nofixture
-import * as budgets from 'aws-cdk-lib/aws-budgets';
-```
-
-<!--BEGIN CFNONLY DISCLAIMER-->
-
-There are no official hand-written ([L2](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_lib)) constructs for this service yet. Here are some suggestions on how to proceed:
-
-- Search [Construct Hub for Budgets construct libraries](https://constructs.dev/search?q=budgets)
-- Use the automatically generated [L1](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_l1_using) constructs, in the same way you would use [the CloudFormation AWS::Budgets resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_Budgets.html) directly.
-
-
-<!--BEGIN CFNONLY DISCLAIMER-->
-
-There are no hand-written ([L2](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_lib)) constructs for this service yet. 
-However, you can still use the automatically generated [L1](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_l1_using) constructs, and use this service exactly as you would using CloudFormation directly.
-
-For more information on the resources and properties available for this service, see the [CloudFormation documentation for AWS::Budgets](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_Budgets.html).
-
-(Read the [CDK Contributing Guide](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and submit an RFC if you are interested in contributing to this construct library.)
-
-<!--END CFNONLY DISCLAIMER-->

package/iac/node_modules/aws-cdk-lib/aws-cassandra/README.md

@@ -1,27 +0,0 @@
-# AWS::Cassandra Construct Library
-
-
-This module is part of the [AWS Cloud Development Kit](https://github.com/aws/aws-cdk) project.
-
-```ts nofixture
-import * as cassandra from 'aws-cdk-lib/aws-cassandra';
-```
-
-<!--BEGIN CFNONLY DISCLAIMER-->
-
-There are no official hand-written ([L2](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_lib)) constructs for this service yet. Here are some suggestions on how to proceed:
-
-- Search [Construct Hub for Cassandra construct libraries](https://constructs.dev/search?q=cassandra)
-- Use the automatically generated [L1](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_l1_using) constructs, in the same way you would use [the CloudFormation AWS::Cassandra resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_Cassandra.html) directly.
-
-
-<!--BEGIN CFNONLY DISCLAIMER-->
-
-There are no hand-written ([L2](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_lib)) constructs for this service yet. 
-However, you can still use the automatically generated [L1](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_l1_using) constructs, and use this service exactly as you would using CloudFormation directly.
-
-For more information on the resources and properties available for this service, see the [CloudFormation documentation for AWS::Cassandra](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_Cassandra.html).
-
-(Read the [CDK Contributing Guide](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and submit an RFC if you are interested in contributing to this construct library.)
-
-<!--END CFNONLY DISCLAIMER-->

package/iac/node_modules/aws-cdk-lib/aws-ce/README.md

@@ -1,27 +0,0 @@
-# AWS::CE Construct Library
-
-
-This module is part of the [AWS Cloud Development Kit](https://github.com/aws/aws-cdk) project.
-
-```ts nofixture
-import * as ce from 'aws-cdk-lib/aws-ce';
-```
-
-<!--BEGIN CFNONLY DISCLAIMER-->
-
-There are no official hand-written ([L2](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_lib)) constructs for this service yet. Here are some suggestions on how to proceed:
-
-- Search [Construct Hub for CE construct libraries](https://constructs.dev/search?q=ce)
-- Use the automatically generated [L1](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_l1_using) constructs, in the same way you would use [the CloudFormation AWS::CE resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_CE.html) directly.
-
-
-<!--BEGIN CFNONLY DISCLAIMER-->
-
-There are no hand-written ([L2](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_lib)) constructs for this service yet. 
-However, you can still use the automatically generated [L1](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_l1_using) constructs, and use this service exactly as you would using CloudFormation directly.
-
-For more information on the resources and properties available for this service, see the [CloudFormation documentation for AWS::CE](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_CE.html).
-
-(Read the [CDK Contributing Guide](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and submit an RFC if you are interested in contributing to this construct library.)
-
-<!--END CFNONLY DISCLAIMER-->

package/iac/node_modules/aws-cdk-lib/aws-certificatemanager/README.md

@@ -1,166 +0,0 @@
-# AWS Certificate Manager Construct Library
-
-
-
-AWS Certificate Manager (ACM) handles the complexity of creating, storing, and renewing public and private SSL/TLS X.509 certificates and keys that
-protect your AWS websites and applications. ACM certificates can secure singular domain names, multiple specific domain names, wildcard domains, or
-combinations of these. ACM wildcard certificates can protect an unlimited number of subdomains.
-
-This package provides Constructs for provisioning and referencing ACM certificates which can be used with CloudFront and ELB.
-
-After requesting a certificate, you will need to prove that you own the
-domain in question before the certificate will be granted. The CloudFormation
-deployment will wait until this verification process has been completed.
-
-Because of this wait time, when using manual validation methods, it's better
-to provision your certificates either in a separate stack from your main
-service, or provision them manually and import them into your CDK application.
-
-**Note:** There is a limit on total number of ACM certificates that can be requested on an account and region within a year.
-The default limit is 2000, but this limit may be (much) lower on new AWS accounts.
-See https://docs.aws.amazon.com/acm/latest/userguide/acm-limits.html for more information.
-
-## DNS validation
-
-DNS validation is the preferred method to validate domain ownership, as it has a number of advantages over email validation.
-See also [Validate with DNS](https://docs.aws.amazon.com/acm/latest/userguide/gs-acm-validate-dns.html)
-in the AWS Certificate Manager User Guide.
-
-If Amazon Route 53 is your DNS provider for the requested domain, the DNS record can be
-created automatically:
-
-```ts
-const myHostedZone = new route53.HostedZone(this, 'HostedZone', {
-  zoneName: 'example.com',
-});
-new acm.Certificate(this, 'Certificate', {
-  domainName: 'hello.example.com',
-  validation: acm.CertificateValidation.fromDns(myHostedZone),
-});
-```
-
-If Route 53 is not your DNS provider, the DNS records must be added manually and the stack will not complete
-creating until the records are added.
-
-```ts
-new acm.Certificate(this, 'Certificate', {
-  domainName: 'hello.example.com',
-  validation: acm.CertificateValidation.fromDns(), // Records must be added manually
-});
-```
-
-When working with multiple domains, use the `CertificateValidation.fromDnsMultiZone()`:
-
-```ts
-const exampleCom = new route53.HostedZone(this, 'ExampleCom', {
-  zoneName: 'example.com',
-});
-const exampleNet = new route53.HostedZone(this, 'ExampleNet', {
-  zoneName: 'example.net',
-});
-
-const cert = new acm.Certificate(this, 'Certificate', {
-  domainName: 'test.example.com',
-  subjectAlternativeNames: ['cool.example.com', 'test.example.net'],
-  validation: acm.CertificateValidation.fromDnsMultiZone({
-    'test.example.com': exampleCom,
-    'cool.example.com': exampleCom,
-    'test.example.net': exampleNet,
-  }),
-});
-```
-
-## Email validation
-
-Email-validated certificates (the default) are validated by receiving an
-email on one of a number of predefined domains and following the instructions
-in the email.
-
-See [Validate with Email](https://docs.aws.amazon.com/acm/latest/userguide/gs-acm-validate-email.html)
-in the AWS Certificate Manager User Guide.
-
-```ts
-new acm.Certificate(this, 'Certificate', {
-  domainName: 'hello.example.com',
-  validation: acm.CertificateValidation.fromEmail(), // Optional, this is the default
-});
-```
-
-## Cross-region Certificates
-
-ACM certificates that are used with CloudFront -- or higher-level constructs which rely on CloudFront -- must be in the `us-east-1` region.
-The `DnsValidatedCertificate` construct exists to facilitate creating these certificates cross-region. This resource can only be used with
-Route53-based DNS validation.
-
-```ts
-declare const myHostedZone: route53.HostedZone;
-new acm.DnsValidatedCertificate(this, 'CrossRegionCertificate', {
-  domainName: 'hello.example.com',
-  hostedZone: myHostedZone,
-  region: 'us-east-1',
-});
-```
-
-## Requesting private certificates
-
-AWS Certificate Manager can create [private certificates](https://docs.aws.amazon.com/acm/latest/userguide/gs-acm-request-private.html) issued by [Private Certificate Authority (PCA)](https://docs.aws.amazon.com/acm-pca/latest/userguide/PcaWelcome.html). Validation of private certificates is not necessary.
-
-```ts
-import * as acmpca from 'aws-cdk-lib/aws-acmpca';
-
-new acm.PrivateCertificate(this, 'PrivateCertificate', {
-  domainName: 'test.example.com',
-  subjectAlternativeNames: ['cool.example.com', 'test.example.net'], // optional
-  certificateAuthority: acmpca.CertificateAuthority.fromCertificateAuthorityArn(this, 'CA',
-    'arn:aws:acm-pca:us-east-1:123456789012:certificate-authority/023077d8-2bfa-4eb0-8f22-05c96deade77'),
-});
-```
-
-## Requesting certificates without transparency logging
-
-Transparency logging can be opted out of for AWS Certificate Manager certificates. See [opting out of certifiacte transparency logging](https://docs.aws.amazon.com/acm/latest/userguide/acm-bestpractices.html#best-practices-transparency) for limits.
-
-```ts
-new acm.Certificate(this, 'Certificate', {
-  domainName: 'test.example.com',
-  transparencyLoggingEnabled: false,
-});
-```
-
-## Importing
-
-If you want to import an existing certificate, you can do so from its ARN:
-
-```ts
-const arn = 'arn:aws:...';
-const certificate = acm.Certificate.fromCertificateArn(this, 'Certificate', arn);
-```
-
-## Sharing between Stacks
-
-To share the certificate between stacks in the same CDK application, simply
-pass the `Certificate` object between the stacks.
-
-## Metrics
-
-The `DaysToExpiry` metric is available via the `metricDaysToExpiry` method for
-all certificates. This metric is emitted by AWS Certificates Manager once per
-day until the certificate has effectively expired.
-
-An alarm can be created to determine whether a certificate is soon due for
-renewal ussing the following code:
-
-```ts
-import * as cloudwatch from 'aws-cdk-lib/aws-cloudwatch';
-
-declare const myHostedZone: route53.HostedZone;
-const certificate = new acm.Certificate(this, 'Certificate', {
-  domainName: 'hello.example.com',
-  validation: acm.CertificateValidation.fromDns(myHostedZone),
-});
-certificate.metricDaysToExpiry().createAlarm(this, 'Alarm', {
-  comparisonOperator: cloudwatch.ComparisonOperator.LESS_THAN_THRESHOLD,
-  evaluationPeriods: 1,
-  threshold: 45, // Automatic rotation happens between 60 and 45 days before expiry
-});
-```

package/iac/node_modules/aws-cdk-lib/aws-certificatemanager/lambda-packages/dns_validated_certificate_handler/README.md

@@ -1,2 +0,0 @@
-## CloudFormation Custom Resource for generating DNS-validated ACM certificates
-This module is part of the [AWS Cloud Development Kit](https://github.com/aws/aws-cdk) project.

package/iac/node_modules/aws-cdk-lib/aws-certificatemanager/suffixes/README.txt

@@ -1,8 +0,0 @@
-Public suffix list obtained from https://publicsuffix.org/.
-
-We build a lookup map that for 90% of the cases can return the probable intended apex domain.
-
-We're ignoring Punycode on purpose.
-
-Whenever you pull a new version of the .dat file, don't forget to run build-map.py.
-Not integrated as part of the build because this file will change only very rarely.

package/iac/node_modules/aws-cdk-lib/aws-chatbot/README.md

@@ -1,44 +0,0 @@
-# AWS::Chatbot Construct Library
-
-
-AWS Chatbot is an AWS service that enables DevOps and software development teams to use Slack chat rooms to monitor and respond to operational events in their AWS Cloud. AWS Chatbot processes AWS service notifications from Amazon Simple Notification Service (Amazon SNS), and forwards them to Slack chat rooms so teams can analyze and act on them immediately, regardless of location.
-
-This module is part of the [AWS Cloud Development Kit](https://github.com/aws/aws-cdk) project.
-
-```ts
-import * as chatbot from 'aws-cdk-lib/aws-chatbot';
-import * as sns from 'aws-cdk-lib/aws-sns';
-import * as iam from 'aws-cdk-lib/aws-iam';
-
-const slackChannel = new chatbot.SlackChannelConfiguration(this, 'MySlackChannel', {
-  slackChannelConfigurationName: 'YOUR_CHANNEL_NAME',
-  slackWorkspaceId: 'YOUR_SLACK_WORKSPACE_ID',
-  slackChannelId: 'YOUR_SLACK_CHANNEL_ID',
-});
-
-slackChannel.addToRolePolicy(new iam.PolicyStatement({
-  effect: iam.Effect.ALLOW,
-  actions: [
-    's3:GetObject',
-  ],
-  resources: ['arn:aws:s3:::abc/xyz/123.txt'],
-}));
-
-slackChannel.addNotificationTopic(new sns.Topic(this, 'MyTopic'));
-```
-
-## Log Group
-
-Slack channel configuration automatically create a log group with the name `/aws/chatbot/<configuration-name>` in `us-east-1` upon first execution with
-log data set to never expire.
-
-The `logRetention` property can be used to set a different expiration period. A log group will be created if not already exists.
-If the log group already exists, it's expiration will be configured to the value specified in this construct (never expire, by default).
-
-By default, CDK uses the AWS SDK retry options when interacting with the log group. The `logRetentionRetryOptions` property
-allows you to customize the maximum number of retries and base backoff duration.
-
-*Note* that, if `logRetention` is set, a [CloudFormation custom
-resource](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cfn-customresource.html) is added
-to the stack that pre-creates the log group as part of the stack deployment, if it already doesn't exist, and sets the
-correct log retention period (never expire, by default).

package/iac/node_modules/aws-cdk-lib/aws-cloud9/README.md

@@ -1,32 +0,0 @@
-# AWS Cloud9 Construct Library
-
-
-This module is part of the [AWS Cloud Development Kit](https://github.com/aws/aws-cdk) project.
-
-```ts nofixture
-import * as cloud9 from 'aws-cdk-lib/aws-cloud9';
-```
-
-<!--BEGIN CFNONLY DISCLAIMER-->
-
-There are no official hand-written ([L2](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_lib)) constructs for this service yet. Here are some suggestions on how to proceed:
-
-- Search [Construct Hub for Cloud9 construct libraries](https://constructs.dev/search?q=cloud9)
-- Use the automatically generated [L1](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_l1_using) constructs, in the same way you would use [the CloudFormation AWS::Cloud9 resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_Cloud9.html) directly.
-
-
-> An experimental construct library for this service is available in preview. Since it is not stable yet, it is distributed
-> as a separate package so that you can pin its version independently of the rest of the CDK. See the package:
->
-> <span class="package-reference">@aws-cdk/aws-cloud9-alpha</span>
-
-<!--BEGIN CFNONLY DISCLAIMER-->
-
-There are no hand-written ([L2](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_lib)) constructs for this service yet. 
-However, you can still use the automatically generated [L1](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_l1_using) constructs, and use this service exactly as you would using CloudFormation directly.
-
-For more information on the resources and properties available for this service, see the [CloudFormation documentation for AWS::Cloud9](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_Cloud9.html).
-
-(Read the [CDK Contributing Guide](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and submit an RFC if you are interested in contributing to this construct library.)
-
-<!--END CFNONLY DISCLAIMER-->

package/iac/node_modules/aws-cdk-lib/aws-cloudformation/README.md

@@ -1,4 +0,0 @@
-# AWS CloudFormation Construct Library
-
-
-This module is part of the [AWS Cloud Development Kit](https://github.com/aws/aws-cdk) project.