> For the complete documentation index, see [llms.txt](https://docs.silk.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silk.us/releases/2026/v9.5.20/features-and-enhancements.md).

# Features and Enhancements

Generally available since May 6, 2026. Explore the new features and enhancements in Silk v9.5.20, including Silk on AWS, Echo Constellation, and general availability of Azure CMK encryption.

## October 2026 refresh

These features and enhancements are available since October 20, 2026.

### IdP-initiated SSO enables one-click access to Flex

You can now sign in to Flex with a single click from your identity provider’s application launcher (for example, Microsoft Entra My Apps), making it easy to access Flex without navigating to it separately.

### Faster DataPod connectivity detection improves monitoring

Flex now detects when a DataPod becomes unreachable in near real time and reports the condition to Silk Clarity, supporting earlier visibility into connectivity issues.

### Additional Google Cloud VM types expand deployment options

This refresh adds support for the following Google Cloud VM types:

* **c.nodes:** c3d-highmem-60, n4-highmem-64, and c4-highmem-64
* **d.nodes:** c2-standard-4

***

## Highlights

The most impactful changes in this release. Expand a highlight for a quick summary and a link to its full description.

<details>

<summary>Silk on AWS</summary>

Deploy Silk on AWS, Microsoft Azure, and Google Cloud.

[Read more about Silk on AWS](#silk-on-aws-expands-multi-cloud-operations)

</details>

<details>

<summary>Management Controller self-recovery</summary>

MC recovery time drops from 20+ minutes to seconds in applicable scenarios.

[Read more about Management Controller self-recovery](#management-controller-self-recovery-improves-operational-resilience)

</details>

<details>

<summary>Multi-VM selection for DataPods</summary>

A new VM selection step during DataPod creation lets you choose different VM types across m.nodes to work around regional capacity constraints.

[Read more about multi-VM selection for DataPods](#multi-vm-selection-introduces-more-flexible-datapod-provisioning-workflows)

</details>

<details>

<summary>Azure CMK encryption (GA)</summary>

Enable customer-managed key encryption directly during DataPod creation.

[Read more about Azure CMK encryption](#azure-cmk-encryption-reaches-general-availability-for-production-deployments)

</details>

<details>

<summary>Echo Constellation</summary>

Graph-based view of Echo resources, lineage, and timeline activity.

[Read more about Echo Constellation](#echo-constellation-transforms-visibility-across-echo-environments)

</details>

<details>

<summary>Oracle pluggable databases (Beta)</summary>

Echo lifecycle management for Oracle PDB environments.

[Read more about Oracle pluggable database support](#beta-support-for-oracle-pluggable-databases-expands-echo-workload-coverage)

</details>

{% embed url="<https://www.loom.com/share/9745be5b80a547e9aa2de1c0ba3117be?_hsenc=p2ANqtz-8Kr40r5cJll2MfsazlU5UQjGzqS5Yea0OZlgIz6Zg6Okj-mWLYEGXNHv_CmSSZnW6HhFfam6mrrCeuzZioZqBWJYE8Pw&_hsmi=2&utm_content=2&utm_medium=email&utm_source=hs_email>" %}

***

## Component versions

Current as of the October 2026 refresh.

<table><thead><tr><th>Silk Component</th><th width="148.8887939453125">Version</th><th>Image Version</th></tr></thead><tbody><tr><td><strong>Silk Flex</strong></td><td>2.20.72</td><td>2.20.72 (Flex OS)</td></tr><tr><td><strong>SDP Management Console (c.node)</strong></td><td>9.5.20.17</td><td><strong>AWS / Azure / Google Cloud</strong><br>k2c-cnode-9-5-20-17</td></tr><tr><td><strong>d.node</strong></td><td>9.5.20.86</td><td><p><strong>AWS</strong><br>aws-dnode-9-5-20-86<br>aws-dnode-9-5-20-86-arm64<br><br><strong>Azure</strong></p><p>azure-dnode-9-5-20-86<br><br><strong>Google Cloud</strong><br>gcp-dnode-9-5-20-86</p></td></tr><tr><td><strong>VSS</strong></td><td>2.0.20</td><td>—</td></tr><tr><td><strong>Host Agent</strong></td><td>1.1.17</td><td>—</td></tr></tbody></table>

***

## Flex and DataPods

### Silk on AWS expands multi-cloud operations

Silk now supports deployment on AWS, extending Silk across all three major cloud providers and enabling organizations to standardize high-performance enterprise data operations across multi-cloud environments.

This expansion gives teams greater control over workload placement and cloud adoption strategy while maintaining consistent operational workflows across AWS, Microsoft Azure, and Google Cloud. Existing customers can adopt AWS without refactoring applications or redesigning operational processes, enabling more flexible infrastructure decisions as your cloud environment evolves.

{% hint style="warning" %}
**Performance considerations**

On AWS, instance bandwidth behavior varies between baseline and burst limits. For sustained, high-bandwidth workloads, size your Silk deployment based on baseline bandwidth rather than peak burst values to ensure predictable performance over time.

For detailed sizing guidance, see **Understand AWS Instance Bandwidth Behavior** in the [Silk on AWS Deployment Guide](https://support.silk.us/sys/document/preview/Silk-on-AWS-Deployment-Guide-260506104227604.pdf).
{% endhint %}

### Management Controller self-recovery improves operational resilience

This release introduces automated, module-based self-recovery for the Management Controller (MC) process. Instead of requiring full c.node recovery, the system can now recover the MC process independently.

This significantly reduces MC recovery time from 20+ minutes to just seconds in applicable recovery scenarios, helping maintain system responsiveness and minimize operational disruption during recovery events.

### Multi-VM selection introduces more flexible DataPod provisioning workflows

The DataPod creation workflow now includes a dedicated VM selection step that allows teams to choose workload profile, configure c.node VM types, and select multiple m.node VM types during deployment.

This workflow gives you significantly more control over how DataPods are provisioned in cloud environments where VM availability can fluctuate regionally or over time. While each m.node uses a single VM type and all d.nodes within an m.node remain consistent, different m.nodes within the same DataPod can use different VM types. This enhancement helps mitigate cloud capacity constraints while maintaining predictable node-level performance characteristics.

Optimize your DataPod deployments for bandwidth-intensive or low-latency workloads while improving deployment flexibility in environments where preferred VM types may be temporarily constrained or unavailable.

<figure><img src="https://1557305422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFUE8J62COhtwFAOs7gSo%2Fuploads%2FrP872T4cprNX75u4xzOs%2Fimage.png?alt=media&#x26;token=34352f2b-cad8-4b26-82a4-7eafa3ba288a" alt=""><figcaption></figcaption></figure>

### Azure CMK encryption reaches general availability for production deployments

Customer-managed key (CMK) encryption is now generally available for Azure environments, enabling customer-controlled encryption for c.node OS disks, VM-based m.node OS disks, and Pv2 m.node data disks using customer-controlled keys.

CMK encryption can be enabled directly during DataPod creation in the Flex UI, streamlining deployment workflows while helping organizations align with internal security and compliance requirements. This capability gives teams more control over encryption key management and lifecycle operations within Azure environments.

### Strengthened password requirements enhance baseline security

{% hint style="warning" %}
Updated password policies now require stronger passwords for all new version installations (not only v9.5.20), aligning with current security standards. This change helps reinforce baseline protection for deployed environments.
{% endhint %}

### Expanded Azure VM support provides greater deployment flexibility

Silk has added support for Standard\_E64s\_v6 and Standard\_D64s\_v6 c.nodes in VM Local Disk deployments on Azure. This release update also re-enables support for D\_v5 and E\_v5 VMs that use Microsoft Azure Network Adapter (MANA).

### Metadata read cache warmup improves post-reconfiguration performance recovery

Following reconfiguration events, the system now automatically warms the metadata read cache on a newly added c.node. This helps latency return to baseline levels more quickly, improving performance consistency and reducing the impact of reconfiguration on active workloads and scaling events.

### Improved system recovery coordination enhances platform stability

Enhancements to internal monitoring, recovery coordination, and failover handling improve how system components detect and respond to runtime conditions during complex recovery operations.

These refinements improve recovery decision timing and operational coordination across platform services, helping maintain more consistent system behavior and reducing the risk of disruption during large-scale recovery events.

### Enhanced Performance tab improves observability in the SDP Management Console

Updates to the **Performance** tab in the SDP Management Console provide clearer visibility into bandwidth utilization and IOPS behavior. These improvements help operators more effectively monitor system health and understand performance trends during normal operation and recovery scenarios.

### SPDK support for d.nodes enhances backend storage processing

This release introduces SPDK-based storage processing support for d.nodes, extending Silk’s ongoing transition toward a more modern and efficient storage processing architecture.

This enhancement improves backend I/O handling efficiency and supports continued resiliency and scalability improvements across the platform. SPDK is now available for both c.nodes and d.nodes.

***

## Echo

### Echo Constellation transforms visibility across Echo environments

Echo Constellation introduces a new graph-based interface for visualizing Echo resources, relationships, lineage, and timeline activity within a unified operational view.

Echo Constellation surfaces complex dependencies and lineage relationships visually to simplify troubleshooting, accelerate operational workflows, and improve visibility across large-scale or rapidly changing environments. Integrated lineage and timeline tracking help cloud teams better understand resource relationships, trace operational changes, and manage Echo environments more efficiently.

<figure><img src="https://1557305422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFUE8J62COhtwFAOs7gSo%2Fuploads%2FC7Zkj7r4NLCaAH67ToDC%2Fimage.png?alt=media&#x26;token=749e9add-fd66-4e71-826c-5613cad444b3" alt=""><figcaption></figcaption></figure>

### Beta support for Oracle pluggable databases expands Echo workload coverage

Echo now introduces beta support for Oracle pluggable database (PDB) environments, extending Echo lifecycle management capabilities to additional enterprise database workloads. With Echo, organizations can instantly provision database copies, automate lifecycle workflows, accelerate development and testing processes, and simplify database management across environments.

{% hint style="info" %}
This beta release introduces foundational support for Oracle database protection and management workflows, including database snapshot creation, database lifecycle operations, and host management capabilities for supported Oracle environments. Initial support focuses on specific Oracle storage configurations and deployment scenarios, with additional functionality and broader platform coverage planned for future releases.
{% endhint %}

### Enhanced multi-resource management streamlines bulk operations

New interaction capabilities, including multi-select and drag-and-drop actions, allow users to manage bulk Echo resources more efficiently. These improvements help reduce the effort required for repetitive management tasks and support more intuitive resource management.

### Recursive path and search capabilities improve resource discoverability

Enhanced search and navigation features allow users to locate resources and visualize full dependency paths within Echo. This improves visibility into complex relationships and supports more effective troubleshooting and planning.

### Cascade deletion streamlines Echo DB and DB-Snapshot cleanup

Echo administrators can now use cascade deletion for Echo DBs and DB-snapshots, allowing parent resources and associated child resources to be removed in a single action. Previously, dependent resources had to be removed individually before parent resources could be deleted.

This enhancement significantly simplifies cleanup workflows, reduces manual effort, and improves management efficiency across complex Echo environments.

<figure><img src="https://1557305422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFUE8J62COhtwFAOs7gSo%2Fuploads%2FKNmao5JV4Jv18LKFpCOz%2Fimage.png?alt=media&#x26;token=1b3c969a-d68a-400f-8b86-ed4bc55a08c0" alt=""><figcaption></figcaption></figure>

### Enhanced agent observability improves system-wide visibility

Expanded telemetry and observability enhancements provide deeper insight into host, agent, and database behavior, enabling faster diagnostics and improved end-to-end visibility across Echo-managed environments.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.silk.us/releases/2026/v9.5.20/features-and-enhancements.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
