Elastic Cloud StrawberryRead every deployment, draft every traffic filter ruleset, approve in one pass
Your Elastic Cloud, worked while you do something else: 3 reads to go through it, 5 writes to change it, and a card in front of every one of those changes.
Open the deployment. Check it against something else. Write the change. Move to the next one. That is the Elastic Cloud afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a deployment until you approve it.
What it can do is exactly what Elastic Cloud exposes to an account you authorise and nothing beyond it: 8 operations, 3 reads and 5 writes. In practice that means it can update a traffic filter ruleset, update a deployment and delete a traffic filter ruleset, and work across the deployments and traffic filter rulesets.
The Elastic Cloud API stops at Elastic Cloud. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the deployments or ask you for them?
3 of the 8 operations are reads.
Your account, not a guess at it: a companion can list traffic filter rulesets, list deployments and get a deployment, and the full list below is the whole list, with nothing inferred from Elastic Cloud's documentation.
The deployments are what most of this inventory is about, alongside the traffic filter rulesets. A companion can hold all 8 of these operations and forty open tabs in the same pass, which is how an afternoon of Elastic Cloud admin becomes a queue you review.
- List Traffic Filter Rulesets
- List Deployments
- Get Deployment
Which deployments wait for your approval?
All 5 write operations wait for you.
A companion can update a traffic filter ruleset, update a deployment and delete a traffic filter ruleset, and each one is staged on an approval card first: you see the deployment, the field and the new value before it lands in Elastic Cloud.
Nothing in Elastic Cloud is sent, changed or deleted on your behalf without that click, and a rejected card leaves the deployment exactly as it was. The gate is the same one on every surface, described at security.
- Update Traffic Filter Ruleset
- Update Deployment
- Delete Traffic Filter Ruleset
- Create Traffic Filter Ruleset
- Create Deployment
Does the deployment sweep have to be asked for every time?
Yes.
Saved as a routine, the Elastic Cloud deployments pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the infrastructure checks, the Elastic Cloud deployments sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents