-
Everpure Cloud Dedicated require an outbound Internet connectivity. Internet connectivity ensures that Everpure Cloud Dedicated can phone home to Pure1 providing logs, alerts, give Pure storage support access and additional cloud management services.
-
In general, we recommend to launch the Purity instance in private subnet with a route to NAT gateway configured in adjoining public subnet. This will provide a route out to the Internet via an Internet Gateway in the public subnet.
-
For PhoneHome connectivity, a Management Security Group needs to be created before Everpure Cloud Dedicated deployment. This security group which contains inbound and outbound rules will be attached to the management ENI (Elastic Network Interface) and will allow Pure1 PhoneHome and Remote Assist connectivity from the Everpure Cloud Dedicated instance. Refer to this guide on how to configure Management Security Group.
General Pure1 PhoneHome Connectivity Requirements
If you are using Network ACLs, you will have to create rules allowing access to the Pure1 Phonehome CIDR block shown below. The rules should be the same as what the Pure Management Security Group in the PAWS Service Catalog template allows.
|
Transport protocol (non-RA): |
HTTPS with 2-way mutual TLS authentication |
|
Application protocol (non-RA): |
REST |
|
RA protocol: |
SSH over HTTPS with 2-way mutual TLS authentication |
|
Client authentication: |
Unique certificate |
|
Server authentication: |
Server certificate verified on the array |
|
Endpoint: |
*.cloud-support.purestorage.com |
|
IPs: |
52.40.255.224/27 |
|
Port(s): |
443 |