{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/amazon-redshift/json-schema/amazon-redshift-create-workgroup-request-schema.json",
  "title": "CreateWorkgroupRequest",
  "x-generated": "2026-11-11",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/amazon-redshift-workgroup-api-openapi.yml#/components/schemas/CreateWorkgroupRequest",
  "type": "object",
  "properties": {
    "workgroupName": {
      "type": "string",
      "description": "The name of the created workgroup."
    },
    "namespaceName": {
      "type": "string",
      "description": "The name of the namespace to associate with the workgroup."
    },
    "baseCapacity": {
      "type": "integer",
      "description": "The base data warehouse capacity of the workgroup in Redshift Processing Units (RPUs)."
    },
    "enhancedVpcRouting": {
      "type": "boolean",
      "description": "The value that specifies whether to turn on enhanced virtual private cloud (VPC) routing, which forces Amazon Redshift Serverless to route traffic through your VPC instead of over the internet."
    },
    "configParameters": {
      "type": "array",
      "items": {
        "$ref": "#/$defs/ConfigParameter"
      },
      "description": "An array of parameters to set for advanced control over a database. The options are auto_mv, datestyle, enable_case_sensitive_identifier, enable_user_activity_logging, query_group, search_path, require_ssl, use_fips_ssl, and either wlm_json_configuration or query monitoring metrics that let you define performance boundaries. You can either specify individual query monitoring metrics (such as max_scan_row_count, max_query_execution_time) or use wlm_json_configuration to define query queues with rules, but not both. If you're using wlm_json_configuration, the maximum size of parameterValue is 80"
    },
    "securityGroupIds": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "An array of security group IDs to associate with the workgroup."
    },
    "subnetIds": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "An array of VPC subnet IDs to associate with the workgroup."
    },
    "publiclyAccessible": {
      "type": "boolean",
      "description": "A value that specifies whether the workgroup can be accessed from a public network."
    },
    "tags": {
      "type": "array",
      "items": {
        "$ref": "#/$defs/RedshiftServerlessTag"
      },
      "description": "A array of tag instances."
    },
    "port": {
      "type": "integer",
      "description": "The custom port to use when connecting to a workgroup. Valid port ranges are 5431-5455 and 8191-8215. The default is 5439."
    },
    "maxCapacity": {
      "type": "integer",
      "description": "The maximum data-warehouse capacity Amazon Redshift Serverless uses to serve queries. The max capacity is specified in RPUs."
    },
    "pricePerformanceTarget": {
      "$ref": "#/$defs/PerformanceTarget"
    },
    "ipAddressType": {
      "type": "string",
      "description": "The IP address type that the workgroup supports. Possible values are ipv4 and dualstack."
    },
    "trackName": {
      "type": "string",
      "description": "An optional parameter for the name of the track for the workgroup. If you don't provide a track name, the workgroup is assigned to the current track."
    },
    "extraComputeForAutomaticOptimization": {
      "type": "boolean",
      "description": "If true, allocates additional compute resources for running automatic optimization operations. Default: false"
    }
  },
  "required": [
    "workgroupName",
    "namespaceName"
  ],
  "$defs": {
    "ConfigParameter": {
      "type": "object",
      "properties": {
        "parameterKey": {
          "type": "string",
          "description": "The key of the parameter. The options are auto_mv, datestyle, enable_case_sensitive_identifier, enable_user_activity_logging, query_group, search_path, require_ssl, use_fips_ssl, and either wlm_json_configuration or query monitoring metrics that let you define performance boundaries. You can either specify individual query monitoring metrics (such as max_scan_row_count, max_query_execution_time) or use wlm_json_configuration to define query queues with rules, but not both. If you're using wlm_json_configuration, the maximum size of parameterValue is 8000 characters. For more information about "
        },
        "parameterValue": {
          "type": "string",
          "description": "The value of the parameter to set."
        }
      }
    },
    "PerformanceTarget": {
      "type": "object",
      "properties": {
        "status": {
          "type": "string",
          "description": "Whether the price performance target is enabled for the workgroup."
        },
        "level": {
          "type": "integer",
          "description": "The target price performance level for the workgroup. Valid values include 1, 25, 50, 75, and 100. These correspond to the price performance levels LOW_COST, ECONOMICAL, BALANCED, RESOURCEFUL, and HIGH_PERFORMANCE."
        }
      }
    },
    "RedshiftServerlessTag": {
      "type": "object",
      "properties": {
        "key": {
          "type": "string",
          "description": "The key to use in the tag."
        },
        "value": {
          "type": "string",
          "description": "The value of the tag."
        }
      },
      "required": [
        "key",
        "value"
      ]
    }
  }
}