Cloud Architect

Corey Quinn Portfolio

Publishes the "Last Week in AWS" newsletter and blog as self-titled "Chief Cloud Economist," dissecting AWS service announcements, pricing changes, and architecture tradeoffs with a consistent focus on cloud cost optimization.

AWSCloud Cost OptimizationCloud EconomicsNewsletter

Location

Coordinates unknown. Vibes: international.

Skills

AWSCloud Cost OptimizationCloud EconomicsNewsletter

What makes it work

A breakdown of the choices that make this portfolio stand out.

1

A clearly stated, narrow specialty

Rather than a generic "cloud consultant" title, the self-given title "Chief Cloud Economist" stakes out one specific lens — cost — and every piece of content reinforces it. Visitors know exactly what problem he solves within one sentence.

2

Long-running, dated newsletter archive

Years of consistent output on the same beat builds a searchable body of analysis that a one-off blog post never could — it demonstrates sustained expertise, not a single take.

3

Commentary that names real AWS tradeoffs by name

Analysis references specific services, pricing tiers, and announcements rather than speaking about "the cloud" in the abstract, which is what makes the writing useful to working architects.

What Cloud Architects can take from this

Specific, actionable tips to apply to your own portfolio — no generic advice.

  • Pick one narrow specialty inside a broad field and let your title say it explicitly — a specific title tells a hiring manager more in three words than a generic one does in a paragraph.

  • Publish on a fixed cadence for years, not a burst of posts followed by silence — the archive itself becomes evidence of expertise.

  • Name the specific services, prices, and tradeoffs you're analyzing instead of writing generically about "the cloud" — specificity is what makes technical writing useful to other practitioners.

Case studies

Three formats, one beat: a weekly newsletter, two podcasts and a map, all aimed at the AWS news cycle. Corey Quinn's portfolio is a media operation with a cost-consulting firm (Duckbill) behind it, and the archive numbers are the credential.

Case StudyintermediateWeekly; issue No. 488 in September 2026

Last Week in AWS (newsletter)

AWSEmail newsletterCloud cost analysisTechnical commentary

A weekly email that filters the week's AWS announcements and pokes fun at what's left. The site's own pitch: Quinn 'goes through the torrent of news about Amazon's cloud ecosystem and strains out the noise.' Every issue is archived and searchable on the site as 'The Snarkive'.

Reading every AWS release and saying in plain words what matters takes real breadth across the platform. Nearly 500 issues show he has kept that up for years.

  • 488 numbered issues, all archived in the searchable 'Snarkive'

  • Issue topics name specific services and events: EC2's 20th birthday, a London AZ outage, DynamoDB vectors

  • Each issue is paired with a short audio episode on the Last Week in AWS Podcast

Case StudyintermediateOngoing; latest episode 24 September 2026

Screaming in the Cloud (podcast)

PodcastLong-form interviewsAWSGCPAzureOracle Cloud

An interview podcast where Quinn talks with cloud practitioners about AWS, GCP, Azure and Oracle Cloud. It is billed as 'Insightful conversations. Less snark.', the long-form counterpart to the newsletter. Episodes run from 4-minute solo segments to roughly 37-minute interviews.

Interviewing engineers about their own systems means asking questions precise enough to get past the marketing. The show covers several clouds, not only AWS.

  • Covers AWS, GCP, Azure and Oracle Cloud, not a single vendor

  • Guests are domain experts, e.g. Matt Rehder on AWS networking

  • Separate from the news-recap show; an open 'Nominate a Guest' form on the site

Projects

ToolintermediateLive interactive map; footer © 2023 The Duckbill Group

AWS Network Map

MapboxOpenStreetMapAWS global infrastructure data

An interactive world map of AWS's physical footprint. Layers can be toggled for Regions (including coming-soon), Local Zones, CloudFront edge locations and regional edge caches, Wavelength Zones by carrier, and Direct Connect locations filtered by port speed (1G, 10G, 100G, MACsec, SiteLink).

Picking regions, edge locations and Direct Connect sites is a real architecture decision. The map puts all of it in one filterable view instead of scattered AWS docs pages.

  • Separate toggles for Regions, Local Zones, CloudFront, Wavelength and Direct Connect

  • Wavelength Zones broken out by carrier: Verizon, KDDI, SK Telecom, Vodafone, Bell

  • Direct Connect filterable by 1G / 10G / 100G, MACsec and SiteLink

Ready to build your portfolio?

Follow the Cloud Architect roadmap — skills, projects, and timeline to get hired.

Cloud Architect Roadmap