Tagged in

aws

Rubrik -  - Automating CloudOut to Amazon S3 Configuration

Product

Automating CloudOut to Amazon S3 Configuration

The ability to archive data to Amazon S3 has been part of the Rubrik platform since our very first product release. This feature, CloudOut, automates lifecycle management by archiving older, mostly unused data to public cloud storage tiers. Using public cloud is often more cost effective and reliable than tape for long-term data retention and has been widely adopted by Rubrik customers.  More details about designing a CloudOut to S3 solution can be found in this blog post.  Preparing your AWS environment for CloudOut is not necessarily difficult, but leveraging automation enables consistent configuration when there are several archive locations. Automating the process utilizing the tools described below not only decreases the chance of error and saves valuable time, but also helps prevent misconfiguration and supports a more reliable and consistent environment.  For these reasons, many of our customers automate the configuration of their AWS environment for CloudOut. The Rubrik Cluster’s archival settings can also be configured using an automation tool. This blog post will cover automating CloudOut to S3 resource configuration using the tools our customers most commonly use: AWS CloudFormation, Ansible, and Terraform. Automation with AWS CloudFormation AWS CloudFormation provides a common language to model and provision all…
Rubrik -  - Designing A CloudOut to Amazon S3 Solution

Product

Designing A CloudOut to Amazon S3 Solution

The majority of Rubrik customers take advantage of our CloudOut capability to archive backup data to a public cloud service provider, often as a replacement for tape. Cloud offers better response times than tape in the event that you must restore data from archive. This solution provides a cost-effective approach and reliable long-term retention. Through the lens of Zaffre Fashion Group (Zaffre), our own field-tested fictional enterprise based on how customers commonly use our product, we’ll examine how a CloudOut to Amazon S3 solution can be architected. Solution Overview As part of their cloud-first strategy, Zaffre leverages CloudOut to support compliance, eliminate tape, and meet long-term retention requirements. Cloud adoption efforts began in 2017 by selecting AWS as the cloud archive location to store on-premises data for a regulatory period.  The long-term retention location is specified as a cloud archive within the Rubrik SLA Domain. This means that once a workload is protected, Rubrik automatically ensures that: Snapshots that have exceeded their local retention threshold are marked for archive. Snapshots and metadata are uploaded to the archive location. Snapshots are marked for expiry once the archive retention threshold is exceeded. Archive consolidation efficiently manages and removes expired snapshots. The following…
Rubrik -  - How to Design Cloud-Native Application Protection for AWS

Product

How to Design Cloud-Native Application Protection for AWS

Designing enterprise architecture is a tough job at any scale. It requires wearing numerous strategic and tactical hats across business and technology subject matters. And, on top of that, days are often filled with never-ending meetings where your mood can be surprisingly dictated by participants’ virtual backgrounds–from tranquil beaches to Brady Bunch. Cloud computing has added interesting wrinkles to the role of an Enterprise Architect (EA). Whereas prior years were focused on data center layout and infrastructure deployments, modern times have pivoted towards an entirely new way of constructing services. Today’s challenges combine a heavy mixture of cloud-native applications, continuous integration and delivery pipelines, API contracts, tag-based governance, service meshes, and other developer-centric frameworks being stitched into on-premises environments to create a hybrid cloud. From Infrastructure to Platforms I consider cloud a sunset for infrastructure engineering and a dawn for platform development. EAs are asked to evaluate migrating “old but financially relevant” on-premises infrastructure and applications into the cloud. Many of these solutions carry baggage from years of updates and redesigns. Getting them to play nicely with the hip, shiny cloud-native applications and services is a golden opportunity. Paying down technical debt or removing some oddball design created by an…
Rubrik -  - Helping Customers with Their Cloud Journey

Product

Helping Customers with Their Cloud Journey

There was a time not so long ago when adopting the public cloud was considered too big of a risk for the enterprise. Today, enterprises are seeing public cloud vendors as strategic partners and exploring new ways to leverage the innovation, agility, and scale of providers like Amazon Web Services (AWS), Microsoft Azure, and Google Cloud. Tim Carr explains how enterprises are embracing the public cloud in a phased approach in this Gestalt IT blog post.  Source: Can a Backup Appliance Really Help your Enterprise Cloud Strategy? – Part 2 These cloud journey phases often look like this: Phase 1: Leverage basic public cloud services that require minimal changes to current workloads or processes. Phase 2: Build out an infrastructure using public cloud resources for new workloads or migrating existing on-premises workloads. Phase 3: Refactor applications to take advantage of public cloud scale and innovations, including more advanced public cloud services. Rubrik was born in the cloud era providing a web-scale platform from day one. Our very first product natively integrated with AWS with a hybrid-cloud operating model, and we’re taking that journey with you. The platform use cases expand as you move up the pyramid of phases in Tim’s diagram…
Rubrik -  - Auto-Protect and Cross-Region Replication Using AWS Tags

Product

Auto-Protect and Cross-Region Replication Using AWS Tags

