@propulsionworks/cloudformation 0.0.1 → 0.1.0

package/out/exports/resources.generated/aws-elasticloadbalancingv2-loadbalancer.d.ts

@@ -0,0 +1,204 @@
+import type { ResourceDefinitionWithAttributes, Tag } from "../main.ts";
+export type ElasticLoadBalancingV2LoadBalancer = ResourceDefinitionWithAttributes<"AWS::ElasticLoadBalancingV2::LoadBalancer", ElasticLoadBalancingV2LoadBalancerProps, ElasticLoadBalancingV2LoadBalancerAttribs>;
+/**
+ * Specifies an Application Load Balancer, a Network Load Balancer, or a Gateway Load Balancer.
+ */
+export type ElasticLoadBalancingV2LoadBalancerProps = {
+    /**
+     * [Network Load Balancers with UDP listeners] Indicates whether to use an IPv6 prefix from each subnet for source NAT. The IP address type must be `dualstack` . The default value is `off` .
+     */
+    EnablePrefixForIpv6SourceNat?: string | undefined;
+    /**
+     * Indicates whether to evaluate inbound security group rules for traffic sent to a Network Load Balancer through AWS PrivateLink . The default is `on` .
+     *
+     * You can't configure this property on a Network Load Balancer unless you associated a security group with the load balancer when you created it.
+     */
+    EnforceSecurityGroupInboundRulesOnPrivateLinkTraffic?: string | undefined;
+    /**
+     * The IP address type. Internal load balancers must use `ipv4` .
+     *
+     * [Application Load Balancers] The possible values are `ipv4` (IPv4 addresses), `dualstack` (IPv4 and IPv6 addresses), and `dualstack-without-public-ipv4` (public IPv6 addresses and private IPv4 and IPv6 addresses).
+     *
+     * Application Load Balancer authentication supports IPv4 addresses only when connecting to an Identity Provider (IdP) or Amazon Cognito endpoint. Without a public IPv4 address the load balancer can't complete the authentication process, resulting in HTTP 500 errors.
+     *
+     * [Network Load Balancers and Gateway Load Balancers] The possible values are `ipv4` (IPv4 addresses) and `dualstack` (IPv4 and IPv6 addresses).
+     */
+    IpAddressType?: string | undefined;
+    /**
+     * The ID of the IPv4 IPAM pool.
+     */
+    Ipv4IpamPoolId?: string | undefined;
+    /**
+     * The load balancer attributes.
+     */
+    LoadBalancerAttributes?: LoadBalancerAttribute[] | undefined;
+    /**
+     * The minimum capacity for a load balancer.
+     */
+    MinimumLoadBalancerCapacity?: MinimumLoadBalancerCapacity | undefined;
+    /**
+     * The name of the load balancer. This name must be unique per region per account, can have a maximum of 32 characters, must contain only alphanumeric characters or hyphens, must not begin or end with a hyphen, and must not begin with "internal-".
+     *
+     * If you don't specify a name, AWS CloudFormation generates a unique physical ID for the load balancer. If you specify a name, you cannot perform updates that require replacement of this resource, but you can perform other updates. To replace the resource, specify a new name.
+     */
+    Name?: string | undefined;
+    /**
+     * The nodes of an Internet-facing load balancer have public IP addresses. The DNS name of an Internet-facing load balancer is publicly resolvable to the public IP addresses of the nodes. Therefore, Internet-facing load balancers can route requests from clients over the internet.
+     *
+     * The nodes of an internal load balancer have only private IP addresses. The DNS name of an internal load balancer is publicly resolvable to the private IP addresses of the nodes. Therefore, internal load balancers can route requests only from clients with access to the VPC for the load balancer.
+     *
+     * The default is an Internet-facing load balancer.
+     *
+     * You can't specify a scheme for a Gateway Load Balancer.
+     */
+    Scheme?: string | undefined;
+    /**
+     * [Application Load Balancers and Network Load Balancers] The IDs of the security groups for the load balancer.
+     */
+    SecurityGroups?: string[] | undefined;
+    /**
+     * The IDs of the subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings, but not both.
+     *
+     * [Application Load Balancers] You must specify subnets from at least two Availability Zones. You can't specify Elastic IP addresses for your subnets.
+     *
+     * [Application Load Balancers on Outposts] You must specify one Outpost subnet.
+     *
+     * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
+     *
+     * [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. For internet-facing load balancer, you can specify one IPv6 address per subnet.
+     *
+     * [Gateway Load Balancers] You can specify subnets from one or more Availability Zones. You can't specify Elastic IP addresses for your subnets.
+     */
+    SubnetMappings?: SubnetMapping[] | undefined;
+    /**
+     * The IDs of the subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings, but not both. To specify an Elastic IP address, specify subnet mappings instead of subnets.
+     *
+     * [Application Load Balancers] You must specify subnets from at least two Availability Zones.
+     *
+     * [Application Load Balancers on Outposts] You must specify one Outpost subnet.
+     *
+     * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
+     *
+     * [Network Load Balancers and Gateway Load Balancers] You can specify subnets from one or more Availability Zones.
+     */
+    Subnets?: string[] | undefined;
+    /**
+     * The tags to assign to the load balancer.
+     */
+    Tags?: Tag[] | undefined;
+    /**
+     * The type of load balancer. The default is `application` .
+     */
+    Type?: string | undefined;
+};
+export type ElasticLoadBalancingV2LoadBalancerAttribs = {
+    /**
+     * The ID of the Amazon Route 53 hosted zone associated with the load balancer. For example, `Z2P70J7EXAMPLE` .
+     */
+    CanonicalHostedZoneID: string;
+    /**
+     * The DNS name for the load balancer. For example, `my-load-balancer-424835706.us-west-2.elb.amazonaws.com` .
+     */
+    DNSName: string;
+    /**
+     * The Amazon Resource Name (ARN) of the load balancer.
+     */
+    LoadBalancerArn: string;
+    /**
+     * The full name of the load balancer. For example, `app/my-load-balancer/50dc6c495c0c9188` .
+     */
+    LoadBalancerFullName: string;
+    /**
+     * The name of the load balancer. For example, `my-load-balancer` .
+     */
+    LoadBalancerName: string;
+    /**
+     * The IDs of the security groups for the load balancer.
+     */
+    SecurityGroups: string[];
+};
+/**
+ * Specifies an attribute for an Application Load Balancer, a Network Load Balancer, or a Gateway Load Balancer.
+ */
+export type LoadBalancerAttribute = {
+    /**
+     * The name of the attribute.
+     *
+     * The following attributes are supported by all load balancers:
+     *
+     * - `deletion_protection.enabled` - Indicates whether deletion protection is enabled. The value is `true` or `false` . The default is `false` .
+     * - `load_balancing.cross_zone.enabled` - Indicates whether cross-zone load balancing is enabled. The possible values are `true` and `false` . The default for Network Load Balancers and Gateway Load Balancers is `false` . The default for Application Load Balancers is `true` , and can't be changed.
+     *
+     * The following attributes are supported by both Application Load Balancers and Network Load Balancers:
+     *
+     * - `access_logs.s3.enabled` - Indicates whether access logs are enabled. The value is `true` or `false` . The default is `false` .
+     * - `access_logs.s3.bucket` - The name of the S3 bucket for the access logs. This attribute is required if access logs are enabled. The bucket must exist in the same region as the load balancer and have a bucket policy that grants Elastic Load Balancing permissions to write to the bucket.
+     * - `access_logs.s3.prefix` - The prefix for the location in the S3 bucket for the access logs.
+     * - `ipv6.deny_all_igw_traffic` - Blocks internet gateway (IGW) access to the load balancer. It is set to `false` for internet-facing load balancers and `true` for internal load balancers, preventing unintended access to your internal load balancer through an internet gateway.
+     * - `zonal_shift.config.enabled` - Indicates whether zonal shift is enabled. The possible values are `true` and `false` . The default is `false` .
+     *
+     * The following attributes are supported by only Application Load Balancers:
+     *
+     * - `idle_timeout.timeout_seconds` - The idle timeout value, in seconds. The valid range is 1-4000 seconds. The default is 60 seconds.
+     * - `client_keep_alive.seconds` - The client keep alive value, in seconds. The valid range is 60-604800 seconds. The default is 3600 seconds.
+     * - `connection_logs.s3.enabled` - Indicates whether connection logs are enabled. The value is `true` or `false` . The default is `false` .
+     * - `connection_logs.s3.bucket` - The name of the S3 bucket for the connection logs. This attribute is required if connection logs are enabled. The bucket must exist in the same region as the load balancer and have a bucket policy that grants Elastic Load Balancing permissions to write to the bucket.
+     * - `connection_logs.s3.prefix` - The prefix for the location in the S3 bucket for the connection logs.
+     * - `routing.http.desync_mitigation_mode` - Determines how the load balancer handles requests that might pose a security risk to your application. The possible values are `monitor` , `defensive` , and `strictest` . The default is `defensive` .
+     * - `routing.http.drop_invalid_header_fields.enabled` - Indicates whether HTTP headers with invalid header fields are removed by the load balancer ( `true` ) or routed to targets ( `false` ). The default is `false` .
+     * - `routing.http.preserve_host_header.enabled` - Indicates whether the Application Load Balancer should preserve the `Host` header in the HTTP request and send it to the target without any change. The possible values are `true` and `false` . The default is `false` .
+     * - `routing.http.x_amzn_tls_version_and_cipher_suite.enabled` - Indicates whether the two headers ( `x-amzn-tls-version` and `x-amzn-tls-cipher-suite` ), which contain information about the negotiated TLS version and cipher suite, are added to the client request before sending it to the target. The `x-amzn-tls-version` header has information about the TLS protocol version negotiated with the client, and the `x-amzn-tls-cipher-suite` header has information about the cipher suite negotiated with the client. Both headers are in OpenSSL format. The possible values for the attribute are `true` and `false` . The default is `false` .
+     * - `routing.http.xff_client_port.enabled` - Indicates whether the `X-Forwarded-For` header should preserve the source port that the client used to connect to the load balancer. The possible values are `true` and `false` . The default is `false` .
+     * - `routing.http.xff_header_processing.mode` - Enables you to modify, preserve, or remove the `X-Forwarded-For` header in the HTTP request before the Application Load Balancer sends the request to the target. The possible values are `append` , `preserve` , and `remove` . The default is `append` .
+     *
+     * - If the value is `append` , the Application Load Balancer adds the client IP address (of the last hop) to the `X-Forwarded-For` header in the HTTP request before it sends it to targets.
+     * - If the value is `preserve` the Application Load Balancer preserves the `X-Forwarded-For` header in the HTTP request, and sends it to targets without any change.
+     * - If the value is `remove` , the Application Load Balancer removes the `X-Forwarded-For` header in the HTTP request before it sends it to targets.
+     * - `routing.http2.enabled` - Indicates whether HTTP/2 is enabled. The possible values are `true` and `false` . The default is `true` . Elastic Load Balancing requires that message header names contain only alphanumeric characters and hyphens.
+     * - `waf.fail_open.enabled` - Indicates whether to allow a WAF-enabled load balancer to route requests to targets if it is unable to forward the request to AWS WAF. The possible values are `true` and `false` . The default is `false` .
+     *
+     * The following attributes are supported by only Network Load Balancers:
+     *
+     * - `dns_record.client_routing_policy` - Indicates how traffic is distributed among the load balancer Availability Zones. The possible values are `availability_zone_affinity` with 100 percent zonal affinity, `partial_availability_zone_affinity` with 85 percent zonal affinity, and `any_availability_zone` with 0 percent zonal affinity.
+     */
+    Key?: string | undefined;
+    /**
+     * The value of the attribute.
+     */
+    Value?: string | undefined;
+};
+/**
+ * The minimum capacity for a load balancer.
+ */
+export type MinimumLoadBalancerCapacity = {
+    /**
+     * The number of capacity units.
+     */
+    CapacityUnits: number;
+};
+/**
+ * Specifies a subnet for a load balancer.
+ */
+export type SubnetMapping = {
+    /**
+     * [Network Load Balancers] The allocation ID of the Elastic IP address for an internet-facing load balancer.
+     */
+    AllocationId?: string | undefined;
+    /**
+     * [Network Load Balancers] The IPv6 address.
+     */
+    IPv6Address?: string | undefined;
+    /**
+     * [Network Load Balancers] The private IPv4 address for an internal load balancer.
+     */
+    PrivateIPv4Address?: string | undefined;
+    /**
+     * [Network Load Balancers with UDP listeners] The IPv6 prefix to use for source NAT. Specify an IPv6 prefix (/80 netmask) from the subnet CIDR block or `auto_assigned` to use an IPv6 prefix selected at random from the subnet CIDR block.
+     */
+    SourceNatIpv6Prefix?: string | undefined;
+    /**
+     * The ID of the subnet.
+     */
+    SubnetId: string;
+};
+//# sourceMappingURL=aws-elasticloadbalancingv2-loadbalancer.d.ts.map

