Please enter search query.
Search <book_title>...
Veritas InfoScale™ 8.0.1 Solutions in Cloud Environments
Last Published:
2022-05-19
Product(s):
InfoScale & Storage Foundation (8.0.1)
Platform: Windows
- Overview and preparation
- Configurations for Amazon Web Services - Windows
- Replication configurations in AWS - Windows
- HA and DR configurations in AWS - Windows
- Failover within a subnet of an AWS AZ using virtual private IP - Windows
- Failover across AWS subnets using overlay IP - Windows
- Public access to InfoScale cluster nodes in AWS using Elastic IP - Windows
- DR from on-premises to AWS and across AWS regions or VPCs - Windows
- DR from on-premises to AWS - Windows
- Configurations for Microsoft Azure - Windows
- Replication to and across cloud environments
VPC security groups example
A security group acts as a virtual firewall for the instance to control inbound and outbound traffic. Therefore, you must make sure that in cluster configuration, ports are enabled in the security groups so that the VMs can communicate with each others.
Consider an example with two VMs that uses two subnets:
Subnet 1: 172.17.1.0/24
Subnet 2: 172.17.2.0/24
With this setup, the following table describes the inbound rules for a security group.
Inbound rules Type Protocol Port range Source ALL UDP UDP 0-65535 172.17.1.0/24 All UDP UDP 0-65535 172.17.2.0/24
This table indicates that the inbound traffic is allowed between the instances that are assigned to the security group.