Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS] x-elb2 Target's access path #777

Open
siasin opened this issue Sep 2, 2024 · 0 comments
Open

[DOCS] x-elb2 Target's access path #777

siasin opened this issue Sep 2, 2024 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@siasin
Copy link

siasin commented Sep 2, 2024

According to the x-elbv2 doc, we were able to create a listener rule with an unique access path in our loadbalancer.

x-elbv2:
  public-alb:
    Lookup:
      loadbalancer:
        Tags:
          Name: my-test-alb
    MacroParameters:
      Ingress:
        ExtSources:
          - IPv4: "0.0.0.0/0"
            Description: ANY
    Properties:
      Scheme: internet-facing
      Type: application
    Listeners:
      - Port: 443
        Protocol: HTTPS
        Certificates:
         - CertificateArn: arn:aws:acm:eu-west-3:yyyy:certificate/xxxxxx
...
        Targets:
          - name: family:my-service
            access: /abc

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:
image

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.

        Targets:
          - name: family:my-service
            access: /abc
          - name: family:my-service
            access: /abc/*

I couldn't find much explanation to define an access path with OR condition in the doc. Is this possible?

@siasin siasin added the documentation Improvements or additions to documentation label Sep 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants