Create Redshift-managed VPC endpoint

Question

I'm trying to create an endpoint for a Redshift serverless cluster in a different account, I granted access to it to the new account and in the form for creating the endpoint (see image I can see in selector the account and cluster, but after clicking create I'm getting "The specified cluster identifier can't be found."

Any idea what could be the reason?

I tried from two different places, from the Configuration -> Create endpoint page and from Clusters -> From other accounts page - both goth the same error.

Enter image description here

Any idea what could be the reason?

I tried from two different places, from the Configuration -> Create endpoint page and from Clusters -> From other accounts page - both goth the same error.

![Enter image description here](/media/postImages/original/IMviVbhWzwRzeAqPdgyoUfbw)

Yaniv Rozenboim · Accepted Answer

The screenshot you attached refers to the menu for creating VPC endpoint to access Redshift Cluster (non-Serverless).

For Serverless you need to navigate to:

Amazon Redshift Serverless -> Workgroup configuration ->  -> Data access (tab) -> Redshift-managed VPC endpoints -> Create Endpoint

From the [documentation](https://docs.aws.amazon.com/redshift/latest/mgmt/managing-cluster-cross-vpc-console-grantee.html):
> For Amazon Redshift Serverless, the VPC endpoints are under the Data access tab, when you choose the workgroup.

re:Post Agent · Answer

The error you're encountering suggests there might be a mismatch or issue with the cluster identifier when creating the Redshift-managed VPC endpoint. Here are a few potential reasons and steps to troubleshoot:

1. Ensure that the cluster identifier you're using is correct and matches exactly with the one in the source account. Even small discrepancies in spelling or capitalization can cause this error.

2. Verify that you have the necessary permissions in both accounts. In the account that owns the Redshift cluster (the grantor account), make sure you've properly granted access to the account that's creating the endpoint (the grantee account).

3. Check if the Redshift cluster is in an available state. If the cluster is in a transitioning state or has any issues, it might not be discoverable when creating the endpoint.

4. Confirm that you're creating the endpoint in the same AWS region as the Redshift cluster. Cross-region endpoints are not supported for Redshift-managed VPC endpoints.

5. If you're using a Redshift Serverless workgroup, ensure you're selecting the correct workgroup name instead of a cluster identifier, as Serverless uses workgroups rather than traditional clusters.

6. Try creating the endpoint using the AWS CLI or SDK instead of the console. Sometimes, this can provide more detailed error messages that can help identify the root cause.

7. If the issue persists, you may need to contact AWS support for further assistance, as there could be an underlying problem with the cross-account access configuration.

Remember, when creating a Redshift-managed VPC endpoint, you need to provide the endpoint name, your AWS account ID, the VPC where the endpoint will be located, the subnet, and the VPC security group. Double-check all these details to ensure they're correct.  
**Sources**  
[Creating a Redshift-managed VPC endpoint - Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/mgmt/managing-cluster-cross-vpc-console-grantee.html)  
[CreateEndpointAccess - Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/APIReference/API_CreateEndpointAccess.html)  
[Achieve peak performance and boost scalability using multiple Amazon Redshift serverless workgroups and Network Load Balancer | AWS Big Data Blog](https://aws.amazon.com/blogs/big-data/achieve-peak-performance-and-boost-scalability-using-multiple-amazon-redshift-serverless-workgroups-and-network-load-balancer/)

Create Redshift-managed VPC endpoint

Relevant content