◆ Amazon DynamoDB

Perform basic aggregation with DynamoDB

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All Amazon DynamoDB tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCalculate the total number of items sold and the average item price for all orders placed last…+
Calculate the total number of items sold and the average item price for all orders placed last Tuesday in the 'Orders' table.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I run this aggregation for the sales report, make sure it can handle millions of orders…+
Before I run this aggregation for the sales report, make sure it can handle millions of orders without timing out or consuming excessive read capacity. I need to know it will complete reliably and efficiently for the finance team.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe sales report aggregation for last month's orders timed out again, and the finance director…+
The sales report aggregation for last month's orders just timed out again, and the finance director is asking for the numbers.
The sales report aggregation for last month's orders timed out again, and the finance director is waiting. I'm using a scan and client-side aggregation, but it's clearly not scaling. I'm afraid of the cost if I just increase read capacity, and I don't know if there's a better, more efficient way to get these basic sums and averages without breaking the bank. What’s the best next move to get those numbers reliably?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe constantly hit performance and cost ceilings when trying to do basic sums and averages on…+
We frequently run into performance and cost issues when performing basic aggregations on large tables.
We constantly hit performance and cost ceilings when trying to do basic sums and averages on large datasets, leading to delayed reports and frustrated stakeholders. I need to stop these reactive fixes. What habit should I change to consistently design and implement aggregation strategies that are both performant and cost-effective from the outset, even for growing datasets?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Amazon DynamoDB's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.