package/out/exports/resources.generated/aws-elasticloadbalancingv2-targetgroup.d.ts

@@ -0,0 +1,220 @@
+import type { ResourceDefinitionWithAttributes, Tag } from "../main.ts";
+export type ElasticLoadBalancingV2TargetGroup = ResourceDefinitionWithAttributes<"AWS::ElasticLoadBalancingV2::TargetGroup", ElasticLoadBalancingV2TargetGroupProps, ElasticLoadBalancingV2TargetGroupAttribs>;
+/**
+ * Specifies a target group for an Application Load Balancer, a Network Load Balancer, or a Gateway Load Balancer.
+ *
+ * Before you register a Lambda function as a target, you must create a `AWS::Lambda::Permission` resource that grants the Elastic Load Balancing service principal permission to invoke the Lambda function.
+ */
+export type ElasticLoadBalancingV2TargetGroupProps = {
+    /**
+     * Indicates whether health checks are enabled. If the target type is `lambda` , health checks are disabled by default but can be enabled. If the target type is `instance` , `ip` , or `alb` , health checks are always enabled and can't be disabled.
+     */
+    HealthCheckEnabled?: boolean | undefined;
+    /**
+     * The approximate amount of time, in seconds, between health checks of an individual target. The range is 5-300. If the target group protocol is TCP, TLS, UDP, TCP_UDP, HTTP or HTTPS, the default is 30 seconds. If the target group protocol is GENEVE, the default is 10 seconds. If the target type is `lambda` , the default is 35 seconds.
+     */
+    HealthCheckIntervalSeconds?: number | undefined;
+    /**
+     * [HTTP/HTTPS health checks] The destination for health checks on the targets.
+     *
+     * [HTTP1 or HTTP2 protocol version] The ping path. The default is /.
+     *
+     * [GRPC protocol version] The path of a custom health check method with the format /package.service/method. The default is / AWS .ALB/healthcheck.
+     */
+    HealthCheckPath?: string | undefined;
+    /**
+     * The port the load balancer uses when performing health checks on targets. If the protocol is HTTP, HTTPS, TCP, TLS, UDP, or TCP_UDP, the default is `traffic-port` , which is the port on which each target receives traffic from the load balancer. If the protocol is GENEVE, the default is port 80.
+     */
+    HealthCheckPort?: string | undefined;
+    /**
+     * The protocol the load balancer uses when performing health checks on targets. For Application Load Balancers, the default is HTTP. For Network Load Balancers and Gateway Load Balancers, the default is TCP. The TCP protocol is not supported for health checks if the protocol of the target group is HTTP or HTTPS. The GENEVE, TLS, UDP, and TCP_UDP protocols are not supported for health checks.
+     */
+    HealthCheckProtocol?: string | undefined;
+    /**
+     * The amount of time, in seconds, during which no response from a target means a failed health check. The range is 2–120 seconds. For target groups with a protocol of HTTP, the default is 6 seconds. For target groups with a protocol of TCP, TLS or HTTPS, the default is 10 seconds. For target groups with a protocol of GENEVE, the default is 5 seconds. If the target type is `lambda` , the default is 30 seconds.
+     */
+    HealthCheckTimeoutSeconds?: number | undefined;
+    /**
+     * The number of consecutive health check successes required before considering a target healthy. The range is 2-10. If the target group protocol is TCP, TCP_UDP, UDP, TLS, HTTP or HTTPS, the default is 5. For target groups with a protocol of GENEVE, the default is 5. If the target type is `lambda` , the default is 5.
+     */
+    HealthyThresholdCount?: number | undefined;
+    /**
+     * The IP address type. The default value is `ipv4` .
+     */
+    IpAddressType?: string | undefined;
+    /**
+     * [HTTP/HTTPS health checks] The HTTP or gRPC codes to use when checking for a successful response from a target. For target groups with a protocol of TCP, TCP_UDP, UDP or TLS the range is 200-599. For target groups with a protocol of HTTP or HTTPS, the range is 200-499. For target groups with a protocol of GENEVE, the range is 200-399.
+     */
+    Matcher?: Matcher | undefined;
+    /**
+     * The name of the target group.
+     *
+     * This name must be unique per region per account, can have a maximum of 32 characters, must contain only alphanumeric characters or hyphens, and must not begin or end with a hyphen.
+     */
+    Name?: string | undefined;
+    /**
+     * The port on which the targets receive traffic. This port is used unless you specify a port override when registering the target. If the target is a Lambda function, this parameter does not apply. If the protocol is GENEVE, the supported port is 6081.
+     */
+    Port?: number | undefined;
+    /**
+     * The protocol to use for routing traffic to the targets. For Application Load Balancers, the supported protocols are HTTP and HTTPS. For Network Load Balancers, the supported protocols are TCP, TLS, UDP, or TCP_UDP. For Gateway Load Balancers, the supported protocol is GENEVE. A TCP_UDP listener must be associated with a TCP_UDP target group. If the target is a Lambda function, this parameter does not apply.
+     */
+    Protocol?: string | undefined;
+    /**
+     * [HTTP/HTTPS protocol] The protocol version. The possible values are `GRPC` , `HTTP1` , and `HTTP2` .
+     */
+    ProtocolVersion?: string | undefined;
+    /**
+     * The tags.
+     */
+    Tags?: Tag[] | undefined;
+    /**
+     * The target group attributes.
+     */
+    TargetGroupAttributes?: TargetGroupAttribute[] | undefined;
+    /**
+     * The type of target that you must specify when registering targets with this target group. You can't specify targets for a target group using more than one target type.
+     *
+     * - `instance` - Register targets by instance ID. This is the default value.
+     * - `ip` - Register targets by IP address. You can specify IP addresses from the subnets of the virtual private cloud (VPC) for the target group, the RFC 1918 range (10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16), and the RFC 6598 range (100.64.0.0/10). You can't specify publicly routable IP addresses.
+     * - `lambda` - Register a single Lambda function as a target.
+     * - `alb` - Register a single Application Load Balancer as a target.
+     */
+    TargetType?: string | undefined;
+    /**
+     * The targets.
+     */
+    Targets?: TargetDescription[] | undefined;
+    /**
+     * The number of consecutive health check failures required before considering a target unhealthy. The range is 2-10. If the target group protocol is TCP, TCP_UDP, UDP, TLS, HTTP or HTTPS, the default is 2. For target groups with a protocol of GENEVE, the default is 2. If the target type is `lambda` , the default is 5.
+     */
+    UnhealthyThresholdCount?: number | undefined;
+    /**
+     * The identifier of the virtual private cloud (VPC). If the target is a Lambda function, this parameter does not apply. Otherwise, this parameter is required.
+     */
+    VpcId?: string | undefined;
+};
+export type ElasticLoadBalancingV2TargetGroupAttribs = {
+    /**
+     * The Amazon Resource Name (ARN) of the load balancer that routes traffic to this target group.
+     */
+    LoadBalancerArns: string[];
+    /**
+     * The Amazon Resource Name (ARN) of the target group.
+     */
+    TargetGroupArn: string;
+    /**
+     * The full name of the target group. For example, `targetgroup/my-target-group/cbf133c568e0d028` .
+     */
+    TargetGroupFullName: string;
+    /**
+     * The name of the target group. For example, `my-target-group` .
+     */
+    TargetGroupName: string;
+};
+/**
+ * Specifies the HTTP codes that healthy targets must use when responding to an HTTP health check.
+ */
+export type Matcher = {
+    /**
+     * You can specify values between 0 and 99. You can specify multiple values (for example, "0,1") or a range of values (for example, "0-5"). The default value is 12.
+     */
+    GrpcCode?: string | undefined;
+    /**
+     * For Application Load Balancers, you can specify values between 200 and 499, with the default value being 200. You can specify multiple values (for example, "200,202") or a range of values (for example, "200-299").
+     *
+     * For Network Load Balancers, you can specify values between 200 and 599, with the default value being 200-399. You can specify multiple values (for example, "200,202") or a range of values (for example, "200-299").
+     *
+     * For Gateway Load Balancers, this must be "200–399".
+     *
+     * Note that when using shorthand syntax, some values such as commas need to be escaped.
+     */
+    HttpCode?: string | undefined;
+};
+/**
+ * Specifies a target to add to a target group.
+ */
+export type TargetDescription = {
+    /**
+     * An Availability Zone or `all` . This determines whether the target receives traffic from the load balancer nodes in the specified Availability Zone or from all enabled Availability Zones for the load balancer.
+     *
+     * For Application Load Balancer target groups, the specified Availability Zone value is only applicable when cross-zone load balancing is off. Otherwise the parameter is ignored and treated as `all` .
+     *
+     * This parameter is not supported if the target type of the target group is `instance` or `alb` .
+     *
+     * If the target type is `ip` and the IP address is in a subnet of the VPC for the target group, the Availability Zone is automatically detected and this parameter is optional. If the IP address is outside the VPC, this parameter is required.
+     *
+     * For Application Load Balancer target groups with cross-zone load balancing off, if the target type is `ip` and the IP address is outside of the VPC for the target group, this should be an Availability Zone inside the VPC for the target group.
+     *
+     * If the target type is `lambda` , this parameter is optional and the only supported value is `all` .
+     */
+    AvailabilityZone?: string | undefined;
+    /**
+     * The ID of the target. If the target type of the target group is `instance` , specify an instance ID. If the target type is `ip` , specify an IP address. If the target type is `lambda` , specify the ARN of the Lambda function. If the target type is `alb` , specify the ARN of the Application Load Balancer target.
+     */
+    Id: string;
+    /**
+     * The port on which the target is listening. If the target group protocol is GENEVE, the supported port is 6081. If the target type is `alb` , the targeted Application Load Balancer must have at least one listener whose port matches the target group port. This parameter is not used if the target is a Lambda function.
+     */
+    Port?: number | undefined;
+};
+/**
+ * Specifies a target group attribute.
+ */
+export type TargetGroupAttribute = {
+    /**
+     * The name of the attribute.
+     *
+     * The following attributes are supported by all load balancers:
+     *
+     * - `deregistration_delay.timeout_seconds` - The amount of time, in seconds, for Elastic Load Balancing to wait before changing the state of a deregistering target from `draining` to `unused` . The range is 0-3600 seconds. The default value is 300 seconds. If the target is a Lambda function, this attribute is not supported.
+     * - `stickiness.enabled` - Indicates whether target stickiness is enabled. The value is `true` or `false` . The default is `false` .
+     * - `stickiness.type` - Indicates the type of stickiness. The possible values are:
+     *
+     * - `lb_cookie` and `app_cookie` for Application Load Balancers.
+     * - `source_ip` for Network Load Balancers.
+     * - `source_ip_dest_ip` and `source_ip_dest_ip_proto` for Gateway Load Balancers.
+     *
+     * The following attributes are supported by Application Load Balancers and Network Load Balancers:
+     *
+     * - `load_balancing.cross_zone.enabled` - Indicates whether cross zone load balancing is enabled. The value is `true` , `false` or `use_load_balancer_configuration` . The default is `use_load_balancer_configuration` .
+     * - `target_group_health.dns_failover.minimum_healthy_targets.count` - The minimum number of targets that must be healthy. If the number of healthy targets is below this value, mark the zone as unhealthy in DNS, so that traffic is routed only to healthy zones. The possible values are `off` or an integer from 1 to the maximum number of targets. The default is `off` .
+     * - `target_group_health.dns_failover.minimum_healthy_targets.percentage` - The minimum percentage of targets that must be healthy. If the percentage of healthy targets is below this value, mark the zone as unhealthy in DNS, so that traffic is routed only to healthy zones. The possible values are `off` or an integer from 1 to 100. The default is `off` .
+     * - `target_group_health.unhealthy_state_routing.minimum_healthy_targets.count` - The minimum number of targets that must be healthy. If the number of healthy targets is below this value, send traffic to all targets, including unhealthy targets. The possible values are 1 to the maximum number of targets. The default is 1.
+     * - `target_group_health.unhealthy_state_routing.minimum_healthy_targets.percentage` - The minimum percentage of targets that must be healthy. If the percentage of healthy targets is below this value, send traffic to all targets, including unhealthy targets. The possible values are `off` or an integer from 1 to 100. The default is `off` .
+     *
+     * The following attributes are supported only if the load balancer is an Application Load Balancer and the target is an instance or an IP address:
+     *
+     * - `load_balancing.algorithm.type` - The load balancing algorithm determines how the load balancer selects targets when routing requests. The value is `round_robin` , `least_outstanding_requests` , or `weighted_random` . The default is `round_robin` .
+     * - `load_balancing.algorithm.anomaly_mitigation` - Only available when `load_balancing.algorithm.type` is `weighted_random` . Indicates whether anomaly mitigation is enabled. The value is `on` or `off` . The default is `off` .
+     * - `slow_start.duration_seconds` - The time period, in seconds, during which a newly registered target receives an increasing share of the traffic to the target group. After this time period ends, the target receives its full share of traffic. The range is 30-900 seconds (15 minutes). The default is 0 seconds (disabled).
+     * - `stickiness.app_cookie.cookie_name` - Indicates the name of the application-based cookie. Names that start with the following prefixes are not allowed: `AWSALB` , `AWSALBAPP` , and `AWSALBTG` ; they're reserved for use by the load balancer.
+     * - `stickiness.app_cookie.duration_seconds` - The time period, in seconds, during which requests from a client should be routed to the same target. After this time period expires, the application-based cookie is considered stale. The range is 1 second to 1 week (604800 seconds). The default value is 1 day (86400 seconds).
+     * - `stickiness.lb_cookie.duration_seconds` - The time period, in seconds, during which requests from a client should be routed to the same target. After this time period expires, the load balancer-generated cookie is considered stale. The range is 1 second to 1 week (604800 seconds). The default value is 1 day (86400 seconds).
+     *
+     * The following attribute is supported only if the load balancer is an Application Load Balancer and the target is a Lambda function:
+     *
+     * - `lambda.multi_value_headers.enabled` - Indicates whether the request and response headers that are exchanged between the load balancer and the Lambda function include arrays of values or strings. The value is `true` or `false` . The default is `false` . If the value is `false` and the request contains a duplicate header field name or query parameter key, the load balancer uses the last value sent by the client.
+     *
+     * The following attributes are supported only by Network Load Balancers:
+     *
+     * - `deregistration_delay.connection_termination.enabled` - Indicates whether the load balancer terminates connections at the end of the deregistration timeout. The value is `true` or `false` . For new UDP/TCP_UDP target groups the default is `true` . Otherwise, the default is `false` .
+     * - `preserve_client_ip.enabled` - Indicates whether client IP preservation is enabled. The value is `true` or `false` . The default is disabled if the target group type is IP address and the target group protocol is TCP or TLS. Otherwise, the default is enabled. Client IP preservation can't be disabled for UDP and TCP_UDP target groups.
+     * - `proxy_protocol_v2.enabled` - Indicates whether Proxy Protocol version 2 is enabled. The value is `true` or `false` . The default is `false` .
+     * - `target_health_state.unhealthy.connection_termination.enabled` - Indicates whether the load balancer terminates connections to unhealthy targets. The value is `true` or `false` . The default is `true` . This attribute can't be enabled for UDP and TCP_UDP target groups.
+     * - `target_health_state.unhealthy.draining_interval_seconds` - The amount of time for Elastic Load Balancing to wait before changing the state of an unhealthy target from `unhealthy.draining` to `unhealthy` . The range is 0-360000 seconds. The default value is 0 seconds.
+     *
+     * Note: This attribute can only be configured when `target_health_state.unhealthy.connection_termination.enabled` is `false` .
+     *
+     * The following attributes are supported only by Gateway Load Balancers:
+     *
+     * - `target_failover.on_deregistration` - Indicates how the Gateway Load Balancer handles existing flows when a target is deregistered. The possible values are `rebalance` and `no_rebalance` . The default is `no_rebalance` . The two attributes ( `target_failover.on_deregistration` and `target_failover.on_unhealthy` ) can't be set independently. The value you set for both attributes must be the same.
+     * - `target_failover.on_unhealthy` - Indicates how the Gateway Load Balancer handles existing flows when a target is unhealthy. The possible values are `rebalance` and `no_rebalance` . The default is `no_rebalance` . The two attributes ( `target_failover.on_deregistration` and `target_failover.on_unhealthy` ) can't be set independently. The value you set for both attributes must be the same.
+     */
+    Key?: string | undefined;
+    /**
+     * The value of the attribute.
+     */
+    Value?: string | undefined;
+};
+//# sourceMappingURL=aws-elasticloadbalancingv2-targetgroup.d.ts.map

