Optional
alpnName of the Application-Layer Protocol Negotiation (ALPN) policy. Can be set if protocol
is TLS
. Valid values are HTTP1Only
, HTTP2Only
, HTTP2Optional
, HTTP2Preferred
, and None
.
Optional
certificateARN of the default SSL server certificate. Exactly one certificate is required if the protocol is HTTPS. For adding additional SSL certificates, see the aws.lb.ListenerCertificate
resource.
Optional
defaultConfiguration block for default actions. Detailed below.
Optional
portPort on which the load balancer is listening. Not valid for Gateway Load Balancers.
Optional
protocolProtocol for connections from clients to the load balancer. For Application Load Balancers, valid values are HTTP
and HTTPS
, with a default of HTTP
. For Network Load Balancers, valid values are TCP
, TLS
, UDP
, and TCP_UDP
. Not valid to use UDP
or TCP_UDP
if dual-stack mode is enabled. Not valid for Gateway Load Balancers.
Optional
sslName of the SSL Policy for the listener. Required if protocol
is HTTPS
or TLS
.
Optional
tagsA map of tags to assign to the resource. .If configured with a provider default_tags
configuration block present, tags with matching keys will overwrite those defined at the provider-level.
NOTE:: Please note that listeners that are attached to Application Load Balancers must use either
HTTP
orHTTPS
protocols while listeners that are attached to Network Load Balancers must use theTCP
protocol.
Generated using TypeDoc
Provides a Load Balancer Listener resource.
{{% examples %}}
Example Usage
{{% example %}}
Forward Action
To a NLB:
{{% /example %}} {{% example %}}
Redirect Action
{{% /example %}} {{% example %}}
Fixed-response Action
{{% /example %}} {{% example %}}
Authenticate-cognito Action
{{% /example %}} {{% example %}}
Authenticate-OIDC Action
{{% /example %}} {{% example %}}
Gateway Load Balancer Listener
{{% /example %}} {{% /examples %}}
Import
Using
pulumi import
, import listeners using their ARN. For example: