Deploying Everpure Cloud Dedicated for GUI

Deploy Everpure Cloud Dedicated from the AWS Marketplace.

1. Go to the AWS Marketplace deployment listing for Everpure Cloud Dedicated.

Note: GovCloud customers will need to first log on to the commercial AWS account that is associated with the GovCloud account and then search for "Everpure Cloud Dedicated" in the AWS Marketplace.

1. In the listing, click Continue to Subscribe.

   

2. Click Continue to Configuration.

   

3. Select your desired version, region and click Continue to Launch.

   

4. Review the selections and click Launch. This launches the AWS CloudFormation stack creation service.

   

5. The CloudFormation stack creation wizard should appear with all the template options pre-selected. Click Next to proceed.

   

6. Enter the required information for your Everpure Cloud Dedicated instance:
7. Enter a Stack name. Stack name is for your Everpure Cloud Dedicated deployment.
8. Enter an ArrayName. ArrayName name is for your virtual appliance and is reflected in the name of the EC2 instances.
9. Enter the RelayHost domain name. RelayHost is your domain name and can be modified later using the Everpure Cloud Dedicated GUI or CLI. Example: purestorage.com
10. Select the PurityInstanceType. PurityInstanceType is the desired Everpure Cloud Dedicated model. You can view the model sizes and details in the Everpure Cloud Dedicated Support Matrix.
11. Enter the LicenseKey. You receive the license key when you create the subscription through a Evergreen//One subscription or the AWS Marketplace.
12. (Optional) In the AlertRecipients field, enter a comma-separated list of email contacts to receive email alerts. You can modify this later using the Everpure Cloud Dedicated GUI or CLI.
13. Select a KeyName. KeyName is the name of an existing AWS Key Pair you wish to use for SSH access.
14. Select the SystemSubnet. SystemSubnet is a private subnet for the system interfaces and requires internet access. Refer to the Network Section for details and network options.
15. Select the ReplicationSubnet. ReplicationSubnet is a private subnet for the Replication interfaces. Refer to the Network Section for details and network options.
16. Select the iSCSISubnet. iSCSISubnet is a private subnet for the iSCSI interfaces. Refer to the Network Section for details and network options.
17. Select the ManagementSubnet. ManagementSubnet is a private subnet for the management interfaces. Refer to the Network Section for details and network options.
18. Select the ReplicationSecurityGroup. ReplicationSecurityGroup allows both inbound and outbound TCP traffic on ports 8117. Refer to Security Group for details.
19. Select the iSCSISecurityGroup. iSCSISecurityGroup security group allows inbound TCP traffic on ports 3260. Refer to Security Group for details.
20. Select the ManagementSecurityGroup. ManagementSecurityGroup allows inbound TCP traffic on ports 22, 80, 8084 as well as inbound/outbound on port 443. Refer to Security Group for details.
21. Select the InstanceTenancy. Default tenancy uses on-demand or reserved shared instances. Dedicated tenancy uses instances that run on hardware dedicated to a single customer's account. Refer to EC2 Instance Tenancy for details.
22. (Optional) Select the EncryptionVolumeWIthDefaultKey. If false (by default) encrypts the attached EBS volumes with the regional AWS managed keys. If true encrypts EBS volumes with customer-managed keys. Refer to Encryption Section for details.
23. Keep the default values for the remaining fields and move to the next step.

    

24. Click Next.
25. Select Stack Options:
    1. (Optional) Apply tags for the Everpure Cloud Dedicated resources.
    2. (Mandatory) Select the IAM Role: PurityServiceRole. Creating this role is a pre-requisite. See IAM Role and Permission for details. This step is required to ensure future capacity upgrades can occur.
    3. In the Stack creation options section, set Termination protection to Enabled.
       Note:

       The IAM role selection is required to deploy Everpure Cloud Dedicated successfully as well as to upgrade or terminate Everpure Cloud Dedicated in the future.

       

26. Click Next .

27. Review the selected parameters. Scroll to the bottom of the page and check the acknowledge box.

28. Click Create stack.

    

29. The Everpure Cloud Dedicated stack takes approximately ten minutes to complete. When complete, the stack should appear with CREATE_COMPLETE status

    

Enabling AWS CloudTrail (Optional)

AWS CloudTrail is a tool used to monitor and log event history in AWS accounts. Customers should use CloudTrail for tracking account activity, troubleshooting issues, and investigating security breaches in their AWS accounts. CloudTrail can also be integrated with other services to trigger actions such as sending alerts.

By default, CloudTrail stores logs for events in the AWS account for 90 days. Customers who wish to store logs for longer than 90 days should create a trail, and specify an S3 bucket where CloudTrail can store logs.

When creating a trail, Pure recommend selecting default options for everything, unless you have a specific reason to select a different option. If you have Everpure Cloud Dedicated instances running in more than one region, be sure to select the option to enable CloudTrail in all regions in the account; not just the current region.

It is important to note that CloudTrail allows for the logging of two type of events: management events and data events. Management events are enabled by default. For data events, CloudTrail allows for the logging of API calls (PUTS/GETS) to Amazon S3. By default, data events for S3 buckets are not enabled.

• If customers do enable logging of data events for S3, Pure recommends customers exclude logging data events by Everpure Cloud Dedicated to its associated S3 bucket. Customers can do this by excluding the Everpure Cloud Dedicated S3 bucket from the data event of a CloudTrail configuration.

For more details on CloudTrail, please check out https://aws.amazon.com/cloudtrail/.