Skip to content

Sign Up as an Individual

One person, one cloud account you already own, no organization to set up. This is RosettaCloud on its own.

RosettaHub is onboarded two ways, and they are genuinely different products rather than two sizes of the same one.

As an individual As an organization
Product RosettaCloud RosettaOps, and RosettaCloud on top of it if you enable MetaCloud
Cloud accounts One you already own and pay for Accounts RosettaHub creates, or ones you already have
Who governs spending You do, through your own AWS billing The platform, through budgets, quotas and policy
Setup One CloudFormation template, a few minutes A deployment runbook, per account
Also listed as RosettaInsight on AWS Marketplace --
Start at This page Onboarding Your Organization

This page covers the individual path. You bring an AWS account, RosettaHub gets keys into it, and you launch environments from the catalog without writing infrastructure code or opening the AWS console.

The Flow

flowchart TD
    Reg["1. Register<br/><i>rosettahub.com or AWS Marketplace</i>"] --> Email["2. Email arrives with your console<br/>credentials, UserUid and ApiKey"]
    Email --> Deploy["3. Deploy the setup template<br/><i>into your own AWS account</i>"]
    Deploy --> Keys["4. Cloud Keys appear<br/><i>one per region</i>"]
    Keys --> Launch["5. Launch a Formation"]

    style Reg fill:#e3f2fd,stroke:#1565c0,color:#000
    style Email fill:#fff9c4,stroke:#f9a825,color:#000
    style Deploy fill:#e8f5e9,stroke:#2e7d32,color:#000
    style Keys fill:#e8f5e9,stroke:#2e7d32,color:#000
    style Launch fill:#e8f5e9,stroke:#2e7d32,color:#000

Step 1 -- Register

Two routes, and they end in the same place.

Submit the user registration form:

https://www.rosettahub.com/registration/user.xhtml

It asks for your first name, last name and email. A phone number is optional. This creates your platform account and nothing else -- no cloud resources are touched, and no AWS credentials are involved yet.

RosettaCloud is listed on AWS Marketplace as RosettaInsight:

RosettaInsight on AWS Marketplace

Subscribing there gives you the same platform account, with two differences: your subscription is billed through your existing AWS bill rather than separately, and the listing offers a Quick Launch deployment that reads your credentials from Secrets Manager instead of asking you to paste them into the template in Step 3.

There is a free tier

You do not need a paid subscription to try the platform, and the Marketplace listing also offers a free trial of the paid plan. The listing carries the current terms for both.

A subscription governs how much you may run on the platform. It is separate from what AWS charges you for the resources themselves, which stay on your own bill either way.

Step 2 -- Receive Your Credentials

RosettaHub emails you:

What Used for
Console credentials Signing in to the RosettaHub web console and the desktop app
UserUid A CloudFormation parameter in Step 3. Identifies which platform account the cloud account attaches to
ApiKey A CloudFormation parameter in Step 3. Authorises the registration call the template makes back to the platform

The API key is a platform credential, not an AWS one

ApiKey authorises registering cloud accounts against your platform account. It is not an AWS access key and it grants nothing inside AWS. Do not paste it into a shared template, a screenshot or a support ticket, and rotate it from the console if you think it has been seen.

Step 3 -- Connect Your AWS Account

You need an AWS account of your own, with permission to create IAM roles in it. RosettaHub does not create this account for you and does not pay for it -- that is the difference between this path and the organization one, where accounts can be vended for you.

Deploy the setup template:

aws cloudformation create-stack \
  --stack-name RosettaHubSetup \
  --region us-east-1 \
  --template-url https://com-rosettahub-public-code.s3.eu-west-1.amazonaws.com/marketplace/2.0.0/RosettaHubManualSetup.yaml \
  --capabilities CAPABILITY_IAM \
  --parameters \
      ParameterKey=UserUid,ParameterValue=<your UserUid> \
      ParameterKey=ApiKey,ParameterValue=<your ApiKey>

Or launch the same template from the CloudFormation console, which is what the Marketplace instructions walk you through. If you subscribed through Marketplace and chose Quick Launch, there are no parameters to fill in.

Region

Launch the stack in us-east-1 unless you have been told otherwise. The stack itself is small and its region does not restrict where you can then run machines -- Cloud Keys are created for every region your account is entitled to.

What the template creates

Four things, all in your account:

Resource What it is
RHKeysRole An IAM role that RosettaHub assumes to provision resources on your behalf. Its trust policy names the RosettaHub AWS account, so nobody else can assume it
Lambda execution role Permissions for the setup function below
Setup Lambda Runs once at deployment. Calls the platform with your UserUid and ApiKey to register the account and create your Cloud Keys
Custom resource Triggers the Lambda during stack creation

There is no agent, no persistent compute, and nothing that keeps running after the stack finishes. Access is a role you can revoke at any time by deleting the stack.

Step 4 -- Launch Something

Sign in with the credentials from Step 2. Your Cloud Keys are already there, one per region, each with a platform-managed network created alongside it.

From here, follow Launch Your First Formation, or go straight to a ready-made environment: Jupyter Lab, RStudio, a data science workbench.

What You Do and Do Not Get

RosettaCloud on its own is a complete product. What it is not is a governance layer, because on this path there is nothing to govern but you.

On this path With RosettaOps
Formations, sessions, images, storages , on accounts where MetaCloud is enabled
Sharing with other users and organizations
Cross-cloud operations
Guardrails on what you can launch From the Cloud Key: permitted instance types, its region, its network Also budgets, quotas, region and service restrictions, enforced on every path including the cloud console
Cost governance Your own AWS bill, after the fact Real-time cost against a budget, with automatic action when it runs low
Account vending, RBAC, landing zone, compliance scanning --

RosettaCloud through RosettaOps

The two products are not alternatives. An organization on RosettaOps reaches everything on this page by enabling MetaCloud on its accounts, which is what the platform calls the scope that lets Formations provision infrastructure. That combination is the full platform: governed accounts, budgets and policy underneath, self-service Formations on top, and every launch subject to the same limits as a click in the cloud console.

Two things to know about it:

  • It is opt-in, per account. MetaCloud is a parameter on the deployment template, not something that arrives by default. See Account Access and Scopes.
  • It is offered only on the Automate edition. The Governance templates behind Observe and Govern declare no parameter that grants it, which is deliberate: MetaCloud creates a role RosettaHub assumes to build infrastructure in the account, and those editions exist precisely to have no such path.

Moving to the organization path later

Nothing here is thrown away if you outgrow it. The organization path adds governance around cloud accounts rather than replacing what you built, and Formations, images and storages you created are yours to keep and share. Start at Onboard Your Organization when you have people other than yourself to account for.

Troubleshooting

Symptom Likely cause
Stack fails at the custom resource UserUid or ApiKey mistyped, or copied with trailing whitespace from the email
Stack succeeds but no Cloud Keys appear The registration call reached the platform but was rejected. Contact support@rosettahub.com with your stack ID
CAPABILITY_IAM error The template creates IAM roles. Re-run with the capability flag, or acknowledge the checkbox in the console
No permission to create the stack You need IAM role-creation rights in the AWS account. An account where you are not an administrator may not allow this

Next Steps

  • The RosettaCloud Model -- the four things you work with, once you have launched one.
  • Cloud Keys -- what they hold, and why deleting one removes the artifacts linked to it.
  • Sharing -- give what you built to someone in another account or another cloud.