Norah Klintberg Sakal

No more default URLs​

Day 9: You built the front-yard house (ALB)

Today: We give it a real address

Here's the situation: Your ALB has a public endpoint:

fargate-alb-1234567890.us-east-1.elb.amazonaws.com

This works, but:
❌ Impossible to remember
❌ Looks unprofessional
❌ Hard to share
❌ Can't use for SSL certificate (Day 11)

What you want:

ai-caller.yourdomain.com

Clean. Professional. Memorable.

Solution: Route 53 + Custom Domain

Your network needs a front-yard house​

Day 8: You tested and validated your network

Today: We build the front door (Application Load Balancer)

Here's the setup:

Trust, but verify​

Days 3-7: You built the entire network infrastructure

Today: We prove it actually works

Here's the situation:

You've built:
✅ VPC with Internet Gateway
✅ Public and private subnets
✅ NAT Gateway
✅ Route Tables
✅ Security Groups

But you haven't actually tested any of it.

What if:

• NAT Gateway isn't running correctly?
• Route tables have the wrong associations?
• Secure Groups are blocking traffic?
• Something is misconfigured?

You'd fund out after deploying your containers (painful debugging)

Solution: Test first, deploy second.

Your network needs smart locks​

Day 6: You built the roads (route tables)

Today: We add the smart locks (Security Groups)

Here's the problem:

But there's NO security layer yet.

Right now:

• Anyone can try to connect to your containers
• No firewall rules
• No access control

That's a security issue.

Solution: Security Groups

Your gates need directions​

Day 5: You built the back gate (NAT Gateway)

Today: We build the roads that connect everything

Here's the problem:

You have:

✅ Neighborhood front gate (Internet Gateway)
✅ Back gate (NAT Gateway)
✅ Front yards (public subnets)
✅ Back yards (private subnets)

But nothing is connected yet.

Your back yard needs an exit​

Day 4: You divided your VPC into front yards (public) and back yards (private)

Today: We build the back gate (NAT Gateway)

Your neighborhood needs houses​

Day 1: Your AI agent's first phone call Day 1 ↗
Day 2: Give your AI agent a real-world mission Day 2 ↗
Day 3: You claimed your territory (VPC) Day 3 ↗

Today: We'll build our neighborhood with subnets

Your AI agent needs a home​

Days 1-2: Your AI caller agent ran on your laptop.

Today: We're moving it to the cloud

Give your AI agent a real mission​

Yesterday, your AI agent called you and you had a basic conversation.

Today? We're giving it a real job: booking restaurant reservations.

By the end of today, your AI agent will:

✅ Call a phone number
✅ Act as your personal assistant
✅ Request a dinner reservation
✅ Handle follow-up questions
✅ Sound professional and polite

And you'll test it by answering the phone and roleplaying as the restaurant.

This is where it gets fun.

Let your AI make real phone calls​

Your AI agent is trapped.

It can write emails. Answer questions. Generate code.

But it is stuck in your chat text box. It can't pick up a phone and call someone.

But what if it could?

What if you could say:

"Hey ChatGPT, call the restaurant and book me a table at 7pm"

or

"Hey ChatGPT, call the doctor's office and reschedule my appointment"

What if your AI agent could exist in the REAL world and not just in your browser?

That's what we're building.