Creating environments and resources.

In MedStack Control, you have the ability to manage cloud resources that are provisioned for privacy compliance by design. Creating clusters, compute nodes, and database servers can be done in a few simple clicks.


All cloud resources you build in MedStack Control are built within MedStack's Azure tenant. We manage all cloud resources through Azure subscriptions and create dedicated infrastructure for your environments only. No one other than you and MedStack have access to manage your resources.

This is an imperative distinction that is often important to entities when performing security assessments. Although not a HIPAA requirement, infrastructure that serves only the client is often preferred by end users requesting security assessments.


There are many measures taken to implement secure design and guarantee compliance for the resources you build in MedStack Control. They are explained in deeper detail on each service's article in this guide.

DDOS and IP spoofing

In the chain of responsibility, it is illustrated that the cloud provider is responsible for DDOS and IP spoofing mitigation.

A virtual network encompasses your docker environment and cloud services operating via MedStack Control. Protecting this virtual network is Azure's networking security.

In regard to DDOS and IP spoofing mitigation, Azure employs their "DDOS protection basic mitigation" which mitigates attack vectors on OSI layers 3 and 4. This includes:

  • Active traffic monitoring and always on protection.
  • Automatic attack mitigations

Updated 2 months ago

What's next

Once you've setup your cluster, you can create the Docker environment or deploy cloud resources.



Creating environments and resources.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.