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

Allow support for ACM SSL cert for publicly exposed services. #93

Closed
JohnPreston opened this issue Jun 27, 2020 · 1 comment · Fixed by #94
Closed

Allow support for ACM SSL cert for publicly exposed services. #93

JohnPreston opened this issue Jun 27, 2020 · 1 comment · Fixed by #94
Assignees
Labels
enhancement New feature or request

Comments

@JohnPreston
Copy link
Member

JohnPreston commented Jun 27, 2020

Is your feature request related to a problem? Please describe.

  • When I already have a public DNS Zone, I provide with its ID
  • I indicate what public hostname I would like the family/service to be published on
  • ACM creates a public certificate for it that gets automatically validated by Route53 record.
  • If I already have a public DNS Namespace I pass the namespace ID and the service gets registered there whereas the
    certificate is added to the route53 zone.

ACM properties page

Describe the solution you'd like


x-acm:
  publicApp:
    Properties: {}
    Settings: {}
    Services:
      - name: serviceA
        ports: [443]

services:
  serviceA:
    x-configs:
      network:
        lb_type: application
        is_public: True
@JohnPreston JohnPreston added the enhancement New feature or request label Jun 27, 2020
@JohnPreston JohnPreston self-assigned this Jun 27, 2020
@JohnPreston JohnPreston linked a pull request Jun 28, 2020 that will close this issue
@JohnPreston
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant