EDWARD “E.T.”
THORNTON.
SIGNAL / 003  •  AWS PROJECT TRANSMISSION

ARCHITECTURE CASE STUDY / AMAZON CONNECT + AWS

Neptune Insurance.

An entire customer experience.
One otherworldly architecture.

A real AWS-hosted insurance demo with interactive claims, policy and support experiences. Behind the interface: a staged omnichannel Amazon Connect architecture, designed to grow without losing the customer journey.

LIVE STATIC PROTOTYPE   /   CONNECT INTEGRATIONS IN PROGRESS

Neptune Insurance Amazon Connect omnichannel contact center project artwork MISSION VIEW / NEPTUNE WEBSITE LIVE ENTER CUSTOMER EXPERIENCE ↗neptune.hireedwardthornton.click
01LIVE CUSTOMER WEBSITE
08INTERACTIVE DEMO PAGES
04OMNICHANNEL DESIGN TARGETS
500AGENT CAPACITY DESIGN TARGET · NOT TESTED
01 / SOLUTION ARCHITECTURE

One connected customer journey.

Voice, chat, SMS and email come together through Amazon Connect. The Neptune website is already live; it becomes the digital entry point for the planned web-chat and claims integrations.

Neptune Insurance unified proposed omnichannel AWS architecture Target design: Voice, web chat from Neptune's live website, SMS, and email feed Amazon Connect flows, queues and routing profiles. Agentic CX and human agents connect to Lambda and proposed insurance services. The existing Neptune customer website is hosted separately on Route 53, CloudFront, and a private S3 origin. Website integration with Connect is planned, not yet live. OMNICHANNEL EXPERIENCE PLANNED TARGET DESIGN CUSTOMER CHANNELS Voice / PSTN Web chat via Neptune website (planned) SMS consent + registration required Email channel setup required Amazon Connect CONTACT CENTER / ORCHESTRATION Contact flows / routing Queues + routing profiles Agent Workspace SERVICE EXPERIENCE Agentic CX + AI bounded self-service Human specialists claims / billing / support context-aware handoff INSURANCE SERVICES AWS Lambda / APIs DynamoDB + S3 Policy / claims APIs mock until integrated GUARDRAILS IAM / least privilege KMS / encryption CloudWatch + CloudTrail Consent / audit NEPTUNE WEBSITE DELIVERY LIVE STATIC EXPERIENCE Neptune customer websiteneptune.hireedwardthornton.click Route 53DNS CloudFront + ACMHTTPS / edge delivery Private S3 originHTML / CSS / JavaScript

↔ SWIPE TO VIEW FULL ARCHITECTURE

The website delivery row is live today. The website's future chat entry point, Amazon Connect channels, AI assistance and insurance-system integrations are proposed and will be validated individually during the lab.

LIVEPROPOSED
02 / THE BUSINESS CHALLENGE

A better way through the complicated moments.

Neptune is a fictional regional property-and-casualty insurer migrating from a legacy contact center. The challenge: give policyholders a clear next step without losing their context when they switch channels or teams.

EXPERIENCE 01

Guided FNOL

An interactive, step-by-step simulated first notice of loss captures bounded sample information, creates a browser-local reference, and demonstrates how a claims handoff can be structured.

EXPERIENCE 02

Policyholder workspace

A synthetic customer dashboard surfaces example auto and home coverage, claim references and status timelines. No authentication or real insurance database is represented.

EXPERIENCE 03

Connected support

Support discovery, scripted assistant preview, and precise placeholders for Connect voice, hosted web chat, SMS and email. Channels are only marked live after configuration and verification.

ARCHITECTURE 04

Intent-aware routing

Designs for policy servicing, billing, auto claims, claim status, escalations, and after-hours tasks with queue and routing-profile boundaries.

ARCHITECTURE 05

Guarded Agentic AI

Proposed conversation automation gathers structured intent and summarizes interactions, while authorized business APIs own validation and sensitive decisions.

ARCHITECTURE 06

Observability by design

A traceable contact journey can correlate ContactIds, flow events, contact records, tasks, and secure, minimal customer-context attributes.

03 / THE FLAGSHIP CUSTOMER JOURNEY

One claim. One continuous story.

A realistic demo scenario starts online and illustrates the future end-to-end journey across channels and the specialist team.

01Start online

Policyholder initiates fictional auto FNOL on the Neptune website.

02Capture safely

Gather minimal structured details, validate and return a simulated reference.

03Continue by channel

After consent and approvals, offer voice, chat or message follow-up.

04Route with context

Connect targets the Auto Claims queue and passes only approved attributes.

05Trace and resolve

Agent or supervisor takes action with auditability and a next-step record.

04 / IMPLEMENTATION ROADMAP

What we're building, and in what order.

Small, testable increments for the 14-day lab. One practical integration at a time, with security and console evidence before moving on.

STAGE 01

Experience foundation

Responsive Neptune site, guided claim simulation, sample dashboard, help center and technical showcase.

Frontend prototype created
STAGE 02

Core Amazon Connect

Instance, numbers, call flows, queue/routing profiles, 2–3 training agents, baseline call testing.

Lab build in progress
STAGE 03

Omnichannel journeys

Hosted chat widget, callback/task patterns, messaging registration and consent, email prerequisites.

Requires configuration
STAGE 04

AI + operations

Agentic self-service, mock Lambda business APIs, secure context, failure tests, dashboards and teach-back.

Planned capstone
05 / ARCHITECTURAL DECISIONS

Built like a real system.
Documented like one, too.

The goal is to practice how an architect makes tradeoffs, not just which buttons to click in the console. This is the deployed foundation and the design logic behind it.

Decision 01 / Edge delivery

CloudFront in front of private S3

The website is stored in a dedicated, private S3 bucket and served through a CloudFront distribution. Origin Access Control keeps the bucket from being used as a public website endpoint.

Decision 02 / Identity

Separate domain, shared portfolio

The live customer demo runs at neptune.hireedwardthornton.click. The portfolio case study lives on the main domain, preserving the existing project presentation.

Decision 03 / HTTPS

ACM and Route 53

Route 53 A and AAAA alias records point to CloudFront. An ACM certificate in us-east-1 secures the custom hostname. DNS validation and HTTPS response were verified during deployment.

Decision 04 / CX boundary

Demo interactions before production APIs

Claims and sample policy journeys operate as a client-side prototype. Future real processing will require authenticated APIs, validation, durable storage, and auditable events.

Decision 05 / Capacity

Design for 500, test small

The 500-agent model is a reference architecture, not 500 provisioned Connect users or 500 concurrent calls. Routing profiles, concurrency, and quotas will be modeled separately.

Decision 06 / Messaging

Consent is a real boundary

SMS will be added only after sender verification, compliant opt-in, and successful delivery tests. A fictional insurance demo is not presented as a licensed insurer.

06 / BUILD LOG

Progress you can inspect.

This project is versioned by milestone. Completed work is separated from planned capabilities; the GitHub repository tracks source, architecture notes, and next steps.

SOURCE CODE / VERSION CONTROL

RedLeopard/neptune-insurance

Website source, deployment scripts, architecture decisions and milestone documentation.

VIEW ON GITHUB
Done / Static customer siteEight-page Neptune experience, responsive layouts, sample claims, sample policy portal, and help center.
Done / AWS web foundationPrivate S3 origin, CloudFront delivery, Route 53 aliases, ACM HTTPS certificate, and a verified HTTP 200 response.
Next / Amazon Connect channelsWire real voice and embedded web chat; validate routing, queues, agent workspace, and channel permissions.
Later / Messaging + agentic AISender verification and consent, email/SMS journeys, identity and claims APIs, AI guardrails, and observability.

Customer website + deployment architecture

Published Neptune via CloudFront and validated the custom hostname, certificate, private bucket, and homepage.

Source control + Connect foundations

Move project source into a dedicated workspace, track milestones in GitHub, and connect the website's first real contact channel.

This is a fictional training and portfolio project. No real policies are sold, and no real customer submissions should be entered.

Project integrity: This is a training and portfolio demonstration. Neptune Insurance is fictional. The website is runnable as a static prototype; the cloud architecture is a staged implementation and target design. The AWS toll-free messaging registration, if pursued, must truthfully identify the actual registering business (Cloud Systems Direct LLC), not use this fictional insurer as proof of an operating business. Synthetic data only; no real customer records or insurance services.