Frequently Asked Questions

Product Information & Use Cases

What is AWS ephemeral storage and how does it differ from persistent storage options like EBS or S3?

AWS ephemeral storage, also known as EC2 instance store, is a temporary block-level storage physically attached to an EC2 instance. It is ideal for use cases where data persistence is not required, such as caching, buffer data, or temporary analytics. In contrast, persistent storage options like Amazon EBS, S3, and EFS are designed to retain data through instance failures and restarts, making them suitable for databases, backups, and long-term storage. Note: Data on ephemeral storage is lost if the instance is stopped, terminated, or if hardware fails, so it is not suitable for critical or long-term data retention.

What are the main use cases for AWS ephemeral storage?

Ephemeral storage is best suited for storing cached data or logs, buffer data for temporary analytics (such as Hadoop jobs), and as a root volume for instances under a load balancer where data persistence is not required. It is also used to reduce costs, as instance store volumes do not incur additional storage charges. Note: Because ephemeral storage is temporary, it should not be used for critical data unless regular backups to persistent storage are performed.

What are the risks and limitations of using AWS ephemeral storage?

Ephemeral storage is temporary and data will be lost if the EC2 instance is stopped, terminated, or if there is a hardware failure. Additionally, if the instance store is attached as an additional volume to an EBS-backed instance for temporary storage, every start and stop of the instance will reset the data. Note: Ephemeral storage is not suitable for critical or long-term data; regular backups to persistent storage are required to avoid data loss.

How does the performance of AWS ephemeral storage compare to EBS-SSD?

According to tests performed by AWS community professionals, instance store (ephemeral storage) is over 5x faster than EBS-SSD for uncached reads and over 10x faster for writes. This makes ephemeral storage optimal for high-performance workloads like MySQL databases where speed is critical. Note: Despite the performance benefits, data on ephemeral storage is not persistent and must be backed up regularly to avoid loss.

How can I back up data from AWS ephemeral storage to persistent storage using N2WS?

To back up data from ephemeral storage (instance store) to persistent storage (EBS) using N2WS, you can follow these steps: 1) Create an EC2 instance with an instance store volume attached; 2) Set up your application or database (e.g., MySQL) on the instance store; 3) Attach an EBS volume to the same instance; 4) Use a pre-backup script in N2WS to copy data from the instance store to the EBS volume before backup; 5) Configure N2WS to automate EBS backups. Note: This process ensures that temporary data is preserved, but requires careful planning and scripting to avoid data loss.

Features & Capabilities

What features does N2WS offer for backup and disaster recovery?

N2WS provides automated backup and recovery for AWS, Azure, and hybrid cloud environments, near-instant recovery, immutable backups, cross-cloud recovery, granular restore (file/folder/environment), intelligent storage tiering, custom disaster recovery retention policies, multi-tenancy for MSPs, and automated compliance reporting. Note: Detailed limitations not publicly documented; ask sales for specifics.

Does N2WS support automation and integrations with other tools?

Yes, N2WS offers a RESTful API for custom integrations and automation of tasks such as user onboarding and backup management. It also provides CLI access and integrates with third-party monitoring tools like Datadog, Splunk, and Bocada, as well as various data management and reporting tools. Note: Some integrations may require additional configuration or licensing; see the pricing page for details.

What technical documentation is available for N2WS users?

N2WS provides comprehensive user guides, release notes, RESTful API documentation, upgrade guides, and IAM permission files. These resources cover deployment, configuration, management, and integration best practices. Access the documentation at docs.n2ws.com/user-guide. Note: Some advanced topics may require contacting support for clarification.

Security & Compliance

What security and compliance certifications does N2WS have?

N2WS is independently certified for ISO/IEC 27001:2022 and is SOC compliant by inheritance, leveraging AWS and Azure compliance features. It also supports compliance with HIPAA, GDPR, FedRAMP, ITAR, and CJIS. Customers can request a copy of the ISO certificate by contacting customer.success@n2ws.com. Note: For the latest compliance status, visit the N2WS Trust Center.

What security features does N2WS provide to protect backups?

N2WS offers immutable, air-gapped backups, end-to-end TLS/HTTPS encryption, multi-factor authentication (MFA), and compliance mode immutability. Backups never leave your cloud environment, ensuring data sovereignty. Note: Some advanced security features may require specific cloud configurations; consult documentation for details.

Implementation & Support

How long does it take to implement N2WS and how easy is it to get started?

Implementations with N2WS can be completed in as little as two weeks. Customers can deploy N2WS as an Amazon Machine Image (AMI) from AWS Marketplace or use CloudFormation templates. Dedicated Customer Success Managers, onboarding calls, and resources like video tutorials and user guides are available. A 30-day free trial is offered without requiring a credit card. Note: Implementation time may vary based on environment complexity.

What feedback have customers given about the ease of use of N2WS?

Customers have praised N2WS for its simplicity and user-friendly features. For example, Shane H, a verified customer, stated, "It's very simple to use and we are an MSP for multiple companies. Support is great and quick to respond." Julian Ware from the City of Oakland said, "You’re just clicking and going. And, to me, that’s what the modern world of backup is." Note: Some advanced configurations may require technical expertise.

Competition & Comparison

How does N2WS compare to AWS Backup?

N2WS offers immutable backups, cross-cloud recovery (AWS and Azure), granular restore (file/folder-level), custom disaster recovery retention policies, multi-tenancy for MSPs, and a RESTful API for automation. AWS Backup is limited to AWS environments, does not support immutable backups or file/folder-level recovery, and requires Lambda scripting for automation. N2WS also provides cost optimization features like intelligent storage tiering and customizable compliance reporting. Note: AWS Backup may be preferable for organizations seeking a basic, AWS-native backup solution without multi-cloud or advanced compliance needs.