package/out/exports/resources.generated/aws-elasticloadbalancingv2-truststore.d.ts

@@ -0,0 +1,42 @@
+import type { ResourceDefinitionWithAttributes, Tag } from "../main.ts";
+export type ElasticLoadBalancingV2TrustStore = ResourceDefinitionWithAttributes<"AWS::ElasticLoadBalancingV2::TrustStore", ElasticLoadBalancingV2TrustStoreProps, ElasticLoadBalancingV2TrustStoreAttribs>;
+/**
+ * Creates a trust store. You must specify `CaCertificatesBundleS3Bucket` and `CaCertificatesBundleS3Key` .
+ */
+export type ElasticLoadBalancingV2TrustStoreProps = {
+    /**
+     * The Amazon S3 bucket for the ca certificates bundle.
+     */
+    CaCertificatesBundleS3Bucket?: string | undefined;
+    /**
+     * The Amazon S3 path for the ca certificates bundle.
+     */
+    CaCertificatesBundleS3Key?: string | undefined;
+    /**
+     * The Amazon S3 object version for the ca certificates bundle. If undefined the current version is used.
+     */
+    CaCertificatesBundleS3ObjectVersion?: string | undefined;
+    /**
+     * The name of the trust store.
+     */
+    Name?: string | undefined;
+    /**
+     * The tags to assign to the trust store.
+     */
+    Tags?: Tag[] | undefined;
+};
+export type ElasticLoadBalancingV2TrustStoreAttribs = {
+    /**
+     * The number of ca certificates in the trust store.
+     */
+    NumberOfCaCertificates: number;
+    /**
+     * The current status of the trust store.
+     */
+    Status: string;
+    /**
+     * The Amazon Resource Name (ARN) of the trust store.
+     */
+    TrustStoreArn: string;
+};
+//# sourceMappingURL=aws-elasticloadbalancingv2-truststore.d.ts.map

