Release notes for Virtual Private Cloud in Amazon Web Services

Learn about new features, improvements, and fixed issues.

Read time 5 minutes

Last updated a day ago

Version 1.3.0 — June 8, 2026

Breaking changes

Mini-USF version 2 upgrade

Upgraded Mini-USF to version 2 to decouple Keycloak from entities, such as projects. Before you upgrade, you must migrate your existing Mini-USF v1 setup. For detailed instructions, refer to Migrate Mini-USF from version 1 to version 2.

Static licenses required as Terraform variables for Pixyz workflows

Provided Pixyz workflows with static licenses via the Terraform variables

pixyz_license

and

pixyz_license_3dds

, instead of manually creating the Kubernetes secret. Set each variable to the base64‑encoded license content.

Improvements

Kubernetes 1.33

Upgraded the EKS cluster to Kubernetes 1.33. Updated EKS‑managed add‑ons to the matching AWS default versions. No node recycling was required.

Distributed object storage by default

Enabled RustFS to run in distributed mode by default for improved resilience. Fixed an out‑of‑memory issue that affected RustFS.

Default monitoring alerts

Added a set of default alerts to the kube-prometheus-stack.

Larger default storage sizes

Increased the default PostgreSQL data volume from 200 GiB to 400 GiB and the pgBackRest backup repository from 400 GiB to 800 GiB. On clusters that use gp3 storage, these volumes resize online during the next ArgoCD sync with no downtime.

Fixed issues

Automation Manager post-install job

Fixed the

automation-manager

post‑install job failing with a permission error when it authenticated to the container registry as a non‑root user.

Version 1.2.3 — May 20, 2026

Fixed issues

Workspace service with an external UVCS server

Modified the

workspace-service

to honor the

uvcs_repository_guid

variable when

enable_uvcs=false

. The workspace pod skips in-cluster UVCS discovery and connects to your pre-existing UVCS repository, so it starts successfully when pointed at an external UVCS server.

Version 1.2.2 — May 12, 2026

Fixed issues

3D Data Streaming workflow retries

Fixed 3D Data Streaming (3DDS) workflows so they increase memory allocation correctly on retry after an out-of-memory failure. Previously, the memory request didn't increase on retries, which could cause repeated failures.

Version 1.2.1 — February 23, 2026

Improvements

Upgraded services

These services have been upgraded:

Asset Manager 1.1.5 with improved timeout issue handling when downloading assets

Version 1.2.0 — February 13, 2026

New features

UVCS deployment through Helm chart

Unity Version Control Server (UVCS) can now be deployed through a Helm chart. To enable this feature, set the Terraform variable

enable_uvcs

true

in your Terraform configuration.

Version 1.1.8 — February 17, 2026

Improvements

RabbitMQ operator monitoring

By default, the RabbitMQ operator no longer creates Prometheus

ServiceMonitor

and

PodMonitor

resources. This prevents errors on clusters that don't have the Prometheus Operator custom resource definitions (CRDs) installed.

Version 1.1.7 — February 16, 2026

Breaking change

Static license file required for Pixyz workflows

Removed support for the FlexLM license server in workflows. You must have a static license file.

Version 1.1.6 — February 12, 2026

Improvements

Valkey deployment command

Added a target for deploying Valkey in the Makefile.

Version 1.1.5 — February 10, 2026

Fixed issues

MinIO operator permissions

Reverted the MinIO operator to use cluster-scoped

ClusterRole

and

ClusterRoleBinding

resources, restoring the previous configuration and undoing the namespaced roles change.

Version 1.1.4 — February 6, 2026

Improvements

RDS PostgreSQL performance defaults

Changed the default RDS PostgreSQL instance type to

db.m6g.xlarge

for more consistent performance, and changed RDS PostgreSQL to use

gp3

storage with 3000 IOPS. You can override these defaults in your Terraform configuration.

Version 1.1.3 — February 4, 2026

Improvements

RDS PostgreSQL and backup defaults

Several defaults were updated:

The default RDS PostgreSQL instance type is now
```
db.t3.xlarge
```
.
The default value of
```
rds_postgres_random_page_cost
```
is now
```
2
```
.
The default value of
```
rds_postgres_allocated_storage
```
is now
```
100
```
.
Default volume mounts were added to the Percona Server for MongoDB (PSMDB) backup configuration.

Version 1.1.2 — December 09, 2025

The version 1.1.2 corresponds to the internal version code v2025.49.267 of Unity Virtual Private Cloud.

