◆ Amazon DynamoDB

Import bulk data from CSV

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 taskTake the attached 'products.csv' file and load all the product data into the 'products' table.…+
Take the attached 'products.csv' file and load all the product data into the 'products' table. Each row is a new product.
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 we import the 'customer_feedback.csv' file, make sure that any 'rating' values are…+
Before we import the 'customer_feedback.csv' file, make sure that any 'rating' values are converted to integers, and if a 'comment' field is empty, it should be stored as 'No comment provided'. This will clean up our analytics.
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 import a 5GB 'historical_sales.csv' file into the 'sales_records' table, but the…+
I'm trying to import a large CSV of historical sales data, but it keeps failing halfway through without clear errors.
I'm trying to import a 5GB 'historical_sales.csv' file into the 'sales_records' table, but the process consistently stops around the 60% mark without a specific error message, leaving partial data. I suspect it's either a memory issue, a timeout, or malformed data in later rows. What's the best approach to debug this large-scale import and ensure all records are processed reliably?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often spend days debugging failed or incomplete bulk data imports from CSVs, especially for…+
I frequently struggle with bulk data imports, often encountering errors or performance bottlenecks.
I often spend days debugging failed or incomplete bulk data imports from CSVs, especially for large datasets or those with inconsistent formatting. This costs us valuable time for data analysis. What habit can I change to systematically prepare for and execute bulk imports, ensuring data integrity and efficient processing every time, rather than reacting to failures?
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.