package/out/exports/resources.generated/aws-elasticloadbalancingv2-truststorerevocation.d.ts

@@ -0,0 +1,44 @@
+import type { ResourceDefinitionWithAttributes } from "../main.ts";
+export type ElasticLoadBalancingV2TrustStoreRevocation = ResourceDefinitionWithAttributes<"AWS::ElasticLoadBalancingV2::TrustStoreRevocation", ElasticLoadBalancingV2TrustStoreRevocationProps, ElasticLoadBalancingV2TrustStoreRevocationAttribs>;
+/**
+ * Adds the specified revocation contents to the specified trust store. You must specify `TrustStoreArn` .
+ */
+export type ElasticLoadBalancingV2TrustStoreRevocationProps = {
+    /**
+     * The revocation file to add.
+     */
+    RevocationContents?: RevocationContent[] | undefined;
+    /**
+     * The Amazon Resource Name (ARN) of the trust store.
+     */
+    TrustStoreArn?: string | undefined;
+};
+export type ElasticLoadBalancingV2TrustStoreRevocationAttribs = {
+    /**
+     * The revocation ID of the revocation file.
+     * @format int64
+     */
+    RevocationId: number;
+};
+/**
+ * Information about a revocation file. You must specify `S3Bucket` and `S3Key` .
+ */
+export type RevocationContent = {
+    /**
+     * The type of revocation file.
+     */
+    RevocationType?: string | undefined;
+    /**
+     * The Amazon S3 bucket for the revocation file.
+     */
+    S3Bucket?: string | undefined;
+    /**
+     * The Amazon S3 path for the revocation file.
+     */
+    S3Key?: string | undefined;
+    /**
+     * The Amazon S3 object version of the revocation file.
+     */
+    S3ObjectVersion?: string | undefined;
+};
+//# sourceMappingURL=aws-elasticloadbalancingv2-truststorerevocation.d.ts.map