@epilot360/icons 0.0.2 → 0.1.0

package/iac/node_modules/aws-cdk-lib/aws-cloudfront-origins/README.md

@@ -1,126 +0,0 @@
-# CloudFront Origins for the CDK CloudFront Library
-
-
-This library contains convenience methods for defining origins for a CloudFront distribution. You can use this library to create origins from
-S3 buckets, Elastic Load Balancing v2 load balancers, or any other domain name.
-
-## S3 Bucket
-
-An S3 bucket can be added as an origin. If the bucket is configured as a website endpoint, the distribution can use S3 redirects and S3 custom error
-documents.
-
-```ts
-const myBucket = new s3.Bucket(this, 'myBucket');
-new cloudfront.Distribution(this, 'myDist', {
-  defaultBehavior: { origin: new origins.S3Origin(myBucket) },
-});
-```
-
-The above will treat the bucket differently based on if `IBucket.isWebsite` is set or not. If the bucket is configured as a website, the bucket is
-treated as an HTTP origin, and the built-in S3 redirects and error pages can be used. Otherwise, the bucket is handled as a bucket origin and
-CloudFront's redirect and error handling will be used. In the latter case, the Origin will create an origin access identity and grant it access to the
-underlying bucket. This can be used in conjunction with a bucket that is not public to require that your users access your content using CloudFront
-URLs and not S3 URLs directly. Alternatively, a custom origin access identity can be passed to the S3 origin in the properties.
-
-### Adding Custom Headers
-
-You can configure CloudFront to add custom headers to the requests that it sends to your origin. These custom headers enable you to send and gather information from your origin that you don’t get with typical viewer requests. These headers can even be customized for each origin. CloudFront supports custom headers for both for custom and Amazon S3 origins.
-
-```ts
-const myBucket = new s3.Bucket(this, 'myBucket');
-new cloudfront.Distribution(this, 'myDist', {
-  defaultBehavior: { origin: new origins.S3Origin(myBucket, {
-    customHeaders: {
-      Foo: 'bar',
-    },
-  })},
-});
-```
-
-## ELBv2 Load Balancer
-
-An Elastic Load Balancing (ELB) v2 load balancer may be used as an origin. In order for a load balancer to serve as an origin, it must be publicly
-accessible (`internetFacing` is true). Both Application and Network load balancers are supported.
-
-```ts
-import * as ec2 from 'aws-cdk-lib/aws-ec2';
-import * as elbv2 from 'aws-cdk-lib/aws-elasticloadbalancingv2';
-
-declare const vpc: ec2.Vpc;
-// Create an application load balancer in a VPC. 'internetFacing' must be 'true'
-// for CloudFront to access the load balancer and use it as an origin.
-const lb = new elbv2.ApplicationLoadBalancer(this, 'LB', {
-  vpc,
-  internetFacing: true,
-});
-new cloudfront.Distribution(this, 'myDist', {
-  defaultBehavior: { origin: new origins.LoadBalancerV2Origin(lb) },
-});
-```
-
-The origin can also be customized to respond on different ports, have different connection properties, etc.
-
-```ts
-import * as elbv2 from 'aws-cdk-lib/aws-elasticloadbalancingv2';
-
-declare const loadBalancer: elbv2.ApplicationLoadBalancer;
-const origin = new origins.LoadBalancerV2Origin(loadBalancer, {
-  connectionAttempts: 3,
-  connectionTimeout: Duration.seconds(5),
-  readTimeout: Duration.seconds(45),
-  keepaliveTimeout: Duration.seconds(45),
-  protocolPolicy: cloudfront.OriginProtocolPolicy.MATCH_VIEWER,
-});
-```
-
-Note that the `readTimeout` and `keepaliveTimeout` properties can extend their values over 60 seconds only if a limit increase request for CloudFront origin response timeout
-quota has been approved in the target account; otherwise, values over 60 seconds will produce an error at deploy time. Consider that this value is
-still limited to a maximum value of 180 seconds, which is a hard limit for that quota.
-
-## From an HTTP endpoint
-
-Origins can also be created from any other HTTP endpoint, given the domain name, and optionally, other origin properties.
-
-```ts
-new cloudfront.Distribution(this, 'myDist', {
-  defaultBehavior: { origin: new origins.HttpOrigin('www.example.com') },
-});
-```
-
-See the documentation of `@aws-cdk/aws-cloudfront` for more information.
-
-## Failover Origins (Origin Groups)
-
-You can set up CloudFront with origin failover for scenarios that require high availability.
-To get started, you create an origin group with two origins: a primary and a secondary.
-If the primary origin is unavailable, or returns specific HTTP response status codes that indicate a failure,
-CloudFront automatically switches to the secondary origin.
-You achieve that behavior in the CDK using the `OriginGroup` class:
-
-```ts
-const myBucket = new s3.Bucket(this, 'myBucket');
-new cloudfront.Distribution(this, 'myDist', {
-  defaultBehavior: {
-    origin: new origins.OriginGroup({
-      primaryOrigin: new origins.S3Origin(myBucket),
-      fallbackOrigin: new origins.HttpOrigin('www.example.com'),
-      // optional, defaults to: 500, 502, 503 and 504
-      fallbackStatusCodes: [404],
-    }),
-  },
-});
-```
-
-## From an API Gateway REST API
-
-Origins can be created from an API Gateway REST API. It is recommended to use a
-[regional API](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-endpoint-types.html) in this case.
-
-```ts
-declare const api: apigateway.RestApi;
-new cloudfront.Distribution(this, 'Distribution', {
-  defaultBehavior: { origin: new origins.RestApiOrigin(api) },
-});
-```
-
-The origin path will automatically be set as the stage name.

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

