Summary
Request to add a new subdomain api.upstream-dso.tacc.utexas.edu to provide dedicated API access for the upstream-dso application.
Background
Currently, the API is accessible through the main domain upstream-dso.tacc.utexas.edu. To improve organization and potentially enable different configurations for API vs web traffic, we need to add a dedicated API subdomain.
Requirements
DNS Configuration
SSL Certificate
Infrastructure Updates
Technical Details
Current Configuration:
- Main domain:
upstream-dso.tacc.utexas.edu
- API accessible at:
upstream-dso.tacc.utexas.edu/docs (FastAPI docs)
Desired Configuration:
- Main domain:
upstream-dso.tacc.utexas.edu (unchanged)
- API domain:
api.upstream-dso.tacc.utexas.edu
- API docs:
api.upstream-dso.tacc.utexas.edu/docs
Docker Compose Changes Needed:
labels:
- traefik.enable=true
- traefik.http.routers.app-api.rule=Host(`api.upstream-dso.tacc.utexas.edu`)
- traefik.http.routers.app-api.tls=true
- traefik.http.services.app-api.loadbalancer.server.port=8000
Challenges Encountered
CAA Record Issue
When attempting to generate SSL certificates with Let's Encrypt, encountered CAA policy restriction:
CAA record for tacc.utexas.edu prevents issuance
Resolution needed:
- Contact TACC IT to either:
- Add Let's Encrypt to CAA record for
tacc.utexas.edu
- Provide alternative certificate solution
- Create CAA exception for
upstream-dso.tacc.utexas.edu subdomains
Acceptance Criteria
Priority
Medium - Improves API organization but doesn't block current functionality
Additional Context
- Server:
upstream-dso
- Current IP: [INSERT_SERVER_IP]
- Traefik version: 2.11
- Let's Encrypt integration: Existing setup using
/etc/letsencrypt mount
Next Steps
- IT Request: Submit request to TACC IT for DNS and certificate authority approval
- DNS Update: Add A record for API subdomain
- Certificate: Generate/expand SSL certificate
- Deploy: Update Traefik configuration
- Test: Verify both domains work correctly
Summary
Request to add a new subdomain
api.upstream-dso.tacc.utexas.eduto provide dedicated API access for the upstream-dso application.Background
Currently, the API is accessible through the main domain
upstream-dso.tacc.utexas.edu. To improve organization and potentially enable different configurations for API vs web traffic, we need to add a dedicated API subdomain.Requirements
DNS Configuration
api.upstream-dso.tacc.utexas.edupointing to the same IP asupstream-dso.tacc.utexas.eduSSL Certificate
api.upstream-dso.tacc.utexas.edutacc.utexas.edudomainInfrastructure Updates
api.upstream-dso.tacc.utexas.eduto the API containerTechnical Details
Current Configuration:
upstream-dso.tacc.utexas.eduupstream-dso.tacc.utexas.edu/docs(FastAPI docs)Desired Configuration:
upstream-dso.tacc.utexas.edu(unchanged)api.upstream-dso.tacc.utexas.eduapi.upstream-dso.tacc.utexas.edu/docsDocker Compose Changes Needed:
Challenges Encountered
CAA Record Issue
When attempting to generate SSL certificates with Let's Encrypt, encountered CAA policy restriction:
Resolution needed:
tacc.utexas.eduupstream-dso.tacc.utexas.edusubdomainsAcceptance Criteria
api.upstream-dso.tacc.utexas.eduresolves to correct IP addressapi.upstream-dso.tacc.utexas.edu/docsupstream-dso.tacc.utexas.educontinues to workPriority
Medium - Improves API organization but doesn't block current functionality
Additional Context
upstream-dso/etc/letsencryptmountNext Steps