◆ Amazon DynamoDB

Query on a secondary index

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 taskQuery the `UserActivity` table using the `action-timestamp-index` to find all 'login' actions…+
Query the `UserActivity` table using the `action-timestamp-index` to find all 'login' actions for `userId` `user789` that occurred after '2024-01-01T00:00:00Z'. Put the results in `user_logins.json`.
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 acceptI need to get all orders from the `Orders` table that were placed by `customer123` and have a…+
I need to get all orders from the `Orders` table that were placed by `customer123` and have a `status` of 'PENDING'. Use the `customer-status-index` for this. Before I give this to the sales team, make sure the output only includes `orderId`, `orderDate`, and `totalAmount`, and is sorted by `orderDate` descending so they see the newest ones first.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm trying to query the `ProductReviews` table for all reviews with a `rating` of 1 for a…+
I'm trying to query for specific items using a non-primary key, but the query is either very slow or returning too many irrelevant results.
I'm trying to query the `ProductReviews` table for all reviews with a `rating` of 1 for a specific `productId`, using the `rating-productId-index`. The query is either taking forever or returning a huge number of items I don't need, making it unusable for the product manager who needs this feedback now. I suspect my index usage might be inefficient. What's the most likely issue with my approach, and what's the best way to structure this query to efficiently get only the bad reviews for that specific product?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently struggle with slow queries or high read costs when trying to fetch data based on…+
I frequently struggle with slow queries or high read costs when trying to fetch data based on attributes that aren't the primary key.
I frequently struggle with slow queries or high read costs when trying to fetch data based on attributes that aren't the primary key, often leading to performance bottlenecks and budget overruns. This impacts my ability to provide quick insights to the business. What habit should I change in my design or querying approach to ensure I'm always leveraging secondary indexes effectively, making my queries faster and more cost-efficient for common access patterns?
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.