Breaking change

Valkey replaces AWS Elasticache: a new Valkey Helm chart replaces AWS Elasticache for Redis OSS. After deploying the latest Helm charts, run the following command to ensure that all services connect to Valkey instead of Elasticache:


kubectl rollout restart deployment -l creator-services-app=asset-solutions --namespace=asset-solutions

if you modified the default namespace, update it in the command accordingly.

New features

Service versions

Unity Dashboard now displays the versions of VPC, Asset Manager, and Pipeline Automation. To view the version of a service, select your profile picture, and then locate the version from the menu.

Bulk edit of assets

You can now edit assets in bulk.

Exploration of complex assembly data in 3D Data Streaming models

Using the new scene hierarchy feature in 3D Data Streaming (3DDS) models, browse through complex engineering assembly data, from 3DDS previews.

Event-based automations

You can now create automations that trigger pipelines based on specific events.

Automation apps

These new automation apps are available:

HTTP Client 0.0.5
Python 0.0.1
Linux Shell 0.0.1

Custom apps

Custom apps are available as a beta feature. To learn how to create a custom app, contact Unity Support.

Improvements

Upgraded services

These services have been upgraded:

Asset Manager 1.1.4
Asset Transformer 1.1.3

Version 1.1.0 — November 4, 2025

New features

Terraform variables for FlexLM licensing

These new Terraform variables are available:

```
flexlm_host
```
: an IP address or the hostname.
```
flexlm_port
```
.

To use these variables, complete these steps:

Add the variables to your Terraform configuration.
Delete the values from their previous location where you previously managed them manually, that is, the
```
flexlm
```
section in the file
```
aws/applications/builtins/values.yaml
```
.
To update the generated Helm charts with the correct values, run the command
```
make apply-<region>
```
.

Improvements

Automated cluster bootstrap

You can now install a cluster-bootstrap Helm chart that automatically creates the required cluster resources, such as storage classes. This feature is enabled by default. However, if you use an existing cluster, this feature is automatically disabled:

enable_eks=false

Warning

If you have installed a cluster-bootstrap Helm chart but have an existing

efs-sc

storage class that you have manually created, you must update the existing storage classes as follows before you upgrade.

To update the existing storage classes before you upgrade, run these commands:


# If you have deployed the solution through Helm, add the Helm management labels to the existing efs-sc storage class. This step isn\'t necessary for ArgoCD.kubectl patch storageclass efs-sc --type='merge' -p='{"metadata":{"labels":{"app.kubernetes.io/managed-by":"Helm"},"annotations":{"meta.helm.sh/release-name":"cluster-bootstrap","meta.helm.sh/release-namespace":"asset-solutions"}}}'# Remove the default flag from the gp2 storage class, because the gp3 storage class becomes the default storage class.kubectl patch storageclass gp2 -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"false"}}}'

Migration from MongoDB to Percona Server for MongoDB

We're migrating away from the MongoDB virtual machine (VM) to Percona Server for MongoDB (PSMDB). PSMDB is based on MongoDB Community Edition but extends it to an Enterprise Edition. Read more about differences between PSMDB and MongoDB in Percona documentation. The new Terraform variable

enable_percona_mongo

is for the deployment of the PSMDB operator and database in your Kubernetes cluster as a parallel setup. This variable is disabled by default. However, to ensure zero downtime, all services initially continue using your current MongoDB instance. The connection string logic follows this priority order:

The custom URI, if provided
The existing MongoDB VM
The new PSMDB cluster

Migrate data at your own pace with this staged approach. Read more about migrating your data to PSMDB.

Monitoring for PSMDB

The new Terraform variable

enable_percona_monitoring

is for the deployment of Percona Monitoring and Management (PMM) for PSMDB monitoring. This variable is disabled by default. To access PMM from outside the Kubernetes cluster, follow these steps:

Expose PMM under a new subdomain.
Generate an API key in PMM for PSMDB to report metrics.
Update the Terraform variable
```
psmdb_pmm_server_token
```
.

Known issues

Asset Manager for Virtual Private Cloud

You can manually create tags for assets, but you can't automatically generate tags. Virtual Private Cloud doesn't support this feature. If you select Generate Tags in the asset properties in edit mode, Asset Manager doesn't suggest any tag and displays an error message. This behavior is expected. This button will be removed in a future version.
If you try to move assets between collections, Asset Manager might not move all assets, but informs you that the operation was successful. This issue is scheduled to be fixed in the next release.