mirror of
https://github.com/hanzoai/team.git
synced 2026-09-30 01:57:35 +00:00
b5f007d35e
* docs: resolve cross-file anchor mismatches from RST-to-MDX migration
The Sphinx-to-Docusaurus migration converted `:ref:`/`{ref}` links using
naive text-slugification, so anchors that pointed to headings in a
different file (e.g. release-summary tables linking into their
respective changelog pages) were emitted as same-page fragments and
silently resolved to nothing.
Built a label registry from the original Sphinx `.. _label:` / `(label)=`
targets to recover the true source file for each cross-reference, then
rewrote the affected links to point at the correct file + heading
anchor. Fixes 282 broken cross-file anchors, primarily in the mobile/
desktop/server release-summary pages, plus assorted same-page anchor
mismatches caught by re-auditing after the prior admonition/anchor fix.
* docs: manually resolve remaining anchor mismatches after cross-file audit
Hand-verified fixes for anchors that fuzzy-matching alone couldn't
safely resolve (confirmed against actual heading text/context, and in a
few cases against the original RST source, before applying):
- Typos and dropped words carried over from the original Sphinx docs
(e.g. "bot-acocunts", "auto-follow-all-new-channel-threads" ->
"follow-all-new-channel-threads").
- Sphinx auto-generated duplicate-heading IDs (#id1/#id3/#id4) resolved
to their real target headings.
- Numbered-step TOC links in enterprise-roll-out-checklist.mdx that
dropped the leading "N. " used in the actual heading slugs.
- Push-notification docs pointing at the wrong file entirely
(environment-configuration-settings instead of
push-notification-server-configuration-settings).
- SAML "saml-enterprise" label resolved to its true cross-file target
(authentication-configuration-settings#saml-2-0), recovered from the
original RST label definition that the automated registry missed
because it sat after an RST transition marker.
- sso-saml-technical references converted from broken same-page/
malformed-path anchors to correct page links.
* docs: fix SAML 2.0 anchor slug (saml-2-0 -> saml-20)
github-slugger strips periods rather than hyphenating them, so "SAML
2.0" slugifies to saml-20, not saml-2-0 as previously fixed.
* docs: fix broken path links found during docs/main migration cleanup
* docs: convert div.tab blocks to Docusaurus Tabs/TabItem components
* docs: restore missing Kubernetes deployment architecture diagrams
The RST-to-MDX migration never copied over the AWS/Azure/Oracle
architecture diagrams referenced by the deployment-architecture-at-scale
page, leaving broken images in each Tabs/TabItem.
* docs: fix 7 anchor mismatches from the fragment/heading audit
Covers three root causes from the anchor mismatch breakdown:
- Fragment repeated the target page's own title instead of a real
heading, so the link is simplified to point at the bare page.
- Heading exists verbatim but lives on a sibling settings page
(experimental-configuration-settings, push-notification-server-
configuration-settings) rather than environment-configuration-settings.
- A page path was mistakenly pasted into a same-page #fragment instead
of being used as a real cross-page link.
* docs: fix 8 anchor slugs that were close but didn't match the real heading
Repoints links whose fragment was a plausible guess (typo, reworded
heading, or wrong section) at the actual auto-generated slug of the
target heading, confirmed by inspecting each target page directly.
* docs: merge split Tabs blocks so tabs render horizontally
The div.tab conversion script split some sibling tab groups into
separate single-item Tabs blocks whenever a stray blockquote marker
sat between them, causing them to render stacked instead of as one
horizontal tab bar. Merges the MySQL/PostgreSQL and Team/Enterprise
Edition tab groups back into single Tabs blocks.
* docs: remove Azure tab and restore Kubernetes deploy content
The Mattermost Operator, Azure, and Oracle platform tabs on the
Kubernetes deployment guide were split across two separate Tabs
blocks (rendering stacked instead of as one tab bar) and all three
tab bodies were empty because the migration never flattened the
original RST include directives. Removes the unsupported Azure tab
and restores the Mattermost Operator and Oracle content from the
pre-migration RST sources as a single merged Tabs block.
* addresscoderabbitreview
* docs: unify Linux/Kubernetes/Containers deploy pages and fix FIPS/STIG placement
Kubernetes and Containers duplicated full install content across a top-level
page (Tabs) and orphaned sidebar subpages that nothing linked to. Reworked
both to follow the Linux page's pattern: shared content on the landing page,
platform-specific instructions live once in their own subpage.
Also removed configure-fips-at-install-time.mdx, which claimed FIPS is
available for native Linux installs — FIPS/STIG in Mattermost is a container
image property (Chainguard-based build), not available outside Docker/
Kubernetes. Consolidated all FIPS/STIG references onto
containers/fips-stig.mdx and pointed the Mattermost Operator subpage (not
Oracle OKE, which doesn't expose image selection) at it.
* docs: fix review findings — image alt text, Important callout markup, typo
- Replace generic alt="image" on scaling diagrams with descriptive text
identifying cloud provider and user scale.
- Convert raw div.important markup in deploy-containers.mdx to the
repo's <Important> component, matching usage elsewhere in the file.
- Fix "Matermost" typo in manage-your-display-options.mdx.
---------
Co-authored-by: Hanzo Dev <[email protected]>
85 lines
6.1 KiB
Plaintext
85 lines
6.1 KiB
Plaintext
---
|
|
title: "Cloud Dedicated"
|
|
---
|
|
import Inc0_cloud_supported_integrations from './cloud-supported-integrations.mdx';
|
|
|
|
Mattermost Cloud Dedicated is designed for larger organizations with higher demands for performance, scalability, customizability, and compliance looking to offload operational overhead and focus on more business-critical tasks.
|
|
|
|
Your own private Mattermost instance running [Mattermost Enterprise](/product-overview/editions-and-offerings) is a Kubernetes cluster hosted and managed by Mattermost that runs on dedicated cloud infrastructure, where resources are exclusively available for your organization.
|
|
|
|
## Reference architecture
|
|
|
|
|
|
|
|
## Available features
|
|
|
|
### Zero-downtime upgrades
|
|
|
|
Mattermost releases biweekly updates and leverages recurring maintenance windows to keep your instance up-to-date with new stable or beta features behind feature flags, fix security issues, and ensure the overall reliability and performance of your environment. Maintenance windows are announced in advance on [https://status.mattermost.com/](https://status.mattermost.com/)
|
|
|
|
Additional support options, including quicker response times, dedicated support personnel, and stronger service level agreements (SLAs), are also available.
|
|
|
|
### Disaster Recovery
|
|
|
|
Mattermost Cloud Dedicated supports data failover to a secondary region/site should the primary instance experiences an unrecoverable outage with guaranteed recovery times.
|
|
|
|
Mattermost supports a **multi-AZ (availability zones)** strategy in the same site/region.
|
|
|
|
Daily backups of the database, object storage, and high availability clusters are captured and retained for 30 days.
|
|
|
|
In addition, highly available observability tools with automated alerting, long-term metrics, and logs retention are retained for a duration of 1 year, or longer, if requred.
|
|
|
|
### Security
|
|
|
|
You have access to all the resources required to run the Mattermost application with the highest security standards, including data encryption at rest and in transit.
|
|
|
|
Your pre-configured cluster is secure by default, based on industry best practices including Data encryption at rest and in transit, TLS certificates life cycle management, and automatic security updates.
|
|
|
|
Mattermost maintains control over network and security policies, including [encryption](#encryption), database, data, object storage, backup schedules, and compliance certifications.
|
|
|
|
### Authentication and authorization
|
|
|
|
Mattermost offers advanced security and authentication options for integrating with corporate directories, including [Active Directory/LDAP](/administration-guide/onboard/ad-ldap), [Okta](/administration-guide/onboard/sso-saml-okta), [OneLogin](/administration-guide/onboard/sso-saml-onelogin), [SAML](/administration-guide/onboard/sso-saml), [Google](/administration-guide/onboard/sso-google), [EntraID](/administration-guide/onboard/sso-entraid), and [OpenID](/administration-guide/onboard/sso-openidconnect).
|
|
|
|
### Secure networking
|
|
|
|
Mattermost Cloud Dedicated supports [IP filtering](/administration-guide/manage/cloud-ip-filtering) through CIDR-based IP ranges, providing flexibility for system administrators to include various authorized IPs or IP ranges for seamless access control. Users attempting to access their [workspace](/end-user-guide/end-user-guide-index) from IPs outside defined ranges are restricted from entry. Cloud system admins can [configure IP filtering](/administration-guide/manage/cloud-ip-filtering#configure-ip-filtering) through their Mattermost System Console.
|
|
|
|
### Encryption
|
|
|
|
Mattermost provides encryption-in-transit and encryption-at-rest capabilities. Mattermost supports [TLS encryption](/deployment-guide/server/setup-tls), including AES-256 with 2048-bit RSA on all data transmissions, between Mattermost client applications and the Mattermost server. You may either set up TLS on the Mattermost Server or [install a proxy such as NGINX](/deployment-guide/server/setup-nginx-proxy), and set up TLS on the proxy.
|
|
|
|
Connections to [Active Directory/LDAP](/administration-guide/onboard/ad-ldap) can [optionally be secured with TLS or stunnel](/administration-guide/configure/authentication-configuration-settings#adldap-port).
|
|
|
|
Connections to calls are secured with a combination of:
|
|
|
|
- TLS: The existing WebSocket channel is used to secure the signaling path.
|
|
- DTLS v1.2 (mandatory): Used for initial key exchange. Supports `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256` and `TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA` algorithms.
|
|
- SRTP (mandatory): Used to encrypt all media packets (i.e. those containing voice or screen share). Supports `AEAD_AES_128_GCM` and `AES128_CM_HMAC_SHA1_80` algorithms.
|
|
|
|
### Cloud native exports
|
|
|
|
Mattermost supports optional [filestore configuration settings](/administration-guide/configure/environment-configuration-settings#enable-dedicated-export-filestore-target) to direct compliance and bulk export data to a separate S3 bucket from standard files. This separate bucket can be configured to allow for secure access by Mattermost Cloud teams as well as admins who manage a given Mattermost deployment. The exports can also be accessed by generating unique download links as needed.
|
|
|
|
The following diagram provides a high-level view of how this functionality works:
|
|
|
|
|
|
|
|
### SMTP
|
|
|
|
Email sent from Mattermost Cloud Dedicated uses SendGrid, and the connection to SendGrid is encrypted.
|
|
|
|
### Audit and observability
|
|
|
|
Mattermost Cloud Dedicated provides access to [audit and system logs](/administration-guide/manage/logging) generated by the application.
|
|
|
|
### Customization
|
|
|
|
The following Mattermost plugins are available for cloud-based deployments:
|
|
|
|
<Inc0_cloud_supported_integrations />
|
|
|
|
## Migrate from a self-hosted instance
|
|
|
|
See our [self-hosted to cloud migration](/administration-guide/manage/cloud-data-export#migrate-from-self-hosted-to-cloud) documentation to learn more about migrating from a self-hosted to a Mattermost Cloud instance.
|