ModifyDBSubnetGroup - Amazon Neptune
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).


Modifies an existing DB subnet group. DB subnet groups must contain at least one subnet in at least two AZs in the Amazon Region.

Request Parameters

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


The description for the DB subnet group.

Type: String

Required: No


The name for the DB subnet group. This value is stored as a lowercase string. You can't modify the default subnet group.

Constraints: Must match the name of an existing DBSubnetGroup. Must not be default.

Example: mySubnetgroup

Type: String

Required: Yes


The EC2 subnet IDs for the DB subnet group.

Type: Array of strings

Required: Yes

Response Elements

The following element is returned by the service.


Contains the details of an Amazon Neptune DB subnet group.

This data type is used as a response element in the DescribeDBSubnetGroups action.

Type: DBSubnetGroup object


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


Subnets in the DB subnet group should cover at least two Availability Zones unless there is only one Availability Zone.

HTTP Status Code: 400


DBSubnetGroupName does not refer to an existing DB subnet group.

HTTP Status Code: 404


Request would result in user exceeding the allowed number of subnets in a DB subnet groups.

HTTP Status Code: 400


The requested subnet is invalid, or multiple subnets were requested that are not all in a common VPC.

HTTP Status Code: 400


The DB subnet is already in use in the Availability Zone.

HTTP Status Code: 400

See Also

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