Usually, Datacoral is responsible for creating the VPC in which all its resources get created, ensuring network isolation for the Datacoral installation.
In certain cases, you might want to use an existing VPC (perhaps an analytics VPC that you already have) or create a new VPC using your devops process for the Datacoral installation instead of relying on Datacoral to do it for you. If you are creating a new VPC, please review the VPC Creation CloudFormation template that we recommend. See here for full instructions on creating a VPC for Datacoral (with all the configurations needed for a successful installation).
In either case, Datacoral needs you to provide information about the VPC where you need Datacoral's installation to be spun up. Information for existing VPC required during installation is in the screenshot below.
In addition, if the Datacoral VPC is different than the VPC with your other resources like Postgres, MySQL, Mongodb databases that you are syncing data from or your Redshift cluster where you are syncing data to, you can use VPC peering to enable Datacoral to connect to the databases or Redshift.
Please see VPC peering for how to setup and test VPC Peering connections between your Datacoral VPC and your existing VPC with other resources .