# Release notes for Self-Hosted Deployment in Amazon Web Services 1.1 > Learn about new features, improvements, and fixed issues. ## 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 Self-Hosted Deployment. ### 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: ```bash 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 Self-Hosted Deployment, 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](/cloud/asset-manager/bulk-metadata-editing.md). #### 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](/cloud/asset-manager/automation-integration/create-event-automation-asset-manager.md). #### 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](https://support.unity.com/hc/en-us/requests/new?ticket_form_id=36798331373844). ### 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: 1. Add the variables to your Terraform configuration. 2. 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`. 3. To update the generated Helm charts with the correct values, run the command `make apply-`. ### 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: ```sh # 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](https://docs.percona.com/percona-server-for-mongodb/7.0/comparison.html) 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: 1. The custom URI, if provided 2. The existing MongoDB VM 3. The new PSMDB cluster Migrate data at your own pace with this staged approach. Read more about [migrating your data to PSMDB](./installation/migrate-to-psmdb.md). #### 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: 1. Expose PMM under a new subdomain. 2. Generate an API key in PMM for PSMDB to report metrics. 3. Update the Terraform variable `psmdb_pmm_server_token`. ### Known issues #### Asset Manager for Self-Hosted Deployment * You can manually create tags for assets, but you can't automatically generate tags. Self-Hosted Deployment 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.