Use Cases & Customer Success

Who can benefit from using N2WS?

N2WS is designed for cloud directors, IT managers, and managed service providers (MSPs) managing complex, multi-cloud environments. It is suitable for enterprises, public sector entities, healthcare, finance, retail, education, and nonprofits. Organizations with petabyte-scale data, strict compliance needs, or cost optimization goals can benefit from N2WS. Note: Smaller organizations with simple backup needs may find simpler solutions sufficient.

What are some real-world success stories of N2WS customers?

Skechers standardized backup and recovery across a multi-cloud estate, reducing costs and improving data protection. St. John's University eliminated legacy tape storage and achieved rapid recovery from accidental deletion. DB Systel (Deutsche Bahn) automated backup for thousands of routes, over 1,500 volumes, and 700 servers. The City of Oakland automated backup for critical mapping data and web applications. Gett saved 50% on cloud costs using N2WS's Resource Control. Note: Results may vary based on environment and implementation. See more case studies.

Pain Points & Business Impact

What problems does N2WS help solve for organizations?

N2WS addresses high disaster recovery costs, downtime and data loss, ransomware threats, manual backup processes, compliance challenges, complexity in multi-cloud environments, scalability for large data volumes, and long-term backup costs. Features like intelligent storage tiering can reduce long-term backup costs by up to 92%. Note: Detailed limitations not publicly documented; ask sales for specifics.

What business impact can customers expect from using N2WS?

Customers can achieve up to 92% savings on long-term backup costs, up to 50% lower compute costs, improved data protection with immutable backups, near-instant recovery, enhanced compliance with automated reporting, operational efficiency through automation, and scalability for petabyte-scale data. Note: Actual results depend on environment and usage patterns.

Backup AWS Ephemeral Storage of an EC2 Instance

A part one of the two-part blog post series describing the advantages of the AWS ephemeral storage solution. Includes reasons for choosing AWS ephemeral storage.
Share post:

Today, most cloud storage solutions are designed for persistence in order for them to be sustained through any type of failure. AWS provides distinct types of storage services that can be divided into two broader categories: persistent and ephemeral. Persistent storage is useful for Filesystem, database storage, analysis, IoT data, distribution of content, backups, and more. Amazon EBS, Amazon S3, and Amazon EFS are highly fault-tolerant persistent storage options. Amazon EC2 instance storage is an AWS ephemeral storage option. In this two-part series, we will look more closely at uses for ephemeral storage and examine a particular use case—how to back up MySQL data from the instance store storage to EBS. We will also illustrate how to automate this process using N2WS Backup & Recovery.

Why Choose Ephemeral Storage

While every organization wants their data to be persistent, there are different use cases for which having persistent data is not a priority. For organizations that place more focus on processing data than storing it, for example, the Amazon EC2 instance store (ephemeral) is the ideal option. Consider the following additional potential uses:

  • To store cached data/logs of a website or web application.
  • To store buffer data or temporary analytics calculation data, such as Hadoop jobs.
  • To achieve fault-tolerant architecture. For example, it can be used as a root volume for instances under a load balancer if you don’t need the data to persist when instances host web servers.
  • Allows the user wants to reduce costs. EBS volumes as instance store volumes do not come with additional costs for storage.

That said, there are a few challenges that come with using ephemeral storage:

  • Instance store volumes are temporary, which means that if the instance is deleted by mistake or there is a failure of hardware, whole data will be lost.
  • If the instance store is attached as an additional volume to an EBS-backed instance for temporary storage, every start and stop of the instance will reset the data.

Instance store volumes are temporary block level storage physically attached to the EC2 instance backup. These directly attached disks also are shared between multiple virtual machines on a single host. A single instance can have one or more instance store volumes attached to it. These are exposed as block devices to the instance. Volumes of these instance store range from 0-23 and are labeled as ephemeral 0 all the way to ephemeral 23. The number of devices allowed and maximum size of that instance store device depends on the type of EC2 instance. As we know, an instance store device is dedicated to a particular instance, but the disk from where that instance storage is created is shared among multiple instances as part of a virtualization technique used by AWS. The diagram below illustrates a host computer/hardware in which multiple instances share the same disk though they will have their own directly attached dedicated instance store volume provided from the same disk. Instance Store Ideology diagram As storage offered via instance store is for temporary use, to persist any data stored on it, a backup of the data on persistent storage, such as EBS, is required.

Use Case with MySQL Database

Follow the steps below:

  1. Create an EC2 instance with an instance store volume attached.
  2. Set up a MySQL database and enter some data.
  3. Attach an EBS volume to the same instance to take MySQL dumps.
  4. Write a before script in N2WS that will copy database backup to EBS directly before backup.
  5. Set up N2WS with EBS automated backup.

It is often recommended that a database should be stored on persistent storage only, but if you plan well, including for backup and limitation of ephemeral storage, you can take advantage of this type of storage, too. Instance store-backed storage is really fast in terms of reads and writes, which makes it optimal for running MySQL. Furthermore, according to tests performed by various AWS community professionals:

  • An instance store is over 5x faster than EBS-SSD for uncached reads.
  • An instance store is over 10x faster than EBS-SSD for writes.

For more about tests, check out EC2 EBS-SSD vs instance-store performance on an EBS-optimized. In part two of the series, we will demonstrate how to perform an automated backup with EBS. In part two of the series, we will demonstrate how to perform an automated backup with EBS. Try N2WS Backup & Recovery for FREE!

You might also like

the disaster-proof backup & DR checklist

What your backup plan is missing...

Fortify your backup plan across every critical dimension with this checklist.