Menu
Amazon Redshift
API Reference (API Version 2012-12-01)

ModifyClusterSubnetGroup

Modifies a cluster subnet group to include the specified list of VPC subnets. The operation replaces the existing list of subnets with the new list of subnets.

Request Parameters

For information about the parameters that are common to all actions, see Common Parameters.

ClusterSubnetGroupName

The name of the subnet group to be modified.

Type: String

Required: Yes

SubnetIds.SubnetIdentifier.N

An array of VPC subnet IDs. A maximum of 20 subnets can be modified in a single request.

Type: Array of strings

Required: Yes

Description

A text description of the subnet group to be modified.

Type: String

Required: No

Response Elements

The following element is returned by the service.

ClusterSubnetGroup

Describes a subnet group.

Type: ClusterSubnetGroup object

Errors

For information about the errors that are common to all actions, see Common Errors.

ClusterSubnetGroupNotFoundFault

The cluster subnet group name does not refer to an existing cluster subnet group.

HTTP Status Code: 400

ClusterSubnetQuotaExceededFault

The request would result in user exceeding the allowed number of subnets in a cluster subnet groups. For information about increasing your quota, go to Limits in Amazon Redshift in the Amazon Redshift Cluster Management Guide.

HTTP Status Code: 400

DependentServiceRequestThrottlingFault

The request cannot be completed because a dependent service is throttling requests made by Amazon Redshift on your behalf. Wait and retry the request.

HTTP Status Code: 400

InvalidSubnet

The requested subnet is not valid, or not all of the subnets are in the same VPC.

HTTP Status Code: 400

SubnetAlreadyInUse

A specified subnet is already in use by another cluster.

HTTP Status Code: 400

UnauthorizedOperation

Your account is not authorized to perform the requested operation.

HTTP Status Code: 400

See Also

For more information about using this API in one of the language-specific AWS SDKs, see the following: