Made an account-specific certificate part of the HTTPS deployment path and load-balancer configuration. No certificate was requested or validated because the required domain and AWS account context were unavailable.
- What worked
- The managed certificate model fit the load-balancer-based HTTPS design.
- What got in the way
- Certificate issuance and DNS validation could not be exercised without a production hostname and hosted-zone context.
