◆ Amazon DynamoDB

Query DynamoDB by date range

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 taskFind all log entries from the 'analytics_events' table for the 'user_login' event type between…+
Find all log entries from the 'analytics_events' table for the 'user_login' event type between October 26, 2023, and October 27, 2023, inclusive. I need the full item for each match to debug the recent authentication issues.
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 hand off this query to the support team, make sure it's efficient. We need to fetch…+
Before I hand off this query to the support team, make sure it's efficient. We need to fetch all 'transaction_completed' events for the last 24 hours from the 'financial_logs' table. Optimize the query so it uses the GSI on 'timestamp' and 'transaction_id' to minimize read capacity units and avoid full table scans, because we're hitting our budget limits with these large queries.
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 'order_history' query on the 'customer_data' table is failing for some of our European…+
The new 'order_history' query is failing for some users, but not all.
The 'order_history' query on the 'customer_data' table is failing for some of our European users, returning no data, but it works fine for US users. I just deployed a change to how we construct the date range for the query, and I'm worried it's a timezone issue or an incorrect index usage. The customer support team is getting swamped with tickets. What's the most likely cause here, and what's the fastest way to verify it without impacting other regions?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm consistently writing queries that perform well in dev but then cause high read capacity…+
I keep writing queries that perform poorly in production.
I'm consistently writing queries that perform well in dev but then cause high read capacity consumption or timeouts in production when dealing with large datasets. I'm struggling to anticipate the real-world scale effects. What habit should I change in my query design or testing process to catch these performance issues before they hit our users and our budget?
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.