Skip to main content

Introducing Self-hosted Environments: Bringing Data Isolation to Your Cloud

· 4 min read
@misosoup

Today, we're excited to announce the Self-hosted Environments Beta. We've learned from our customers that with the need for data security and compliance on the rise, building and maintaining environments and dependencies to support their existing DevOps processes and workflows is a non-trivial matter.

Currently, engineering teams must choose between speed and compliance. When building or modifying data infrastructure, this can mean lost time or potentially putting sensitive data at risk.

Self-Hosted Meroxa Environment

Self-hosted Environments can now be provisioned with Meroxa in an existing cloud provider with just a few steps.

Environments play a key role by encapsulating settings in an isolated subnet where data application resources can exist and operate securely. By sequestering development and testing efforts in environments as part of the DevOps lifecycle, engineers mitigate impact risk on existing systems and customers.

At Meroxa, we've done the work to eliminate implementation complexity for our customers while still offering complete operational control over their data security, compliance, and performance needs.

Getting started​

To get started with Self-hosted Environments Beta, take the following steps:

  1. If you don't already have a Meroxa account, request a demo.
  2. Sign-up for the Self-hosted Environments Beta.

A member of our team will reach out with the next steps. You will need access to your cloud provider to generate credentials with the necessary permissions to provision an environment.

With Self-hosted Environments, you get all the power and utility of the Meroxa platform. Allowing easy creation and management of Resources, Connectors, and Pipelines through our Dashboard or CLI - all with your data securely isolated in your cloud.

The Meroxa Platform performs a preflight check to verify permissions before generating a new VPC and the associated dependencies in your cloud. A secure remote connection will be maintained automatically with the Meroxa platform for the control plane to ensure everything operates smoothly.

As part of the environment provisioning process, credentials from your cloud provider with the appropriate permissions are required.

As part of the environment provisioning process, credentials from your cloud provider with the appropriate permissions are required.

$ meroxa env create my-env \
--type selfhosted \
--provider aws \
--config {"aws_access_key_id":"$AWS_ACCESS_ID", "aws_secret_access_key": "$AWS_SECRET_KEY" }

Creating Self-hosted Environments is made easy through our CLI.

Once successfully provisioned, you are ready to start creating Resources, Pipelines, and Connectors to move your data within your Self-hosted Environment.

When configuring your resource, you have the option to indicate which environment you'd like to create your Resources and Pipelines for via our secure dashboard.

When configuring your resource, you have the option to indicate which environment you'd like to create your Resources and Pipelines for via our secure dashboard.

# Create a resource to your Meroxa Environment

$ meroxa resource create my-postgres \
--type postgres
--env my-env
--url postgres://user:[email protected]:5432/db_name

# Create a pipeline to your Enviornment

$ meroxa pipeline create my-pipeline --env my-env

Using the ‘env’ tag in the CLI for Resource and Pipeline creation commands allows you to indicate which environment to create them in. The default environment is common.

You’re now ready to build out your Turbine app! If you need help, check out our getting started guide.

What's supported​

Self-hosted Environments may be provisioned in the following Amazon Web Services (AWS) regions:

  • us-east-1 (N. Virginia)
  • us-west-2 (Oregon)
  • ap-northeast-1 (Tokyo)
  • eu-central-1 (Frankfurt)

We do not currently support the provisioning of environments within existing VPCs.

Don't see your cloud provider or preferred region? You can still sign up for the beta—we'd love to hear how we might best support your needs!

Learn more​

Are you as excited about real-time streaming applications as we are? We'd love for you to take Self-hosted Environments for a spin. Sign up for the Self-hosted Environments Beta today — we will be in touch with the next steps! For more details, see our documentation.

Sign up for the Self-hosted Environments Beta

As always,