@epilot360/icons 0.0.2 → 1.0.0

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

@@ -1,194 +0,0 @@
-# Amazon Simple Email Service Construct Library
-
-
-This module is part of the [AWS Cloud Development Kit](https://github.com/aws/aws-cdk) project.
-
-## Email receiving
-
-Create a receipt rule set with rules and actions (actions can be found in the
-`@aws-cdk/aws-ses-actions` package):
-
-```ts
-import * as s3 from 'aws-cdk-lib/aws-s3';
-import * as actions from 'aws-cdk-lib/aws-ses-actions';
-
-const bucket = new s3.Bucket(this, 'Bucket');
-const topic = new sns.Topic(this, 'Topic');
-
-new ses.ReceiptRuleSet(this, 'RuleSet', {
-  rules: [
-    {
-      recipients: ['hello@aws.com'],
-      actions: [
-        new actions.AddHeader({
-          name: 'X-Special-Header',
-          value: 'aws',
-        }),
-        new actions.S3({
-          bucket,
-          objectKeyPrefix: 'emails/',
-          topic,
-        }),
-      ],
-    },
-    {
-      recipients: ['aws.com'],
-      actions: [
-        new actions.Sns({
-          topic,
-        }),
-      ],
-    },
-  ],
-});
-```
-
-Alternatively, rules can be added to a rule set:
-
-```ts
-const ruleSet = new ses.ReceiptRuleSet(this, 'RuleSet');
-
-const awsRule = ruleSet.addRule('Aws', {
-  recipients: ['aws.com'],
-});
-```
-
-And actions to rules:
-
-```ts
-import * as actions from 'aws-cdk-lib/aws-ses-actions';
-
-declare const awsRule: ses.ReceiptRule;
-declare const topic: sns.Topic;
-awsRule.addAction(new actions.Sns({
-  topic,
-}));
-```
-
-When using `addRule`, the new rule is added after the last added rule unless `after` is specified.
-
-### Drop spams
-
-A rule to drop spam can be added by setting `dropSpam` to `true`:
-
-```ts
-new ses.ReceiptRuleSet(this, 'RuleSet', {
-  dropSpam: true,
-});
-```
-
-This will add a rule at the top of the rule set with a Lambda action that stops processing messages that have at least one spam indicator. See [Lambda Function Examples](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email-action-lambda-example-functions.html).
-
-
-### Receipt filter
-
-Create a receipt filter:
-
-```ts
-new ses.ReceiptFilter(this, 'Filter', {
-  ip: '1.2.3.4/16', // Will be blocked
-});
-```
-
-An allow list filter is also available:
-
-```ts
-new ses.AllowListReceiptFilter(this, 'AllowList', {
-  ips: [
-    '10.0.0.0/16',
-    '1.2.3.4/16',
-  ],
-});
-```
-
-This will first create a block all filter and then create allow filters for the listed ip addresses.
-
-## Email sending
-
-### Dedicated IP pools
-
-When you create a new Amazon SES account, your emails are sent from IP addresses that are shared with other
-Amazon SES users. For [an additional monthly charge](https://aws.amazon.com/ses/pricing/), you can lease
-dedicated IP addresses that are reserved for your exclusive use.
-
-Use the `DedicatedIpPool` construct to create a pool of dedicated IP addresses:
-
-```ts
-new ses.DedicatedIpPool(this, 'Pool');
-```
-
-The pool can then be used in a configuration set.
-
-### Configuration sets
-
-Configuration sets are groups of rules that you can apply to your verified identities. A verified identity is
-a domain, subdomain, or email address you use to send email through Amazon SES. When you apply a configuration
-set to an email, all of the rules in that configuration set are applied to the email.
-
-Use the `ConfigurationSet` construct to create a configuration set:
-
-```ts
-declare const myPool: ses.IDedicatedIpPool;
-
-new ses.ConfigurationSet(this, 'ConfigurationSet', {
-  customTrackingRedirectDomain: 'track.cdk.dev',
-  suppressionReasons: ses.SuppressionReasons.COMPLAINTS_ONLY,
-  tlsPolicy: ses.ConfigurationSetTlsPolicy.REQUIRE,
-  dedicatedIpPool: myPool,
-});
-```
-
-### Email identity
-
-In Amazon SES, a verified identity is a domain or email address that you use to send or receive email. Before you
-can send an email using Amazon SES, you must create and verify each identity that you're going to use as a `From`,
-`Source`, `Sender`, or `Return-Path` address. Verifying an identity with Amazon SES confirms that you own it and
-helps prevent unauthorized use.
-
-To verify an identity for a hosted zone, you create an `EmailIdentity`:
-
-```ts
-declare const myHostedZone: route53.IPublicHostedZone;
-
-const identity = new ses.EmailIdentity(stack, 'Identity', {
-  identity: ses.Identity.publicHostedZone(myHostedZone),
-  mailFromDomain: 'mail.cdk.dev',
-});
-```
-
-By default, [Easy DKIM](https://docs.aws.amazon.com/ses/latest/dg/send-email-authentication-dkim-easy.html) with
-a 2048-bit DKIM key is used.
-
-You can instead configure DKIM authentication by using your own public-private key pair. This process is known
-as [Bring Your Own DKIM (BYODKIM)](https://docs.aws.amazon.com/ses/latest/dg/send-email-authentication-dkim-bring-your-own.html):
-
-```ts
-declare const myHostedZone: route53.IPublicHostedZone;
-
-new ses.EmailIdentity(stack, 'Identity', {
-  identity: ses.Identity.publicHostedZone(myHostedZone),
-  dkimIdentity: DkimIdentity.byoDkim({
-    privateKey: SecretValue.secretsManager('dkim-private-key'),
-    publicKey: '...base64-encoded-public-key...',
-    selector: 'selector',
-  }),
-});
-```
-
-When using `publicHostedZone()` for the identity, all necessary Amazon Route 53 records are created automatically:
-
-* CNAME records for Easy DKIM
-* TXT record for BYOD DKIM
-* MX and TXT records for the custom MAIL FROM
-
-When working with `domain()`, records must be created manually:
-
-```ts
-const identity = new ses.EmailIdentity(stack, 'Identity', {
-  identity: ses.Identity.domain('cdk.dev'),
-});
-
-for (const record of identity.dkimRecords) {
-  // create CNAME records using `record.name` and `record.value`
-}
-```

package/iac/node_modules/aws-cdk-lib/aws-ses-actions/README.md

@@ -1,16 +0,0 @@
-# Amazon Simple Email Service Actions Library
-
-
-This module contains integration classes to add action to SES email receiving rules.
-Instances of these classes should be passed to the `rule.addAction()` method.
-
-Currently supported are:
-
-* [Add header](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email-action-add-header.html)
-* [Bounce](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email-action-bounce.html)
-* [Lambda](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email-action-lambda.html)
-* [S3](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email-action-s3.html)
-* [SNS](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email-action-sns.html)
-* [Stop](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email-action-stop.html)
-
-See the README of `@aws-cdk/aws-ses` for more information.

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

@@ -1,41 +0,0 @@
-# AWS::Signer Construct Library
-
-
-AWS Signer is a fully managed code-signing service to ensure the trust and integrity of your code. Organizations validate code against
-a digital signature to confirm that the code is unaltered and from a trusted publisher. For more information, see [What Is AWS
-Signer?](https://docs.aws.amazon.com/signer/latest/developerguide/Welcome.html)
-
-## Table of Contents
-
-- [Signing Platform](#signing-platform)
-- [Signing Profile](#signing-profile)
-
-## Signing Platform
-
-A signing platform is a predefined set of instructions that specifies the signature format and signing algorithms that AWS Signer should use
-to sign a zip file. For more information go to [Signing Platforms in AWS Signer](https://docs.aws.amazon.com/signer/latest/developerguide/gs-platform.html).
-
-AWS Signer provides a pre-defined set of signing platforms. They are available in the CDK as -
-
-```text
-Platform.AWS_IOT_DEVICE_MANAGEMENT_SHA256_ECDSA
-Platform.AWS_LAMBDA_SHA384_ECDSA
-Platform.AMAZON_FREE_RTOS_TI_CC3220SF
-Platform.AMAZON_FREE_RTOS_DEFAULT
-```
-
-## Signing Profile
-
-A signing profile is a code-signing template that can be used to pre-define the signature specifications for a signing job.
-A signing profile includes a signing platform to designate the file type to be signed, the signature format, and the signature algorithms.
-For more information, visit [Signing Profiles in AWS Signer](https://docs.aws.amazon.com/signer/latest/developerguide/gs-profile.html).
-
-The following code sets up a signing profile for signing lambda code bundles -
-
-```ts
-const signingProfile = new signer.SigningProfile(this, 'SigningProfile', { 
-  platform: signer.Platform.AWS_LAMBDA_SHA384_ECDSA,
-});
-```
-
-A signing profile is valid by default for 135 months. This can be modified by specifying the `signatureValidityPeriod` property.

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

@@ -1,184 +0,0 @@
-# Amazon Simple Notification Service Construct Library
-
-
-Add an SNS Topic to your stack:
-
-```ts
-const topic = new sns.Topic(this, 'Topic', {
-  displayName: 'Customer subscription topic',
-});
-```
-
-Add a FIFO SNS topic with content-based de-duplication to your stack:
-
-```ts
-const topic = new sns.Topic(this, 'Topic', {
-  contentBasedDeduplication: true,
-  displayName: 'Customer subscription topic',
-  fifo: true,
-  topicName: 'customerTopic',
-});
-```
-
-Note that FIFO topics require a topic name to be provided. The required `.fifo` suffix will be automatically added to the topic name if it is not explicitly provided.
-
-## Subscriptions
-
-Various subscriptions can be added to the topic by calling the
-`.addSubscription(...)` method on the topic. It accepts a *subscription* object,
-default implementations of which can be found in the
-`@aws-cdk/aws-sns-subscriptions` package:
-
-Add an HTTPS Subscription to your topic:
-
-```ts
-const myTopic = new sns.Topic(this, 'MyTopic');
-
-myTopic.addSubscription(new subscriptions.UrlSubscription('https://foobar.com/'));
-```
-
-Subscribe a queue to the topic:
-
-```ts
-declare const queue: sqs.Queue;
-const myTopic = new sns.Topic(this, 'MyTopic');
-
-myTopic.addSubscription(new subscriptions.SqsSubscription(queue));
-```
-
-Note that subscriptions of queues in different accounts need to be manually confirmed by
-reading the initial message from the queue and visiting the link found in it.
-
-### Filter policy
-
-A filter policy can be specified when subscribing an endpoint to a topic.
-
-Example with a Lambda subscription:
-
-```ts
-import * as lambda from 'aws-cdk-lib/aws-lambda';
-
-const myTopic = new sns.Topic(this, 'MyTopic');
-declare const fn: lambda.Function;
-
-// Lambda should receive only message matching the following conditions on attributes:
-// color: 'red' or 'orange' or begins with 'bl'
-// size: anything but 'small' or 'medium'
-// price: between 100 and 200 or greater than 300
-// store: attribute must be present
-myTopic.addSubscription(new subscriptions.LambdaSubscription(fn, {
-  filterPolicy: {
-    color: sns.SubscriptionFilter.stringFilter({
-      allowlist: ['red', 'orange'],
-      matchPrefixes: ['bl'],
-    }),
-    size: sns.SubscriptionFilter.stringFilter({
-      denylist: ['small', 'medium'],
-    }),
-    price: sns.SubscriptionFilter.numericFilter({
-      between: { start: 100, stop: 200 },
-      greaterThan: 300,
-    }),
-    store: sns.SubscriptionFilter.existsFilter(),
-  },
-}));
-```
-
-### Example of Firehose Subscription
-
-```ts
-import { DeliveryStream } from 'aws-cdk-lib/aws-kinesisfirehose';
-
-const topic = new sns.Topic(this, 'Topic');
-declare const stream: DeliveryStream;
-
-new sns.Subscription(this, 'Subscription', {
-  topic,
-  endpoint: stream.deliveryStreamArn,
-  protocol: sns.SubscriptionProtocol.FIREHOSE,
-  subscriptionRoleArn: "SAMPLE_ARN", //role with permissions to send messages to a firehose delivery stream
-});
-```
-
-## DLQ setup for SNS Subscription
-
-CDK can attach provided Queue as DLQ for your SNS subscription.
-See the [SNS DLQ configuration docs](https://docs.aws.amazon.com/sns/latest/dg/sns-configure-dead-letter-queue.html) for more information about this feature.
-
-Example of usage with user provided DLQ.
-
-```ts
-const topic = new sns.Topic(this, 'Topic');
-const dlQueue = new sqs.Queue(this, 'DeadLetterQueue', {
-  queueName: 'MySubscription_DLQ',
-  retentionPeriod: Duration.days(14),
-});
-
-new sns.Subscription(this, 'Subscription', {
-  endpoint: 'endpoint',
-  protocol: sns.SubscriptionProtocol.LAMBDA,
-  topic,
-  deadLetterQueue: dlQueue,
-});
-```
-
-## CloudWatch Event Rule Target
-
-SNS topics can be used as targets for CloudWatch event rules.
-
-Use the `@aws-cdk/aws-events-targets.SnsTopic`:
-
-```ts
-import * as codecommit from 'aws-cdk-lib/aws-codecommit';
-import * as targets from 'aws-cdk-lib/aws-events-targets';
-
-declare const repo: codecommit.Repository;
-const myTopic = new sns.Topic(this, 'Topic');
-
-repo.onCommit('OnCommit', {
-  target: new targets.SnsTopic(myTopic),
-});
-```
-
-This will result in adding a target to the event rule and will also modify the
-topic resource policy to allow CloudWatch events to publish to the topic.
-
-## Topic Policy
-
-A topic policy is automatically created when `addToResourcePolicy` is called, if
-one doesn't already exist. Using `addToResourcePolicy` is the simplest way to
-add policies, but a `TopicPolicy` can also be created manually.
-
-```ts
-const topic = new sns.Topic(this, 'Topic');
-const topicPolicy = new sns.TopicPolicy(this, 'TopicPolicy', {
-  topics: [topic],
-});
-
-topicPolicy.document.addStatements(new iam.PolicyStatement({
-  actions: ["sns:Subscribe"],
-  principals: [new iam.AnyPrincipal()],
-  resources: [topic.topicArn],
-}));
-```
-
-A policy document can also be passed on `TopicPolicy` construction
-
-```ts
-const topic = new sns.Topic(this, 'Topic');
-const policyDocument = new iam.PolicyDocument({
-  assignSids: true,
-  statements: [
-    new iam.PolicyStatement({
-      actions: ["sns:Subscribe"],
-      principals: [new iam.AnyPrincipal()],
-      resources: [topic.topicArn],
-    }),
-  ],
-});
-
-const topicPolicy = new sns.TopicPolicy(this, 'Policy', {
-  topics: [topic],
-  policyDocument,
-});
-```

package/iac/node_modules/aws-cdk-lib/aws-sns-subscriptions/README.md

@@ -1,120 +0,0 @@
-# CDK Construct Library for Amazon Simple Notification Service Subscriptions
-
-
-This library provides constructs for adding subscriptions to an Amazon SNS topic.
-Subscriptions can be added by calling the `.addSubscription(...)` method on the topic.
-
-## Subscriptions
-
-Subscriptions can be added to the following endpoints:
-
-* HTTPS
-* Amazon SQS
-* AWS Lambda
-* Email
-* SMS
-
-Subscriptions to Amazon SQS and AWS Lambda can be added on topics across regions.
-
-Create an Amazon SNS Topic to add subscriptions.
-
-```ts
-const myTopic = new sns.Topic(this, 'MyTopic');
-```
-
-### HTTPS
-
-Add an HTTP or HTTPS Subscription to your topic:
-
-```ts
-const myTopic = new sns.Topic(this, 'MyTopic');
-
-myTopic.addSubscription(new subscriptions.UrlSubscription('https://foobar.com/'));
-```
-
-The URL being subscribed can also be [tokens](https://docs.aws.amazon.com/cdk/latest/guide/tokens.html), that resolve
-to a URL during deployment. A typical use case is when the URL is passed in as a [CloudFormation
-parameter](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/parameters-section-structure.html). The
-following code defines a CloudFormation parameter and uses it in a URL subscription.
-
-```ts
-const myTopic = new sns.Topic(this, 'MyTopic');
-const url = new CfnParameter(this, 'url-param');
-
-myTopic.addSubscription(new subscriptions.UrlSubscription(url.valueAsString));
-```
-
-### Amazon SQS
-
-Subscribe a queue to your topic:
-
-```ts
-const myQueue = new sqs.Queue(this, 'MyQueue');
-const myTopic = new sns.Topic(this, 'MyTopic');
-
-myTopic.addSubscription(new subscriptions.SqsSubscription(myQueue));
-```
-
-KMS key permissions will automatically be granted to SNS when a subscription is made to
-an encrypted queue.
-
-Note that subscriptions of queues in different accounts need to be manually confirmed by
-reading the initial message from the queue and visiting the link found in it.
-
-### AWS Lambda
-
-Subscribe an AWS Lambda function to your topic:
-
-```ts
-import * as lambda from 'aws-cdk-lib/aws-lambda';
-
-const myTopic = new sns.Topic(this, 'myTopic');
-declare const myFunction: lambda.Function;
-myTopic.addSubscription(new subscriptions.LambdaSubscription(myFunction));
-```
-
-### Email
-
-Subscribe an email address to your topic:
-
-```ts
-const myTopic = new sns.Topic(this, 'MyTopic');
-myTopic.addSubscription(new subscriptions.EmailSubscription('foo@bar.com'));
-```
-
-The email being subscribed can also be [tokens](https://docs.aws.amazon.com/cdk/latest/guide/tokens.html), that resolve
-to an email address during deployment. A typical use case is when the email address is passed in as a [CloudFormation
-parameter](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/parameters-section-structure.html). The
-following code defines a CloudFormation parameter and uses it in an email subscription.
-
-```ts
-const myTopic = new sns.Topic(this, 'Topic');
-const emailAddress = new CfnParameter(this, 'email-param');
-
-myTopic.addSubscription(new subscriptions.EmailSubscription(emailAddress.valueAsString));
-```
-
-Note that email subscriptions require confirmation by visiting the link sent to the
-email address.
-
-### SMS
-
-Subscribe an sms number to your topic:
-
-```ts
-const myTopic = new sns.Topic(this, 'Topic');
-
-myTopic.addSubscription(new subscriptions.SmsSubscription('+15551231234'));
-```
-
-The number being subscribed can also be [tokens](https://docs.aws.amazon.com/cdk/latest/guide/tokens.html), that resolve
-to a number during deployment. A typical use case is when the number is passed in as a [CloudFormation
-parameter](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/parameters-section-structure.html). The
-following code defines a CloudFormation parameter and uses it in an sms subscription.
-
-```ts
-const myTopic = new sns.Topic(this, 'Topic');
-const smsNumber = new CfnParameter(this, 'sms-param');
-
-myTopic.addSubscription(new subscriptions.SmsSubscription(smsNumber.valueAsString));
-```

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

@@ -1,57 +0,0 @@
-# Amazon Simple Queue Service Construct Library
-
-
-Amazon Simple Queue Service (SQS) is a fully managed message queuing service that 
-enables you to decouple and scale microservices, distributed systems, and serverless 
-applications. SQS eliminates the complexity and overhead associated with managing and 
-operating message oriented middleware, and empowers developers to focus on differentiating work. 
-Using SQS, you can send, store, and receive messages between software components at any volume, 
-without losing messages or requiring other services to be available. 
-
-## Installation
-
-Import to your project:
-
-```ts nofixture
-import * as sqs from 'aws-cdk-lib/aws-sqs';
-```
-
-## Basic usage
-
-
-Here's how to add a basic queue to your application:
-
-```ts
-new sqs.Queue(this, 'Queue');
-```
-
-## Encryption
-
-If you want to encrypt the queue contents, set the `encryption` property. You can have
-the messages encrypted with a key that SQS manages for you, or a key that you
-can manage yourself.
-
-```ts
-// Use managed key
-new sqs.Queue(this, 'Queue', {
-  encryption: sqs.QueueEncryption.KMS_MANAGED,
-});
-
-// Use custom key
-const myKey = new kms.Key(this, 'Key');
-
-new sqs.Queue(this, 'Queue', {
-  encryption: sqs.QueueEncryption.KMS,
-  encryptionMasterKey: myKey,
-});
-```
-
-## First-In-First-Out (FIFO) queues
-
-FIFO queues give guarantees on the order in which messages are dequeued, and have additional
-features in order to help guarantee exactly-once processing. For more information, see
-the SQS manual. Note that FIFO queues are not available in all AWS regions.
-
-A queue can be made a FIFO queue by either setting `fifo: true`, giving it a name which ends
-in `".fifo"`, or by enabling a FIFO specific feature such as: content-based deduplication, 
-deduplication scope or fifo throughput limit.