Introduction

The deployment of cloud-based live production workflows using Viz Now involves the automated provisioning of various AWS resources, such as EC2 instances, security groups, IAM roles, VPCs, and storage components. These resources are created directly in your AWS account, enabling and maintaining full customer control and ownership.

While Viz Now provides a strong foundation and starting point in terms of security posture, it is ultimately the responsibility of you, the customer, to ensure that these resources are properly secured according to organizational security policies and operational needs.

We strongly recommend referring to AWS security best practices and documentation for each service involved in a Viz Now deployment. Customers should review and, if necessary, adapt the configurations post-deployment, to align with their internal security standards, compliance frameworks, and threat models.

Our Commitment to Secure Defaults

Viz Now is being continuously improved to offer:

  • More secure-by-default templates for deployments.

  • Optional security configurations during setup.

  • Transparent documentation of ports, protocols, IAM permissions, and network exposure.

This section presents

It provides:

  • A detailed list of network ports and protocols opened by default.

  • An overview of IAM permissions used by Viz Now roles.

  • Important warnings about manual changes that may be overwritten during redeployment.

  • Suggestions for enhancing your security posture based on your infrastructure setup and use case.

We will continue to evolve this section with updated recommendations, configurable options, and integration best practices.

Note: If you have specific security requirements or constraints, we encourage you to contact our team to discuss how Viz Now can best be configured for your environment.