@@ -1,189 +0,0 @@
-# AWS CloudTrail Construct Library
-
-
-## Trail
-
-AWS CloudTrail enables governance, compliance, and operational and risk auditing of your AWS account. Actions taken by
-a user, role, or an AWS service are recorded as events in CloudTrail. Learn more at the [CloudTrail
-documentation](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-user-guide.html).
-
-The `Trail` construct enables ongoing delivery of events as log files to an Amazon S3 bucket. Learn more about [Creating
-a Trail for Your AWS Account](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-create-and-update-a-trail.html).
-The following code creates a simple CloudTrail for your account -
-
-```ts
-const trail = new cloudtrail.Trail(this, 'CloudTrail');
-```
-
-By default, this will create a new S3 Bucket that CloudTrail will write to, and choose a few other reasonable defaults
-such as turning on multi-region and global service events. 
-The defaults for each property and how to override them are all documented on the `TrailProps` interface.
-
-## Log File Validation
-
-In order to validate that the CloudTrail log file was not modified after CloudTrail delivered it, CloudTrail provides a
-digital signature for each file. Learn more at [Validating CloudTrail Log File
-Integrity](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-log-file-validation-intro.html).
-
-This is enabled on the `Trail` construct by default, but can be turned off by setting `enableFileValidation` to `false`.
-
-```ts
-const trail = new cloudtrail.Trail(this, 'CloudTrail', {
-  enableFileValidation: false,
-});
-```
-
-## Notifications
-
-Amazon SNS notifications can be configured upon new log files containing Trail events are delivered to S3.
-Learn more at [Configuring Amazon SNS Notifications for
-CloudTrail](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/configure-sns-notifications-for-cloudtrail.html).
-The following code configures an SNS topic to be notified -
-
-```ts
-const topic = new sns.Topic(this, 'TrailTopic');
-const trail = new cloudtrail.Trail(this, 'CloudTrail', {
-  snsTopic: topic,
-});
-```
-
-## Service Integrations
-
-Besides sending trail events to S3, they can also be configured to notify other AWS services -
-
-### Amazon CloudWatch Logs
-
-CloudTrail events can be delivered to a CloudWatch Logs LogGroup. By default, a new LogGroup is created with a
-default retention setting. The following code enables sending CloudWatch logs but specifies a particular retention
-period for the created Log Group.
-
-```ts
-import * as logs from 'aws-cdk-lib/aws-logs';
-
-const trail = new cloudtrail.Trail(this, 'CloudTrail', {
-  sendToCloudWatchLogs: true,
-  cloudWatchLogsRetention: logs.RetentionDays.FOUR_MONTHS, 
-});
-```
-
-If you would like to use a specific log group instead, this can be configured via `cloudwatchLogGroup`.
-
-### Amazon EventBridge
-
-Amazon EventBridge rules can be configured to be triggered when CloudTrail events occur using the `Trail.onEvent()` API.
-Using APIs available in `aws-events`, these events can be filtered to match to those that are of interest, either from
-a specific service, account or time range. See [Events delivered via
-CloudTrail](https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/EventTypes.html#events-for-services-not-listed)
-to learn more about the event structure for events from CloudTrail.
-
-The following code filters events for S3 from a specific AWS account and triggers a lambda function.
-
-```ts
-const myFunctionHandler = new lambda.Function(this, 'MyFunction', {
-  code: lambda.Code.fromAsset('resource/myfunction'),
-  runtime: lambda.Runtime.NODEJS_14_X,
-  handler: 'index.handler',
-});
-
-const eventRule = cloudtrail.Trail.onEvent(this, 'MyCloudWatchEvent', {
-  target: new targets.LambdaFunction(myFunctionHandler),
-});
-
-eventRule.addEventPattern({
-  account: ['123456789012'],
-  source: ['aws.s3'],
-});
-```
-
-## Multi-Region & Global Service Events
-
-By default, a `Trail` is configured to deliver log files from multiple regions to a single S3 bucket for a given
-account. This creates shadow trails (replication of the trails) in all of the other regions. Learn more about [How
-CloudTrail Behaves Regionally](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-concepts.html#cloudtrail-concepts-regional-and-global-services)
-and about the [`IsMultiRegion`
-property](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloudtrail-trail.html#cfn-cloudtrail-trail-ismultiregiontrail).
-
-For most services, events are recorded in the region where the action occurred. For global services such as AWS IAM,
-AWS STS, Amazon CloudFront, Route 53, etc., events are delivered to any trail that includes global services. Learn more
-[About Global Service Events](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-concepts.html#cloudtrail-concepts-global-service-events).
-
-Events for global services are turned on by default for `Trail` constructs in the CDK.
-
-The following code disables multi-region trail delivery and trail delivery for global services for a specific `Trail` -
-
-```ts
-const trail = new cloudtrail.Trail(this, 'CloudTrail', {
-  // ...
-  isMultiRegionTrail: false,
-  includeGlobalServiceEvents: false,
-});
-```
-
-## Events Types
-
-**Management events** provide information about management operations that are performed on resources in your AWS
-account. These are also known as control plane operations. Learn more about [Management
-Events](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-concepts.html#cloudtrail-concepts-events).
-
-By default, a `Trail` logs all management events. However, they can be configured to either be turned off, or to only
-log 'Read' or 'Write' events. 
-
-The following code configures the `Trail` to only track management events that are of type 'Read'.
-
-```ts
-const trail = new cloudtrail.Trail(this, 'CloudTrail', {
-  // ...
-  managementEvents: cloudtrail.ReadWriteType.READ_ONLY,
-});
-```
-
-**Data events** provide information about the resource operations performed on or in a resource. These are also known
-as data plane operations. Learn more about [Data
-Events](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-concepts.html#cloudtrail-concepts-events).
-By default, no data events are logged for a `Trail`.
-
-AWS CloudTrail supports data event logging for Amazon S3 objects and AWS Lambda functions.
-
-The `logAllS3DataEvents()` API configures the trail to log all S3 data events while the `addS3EventSelector()` API can
-be used to configure logging of S3 data events for specific buckets and specific object prefix. The following code
-configures logging of S3 data events for `fooBucket` and with object prefix `bar/`.
-
-```ts
-import * as s3 from 'aws-cdk-lib/aws-s3';
-
-const trail = new cloudtrail.Trail(this, 'MyAmazingCloudTrail');
-declare const bucket: s3.Bucket;
-
-// Adds an event selector to the bucket foo
-trail.addS3EventSelector([{
-  bucket,
-  objectPrefix: 'bar/',
-}]);
-```
-
-Similarly, the `logAllLambdaDataEvents()` configures the trail to log all Lambda data events while the
-`addLambdaEventSelector()` API can be used to configure logging for specific Lambda functions. The following code
-configures logging of Lambda data events for a specific Function.
-
-```ts
-const trail = new cloudtrail.Trail(this, 'MyAmazingCloudTrail');
-const amazingFunction = new lambda.Function(this, 'AnAmazingFunction', {
-  runtime: lambda.Runtime.NODEJS_14_X,
-  handler: "hello.handler",
-  code: lambda.Code.fromAsset("lambda"),
-});
-
-// Add an event selector to log data events for the provided Lambda functions.
-trail.addLambdaEventSelector([ amazingFunction ]);
-```
-
-## Organization Trail
-
-It is possible to create a trail that will be applied to all accounts in an organization if the current account manages an organization.
-To enable this, the property `isOrganizationTrail` must be set. If this property is set and the current account does not manage an organization, the stack will fail to deploy.
-
-```ts
-new cloudtrail.Trail(this, 'OrganizationTrail', {
-  isOrganizationTrail: true,
-});
-```