---
schema_version: "1"
id: 3db4f33d1f8c9a2cbce71be5110e65d9ff9f7155468fb4b64761260c6d08dc2e
title: Configuring Inbound TLS for Managed Flex Gateway
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/1.12/flex-managed-inbound-tls-config.md
canonical_url: https://docs.mulesoft.com/gateway/1.12/flex-managed-inbound-tls-config
source_site: docs.mulesoft.com
content_type: documentation
content_hash: f966755509ef5a6dcbe0759d43a63aa00142d518072a0fabeadaed3ce02efa02
description: MuleSoft Documentation Site
release: "1.12"
latest: false
---
---
product: Omni Gateway
version: 1.12
---

# Configuring Inbound TLS for Managed Flex Gateway

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

For Managed Flex Gateway deployed on CloudHub 2.0, the CloudHub 2.0 private space manages the
inbound TLS.

To configure a TLS context for the private space you’re deploying your Managed Flex Gateway to, see
[Configuring Domains and Certificates (TLS Context) for a Private Space](https://docs.mulesoft.com/cloudhub-2/ps-config-domains).

Configuring a TLS context for your private space means all APIs deployed to Managed Flex Gateways in
the private space are HTTPS and secure.

To configure outbound TLS context, see
[Configuring Outbound TLS for Managed Flex Gateway](https://docs.mulesoft.com/gateway/1.12/flex-managed-outbound-tls-config).