Skip to main content

Infrastructure Management

You manage the cloud infrastructure that powers your Booga Enterprise tenant from the Admin Portal’s Infrastructure area. There you provision stacks, watch deployment health, reconcile configuration drift, and align user access with the regions where resources run. This guide explains what you see on screen, which actions you can take on each stack, and how subscriptions and entitlements shape what you are allowed to deploy. For broader product documentation, see the Booga Enterprise documentation site.

Overview​

Infrastructure Management lets you provision, monitor, and manage cloud resources for your tenant. The experience is organized with a tabbed layout so you can move between focused views—such as your stack list, operational tooling, and assignment workflows—without losing context.

Resources are deployed as infrastructure stacks. Each stack belongs to a cloud provider and region, carries one or more resource type labels, and reports a status that reflects whether deployments are healthy, in progress, or need attention. The platform may also flag drift when live cloud state no longer matches the desired configuration you manage in Booga Enterprise.

You interact with stacks through explicit actions: refreshing state, inspecting outputs and run history, running health checks, restarting where supported, and removing stacks when you no longer need them. Separate dialogs help you request new capacity, assign users to regions, review what your subscription allows, and clean up resources that have become orphaned from active stacks.

Prerequisites​

Before you rely on Infrastructure Management for production changes, confirm the following:

  • You hold an Admin or SuperUser role. Without that access, the Admin Portal does not expose infrastructure controls.
  • Your tenant has an active subscription that includes infrastructure entitlements. Provisioning and some operations are blocked when your plan does not include the requested capabilities or regions.
  • You have a clear picture of cloud requirements: which providers and regions you need, which resource types (storage, compute, search, and so on) your workloads depend on, and who must access which regional footprint.

If you are unsure about entitlements, open Subscription Management or use the Features view described later in this guide before you schedule large provisioning work.

Security Considerations​

Important: Infrastructure changes can affect application availability and incur cloud costs. All changes are logged for audit.

Treat every provision, restart, and delete as a production change. Prefer maintenance windows for disruptive operations, confirm you are targeting the correct stack and region, and keep regional user assignments aligned with data residency and access policies. When you delegate work, ensure colleagues understand that infrastructure screens can expose connection details in Outputs and similar views—share those details only through approved channels.

Cloud Providers​

Booga Enterprise supports provisioning across Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP). Each stack is tied to a single provider and region; you choose compatible combinations when you provision and when you review entitlements.

Stacks are created in specific regions based on what your subscription allows. If a region does not appear as available when you start a Provision Request, your plan or tenant configuration may not include it—verify entitlements before opening a support case.

Resource Types​

Stacks can include multiple logical capabilities. In the UI, these appear as resource type badges on each stack. Common types include:

  • Storage
  • Compute
  • Vector Database
  • Search
  • Workers
  • Machine Learning

The exact mix on a stack depends on what was provisioned and how your workloads use the platform. Use badges as a quick signal when you scan many stacks or when you coordinate with teams who own specific services.

Viewing Infrastructure Stacks​

The main infrastructure view lists every provisioned stack you are allowed to see. For each stack you typically get:

  • Stack name and a project identifier that groups the stack in your tenant’s inventory.
  • Cloud provider (Azure, AWS, or GCP) and region.
  • Resource type badges summarizing what the stack delivers.
  • A status indicator that shows whether the stack is healthy, transitioning, failed, or removed.
  • A drift indicator when the platform detects that live infrastructure no longer matches the intended configuration.

Use this list as your operational home: start here when users report outages, when costs spike, or when you need to confirm that new provisioning finished successfully.

Status Indicators​

Statuses use consistent color language so you can scan the page quickly:

  • Running, Succeeded, Active, Ready, and Available (green) — The stack is in a healthy, usable state for normal operations.
  • Pending, Creating, and Updating (orange) — Work is still in flight. Expect temporary unavailability or partial functionality until the operation completes.
  • Failed, Deleting, and Deleted (red) — Something went wrong or the stack is being torn down. Failed stacks need investigation; Deleting / Deleted indicate removal or cleanup in progress or completed.

When you see drift detected, treat it as a warning: refresh or reconcile the stack so desired state and actual state match before minor differences turn into incidents.

Provisioning New Resources​

When you need additional capacity or a new footprint, use the provision action to open the Provision Request dialog. There you select cloud provider, region, and resource type according to what your subscription permits.

The system validates your request against plan limits and entitlements before work begins. If validation fails, adjust the request—choose another region, reduce scope, or upgrade the subscription—rather than retrying the same ineligible combination repeatedly.

Multiple stacks and subscriptions (enterprise)​

Enterprise plans define how many resource stacks a single subscription can attach to (for example one primary footprint plus additional regions). When you already use every stack slot that subscription allows and you need another region or isolated footprint, the app may open a new subscription checkout instead of the usual provision dialog: you purchase a separate subscription for the same product with its own per-seat quantity and billing. After checkout completes, return to Infrastructure and provision the new stack under that subscription. Treat each stack-backed subscription as its own line item for seats and cancellation—see Subscription Management.

Stack Actions​

For each stack, you can perform operations that match how you run cloud infrastructure day to day:

  • Refresh — Pull the latest state from the cloud provider and reconcile what you see in Booga Enterprise. Use this after external changes or when you suspect stale metadata.
  • View Outputs — Open stack outputs such as endpoints, identifiers, and connection-related values your applications and integrations need. Handle this information as sensitive.
  • Copy — Copy identifiers or output values to your clipboard where the UI offers it, so you can paste into tickets or configuration without retyping.
  • View Runs — Open deployment history and logs so you can see what the platform last attempted and why a run succeeded or failed.
  • Health Check — Open Resource Health details to monitor health signals for the stack’s resources when you need to diagnose performance or availability issues.
  • Restart — Restart the stack where the platform supports it. Expect a confirmation step because this can interrupt workloads.
  • Delete — Remove the stack. Destructive actions use confirmation steps (including acknowledgements you must select) so you understand that data and endpoints in that stack may be lost or require export first. Always read the confirmation text carefully and download or migrate data from storage, search, and vector services before confirming if you need to retain it.
  • Delete permanently — When available, completes hard removal where the product distinguishes soft delete from permanent cleanup. Always read the confirmation text carefully.

The exact availability of an action can depend on stack status and your permissions; disabled controls usually mean the operation is not valid for the current state.

User Region Assignment​

You control which geographic regions individual users may use by opening the Assign User dialog from the relevant workflow. Assignments ensure people access infrastructure and dependent features only where your organization allows—supporting data residency, performance, and least-privilege access.

Plan region assignments before large provisioning efforts so you do not strand users in regions they cannot use. When roles or teams change, revisit assignments alongside User Management.

Subscription Entitlements​

Your infrastructure capabilities are governed by your subscription and entitlements. The Features view summarizes what your current plan includes—such as eligible providers, regions, maximum stacks per subscription, and product capabilities—so you understand boundaries before you request new stacks.

You cannot provision resources beyond your entitlements. If you need additional capacity, more stacks than one subscription allows, or new regions, work through additional subscriptions (when offered), seat or plan upgrades, or internal approval processes that align with your organization’s billing and governance.

Orphaned Resources​

Over time, cloud resources can become detached from the stacks that originally managed them. The Orphaned Resources view surfaces those stragglers so you can review and clean them up. Removing confirmed orphans helps you avoid paying for unused capacity and reduces security exposure from forgotten assets.

Treat cleanup as deliberate: verify that a resource is truly unused and that no hidden dependency still points to it before you delete.

Worker Pool Metrics​

When your deployment includes Workers, you can open Worker Pool Metrics to monitor pool performance and resource utilization. Use this view when you tune concurrency, investigate queueing, or validate that worker capacity matches workload demand.

Pair metrics with Health Check and View Runs when you chase intermittent failures—numbers alone rarely tell the whole story without the corresponding deployment context.

Best Practices​

  • Monitor stack health on a regular cadence, not only when users complain. Early attention to Failed or long-running Updating states prevents larger outages.
  • Address drift warnings promptly. Drift often precedes failed deployments or configuration surprises in downstream applications.
  • Clean up orphaned resources after reorganizations or decommissioning projects so your cloud bill and attack surface stay under control.
  • Plan region assignments before you expand infrastructure, especially when multiple teams share the same tenant.
  • Schedule risky changes—large provisions, restarts, deletes—during low-usage periods and communicate windows to stakeholders who depend on affected services.

Troubleshooting​

  • Stack stuck in Creating — Confirm your subscription includes the requested provider, region, and resource entitlements. Try Refresh after a few minutes; if state does not advance, use View Runs for error detail and verify there are no org-wide blocks on cloud access.
  • Failed status — Open View Runs first. Logs usually point to quota, permission, or validation errors from the cloud or the deployment engine. Fix the underlying issue before you retry destructive fixes.
  • Cannot provision — Revisit Features and your subscription. If the plan should include infrastructure but controls stay disabled, verify your role and that billing or entitlement sync completed. If the UI offers Subscribe or add a subscription for another stack, complete that in Subscription Management / checkout first, then provision again.
  • Drift detected — Run Refresh to reconcile state with the provider. If drift returns immediately, investigate whether someone changed resources outside Booga Enterprise or whether automation is fighting manual edits.

For more guides and reference material, continue with the Booga Enterprise documentation site.

⏱️ Read time: 12 minutes | 📊 Difficulty: advanced