
65 Prompts, Zero Guesswork: Inside Amazon Q's New Prompt Library
Amazon Q's prompt library jumped from 15 to 65 prompts. Here's what I use it for daily, straight from the AWS console.
I opened the AWS console last week to check a client's EC2 spend and noticed a small "prompt library" icon sitting next to Amazon Q's chat box. I almost skipped past it. Glad I didn't.
It's a searchable catalog of 65 pre-built prompts, organized by response type and AWS service, that you can fire at Amazon Q without writing a single sentence yourself. Click a card, and Q runs it. Here's what's actually in there and where it earns its place in a real workflow.

Why this actually matters
Here's the problem it solves for me: listing running EC2 instances across every account in an org used to mean either scripting it with boto3 or paying for something like AWS Global View. Neither is wrong, but both are overhead for a question that should take ten seconds to answer. Q's prompt library gets you there in one click, straight from the console, with no setup.
There's a quieter benefit too. A lot of engineers paste account IDs, resource ARNs, and config snippets into general-purpose AI chat tools to get help — which means corporate and account data is leaving AWS entirely. Amazon Q runs inside the console, against your own account, so that data never has to leave in the first place. For anyone doing this day to day, that's not a small thing.

I also went back and checked: when I first started poking around Q's prompt library, it had 12 or 15 prompts. It's at 65 now. That growth tells me AWS is actually watching what people ask Q day to day and turning the common ones into one-click prompts. It's a good sign for where this is headed.
What I've actually used it for
I've been using Amazon Q since it first showed up embedded in the console, and that's the version of it I keep coming back to — not a separate app, just there in the same tab you're already working in. Over time it's helped me resolve real cost issues and networking issues on client accounts, not just answer trivia questions about them.

It's also been useful for the more basic stuff I get asked constantly by people newer to AWS: what are the different ways to connect to an EC2 instance over SSH, what is Bedrock and how do you generate code against it, that kind of thing. Before Q, answering those meant jumping across four or five open tabs — docs, console, maybe a blog post. Now it's one conversation in the same window.
What's on the shelf

The library splits into three response types:
- Q&A (51 prompts) — conversational answers. Think "Do I have over-provisioned EC2 instances?" or "What are easy, low-risk ways to lower my bill?"
- Table (4 prompts) — structured lists. "List running EC2 instances," "List VPCs without VPC Flow Logs."
- Visualization (10 prompts) — charts, no config needed. "Graph EC2 cost per vCPU hour over the last 3 weeks," "Pie chart of EC2-Other costs last month."
You can filter by service too. EC2 alone has 15 prompts tagged to it, spanning compute, networking, and cost. Billing and Cost Management dominates the list with 27 prompts — unsurprising, since cost visibility is the thing everyone actually asks Q for.
The part that matters: these aren't generic
I tested a handful against a client account. "Which regions is tag cost center=Marketing spending the most in?" pulled real chargeback numbers by region, tag-filtered, no follow-up needed. "Do I have any outstanding invoices?" and "What is my account's default payment method?" — small, boring questions that used to mean three console clicks each — now take one.
The visualization prompts are where I got surprised. "Show me an area chart of EC2 costs by instance type by day this month" rendered instantly, broken down exactly as described. No chart-building, no exporting to a spreadsheet first.
Where I'd actually reach for this
- Onboarding a new account. Running through "List running EC2 instances," "List S3 buckets with tag value 'production'," and "List RDS databases without CloudWatch alarms" back to back gives you a fast inventory snapshot before you touch anything.
- Monthly cost reviews. "Summarize last month's spending trends" plus "Have there been any cost anomalies in the last 30 days? What caused them?" replaces the first hour of a FinOps sync.
- Security spot-checks. "Identify my top network security findings" and "List VPCs without VPC Flow Logs" are exactly the kind of question a junior engineer forgets to ask.

What I'd like to see next
One feature request: a custom prompt library. Right now the 65 prompts are AWS's picks. I'd like the ability to submit prompts I use regularly — the five or ten questions I ask on every client engagement — have AWS review them, and add them to a custom library scoped to my account or org. That would turn this from a shared catalog into something closer to a personal runbook.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article