--- name: azion-edit-stop-or-delete-a-stream description: >- Change the settings of a Data Stream stream, stop it and start it again, or delete it, in Azion Console or with the Azion API. --- # Edit, stop, or delete a stream You can edit, stop, or delete a [Data Stream](/en/documentation/platform/data-stream/) stream from Azion Console or with the Azion API. To create a stream, refer to the [Data Stream quickstart](/en/documentation/platform/data-stream/quickstart/). A stopped stream keeps its settings and sends nothing until you start it again. A deleted stream is gone with its settings. For every field you can change, refer to [Stream settings](/en/documentation/platform/data-stream/stream-settings/). --- Select your interface once. The prerequisites and every task below show only that path. ## Prerequisites - A stream on your Azion account. To create one, refer to the [Data Stream quickstart](/en/documentation/platform/data-stream/quickstart/). - The **Edit Data Stream** permission. With **View Data Stream** only, you can see the streams but not edit, stop, or delete them. For details, refer to [Stream settings](/en/documentation/platform/data-stream/stream-settings/#permissions). **Console** - Access to Azion Console. To sign in, refer to [How to access Azion Console](/en/documentation/guides/platform/account-and-billing/how-to-access-azion-console/). - An account with fewer than 3,000 workloads. At 3,000 workloads or more, the Console blocks the stream forms, and you manage streams through the API only. **API** - A personal token. To create one, refer to [How to manage a personal token](/en/documentation/guides/platform/account-and-billing/personal-tokens/). - `curl`. - The ID of the stream. The list response of `GET /v4/workspace/stream/streams` carries it in the `id` field of each stream. In Azion Console, it is the number at the end of the stream's edit page URL, `/data-stream/edit/`. --- ## Edit a stream An edit keeps the stream's ID and changes only the settings you save. Saving checks the format of the fields, not the endpoint, so a wrong credential shows up later as failed sends. **Console** To edit a stream in Azion Console: 1. **Open Data Stream** Access [Azion Console](https://console.azion.com/) > **Data Stream**. 2. **Open the stream** In the list, select the row of the stream. The edit page opens, titled with the stream's name. A stream without sampling opens with *Filter Workloads* selected in **Option**, because the form reads the option from the stream's transforms. 3. **Change the settings** In the **General**, **Input**, **Transform**, **Render Template**, **Output**, or **Status** section, change the fields you need. The **Output** section labels the endpoint field **Connector**. On an edit, the Console does not require the S3 **Secret Key**. For AWS Kinesis Data Firehose, enter **Secret Key** again on every save. 4. **Select Save** 5. **Confirm the sampling warning** If **Sampling** is on, the **Attention** dialog opens with `After activating and saving these settings, all other Data Streams will be disabled.` Select **Confirm**. The Console shows `Your data stream has been updated`. **API** To edit a stream with the API, send a `PATCH` request with only the keys you change. This example renames the stream. Replace `` with the ID of your stream: ```bash curl -X PATCH 'https://api.azion.com/v4/workspace/stream/streams/' \ -H 'Content-Type: application/json' \ -H 'Authorization: Token [TOKEN VALUE]' \ -d '{"name": "activity-to-bucket"}' ``` The API answers `200` with the stored stream: ```json { "state": "executed", "data": { "id": 12345, "name": "activity-to-bucket", "last_editor": "user@example.com", "created": "2026-01-01T11:30:47.000000Z", "last_modified": "2026-01-01T11:30:59.000000Z", "product_version": "1.0", "active": true, "inputs": [{ "type": "raw_logs", "attributes": { "data_source": "activity_history" } }], "transform": [ { "type": "sampling", "attributes": { "rate": 100 } }, { "type": "render_template", "attributes": { "template": 251 } } ], "outputs": […] } } ``` The `name` is the one you sent, and `last_modified` moves forward. The data source, transforms, and endpoint stay as they were. To replace the whole stream, send a `PUT` request with the keys a create requires: `name`, `inputs`, `transform`, and `outputs`. For the body of each key, refer to [Stream settings](/en/documentation/platform/data-stream/stream-settings/#stream-object). Edits take a few minutes to propagate. Saving an active stream that uses sampling deactivates every other stream on the account. After you change the endpoint, check the next sends in [Real-Time Events](/en/documentation/platform/real-time-events/data-sources/#data-stream): each send is recorded with the status code the endpoint returned. --- ## Stop a stream A stopped stream keeps its settings, so you can start it again without configuring it. **Console** To stop a stream in Azion Console: 1. **Open Data Stream** Access [Azion Console](https://console.azion.com/) > **Data Stream**. The **Status** column shows each stream as *Active* or *Inactive*. 2. **Open the stream** In the list, select the row of the stream. 3. **Turn off Active** In the **Status** section, turn off **Active**. 4. **Select Save** 5. **Confirm the sampling warning** If the **Attention** dialog opens, select **Confirm**. The Console shows `Your data stream has been updated`, and the list shows the stream as *Inactive*. To start the stream again, turn on **Active** and select **Save**. **API** To stop a stream with the API, send a `PATCH` request that sets `active` to `false`: ```bash curl -X PATCH 'https://api.azion.com/v4/workspace/stream/streams/' \ -H 'Content-Type: application/json' \ -H 'Authorization: Token [TOKEN VALUE]' \ -d '{"active": false}' ``` The API answers `200` with the stored stream: ```json { "state": "executed", "data": { "id": 12345, "name": "activity-to-bucket", … "last_modified": "2026-01-01T12:03:37.000000Z", "product_version": "1.0", "active": false, … } } ``` The stream reads `"active": false`, and its other settings are unchanged. To start the stream again, send the same request with `{"active": true}`. A change of active state takes effect after one to two minutes. During that window, the stream can keep sending. After it, [Real-Time Events](/en/documentation/platform/real-time-events/data-sources/#data-stream) records no further send from the stopped stream to its endpoint. > **Caution** > > Starting a stream that uses sampling deactivates every other stream on the account, and the API returns no warning. A rate of `100` counts as sampling. To run several streams at once, give each one a workload filter instead. For the steps, refer to [Associate workloads with a stream](/en/documentation/guides/platform/observability/data-stream-associate-workloads/). --- ## Delete a stream Deleting a stream removes it and its settings. A deleted stream cannot be restored: the Console warns `Once confirmed, this action can't be reversed.` To pause a stream and keep its settings, stop it instead. **Console** To delete a stream in Azion Console: 1. **Open Data Stream** Access [Azion Console](https://console.azion.com/) > **Data Stream**. 2. **Select Delete** In the row of the stream, select **Delete**, the trash icon. The **Delete stream** dialog opens. 3. **Enter the stream's name** In the box, enter the name of the stream exactly as the dialog quotes it. 4. **Select Delete** The Console shows `Data Stream successfully deleted`. **API** To delete a stream with the API, send a `DELETE` request: ```bash curl -X DELETE 'https://api.azion.com/v4/workspace/stream/streams/' \ -H 'Authorization: Token [TOKEN VALUE]' ``` The API answers `200`: ```json {"state":"executed"} ``` The `"state": "executed"` value confirms that the API deleted the stream. --- ## Next steps - [Stream settings](/en/documentation/platform/data-stream/stream-settings.md): Look up every field you can change, with its values, defaults, and errors. - [Data Stream quickstart](/en/documentation/platform/data-stream/quickstart.md): Create a stream and confirm that its first logs reach the endpoint. - [Troubleshoot Data Stream](/en/documentation/platform/data-stream/troubleshooting.md): Fix a stream that stops sending or an endpoint that rejects the logs.