cloudflare-named-tunnel-route53

What problem does it solve?

This skill solves the problem of accessing web services running on AWS instances behind NAT gateways, with shared public IPs, or with blocked inbound ports 80/443, where standard nginx + Let's Encrypt TLS setups are not feasible.

Core Features & Use Cases

• Supports both temporary Cloudflare Quick Tunnels for ad-hoc testing and permanent Named Tunnels for stable long-term HTTPS endpoints.
• Automates Route53 CNAME record creation to map custom subdomains to tunnel endpoints without manual DNS configuration.
• Includes troubleshooting guidance for common AWS networking issues including port blocking, Docker port conflicts, and certbot credential path errors when using Route53 DNS validation.
• Use Case: A development team testing a chatbot service on an AWS EC2 instance behind a NAT gateway can use this skill to set up a persistent HTTPS subdomain in minutes without modifying public firewall rules or managing TLS certificates manually.

Quick Start

Use this skill to configure a stable HTTPS subdomain for your local service running on an AWS instance behind NAT by setting up a Cloudflare Named Tunnel and updating your Route53 DNS records.