If you already have an AWS account and are familiar with AWS's basic concept and services you can skip this section.
To deploy a Weka cluster in AWS, you will need to create an AWS account.
You should be familiar with the following concepts and services that will be used as part of the Weka cluster deployment:
The following diagram illustrates the components of deployment in AWS:
The Weka system is a distributed cluster protected from 2 or 4 failure domains failures, providing fast rebuild times as described in the Weka system overview section.
It is advisable to use periodic (incremental) snapshots to back-up the data and protect from multiple EC2 instances failures. The recovery point objective (RPO) would be determined by the cadence in which the snapshots are taken and uploaded to S3. The RPO changes between the type of data, regulations, and company policies, but it is advisable to upload at least daily snapshots (Snap-To-Object) of the critical filesystems.
In case of a failure and a need to recover from a backup, it is just a matter of spinning up a cluster using the Self-Service Portal or CloudFormation and creating filesystems from those snapshots. There is no need to wait for the data to reach the EC2 volumes. It is instantly accessible via S3. The recovery time objective (RTO) for this operation mainly depends on the time it takes to deploy the CloudFormation stack and will typically be below 30 min.
The use of Weka snapshots uploaded to S3 combined with S3 cross-region replication enables the protection from an AWS region failure.
For security reasons, it is advisable to rotate the SSH keys used for the EC2 instances.
To rotate the SSH keys, follow these steps as described in Adding or replacing a key pair for your instance and How to use AWS Secrets Manager to securely store and rotate SSH key pairs.