Step-by-Step Setup: deSEC.io + AWS (S3 + Route 53 + CloudFront + ACM)

step-by-step guide using deSEC.io as a free domain provider, to secure and serve a static S3 website via HTTPS using Route 53, CloudFront, and ACM

⸻

✅ Step-by-Step Setup: deSEC.io + AWS (S3 + Route 53 + CloudFront + ACM)

⸻

🧩 Step 1: Register Free Domain on deSEC.io

1. Visit https://desec.io

2. Sign up and verify your email.

3. Go to “Domains”, and request a new free domain like:

yourname.dedyn.io

⸻

🧩 Step 2: Set Up S3 Static Website

1. Go to Amazon S3.

2. Create a new bucket (e.g., raj-static-site).

3. Enable static website hosting:

• Index document: index.html

4. Upload your website files (e.g., index.html, style.css, etc.)

5. Set permissions:

• Make the files public (or configure CloudFront OAI for private access).

⸻

🧩 Step 3: Configure Route 53

1. Go to Route 53 > Hosted Zones.

2. Create a new public hosted zone for:

yourname.dedyn.io

3. Copy the NS records (Name servers).

⸻

🧩 Step 4: Point deSEC to Route 53

1. In deSEC DNS dashboard, go to your domain settings.

2. Replace deSEC’s default name servers with AWS Route 53 NS values (from step 3).

⸻

🧩 Step 5: Request SSL Certificate in ACM

1. Go to AWS Certificate Manager (ACM).

2. Request a public certificate for:

yourname.dedyn.io

3. Choose DNS validation.

4. ACM will give CNAME records.

5. Go back to Route 53 and add these CNAME records in your hosted zone.

⸻

🧩 Step 6: Create CloudFront Distribution

1. Go to CloudFront.

2. Create new distribution:

• Origin domain: Your S3 website endpoint (not the bucket name)

• Set Viewer Protocol Policy to: Redirect HTTP to HTTPS

• Alternate domain name (CNAME): yourname.dedyn.io

• Select the SSL certificate from ACM.

3. Deploy the distribution and wait until it’s active.

⸻

🧩 Step 7: Add Route 53 Alias Record

1. In your Route 53 hosted zone:

• Add a new record:

• Type: A (Alias)

• Alias target: Your CloudFront distribution domain

⸻

✅ Final Testing:

• Go to:

https://yourname.dedyn.io

• It should:

• Load your static S3 website

• Be served over HTTPS

• Use your custom deSEC domain

⸻