meshcloud

meshcloud

  • User Docs
  • Operator Docs
  • API Docs
  • Release Notes
  • FAQ
  • Help
  • Feedback

›meshcloud

meshcloud

  • Overview
  • meshCustomer
  • meshProject
  • meshTenant
  • meshTenant Quota
  • Landing Zones
  • User Account
  • meshPlatforms
  • Project Resources
  • Project Metering
  • Payment Methods
  • Budget Alerts
  • Service Users
  • Metadata Tags
  • meshPolicies

meshMarketplace

  • Overview
  • Service Instances

Administration

  • Overview
  • meshCustomers
  • meshProjects
  • meshTenants
  • Delete Tenants
  • meshUsers
  • meshPlatforms
  • Landing Zones
  • Usage Reports
  • Resource Inventory
  • Service Brokers
  • Analytics
  • Guide: Emergency Users
  • meshPolicies
  • Unmanaged Tenants
  • meshStack Settings
  • API Users

Platforms

  • OpenStack
  • Cloud Foundry
  • Azure
  • Other Platforms

Guides

  • How to onboard your team to your meshCustomer
  • How to create a meshProject
  • How to onboard your team to a meshProject
  • How to change the Customer Owner of a meshCustomer via API
  • How to delete meshObjects in the meshPanel

FAQ

  • Projects FAQ
Edit

Landing Zones

Landing Zones describe a set of policies that are automatically applied to tenants created for a meshProject. They relate to a "bootstrap" configuration in the meshPlatform, that sets up and configures the cloud tenant according to policies and requirements of your company.

Typical use-cases for Landing Zones are setting up cloud tenants to restrict administrative privileges over core configuration like identity and access management. This ensures company policies with regards to authentication and authorization are consistently enforced across all cloud tenants. Other common use cases include cloud service or region restrictions to ensure compliance regarding data processing restrictions.

Another use-case is defining default quotas in private cloud environments that are directly applied to your meshTenant after creation. This allows your operators to provide you direct access with a limited scope. When you require a higher quota, you can create a quota request, which must be approved by a platform operator.

Operators can provide multiple Landing Zones per meshPlatform. This allows e.g. different setups for a Dev, QA and Production stage. Landing zones can also consume project meta-data like cost-center or similar attributes and use it.

Only your Platform Operators can configure Landing Zones and control their content. Your operations team can provide details how Landing Zones are used in your meshcloud installation.

Using Landing Zones

Customer administrators can chose a Landing zone when adding meshTenants to a meshProject. It is not possible to change the chosen Landing Zone of an existing meshTenant. The only way of doing so is by removing the meshTenant and creating another by re-adding the same meshPlatform to the Project again.

Last updated on 3/21/2023
← meshTenant QuotaUser Account →
  • Using Landing Zones
meshcloud
Docs
User DocumentationOperator Documentation
Community & Follow us
TwitterFacebookLinkedInXING
More
Release NotesGitHub
Copyright © 2023 meshcloud GmbH