Rubrik Polaris, our innovative SaaS platform, delivers a new breed of data management applications designed to tackle data fragmentation and simplify protection across data centers and clouds.  Many customers who have adopted Polaris leverage the platform for their AWS workloads and are continuing to look for ways to increase automation and ditch manual tasks and ad-hoc scripts.  In response to these needs, Polaris now has the ability to protect Amazon Elastic Compute Cloud (EC2) instances and Amazon Elastic Block Store (EBS) volumes automatically upon creation through the use of snapshots. Once these snapshots have been taken, they can be configured to replicate automatically to another AWS Region. Auto-Protecting Using AWS Tags When speaking with our customers, we found that many want the ability to automatically apply appropriate protection policies to resources whenever an Amazon EC2 instance or Amazon EBS volume is created. By leveraging AWS tags, Polaris gives users the flexibility to determine precisely which resources to protect and when they should be protected. Polaris makes setting up auto-protection using tags incredibly simple to implement. Users simply need to create a tag rule in the Polaris dashboard that specifies the: tag to monitor. AWS account to manage. SLA Domain that…
Rubrik -  - Deploying a Secure Data Protection as a Service Solution with Rubrik Polaris

Product

Deploying a Secure Data Protection as a Service Solution with Rubrik Polaris

Cloud security is one of the topics du jour in the enterprise IT space. In fact, it’s a big enough topic that Amazon Web Services (AWS) hosted their own security conference, AWS re:Inforce, back in June. It highlights the challenge with securing your data in the cloud,  especially if you are using tools and approaches that were not designed for security from the start. Not adhering to good security practices exposes cloud customers to the potential risk of being hacked and having data stolen. To assist customers and partners with building secure solutions, AWS has codified recommended practices and principles into the security pillar of their AWS Well-Architected Framework. The Well-Architected Framework is a tool for evaluating the soundness of any solution running on AWS and leveraging their services. The framework is comprised of five conceptual areas called pillars, including the security pillar.  So where does Rubrik Polaris fit into this picture? We previously announced the general availability of AWS native protection support in Rubrik Polaris, our Software-as-a-Service (SaaS) platform for cloud data management. Now, we want to explore how Polaris is able to build a secure solution for protecting Amazon EC2 instances and Amazon EBS volumes using the recommended…
Rubrik -  - Managing Encrypted AWS Snapshots with Rubrik Polaris

Product

Managing Encrypted AWS Snapshots with Rubrik Polaris

Werner Vogels, CTO of AWS, has taken to wearing a T-shirt during his recent keynote speeches with the admonition, Encrypt Everything. This statement highlights the growing concerns over unauthorized access of data and regulations like the General Data Protection Regulation. Encrypting everything  is no longer just a nice-have, it’s a must-have for any business with workloads running in a public cloud. The challenge for most customers is knowing what encryption method to choose and how to properly manage their encryption keys. Making the wrong choices can leave a customer’s data as unprotected as it would be with no encryption at all. AWS, as well as other cloud providers, offers a number of options for simplifying the encryption of data in transit and at rest. This includes the capability to encrypt data stored in a customer’s Amazon Elastic Block Storage (EBS) volumes. This feature can be enabled with a check of a box, and the encryption is automatically handled using the AWS Key Management Service (KMS). To ensure end-to-end encryption, including when a snapshot of an Amazon EBS volume is taken and backed up, AWS will automatically encrypt the snapshot of any encrypted Amazon EBS volume. Supporting this capability is now…
Rubrik -  - Simplifying AWS Native Protection with Rubrik Polaris

Product

Simplifying AWS Native Protection with Rubrik Polaris

Why Polaris for AWS? Last year, Rubrik introduced the world to Polaris, our innovative SaaS offering for a new breed of data management apps. Our first Polaris app was Polaris GPS, which provides customers with centralized management and monitoring of their globally-distributed Rubrik infrastructure. We quickly followed that up with our second application, Polaris Radar, which leverages machine learning to help customers detect and recover from ransomware. However, with organizations driving cloud adoption more and more, we always knew protecting workloads running in the cloud would be a key focus of Polaris. We spearheaded these efforts with Office 365 protection in our Andes release. This was just the beginning, and I’m happy to announce that Rubrik has now released native protection for Amazon Web Service (AWS) workloads using Polaris. Building on the capabilities of our flagship Cloud Data Management (CDM) product, Polaris integrates with the native snapshot capabilities and APIs provided by AWS for protecting Amazon EC2 instances and Amazon EBS volumes. This tight integration provides Rubrik customers with a central point of management to address various data protection use cases. Why should customers use Polaris to protect Amazon EC2 and Amazon EBS? As a SaaS solution, Polaris provides many…
Rubrik -  - Tech Walkthrough: Amazon EC2 Protection with Rubrik

Product

Tech Walkthrough: Amazon EC2 Protection with Rubrik

In a previous post, I previewed Rubrik’s support for Amazon Elastic Compute Cloud (EC2) native protection, and it’s been rewarding seeing customers use this capability to protect their AWS workloads. With the exciting announcements recently revealed at AWS re:Invent, this is a good time to walk through some of Rubrik’s Amazon EC2 protection capabilities. Prerequisites First thing you’ll need is an AWS account with some Amazon EC2 instances launched and running in one or more AWS Regions. Note that these instances must be using Amazon Elastic Block Storage (EBS) volumes since Rubrik will be leveraging Amazon EBS snapshots for data protection. On the Rubrik side, you’ll need either a Rubrik instance running on-premises with network connectivity to AWS or a Rubrik Cloud Cluster with access to your AWS account. There is also some preliminary configuration work, detailed in Rubrik documentation, that has to be completed before we can start managing native Amazon EC2 protection: Identify a Virtual Private Cloud (VPC) and Subnet where the transient Rubirk EC2 instance will be launched. This Rubrik instance will be used for the indexing of Amazon EBS snapshots. Create a Security Group that allows inbound access over TCP through ports 2002 and 7780. This…