@epilot360/icons 0.0.1 → 0.0.2

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

@@ -0,0 +1,27 @@
+# Amazon ElastiCache Construct Library
+
+
+This module is part of the [AWS Cloud Development Kit](https://github.com/aws/aws-cdk) project.
+
+```ts nofixture
+import * as elasticache from 'aws-cdk-lib/aws-elasticache';
+```
+
+<!--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 ElastiCache construct libraries](https://constructs.dev/search?q=elasticache)
+- 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::ElastiCache resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_ElastiCache.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::ElastiCache](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_ElastiCache.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-elasticbeanstalk/README.md

@@ -0,0 +1,27 @@
+# AWS Elastic Beanstalk Construct Library
+
+
+This module is part of the [AWS Cloud Development Kit](https://github.com/aws/aws-cdk) project.
+
+```ts nofixture
+import * as elasticbeanstalk from 'aws-cdk-lib/aws-elasticbeanstalk';
+```
+
+<!--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 ElasticBeanstalk construct libraries](https://constructs.dev/search?q=elasticbeanstalk)
+- 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::ElasticBeanstalk resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_ElasticBeanstalk.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::ElasticBeanstalk](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_ElasticBeanstalk.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-elasticloadbalancing/README.md

@@ -0,0 +1,40 @@
+# Amazon Elastic Load Balancing Construct Library
+
+
+The `@aws-cdk/aws-elasticloadbalancing` package provides constructs for configuring
+classic load balancers.
+
+## Configuring a Load Balancer
+
+Load balancers send traffic to one or more AutoScalingGroups. Create a load
+balancer, set up listeners and a health check, and supply the fleet(s) you want
+to load balance to in the `targets` property.
+
+```ts
+declare const vpc: ec2.IVpc;
+const lb = new elb.LoadBalancer(this, 'LB', {
+  vpc,
+  internetFacing: true,
+  healthCheck: {
+    port: 80,
+  },
+});
+
+declare const myAutoScalingGroup: autoscaling.AutoScalingGroup;
+lb.addTarget(myAutoScalingGroup);
+lb.addListener({
+  externalPort: 80,
+});
+```
+
+The load balancer allows all connections by default. If you want to change that,
+pass the `allowConnectionsFrom` property while setting up the listener:
+
+```ts
+declare const mySecurityGroup: ec2.SecurityGroup;
+declare const lb: elb.LoadBalancer;
+lb.addListener({
+  externalPort: 80,
+  allowConnectionsFrom: [mySecurityGroup],
+});
+```

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

@@ -0,0 +1,569 @@
+# Amazon Elastic Load Balancing V2 Construct Library
+
+
+
+The `@aws-cdk/aws-elasticloadbalancingv2` package provides constructs for
+configuring application and network load balancers.
+
+For more information, see the AWS documentation for
+[Application Load Balancers](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/introduction.html)
+and [Network Load Balancers](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/introduction.html).
+
+## Defining an Application Load Balancer
+
+You define an application load balancer by creating an instance of
+`ApplicationLoadBalancer`, adding a Listener to the load balancer
+and adding Targets to the Listener:
+
+```ts
+import { AutoScalingGroup } from 'aws-cdk-lib/aws-autoscaling';
+declare const asg: AutoScalingGroup;
+
+declare const vpc: ec2.Vpc;
+
+// Create the load balancer in a VPC. 'internetFacing' is 'false'
+// by default, which creates an internal load balancer.
+const lb = new elbv2.ApplicationLoadBalancer(this, 'LB', {
+  vpc,
+  internetFacing: true
+});
+
+// Add a listener and open up the load balancer's security group
+// to the world.
+const listener = lb.addListener('Listener', {
+  port: 80,
+
+  // 'open: true' is the default, you can leave it out if you want. Set it
+  // to 'false' and use `listener.connections` if you want to be selective
+  // about who can access the load balancer.
+  open: true,
+});
+
+// Create an AutoScaling group and add it as a load balancing
+// target to the listener.
+listener.addTargets('ApplicationFleet', {
+  port: 8080,
+  targets: [asg]
+});
+```
+
+The security groups of the load balancer and the target are automatically
+updated to allow the network traffic.
+
+One (or more) security groups can be associated with the load balancer;
+if a security group isn't provided, one will be automatically created.
+
+```ts
+declare const vpc: ec2.Vpc;
+
+const securityGroup1 = new ec2.SecurityGroup(this, 'SecurityGroup1', { vpc });
+const lb = new elbv2.ApplicationLoadBalancer(this, 'LB', {
+  vpc,
+  internetFacing: true,
+  securityGroup: securityGroup1, // Optional - will be automatically created otherwise
+});
+
+const securityGroup2 = new ec2.SecurityGroup(this, 'SecurityGroup2', { vpc });
+lb.addSecurityGroup(securityGroup2);
+```
+
+### Conditions
+
+It's possible to route traffic to targets based on conditions in the incoming
+HTTP request. For example, the following will route requests to the indicated
+AutoScalingGroup only if the requested host in the request is either for
+`example.com/ok` or `example.com/path`:
+
+```ts
+declare const listener: elbv2.ApplicationListener;
+declare const asg: autoscaling.AutoScalingGroup;
+
+listener.addTargets('Example.Com Fleet', {
+  priority: 10,
+  conditions: [
+    elbv2.ListenerCondition.hostHeaders(['example.com']),
+    elbv2.ListenerCondition.pathPatterns(['/ok', '/path']),
+  ],
+  port: 8080,
+  targets: [asg]
+});
+```
+
+A target with a condition contains either `pathPatterns` or `hostHeader`, or
+both. If both are specified, both conditions must be met for the requests to
+be routed to the given target. `priority` is a required field when you add
+targets with conditions. The lowest number wins.
+
+Every listener must have at least one target without conditions, which is
+where all requests that didn't match any of the conditions will be sent.
+
+### Convenience methods and more complex Actions
+
+Routing traffic from a Load Balancer to a Target involves the following steps:
+
+- Create a Target Group, register the Target into the Target Group
+- Add an Action to the Listener which forwards traffic to the Target Group.
+
+A new listener can be added to the Load Balancer by calling `addListener()`.
+Listeners that have been added to the load balancer can be listed using the
+`listeners` property.  Note that the `listeners` property will throw an Error
+for imported or looked up Load Balancers.
+
+Various methods on the `Listener` take care of this work for you to a greater
+or lesser extent:
+
+- `addTargets()` performs both steps: automatically creates a Target Group and the
+  required Action.
+- `addTargetGroups()` gives you more control: you create the Target Group (or
+  Target Groups) yourself and the method creates Action that routes traffic to
+  the Target Groups.
+- `addAction()` gives you full control: you supply the Action and wire it up
+  to the Target Groups yourself (or access one of the other ELB routing features).
+
+Using `addAction()` gives you access to some of the features of an Elastic Load
+Balancer that the other two convenience methods don't:
+
+- **Routing stickiness**: use `ListenerAction.forward()` and supply a
+  `stickinessDuration` to make sure requests are routed to the same target group
+  for a given duration.
+- **Weighted Target Groups**: use `ListenerAction.weightedForward()`
+  to give different weights to different target groups.
+- **Fixed Responses**: use `ListenerAction.fixedResponse()` to serve
+  a static response (ALB only).
+- **Redirects**: use `ListenerAction.redirect()` to serve an HTTP
+  redirect response (ALB only).
+- **Authentication**: use `ListenerAction.authenticateOidc()` to
+  perform OpenID authentication before serving a request (see the
+  `@aws-cdk/aws-elasticloadbalancingv2-actions` package for direct authentication
+  integration with Cognito) (ALB only).
+
+Here's an example of serving a fixed response at the `/ok` URL:
+
+```ts
+declare const listener: elbv2.ApplicationListener;
+
+listener.addAction('Fixed', {
+  priority: 10,
+  conditions: [
+    elbv2.ListenerCondition.pathPatterns(['/ok']),
+  ],
+  action: elbv2.ListenerAction.fixedResponse(200, {
+    contentType: elbv2.ContentType.TEXT_PLAIN,
+    messageBody: 'OK',
+  })
+});
+```
+
+Here's an example of using OIDC authentication before forwarding to a TargetGroup:
+
+```ts
+declare const listener: elbv2.ApplicationListener;
+declare const myTargetGroup: elbv2.ApplicationTargetGroup;
+
+listener.addAction('DefaultAction', {
+  action: elbv2.ListenerAction.authenticateOidc({
+    authorizationEndpoint: 'https://example.com/openid',
+    // Other OIDC properties here
+    clientId: '...',
+    clientSecret: SecretValue.secretsManager('...'),
+    issuer: '...',
+    tokenEndpoint: '...',
+    userInfoEndpoint: '...',
+
+    // Next
+    next: elbv2.ListenerAction.forward([myTargetGroup]),
+  }),
+});
+```
+
+If you just want to redirect all incoming traffic on one port to another port, you can use the following code:
+
+```ts
+declare const lb: elbv2.ApplicationLoadBalancer;
+
+lb.addRedirect({
+  sourceProtocol: elbv2.ApplicationProtocol.HTTPS,
+  sourcePort: 8443,
+  targetProtocol: elbv2.ApplicationProtocol.HTTP,
+  targetPort: 8080,
+});
+```
+
+If you do not provide any options for this method, it redirects HTTP port 80 to HTTPS port 443.
+
+By default all ingress traffic will be allowed on the source port. If you want to be more selective with your
+ingress rules then set `open: false` and use the listener's `connections` object to selectively grant access to the listener.
+
+## Defining a Network Load Balancer
+
+Network Load Balancers are defined in a similar way to Application Load
+Balancers:
+
+```ts
+declare const vpc: ec2.Vpc;
+declare const asg: autoscaling.AutoScalingGroup;
+
+// Create the load balancer in a VPC. 'internetFacing' is 'false'
+// by default, which creates an internal load balancer.
+const lb = new elbv2.NetworkLoadBalancer(this, 'LB', {
+  vpc,
+  internetFacing: true
+});
+
+// Add a listener on a particular port.
+const listener = lb.addListener('Listener', {
+  port: 443,
+});
+
+// Add targets on a particular port.
+listener.addTargets('AppFleet', {
+  port: 443,
+  targets: [asg]
+});
+```
+
+One thing to keep in mind is that network load balancers do not have security
+groups, and no automatic security group configuration is done for you. You will
+have to configure the security groups of the target yourself to allow traffic by
+clients and/or load balancer instances, depending on your target types.  See
+[Target Groups for your Network Load
+Balancers](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-target-groups.html)
+and [Register targets with your Target
+Group](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/target-group-register-targets.html)
+for more information.
+
+## Targets and Target Groups
+
+Application and Network Load Balancers organize load balancing targets in Target
+Groups. If you add your balancing targets (such as AutoScalingGroups, ECS
+services or individual instances) to your listener directly, the appropriate
+`TargetGroup` will be automatically created for you.
+
+If you need more control over the Target Groups created, create an instance of
+`ApplicationTargetGroup` or `NetworkTargetGroup`, add the members you desire,
+and add it to the listener by calling `addTargetGroups` instead of `addTargets`.
+
+`addTargets()` will always return the Target Group it just created for you:
+
+```ts
+declare const listener: elbv2.NetworkListener;
+declare const asg1: autoscaling.AutoScalingGroup;
+declare const asg2: autoscaling.AutoScalingGroup;
+
+const group = listener.addTargets('AppFleet', {
+  port: 443,
+  targets: [asg1],
+});
+
+group.addTarget(asg2);
+```
+
+### Sticky sessions for your Application Load Balancer
+
+By default, an Application Load Balancer routes each request independently to a registered target based on the chosen load-balancing algorithm. However, you can use the sticky session feature (also known as session affinity) to enable the load balancer to bind a user's session to a specific target. This ensures that all requests from the user during the session are sent to the same target. This feature is useful for servers that maintain state information in order to provide a continuous experience to clients. To use sticky sessions, the client must support cookies.
+
+Application Load Balancers support both duration-based cookies (`lb_cookie`) and application-based cookies (`app_cookie`). The key to managing sticky sessions is determining how long your load balancer should consistently route the user's request to the same target. Sticky sessions are enabled at the target group level. You can use a combination of duration-based stickiness, application-based stickiness, and no stickiness across all of your target groups.
+
+```ts
+declare const vpc: ec2.Vpc;
+
+// Target group with duration-based stickiness with load-balancer generated cookie
+const tg1 = new elbv2.ApplicationTargetGroup(this, 'TG1', {
+  targetType: elbv2.TargetType.INSTANCE,
+  port: 80,
+  stickinessCookieDuration: Duration.minutes(5),
+  vpc,
+});
+
+// Target group with application-based stickiness
+const tg2 = new elbv2.ApplicationTargetGroup(this, 'TG2', {
+  targetType: elbv2.TargetType.INSTANCE,
+  port: 80,
+  stickinessCookieDuration: Duration.minutes(5),
+  stickinessCookieName: 'MyDeliciousCookie',
+  vpc,
+});
+```
+
+For more information see: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/sticky-sessions.html#application-based-stickiness
+
+### Setting the target group protocol version
+
+By default, Application Load Balancers send requests to targets using HTTP/1.1. You can use the [protocol version](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-target-groups.html#target-group-protocol-version) to send requests to targets using HTTP/2 or gRPC.
+
+```ts
+declare const vpc: ec2.Vpc;
+
+const tg = new elbv2.ApplicationTargetGroup(this, 'TG', {
+  targetType: elbv2.TargetType.IP,
+  port: 50051,
+  protocol: elbv2.ApplicationProtocol.HTTP,
+  protocolVersion: elbv2.ApplicationProtocolVersion.GRPC,
+  healthCheck: {
+    enabled: true,
+    healthyGrpcCodes: '0-99',
+  },
+  vpc,
+});
+```
+
+## Using Lambda Targets
+
+To use a Lambda Function as a target, use the integration class in the
+`@aws-cdk/aws-elasticloadbalancingv2-targets` package:
+
+```ts
+import * as lambda from 'aws-cdk-lib/aws-lambda';
+import * as targets from 'aws-cdk-lib/aws-elasticloadbalancingv2-targets';
+
+declare const lambdaFunction: lambda.Function;
+declare const lb: elbv2.ApplicationLoadBalancer;
+
+const listener = lb.addListener('Listener', { port: 80 });
+listener.addTargets('Targets', {
+  targets: [new targets.LambdaTarget(lambdaFunction)],
+
+  // For Lambda Targets, you need to explicitly enable health checks if you
+  // want them.
+  healthCheck: {
+    enabled: true,
+  }
+});
+```
+
+Only a single Lambda function can be added to a single listener rule.
+
+## Using Application Load Balancer Targets
+
+To use a single application load balancer as a target for the network load balancer, use the integration class in the
+`@aws-cdk/aws-elasticloadbalancingv2-targets` package:
+
+```ts
+import * as targets from 'aws-cdk-lib/aws-elasticloadbalancingv2-targets';
+import * as ecs from 'aws-cdk-lib/aws-ecs';
+import * as patterns from 'aws-cdk-lib/aws-ecs-patterns';
+
+declare const vpc: ec2.Vpc;
+
+const task = new ecs.FargateTaskDefinition(this, 'Task', { cpu: 256, memoryLimitMiB: 512 });
+task.addContainer('nginx', {
+  image: ecs.ContainerImage.fromRegistry('public.ecr.aws/nginx/nginx:latest'),
+  portMappings: [{ containerPort: 80 }],
+});
+
+const svc = new patterns.ApplicationLoadBalancedFargateService(this, 'Service', {
+  vpc,
+  taskDefinition: task,
+  publicLoadBalancer: false,
+});
+
+const nlb = new elbv2.NetworkLoadBalancer(this, 'Nlb', {
+  vpc,
+  crossZoneEnabled: true,
+  internetFacing: true,
+});
+
+const listener = nlb.addListener('listener', { port: 80 });
+
+listener.addTargets('Targets', {
+  targets: [new targets.AlbTarget(svc.loadBalancer, 80)],
+  port: 80,
+});
+
+new CfnOutput(this, 'NlbEndpoint', { value: `http://${nlb.loadBalancerDnsName}`})
+```
+
+Only the network load balancer is allowed to add the application load balancer as the target.
+
+## Configuring Health Checks
+
+Health checks are configured upon creation of a target group:
+
+```ts
+declare const listener: elbv2.ApplicationListener;
+declare const asg: autoscaling.AutoScalingGroup;
+
+listener.addTargets('AppFleet', {
+  port: 8080,
+  targets: [asg],
+  healthCheck: {
+    path: '/ping',
+    interval: Duration.minutes(1),
+  }
+});
+```
+
+The health check can also be configured after creation by calling
+`configureHealthCheck()` on the created object.
+
+No attempts are made to configure security groups for the port you're
+configuring a health check for, but if the health check is on the same port
+you're routing traffic to, the security group already allows the traffic.
+If not, you will have to configure the security groups appropriately:
+
+```ts
+declare const lb: elbv2.ApplicationLoadBalancer;
+declare const listener: elbv2.ApplicationListener;
+declare const asg: autoscaling.AutoScalingGroup;
+
+listener.addTargets('AppFleet', {
+  port: 8080,
+  targets: [asg],
+  healthCheck: {
+    port: '8088',
+  }
+});
+
+asg.connections.allowFrom(lb, ec2.Port.tcp(8088));
+```
+
+## Using a Load Balancer from a different Stack
+
+If you want to put your Load Balancer and the Targets it is load balancing to in
+different stacks, you may not be able to use the convenience methods
+`loadBalancer.addListener()` and `listener.addTargets()`.
+
+The reason is that these methods will create resources in the same Stack as the
+object they're called on, which may lead to cyclic references between stacks.
+Instead, you will have to create an `ApplicationListener` in the target stack,
+or an empty `TargetGroup` in the load balancer stack that you attach your
+service to.
+
+For an example of the alternatives while load balancing to an ECS service, see the
+[ecs/cross-stack-load-balancer
+example](https://github.com/aws-samples/aws-cdk-examples/tree/master/typescript/ecs/cross-stack-load-balancer/).
+
+## Protocol for Load Balancer Targets
+
+Constructs that want to be a load balancer target should implement
+`IApplicationLoadBalancerTarget` and/or `INetworkLoadBalancerTarget`, and
+provide an implementation for the function `attachToXxxTargetGroup()`, which can
+call functions on the load balancer and should return metadata about the
+load balancing target:
+
+```ts
+class MyTarget implements elbv2.IApplicationLoadBalancerTarget {
+  public attachToApplicationTargetGroup(targetGroup: elbv2.ApplicationTargetGroup): elbv2.LoadBalancerTargetProps {
+    // If we need to add security group rules
+    // targetGroup.registerConnectable(...);
+    return {
+      targetType: elbv2.TargetType.IP,
+      targetJson: { id: '1.2.3.4', port: 8080 },
+    };
+  }
+}
+```
+
+`targetType` should be one of `Instance` or `Ip`. If the target can be
+directly added to the target group, `targetJson` should contain the `id` of
+the target (either instance ID or IP address depending on the type) and
+optionally a `port` or `availabilityZone` override.
+
+Application load balancer targets can call `registerConnectable()` on the
+target group to register themselves for addition to the load balancer's security
+group rules.
+
+If your load balancer target requires that the TargetGroup has been
+associated with a LoadBalancer before registration can happen (such as is the
+case for ECS Services for example), take a resource dependency on
+`targetGroup.loadBalancerAttached` as follows:
+
+```ts
+declare const resource: Resource;
+declare const targetGroup: elbv2.ApplicationTargetGroup;
+
+// Make sure that the listener has been created, and so the TargetGroup
+// has been associated with the LoadBalancer, before 'resource' is created.
+
+Node.of(resource).addDependency(targetGroup.loadBalancerAttached);
+```
+
+## Looking up Load Balancers and Listeners
+
+You may look up load balancers and load balancer listeners by using one of the
+following lookup methods:
+
+- `ApplicationLoadBalancer.fromlookup(options)` - Look up an application load
+  balancer.
+- `ApplicationListener.fromLookup(options)` - Look up an application load
+  balancer listener.
+- `NetworkLoadBalancer.fromLookup(options)` - Look up a network load balancer.
+- `NetworkListener.fromLookup(options)` - Look up a network load balancer
+  listener.
+
+### Load Balancer lookup options
+
+You may look up a load balancer by ARN or by associated tags. When you look a
+load balancer up by ARN, that load balancer will be returned unless CDK detects
+that the load balancer is of the wrong type. When you look up a load balancer by
+tags, CDK will return the load balancer matching all specified tags. If more
+than one load balancer matches, CDK will throw an error requesting that you
+provide more specific criteria.
+
+**Look up a Application Load Balancer by ARN**
+
+```ts
+const loadBalancer = elbv2.ApplicationLoadBalancer.fromLookup(this, 'ALB', {
+  loadBalancerArn: 'arn:aws:elasticloadbalancing:us-east-2:123456789012:loadbalancer/app/my-load-balancer/1234567890123456',
+});
+```
+
+**Look up an Application Load Balancer by tags**
+
+```ts
+const loadBalancer = elbv2.ApplicationLoadBalancer.fromLookup(this, 'ALB', {
+  loadBalancerTags: {
+    // Finds a load balancer matching all tags.
+    some: 'tag',
+    someother: 'tag',
+  },
+});
+```
+
+## Load Balancer Listener lookup options
+
+You may look up a load balancer listener by the following criteria:
+
+- Associated load balancer ARN
+- Associated load balancer tags
+- Listener ARN
+- Listener port
+- Listener protocol
+
+The lookup method will return the matching listener. If more than one listener
+matches, CDK will throw an error requesting that you specify additional
+criteria.
+
+**Look up a Listener by associated Load Balancer, Port, and Protocol**
+
+```ts
+const listener = elbv2.ApplicationListener.fromLookup(this, 'ALBListener', {
+  loadBalancerArn: 'arn:aws:elasticloadbalancing:us-east-2:123456789012:loadbalancer/app/my-load-balancer/1234567890123456',
+  listenerProtocol: elbv2.ApplicationProtocol.HTTPS,
+  listenerPort: 443,
+});
+```
+
+**Look up a Listener by associated Load Balancer Tag, Port, and Protocol**
+
+```ts
+const listener = elbv2.ApplicationListener.fromLookup(this, 'ALBListener', {
+  loadBalancerTags: {
+    Cluster: 'MyClusterName',
+  },
+  listenerProtocol: elbv2.ApplicationProtocol.HTTPS,
+  listenerPort: 443,
+});
+```
+
+**Look up a Network Listener by associated Load Balancer Tag, Port, and Protocol**
+
+```ts
+const listener = elbv2.NetworkListener.fromLookup(this, 'ALBListener', {
+  loadBalancerTags: {
+    Cluster: 'MyClusterName',
+  },
+  listenerProtocol: elbv2.Protocol.TCP,
+  listenerPort: 12345,
+});
+```