Adam-D-Lewis
commented
3 weeks ago Sorry for the long delay in getting a response. Extending automatic DNS provision to include Route 53 would be useful and I'd support a PR adding that if it's something you're interested in working on.
You mentioned adding a new stage for AWS deployments. We don't do that for any existing stages so there are likely some issues to think through doing that. Preferably, we would add the additional steps in an existing stage and make the new features optional through the nebari config.
ronald50928
Feature description
When deploying Nebari using AWS, the step that it is looking to find the IP and getting the DNS resolution, what are the opportunities to make this change part of the automation, where the ACM certificate gets passed in the configuration as long as it was created before deployment?
Is there a way to automate this in Terraform or a feature in the works? That a stage/ module will look for the ACM add it to the CLB and make the R53 record changes required to send traffic to the CLB created during deployment.
https://www.nebari.dev/docs/how-tos/domain-registry#setting-up-a-dns https://www.nebari.dev/docs/how-tos/domain-registry#using-other-dns-providers https://www.nebari.dev/docs/how-tos/nebari-aws#deploying-nebari https://www.nebari.dev/docs/how-tos/nebari-aws#deploying-nebari:~:text=During%20deployment%2C%20Nebari%20will%20require%20you%20to%20set%20a%20DNS%20record%20for%20the%20domain%20defined%20during%20initialize.%20Follow%20the%20instructions%20on%20How%20to%20set%20a%20DNS%20record%20for%20Nebari%20for%20an%20overview%20of%20the%20required%20steps.
Value and/or benefit
A cleaner and almost end to end private deployment on AWS. Currently the AWS deployment of Nebari within a private subnet and using ACM requires additional steps. This will cover an additional step in the AWS deployment and potentially adding a session in the "using other dns providers."
Anything else?
To add to formal documentation in Using other DNS providers :
During your AWS Deployment, terraform will output a similar like this:
At this time the user needs to go the AWS Management Console or via AWS CLI and take the record name(previouslly created) or created at the time of deployment and add the load balancer mentioned above into the R53 record. The record that refers this deployment should be related to the "domain:" being defined during the nebari init --guided-init in the step: "domain will be the domain endpoint for your Nebari instance."
Once this step above is completed the user should start seeing the behavior below. Or can re-deploy the deployment and should pickup the DNS rsolution. See below:
in addition, when using ACM within a private environment deployment the user(s) or administrator deploy the product need to go to the CLB created by the deployment and change the listening port 443 from TCP to SSL and add the ACM certificate to that listing port. action that can be automated.