Apr11

Scylla Cloud Onboarding

Subscribe to Our Blog

Scylla Cloud Migration

We recently launched Scylla Cloud, allowing you to get the most out of Scylla while not having to burden yourself with cluster management tasks.

Worried about scaling up or out? Replacing a node? Monitoring disk usage? Scheduling and keeping an eye on repairs and backups? Taking care of various security settings? Applying hotfixes? Well have no fear! We will take care of all these concerns for you and much more.

In this blog post we will cover the initial onboarding process, including creating an account and spinning up a cluster. In another upcoming blog we will cover specific migration options you have to get your data into Scylla Cloud.

Deploy a Cluster

After you sign-up for Scylla Cloud it’s now time to sign-in and create your cluster:

  1. Set your cluster name
  2. Set the allowed IPs: your client / driver IPs (IP ranges are supported)
  3. Cloud provider is AWS, select the region for your cluster deployment
  4. Select the instance type to be used (i3 family options, or t2 for developers)
  5. Select the Replication Factor (RF) and Number of nodes (Num nodes options, corresponds to RF)
  6. Optional: Check the box if you wish to enable VPC peering, and enter the Cluster Network CIDR. For each cluster we create a separate VPC. For each availability zone we create a subnet with 256 IPs. You can choose any range from the private ones 10.x.x.x or 192.168.x.x or 172.x.x.x

    Note: Please choose a CIDR that won’t overlap your existing VPCs.

Note: Distribution to Availability Zones (AZs) correspond to the RF. At the bottom section you will see an illustration of the AZs node distribution. Nodes will be evenly distributed between AZs.

Create a Cluster

Launching the Cluster

Next you will be able to see the cluster bootstrapping in progress until it’s completed.

Launching Cluster

Cluster is ready

When the cluster is up and running, you can already observe 3 major metrics in the UI:

  • Requests (Ops/Sec)
  • Storage space – Consumed disk space
  • Load (Scylla cpu-reactor load) – Load generated by Scylla

Cluster status

Add VPC Peering

If you enabled VPC peering, you will now see the screen to configure it. There are 3 steps: Request, Accept and Route.

1st step – Request: In order to setup the VPC peering we will need you to provide us the following details:

  1. AWS Account Number → for example: 868456412743
  2. VPC ID → for example: vpc-094d5a56043du234jf
  3. VPC CIDR → for example: 10.0.0.0/16
  4. Region → for example: us-east-1

AWS Details for VPC peering

Don’t forget to mark the check-box to add the VPC network to the cluster’s allowed IPs (if you do forget, you can still add it later manually).

Press the “Submit VPC Peering Request” button; this takes you to the 2nd step.

2nd step – Accept: Here you will find detailed explanations with screenshots on how to accept the request on your AWS UI.

Once you completed the needed steps on AWS, go back to Scylla Cloud UI and press the “Connect” button to get to the third step.

3rd step – Route: here there are also detailed steps and screenshots on how to setup the routing tables via the AWS UI.

Once you have completed the steps on AWS, go back to Scylla Cloud UI and press “Done”.

Connect to Scylla Cloud using various drivers

If you did not enable VPC peering, once the cluster bootstrap is done, you will be redirected to the “Connect” tab. Here you can find client side code examples on how to connect to your Scylla Cloud cluster using various drivers.

The examples already include the relevant details for your cluster, like the IP and datacenter name. Examples are provided for the following drivers:

  • Cqlsh
  • Java
  • Python
  • Ruby
  • Others

Connecting apps

Cluster view

Go to Cluster view and select your cluster to see a high level view of your cluster details:

  • Cluster ID
  • Scylla version
  • Cluster size
  • Replication Factor
  • CIDR Block (optional) -> CIDR block you’ll want us to create Scylla Cloud Cluster → for example: 10.0.0.0/16 (Needs to be different from your application VPC CIDR)
  • Allowed IPs → you can edit it from this view as well, adding or removing IPs / IP ranges
  • Public IP | Private IP | Status | Region | AZ | Instance Type
  • On the top right side you can observe the 3 major metrics mentioned earlier

Cluster view

Note: If you checked “Enable VPC peering” check-box and did not complete the VPC peering yet, you will see the “Add VPC Peering” notice at the top

Scylla Cloud Metrics

From your cluster view you can dive into the “Monitor” tab to see the following list of metrics:

  • CPU Load
  • Requests Served
  • Read Rate
  • Average Read Latency
  • Writes Rate
  • Average Write Latency

Note: We are constantly improving the metrics exposed to the UI, so over time the list will grow. Scylla DevOps are monitoring thousands of metrics per node for you in the background.

Scylla Cloud metrics

Resize / Delete cluster

Want to resize or delete your cluster? No worries, here’s how to do it.

  1. In your cluster view, click on “Actions” tab, there you’ll find 2 options: Resize / Delete
  2. Submit the request and our DevOps will take care of it for you.

Resize Cluster / Delete Cluster

Resize cluster

We manage everything for you!

  • Monitor thousands of metrics per server
  • Set automatic recurring repairs
  • Set Alerts
  • Disk Space
  • CQL connection (node down)
  • Backups (last 3 days, week + 2 weeks)
  • Security settings
  • Authentication Encryption
  • Applying hotfixes and upgrades

Expert Cloud Support

Keep in mind that upon signing up for Scylla Cloud we create a Zendesk account for you, if you don’t have one already. This allows you to press the “Support” button in the Scylla Cloud user interface for immediate access to your Zendesk account and to submit a ticket.

The Scylla support response team is there for you 24/7/365. We have DevOps monitoring your cluster and taking care of any request for scaling-up/out you might have, as well as engineers (Tiers 1-4) around the globe to respond to any Critical and High priority tickets.

Submit a ticket

Something’s not right? Cluster unavailable, Performance issues? Here’s how to submit a ticket.

  1. Press the “Support” button and you will be redirected into Zendesk
  2. Use the “Submit a request” form.

Submit request

Ticket Priority

Please make sure to select the appropriate Ticket priority. P1 and P2 tickets triggers On-Call DevOps / Engineers to engage and help resolve the issue.

  • Urgent (P1)
    • Cluster unavailable
    • Possible data lost
    • Possible data corrupted
  • High (P2)
    • Cluster is partially available (degraded)
    • Cluster suffers from major performance problems
  • Normal (P3)
    • Cluster suffers from minor performance issues
  • Low (P4)
    • Questions, Requests

Upgrades and Maintenance

Scylla Cloud runs the Scylla Enterprise edition. From time to time there are patch releases. In some cases we will define some upgrades as critical ones. Mandating an upgrade. Don’t worry, we’re not gonna pull the rug from under your feet – All upgrade procedures will be coordinated with the user.

Next Steps

After you get your cluster up and running, the next step is to load your data. We will be publishing a migration blog soon on migrating specifically to Scylla Cloud, but for now you might want to read our blog about migration strategies or watch the on-demand webinar.

If you do try Scylla Cloud, we’d love to hear your feedback, either via our Slack channel, or by dropping us a line.

Sign up for Scylla Cloud

Tomer SandlerAbout Tomer Sandler

Tomer Sandler joined ScyllaDB as a solution architect after a 12 year career in SW Quality Engineering, mostly in storage and telecom lawful interception domains. Prior to ScyllaDB, Tomer held various QA management roles at Dell EMC, leading a group of QA engineers and information developers for ScaleIO storage.
In his free time he enjoys hiking, playing the saxophone, spending time with his family and last but not least, engaging in OSINT (Open Source Intelligence) research.


Tags: Scylla Cloud, technical support, VPC peering