Can’t access VPC to launch my Amazon Redshift cluster? We can help you.

At Bobcares we assist our customers with several AWS queries as part of our AWS Support Services for AWS users, and online service providers.

Today, let us discuss how to resolve this Redshift error.

Can’t access VPC to launch my Amazon Redshift cluster

 
Usually, issue might occur due to below reasons:

• The VPC doesn’t exist in the same Region that you’re trying to create your Amazon Redshift cluster in.
• The VPC isn’t associate with a cluster subnet group.

How to resolve it?

 
Today, let us see the steps followed by our Support techs to access your VPC in Amazon Redshift:

1.Firstly, create a VPC in the same Region that you want to launch an Amazon Redshift cluster.

2.Then, create a cluster subnet group.

3.Launch an Amazon Redshift cluster into the VPC. In the Additional configurations section, switch off Use defaults. Then, choose the VPC that you want from the drop-down list.

Creating a cluster subnet group

 
You must have at least one cluster subnet group defined to provision a cluster in a VPC.

In order to create a cluster subnet group follow below steps:

1.Firstly, sign in to the AWS Management Console and open the Amazon Redshift console at https://console.aws.amazon.com/redshift/.
2.On the navigation menu, choose CONFIG, then choose Subnet groups. The list of subnet groups is displayed.
3.Then, choose Create cluster subnet group to display the create page.
4.Enter information for the subnet group, including which subnets to add.
5.Finally, choose Create cluster subnet group to create the group with the subnets that you chose.

[Need help with the Amazon error? We’d be happy to assist]

Conclusion

 
In short, today we saw how our  Support Techs resolve this Redshift error.