Connect Your AI Agent with Elastic Cloud for Slack

Update an existing traffic filter ruleset in Elastic Cloud. The underlying API replaces the whole ruleset, so this action first reads the current ruleset and merges your changes over it — supply only the fields you want to change. The ruleset's type and region are immutable after creation and are carried over automatically. Run List Traffic Filter Rulesets first to find the ruleset ID. See the documentation

Update an existing Elastic Cloud deployment, including resizing cluster capacity. Cluster resize is performed here by supplying updated resources sizing (no separate resize action exists). Run List Deployments first to find the deployment ID. See the documentation

List all traffic filter rulesets in your Elastic Cloud organization. Use this first to discover ruleset IDs before calling Update Traffic Filter Ruleset or Delete Traffic Filter Ruleset. See the documentation

List all deployments in your Elastic Cloud organization. Use this first to discover deployment IDs before calling Get Deployment or Update Deployment. See the documentation

Retrieve a single Elastic Cloud deployment by ID. Run List Deployments first to find a valid deployment ID. See the documentation

Permanently delete a traffic filter ruleset from Elastic Cloud. This is irreversible. Run List Traffic Filter Rulesets first to find the ruleset ID. See the documentation

Create a new traffic filter ruleset in Elastic Cloud. The API requires a name, type, region, rules, and include-by-default flag. Note that type and region cannot be changed after the ruleset is created. See the documentation

Create a new Elastic Cloud deployment. Requires a name, region, and version at minimum. Provide the resources JSON object to configure Elasticsearch/Kibana/APM topology; omit it to accept region defaults. See the documentation