We need to add an alternative path for the access path (e.g. or /abc/*). Right now, we can do the following in AWS console:
However, we don't want to edit the rule condition via console but to create this rule directly with x-elb2 definition when the stack is being deployed.
I found the following which might do the work. However, this will create 2 rules instead of one.
According to the x-elbv2 doc, we were able to create a listener rule with an unique access path in our loadbalancer.
We need to add an alternative path for the access path (e.g. or /abc/*). Right now, we can do the following in AWS console:
However, we don't want to edit the rule condition via console but to create this rule directly with x-elb2 definition when the stack is being deployed.
I found the following which might do the work. However, this will create 2 rules instead of one.
I couldn't find much explanation to define an access path with OR condition in the doc. Is this possible?