◆ Elasticsearch

Implement Elasticsearch security best practices

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCreate a new role named 'reporting_analyst' that can only read data from the 'sales_data'…+
Create a new role named 'reporting_analyst' that can only read data from the 'sales_data' index. Grant this role to the user 'MariaLopez'.
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 the external audit next month, review our current security configuration for the…+
Before the external audit next month, review our current security configuration for the 'customer_pii' index. Identify any users or roles with write access that shouldn't have it, and flag any missing field-level security for sensitive fields like 'social_security_number'.
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 CISO just asked for a full report on who can access financial data, specifically the…+
Our CISO just asked for a full report on who can access financial data, and I'm not sure our current setup is fully compliant.
The CISO just asked for a full report on who can access financial data, specifically the 'transactions_2023' index. I'm worried our current role assignments might be too broad, especially for some legacy applications. I don't want to accidentally revoke access for critical services. What's the quickest way to get a clear picture of effective permissions on that index, and what's the safest first step to tighten anything I find?
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 constantly scrambling to prove compliance for data access to auditors and internal teams.…+
I'm always scrambling to prove compliance for data access.
I'm constantly scrambling to prove compliance for data access to auditors and internal teams. It's hard to get a clear, consistent view of who can do what across all our indices. I'm losing credibility because I can't answer quickly. What habit should I change in how I manage roles and permissions to make our security posture more transparent and auditable?
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 Elasticsearch'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.