Replace an external datastore definition

• Latest Dynatrace
• Reference
• Published Oct 13, 2026

Fully update an external datastore definition in Dynatrace Grail with the External Datastores API, using optimistic locking to avoid conflicting changes.

Overview

Fully update an existing external datastore definition.

All fields must be provided. The name field cannot be changed after creation.

The following fields can be updated:

Uses optimistic locking - pass the current version via the optimistic-locking-version query parameter.

Authentication

To execute this request, you need a platform token or OAuth access token with storage:external-datastore-definitions:write scope. To learn how to obtain and use it, see Tokens and authentication.

Parameters

{
  "type": "s3://",
  "name": "my-s3-store",
  "displayName": "My S3 Store",
  "bucketName": "my-s3-bucket",
  "region": "us-east-2",
  "connectionId": "my-connection-id",
  "connectionName": "my-connection-name",
  "version": 1
}

Response

{
  "type": "s3://",
  "name": "my-s3-store",
  "displayName": "My S3 Store",
  "bucketName": "my-s3-bucket",
  "region": "us-east-2",
  "connectionId": "my-connection-id",
  "connectionName": "my-connection-name",
  "version": 2
}

{
  "error": {
    "message": "Constraint Violations",
    "details": {
      "constraintViolations": [
        {
          "message": "must not be blank",
          "parameterDescriptor": "bucketName"
        }
      ]
    },
    "code": 400
  }
}