W E K A
3.14
3.14
  • WEKA v3.14 Documentation
  • Weka System Overview
    • About the WEKA System
    • SSD Capacity Management
    • Filesystems, Object Stores & Filesystem Groups
    • Weka Networking
    • Data Lifecycle Management
    • Weka Client & Mount Modes
    • Glossary
  • Getting Started with Weka
    • Quick Install Guide
    • Managing the Weka System
    • CLI Overview
    • GUI Overview
    • Serving IOs with WekaFS
  • Planning & Installation
    • Prerequisites for Installation
    • Bare Metal Installation
      • Planning a Weka System Installation
      • Setting Up the Hosts
        • SR-IOV Enablement
      • Obtaining the Weka Install File
      • Weka System Installation Process Using the CLI
      • Adding Clients
    • AWS Installation
      • Self-Service Portal
      • CloudFormation Template Generator
      • Deployment Types
      • AWS Outposts Deployment
      • Supported EC2 Instance Types
      • Adding Clients
      • Auto Scaling Group
      • Troubleshooting
  • Performance
    • Testing Weka Performance
      • Test Environment Details
  • WekaFS Filesystems
    • Managing Filesystems, Object Stores & Filesystem Groups
      • Managing Object Stores
      • Managing Filesystem Groups
      • Managing Filesystems
      • Attaching/Detaching Object Stores to/from Filesystems
      • KMS Management
    • Advanced Data Lifecycle Management
      • Advanced Time-based Policies for Data Storage Location
      • Data Management in Tiered Filesystems
      • Transition Between Tiered and SSD-Only Filesystems
      • Manual fetch and release of data
    • Mounting Filesystems
    • Snapshots
    • Snap-To-Object
    • Quota Management
  • Additional Protocols
    • NFS
    • SMB
      • SMB Management Using CLIs
      • SMB Management Using the GUI
    • S3
      • S3 Cluster Management
      • S3 Buckets Management
      • S3 Users and Authentication
      • S3 Information Lifecycle Management
      • Audit S3 APIs
      • S3 Limitations
      • S3 Examples using boto3
  • Operation Guide
    • Alerts
      • List of Alerts
    • Events
      • List of Events
    • Statistics
      • List of Statistics
    • System Congestion
    • Security
      • User Management
      • Organizations
    • Expanding & Shrinking Cluster Resources
      • Expand & Shrink Overview
      • Stages in Adding a Backend Host
      • Expansion of Specific Resources
      • Shrinking a Cluster
    • Background Tasks
    • Upgrading Weka Versions
  • Billing & Licensing
    • License Overview
    • Classic License
    • Pay-As-You-Go License
  • Support
    • Prerequisites and Compatibility
    • Getting Support for Your Weka System
    • The Weka Support Cloud
    • Diagnostics CLI Command
  • Appendix
    • Weka CSI Plugin
    • External Monitoring
    • Snapshot Management
  • REST API
Powered by GitBook
On this page
  • Before You Begin
  • Best Practices
  • Backup and Recovery
  • SSH Keys Rotation
  1. Planning & Installation

AWS Installation

This section provides the detailed instructions on how to install a Weka filesystem in AWS.

PreviousAdding ClientsNextSelf-Service Portal

Last updated 3 years ago

Before You Begin

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 .

You should be familiar with the following concepts and services that will be used as part of the Weka cluster deployment:

  • - Identity and access management

  • , and

  • instances and

  • - Object storage (to be used for tiering data)

The following diagram illustrates the components of deployment in AWS:

Best Practices

Backup and Recovery

Resiliency

Instance Failure

Upload Snapshots to S3

Cross AZ Failure

Region Failure

The use of Weka snapshots uploaded to S3 combined with S3 cross-region replication enables the protection from an AWS region failure.

SSH Keys Rotation

For security reasons, it is advisable to rotate the SSH keys used for the EC2 instances.

The Weka system is a distributed cluster protected from 2 or 4 failure domains failures, providing fast rebuild times as described in the section.

In case of an instance failure, the Weka system will the data. To regain the reduced compute and storage due to the instance failure to the cluster, .

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 () 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 or 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.

Refer to .

To rotate the SSH keys, follow these steps as described in and .

Self-Service Portal
CloudFormation
Adding or replacing a key pair for your instance
How to use AWS Secrets Manager to securely store and rotate SSH key pairs
create an AWS account
IAM
VPCs
subnets
security groups
EC2
ssh keys
S3
Cloud Formation
add a new instance to the cluster
Weka system overview
rebuild
Snap-To-Object
Protecting Data Against AWS Availability Zone Failures
AWS Architecture Diagram