Closed
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Preview Environment DestroyedThe preview environment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add self-contained TLS/DNS system using Let's Encrypt wildcard certs and Route53. Each regional deployment manages its own TLS without external proxy dependencies — SDK clients connect directly to workers over HTTPS.
Architecture
*.{domain}wildcard cert via ACME DNS-01 challenge + Route53, uploads cert/key to S3, renews every 12hw-{id}.{domain}A records in Route53 on boot, delete on shutdownhttps://w-xxx.domainas connectURL — SDK connects direct to workerHA hardening
ObtainOrRenew()before autoscaler starts — cert is in S3 before any worker launchestls: ok|expiring_soon|expired|no_certwith expiry time, returns 503 when degradedConfiguration required
OPENSANDBOX_ROUTE53_HOSTED_ZONE_ID,OPENSANDBOX_ACME_EMAILroute53:ChangeResourceRecordSets,route53:ListResourceRecordSets,route53:GetChangefor server;route53:ChangeResourceRecordSets+s3:GetObjectfor workersNew packages
internal/certmanager/— server-side ACME manager + worker-side S3 cert fetcherinternal/dns/— Route53 client (A records, TXT records, listing)internal/controlplane/dns_cleaner.go— stale DNS record cleanupModified
internal/config/— new env vars:ROUTE53_HOSTED_ZONE_ID,ACME_EMAIL,CERT_S3_BUCKET,CERT_S3_PREFIXinternal/compute/ec2.go— passes Route53 config in EC2 user data for worker DNS registrationinternal/controlplane/redis_registry.go—InternalHTTPAddr()for VPC-internal routinginternal/proxy/controlplane_proxy.go— uses VPC-internal HTTP for control-plane→worker trafficinternal/worker/http_server.go— removed/caddy/check, addedStartTLSWithCert(), cert health reportingcmd/server/main.go— cert manager init, DNS cleanercmd/worker/main.go— cert fetcher, HTTPS on :443deploy/ec2/setup-instance.sh— removed Caddy, added Route53 DNS registration/cleanup/verification