You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provide steps to replicate. This should include: exact ebcli commands, any relevant configuration files(sanitized), platform version, region, as well as any additional information you think is relevant.
However, after env was created, there two places indicated that aws:elbv2:listener:listener_port wasn't honored.
In ALB Listener rules
Go to AWS console, in ALB, select the <alb_arn> and listener 443, EB created a new rule which HTTP Host Header was not <my_website_domain>, instead, it was the EB env domain (I presume this is the default rule, instead of the "test" rule)
In EB env configuration
Go to AWS console, open configuration of the create EB env, choose "edit" in "Instance traffic and scaling", go to "Rules" section (bottom of the page), there were two entries, the first one: name = default, listener port = 443, priority = 2, host header = <eb_env_domain>, path patterns = /*, which I presume was the defult rule. The second one was the problematic one, it had name = test, listener port is null (blank as shown in the table), priority = 1, host headers = <my_website_domain>, <eb_env_domain>, path patterns = /*. In my understanding, the listener port should be 443 for the second one but it wasn't.
See two screenshots below for settings in ALB after updated by EB CLI, and settings in EB after updated by EB CLI.
Expected result
I want to use the config in .ebextensions to create rule in shared ALB which allows the host header of my domain.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
OS: mac os 12.6
EBCLI version: EB CLI 3.20.8 (Python 3.8.16 (default, Dec 16 2022, 20:05:32)
AWS Region: us-west-2
The text was updated successfully, but these errors were encountered:
Description
When using shared ALB, rules option under "aws:elbv2:listener:listener_port" are not honored, which should be supported as indicated by doc.
Steps to reproduce
Provide steps to replicate. This should include: exact
ebcli
commands, any relevant configuration files(sanitized), platform version, region, as well as any additional information you think is relevant.config In .ebextensions:
eb commands:
However, after env was created, there two places indicated that
aws:elbv2:listener:listener_port
wasn't honored.Go to AWS console, in ALB, select the <alb_arn> and listener 443, EB created a new rule which HTTP Host Header was not <my_website_domain>, instead, it was the EB env domain (I presume this is the default rule, instead of the "test" rule)
Go to AWS console, open configuration of the create EB env, choose "edit" in "Instance traffic and scaling", go to "Rules" section (bottom of the page), there were two entries, the first one: name = default, listener port = 443, priority = 2, host header = <eb_env_domain>, path patterns =
/*
, which I presume was the defult rule. The second one was the problematic one, it had name = test, listener port is null (blank as shown in the table), priority = 1, host headers = <my_website_domain>, <eb_env_domain>, path patterns =/*
. In my understanding, the listener port should be 443 for the second one but it wasn't.See two screenshots below for settings in ALB after updated by EB CLI, and settings in EB after updated by EB CLI.

Expected result
I want to use the config in .ebextensions to create rule in shared ALB which allows the host header of my domain.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
OS: mac os 12.6
EBCLI version: EB CLI 3.20.8 (Python 3.8.16 (default, Dec 16 2022, 20:05:32)
AWS Region: us-west-2
The text was updated successfully, but these errors were encountered: