Troubleshooting

Everpure Cloud Dedicated for AWS
Audience
Public
Technology Integrations
Amazon Web Services (AWS)
Source Type
Documentation

Overview

Everpure Cloud Dedicated for AWS is a software-defined storage service powered by the Purity Operating Environment and deployed in an Amazon VPC using native AWS resources. It delivers enterprise data services such as data reduction, snapshots, encryption, and replication, while preserving common operational workflows across on-premises FlashArray and AWS deployments.

This troubleshooting page is intended to help operators quickly determine whether an issue is rooted in the Everpure Cloud Dedicated deployment itself, the surrounding AWS networking and infrastructure, or the backend resources that support the array. For AWS-based deployments, troubleshooting can extend beyond the array and into services such as CloudFormation and CloudWatch.

Key Benefits

Everpure Cloud Dedicated for AWS gives teams a consistent storage operations model across on-premises and cloud environments, including the same GUI, CLI, and API-driven workflows used with FlashArray. That consistency reduces the time required to isolate issues and helps teams distinguish between storage configuration problems and AWS infrastructure issues, especially because virtual drive failures in AWS can surface as EC2 or platform-level problems rather than traditional hardware failures.

Audience & Use Cases

This page is for cloud administrators, storage administrators, platform engineers, and support teams responsible for deploying or operating Everpure Cloud Dedicated for AWS in Amazon VPCs. Use it when validating prerequisites, reviewing deployment readiness, checking network and security configuration, investigating controller or virtual drive behavior, or collecting the right data before escalating to support.

How it Works

  1. Validate that the target AWS region, availability zone, instance availability, and deployment prerequisites are supported before you begin deeper troubleshooting.
  2. Review the deployment path and stack state in AWS Marketplace and CloudFormation to confirm that the base deployment completed successfully.
  3. Verify networking across the system, replication, iSCSI, and management interfaces, including private subnets, required security groups, DNS, and outbound internet access for the system subnet.
  4. Check AWS-side dependencies such as VPC endpoints, CloudWatch, and CloudFormation when symptoms point outside the array itself.
  5. If the issue persists, gather logs and escalate with the appropriate troubleshooting data so support can continue the investigation efficiently.

Prerequisites

Before troubleshooting or deploying Everpure Cloud Dedicated for AWS, make sure the environment meets the current support matrix for region and required AWS resources. Some otherwise supported regions still have availability zones that do not provide the required c5n.9xlarge and c5n.18xlarge instances, so availability must be validated at the AZ level as well.

At minimum, the deployment prerequisites include a VPC with private and public subnets, VPC endpoints for Amazon S3 and DynamoDB, security groups for iSCSI, management, and replication, an IAM role with sufficient permissions, an EC2 key pair, a license key, and the AWS account ID added to Pure1.

All Everpure Cloud Dedicated subnets must be private, the system subnet must have outbound internet access, and VPC DNS resolution must be enabled. For IP planning, a new deployment requires 20 initial private IP addresses, and a capacity upgrade requires seven additional private IP addresses from the system subnet.

If you are deploying with Terraform, you also need Terraform, the AWS CLI, and the Everpure Cloud Dedicated Terraform provider configured on the host used for deployment.

Deployment

To start building, go to the AWS Marketplace listing for Pure Storage Cloud Dedicated, click Continue to Subscribe, then Continue to Configuration, choose the version and region, click Continue to Launch, and then Launch to open the AWS CloudFormation stack creation workflow. From there, step through the template, provide the required array, networking, security, and licensing values, select the mandatory IAM role, and create the stack.

Additional Information