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

Feature request: Deploy NLB in front of Helix Core for TLS termination #408

Closed
henrykie opened this issue Dec 9, 2024 · 0 comments · Fixed by #410
Closed

Feature request: Deploy NLB in front of Helix Core for TLS termination #408

henrykie opened this issue Dec 9, 2024 · 0 comments · Fixed by #410
Assignees
Labels
feature-request feature request

Comments

@henrykie
Copy link
Contributor

henrykie commented Dec 9, 2024

Use case

Support TLS termination at the NLB with trusted certificate. This will allow p4 clients to connect without p4 trust.

Solution/User Experience

Deploy the module with an NLB attached:

module "helix_core" {
  source = "cloud-game-development-toolkit/modules/perforce/helix-core"
  ...
  deploy_network_load_balancer = true
  certificate_arn = aws_acm_certificate.helix_core.arn

Alternative solutions

Currently Helix Core creates self-signed SSL certificates (that must be trusted by the client). This is fine for most use cases, but automated deployments that rely on a p4 client fail without a trust.

@henrykie henrykie added feature-request feature request triage to be triaged by project maintainers labels Dec 9, 2024
@henrykie henrykie self-assigned this Dec 9, 2024
@gabebatista gabebatista removed the triage to be triaged by project maintainers label Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request feature request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants