UpdateEndpointAccess - Amazon Redshift Serverless


Updates an Amazon Redshift Serverless managed endpoint.

Request Syntax

{ "endpointName": "string", "vpcSecurityGroupIds": [ "string" ] }

Request Parameters

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

The request accepts the following data in JSON format.


The name of the VPC endpoint to update.

Type: String

Required: Yes


The list of VPC security groups associated with the endpoint after the endpoint is modified.

Type: Array of strings

Required: No

Response Syntax

{ "endpoint": { "address": "string", "endpointArn": "string", "endpointCreateTime": "string", "endpointName": "string", "endpointStatus": "string", "port": number, "subnetIds": [ "string" ], "vpcEndpoint": { "networkInterfaces": [ { "availabilityZone": "string", "networkInterfaceId": "string", "privateIpAddress": "string", "subnetId": "string" } ], "vpcEndpointId": "string", "vpcId": "string" }, "vpcSecurityGroups": [ { "status": "string", "vpcSecurityGroupId": "string" } ], "workgroupName": "string" } }

Response Elements

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.


The updated VPC endpoint.

Type: EndpointAccess object


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


You do not have sufficient access to perform this action.

HTTP Status Code: 400


The submitted action has conflicts.

HTTP Status Code: 400


The request processing has failed because of an unknown error, exception or failure.

HTTP Status Code: 500


The resource could not be found.

HTTP Status Code: 400


The input failed to satisfy the constraints specified by an AWS service.

HTTP Status Code: 400

See Also

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