publicApi | boolean | Whether the construct is deploying a private or public API. This has implications for the VPC and ALB. |
loadBalancerProps? | elasticloadbalancingv2.ApplicationLoadBalancerProps | Optional custom properties for a new loadBalancer. Providing both this and existingLoadBalancer is an error. This cannot specify a VPC, it will use the VPC in existingVpc or the VPC created by the construct. |
existingLoadBalancerObj? | elasticloadbalancingv2.ApplicationLoadBalancer | [existing Application Load Balancer to incorporate into the construct architecture. Providing both this and loadBalancerProps is an error. The VPC containing this loadBalancer must match the VPC provided in existingVpc. |
listenerProps? | ApplicationListenerProps | Props to define the listener. Must be provided when adding the listener to an ALB (eg - when creating the alb), may not be provided when adding a second target to an already established listener. When provided, must include either a certificate or protocol: HTTP |
targetGroupProps? | ApplicationTargetGroupProps | Optional custom properties for a new target group. If your application requires end to end encryption, then you should set the protocol attribute to elb.ApplicationProtocol.HTTPS and use a container that can accept HTTPS traffic. |
ruleProps? | AddRuleProps | Rules for directing traffic to the target being created. Must not be specified for the first listener added to an ALB, and must be specified for the second target added to a listener. Add a second target by instantiating this construct a second time and providing the existingAlb from the first instantiation. |
vpcProps? | ec2.VpcProps | Optional custom properties for a VPC the construct will create. This VPC will be used by the new ALB and any Private Hosted Zone the construct creates (that's why loadBalancerProps and privateHostedZoneProps can't include a VPC). Providing both this and existingVpc is an error. |
existingVpc? | ec2.IVpc | An existing VPC in which to deploy the construct. Providing both this and vpcProps is an error. If the client provides an existing load balancer and/or existing Private Hosted Zone, those constructs must exist in this VPC. |
logAlbAccessLogs? | boolean | Whether to turn on Access Logs for the Application Load Balancer. Uses an S3 bucket with associated storage costs.Enabling Access Logging is a best practice. default - true |
albLoggingBucketProps? | s3.BucketProps | Optional properties to customize the bucket used to store the ALB Access Logs. Supplying this and setting logAccessLogs to false is an error. @default - none |
clusterProps | ecs.ClusterProps | Optional properties to create a new ECS cluster. To provide an existing cluster, use the cluster attribute of fargateServiceProps. |
ecrRepositoryArn | string]() | The arn of an ECR Repository containing the image to use to generate the containers. Either this or the image property of containerDefinitionProps must be provided. format: arn:aws:ecr:region:account number:repository/Repository Name |
ecrImageVersion | string]() | The version of the image to use from the repository. Defaults to 'Latest' |
containerDefinitionProps | [ecs.ContainerDefinitionProps / | any]() |
fargateTaskDefinitionProps | [ecs.FargateTaskDefinitionProps / | any]() |
fargateServiceProps | [ecs.FargateServiceProps / | any]() |
existingFargateServiceObject | ecs.FargateService | A Fargate Service already instantiated (probably by another Solutions Construct). If this is specified, then no props defining a new service can be provided, including: existingImageObject, ecrImageVersion, containerDefintionProps, fargateTaskDefinitionProps, ecrRepositoryArn, fargateServiceProps, clusterProps, existingClusterInterface |
existingContainerDefinitionObject | ecs.ContainerDefinition | A container definition already instantiated as part of a Fargate service. This much be the container in the existingFargateServiceObject |