Skip to content

Resource Pools ​

Feature Overview ​

ItemContent
Applicable RolesOperators
Navigation PathAI Infra(On-Cloud) > Access Management > Resource Pools
Page Route/infrahub/op/access/region
Managed ObjectsRegional resource pools under cloud platforms and their enabled states

Beginner Explanation ​

Resource Pools controls whether cloud regions are available. Enabled pools can enter authorization and scheduling scopes; disabling affects deployment choices.

Terminology ​

TermDescription
Resource PoolAn available resource scope organized by cloud platform and region.
Enabled StateWhether a pool can enter authorization and scheduling workflows.
Enabled OnlyA filter that shows only enabled pools.

Select a cloud platform and review its pools, assess authorization and deployment impact, then change the target state and verify downstream visibility.

Beginner Checklist ​

ScenarioDo FirstDo Not Do Directly
First visitReview existing objects, states, and available actionsChange an unknown object
Before a changeVerify upstream dependencies, impact scope, and target objectSkip dependency and impact checks
After completionValidate the current and downstream pages with Result ValidationRely only on a success message
Page errorRecord the redacted object, time, and page messageSubmit repeatedly or record real credentials

Prerequisites ​

  1. The current account has the permission required for Resource Pools.
  2. The target cloud platform is connected and its pool list loads correctly.
  3. Before changing state, check tenant authorization, business authorization, scheduling policies, and existing deployments.

Page Description ​

The left side lists cloud platforms; the right side shows regional pools and state switches for the selected platform.

Page screenshots:

Resource Pools page

The image shows the Resource Pools management page, with connected cloud platforms listed on the left and corresponding regional resource pools with enable/disable toggles on the right.

Main Operations ​

View Resource Pools ​

  1. Select the target cloud platform on the left.
  2. Use Enabled Only within the step when a narrower list is needed.
  3. Verify region names and enabled states.

Enable or Disable Resource Pool ​

  1. Locate the target region and confirm its current state.
  2. Toggle the state switch and read the region and action in the confirmation message.
  3. Click "Confirm" and refresh the list.
  4. Verify the expected visibility on authorization and deployment pages.

Enable or disable a resource pool

The image shows the secondary confirmation dialog when enabling or disabling a regional resource pool, where you must confirm the target region before proceeding.

Parameter Reference ​

Field NameRequiredField TypeExampleDescription
Cloud PlatformYesList itemAlibaba CloudCloud platform that owns the resource pools.
Resource Pool CountSystem-generatedNumber26 itemsNumber of resource pools under the current cloud platform.
Resource Pool NameSystem-generatedTextChina (Hangzhou)Resource pool name displayed by region on the current page.
Enabled StatusYesSwitchOn / OffControls whether the resource pool can continue to be authorized, displayed, or scheduled.
Show only enabledNoCheckboxSelected / unselectedFilters the list to show only enabled resource pools.
Name SearchNoInputDisplayed on pageSearches cloud platform or resource pool related entries by name.
ImportNoAction buttonImportImports resource pool related configuration and may affect real configuration. Use with caution.
ExportNoAction buttonExportExports resource pool list or configuration data. Pay attention to sensitive information.
Confirmation PromptSystem-generatedDialogAre you sure you want to Disable region China (Hangzhou)?Secondary confirmation shown before enabling or disabling.
CancelNoAction buttonCancelCloses the confirmation dialog without applying the change.
OKNoHigh-risk actionOKConfirms enabling or disabling the resource pool and applies a real status change.

Pitfalls ​

  • Do not skip the upstream dependency check: The target cloud platform is connected and its pool list loads correctly.
  • Confirm impact before a configuration change: Before changing state, check tenant authorization, business authorization, scheduling policies, and existing deployments.
  • A success message does not prove downstream synchronization. Use Result Validation afterward.
  • Use only <API_KEY>, <PERSONAL_KEY>, <ACCESS_KEY_ID>, <ACCESS_KEY_SECRET>, <BASE_URL>, and <ENDPOINT_PATH> for credential and endpoint examples.

Result Validation ​

Check ItemSuccess SignalIf Abnormal
Page is accessibleTitle, navigation, and main content display correctlyCheck role permission and navigation path
Managed objects are visibleRegional resource pools under cloud platforms and their enabled states display as expectedClear filters and verify upstream dependencies
Operation result is savedThe expected state or new record appearsReview page messages, required fields, and dependencies
Downstream result is consistentAssociated pages show the changeWait for synchronization, refresh, and return to the responsible object

FAQ ​

Target Object Is Missing in Resource Pools ​

Symptom:

The expected object is missing from the list or selector.

Possible Causes:

  • Active query criteria filter out the target object.
  • An upstream object is disabled, or the current role lacks visibility.

Resolution:

  1. Clear filters and refresh the page.
  2. Verify the prerequisite object: The target cloud platform is connected and its pool list loads correctly.
  3. Confirm the current role and data scope, then locate the object again.

Resource Pools Action Is Unavailable ​

Symptom:

An expected button, menu, or state switch is unavailable.

Possible Causes:

  • The current account lacks the required action permission.
  • Object state, references, or prerequisites block the action.

Resolution:

  1. Verify the permission for the action and the current object state.
  2. Check references and prerequisites identified by the page message.
  3. Remove the blocker, refresh the page, and perform the action once.

Resource Pools Change Does Not Reach Downstream ​

Symptom:

The page reports success, but a downstream page still shows the old state.

Possible Causes:

  • An associated page has stale cache or synchronization delay.
  • The current and downstream pages use different roles, tenants, or data scopes.

Resolution:

  1. Wait for synchronization and refresh both pages.
  2. Confirm that both pages use the same role, tenant, and object scope.
  3. If they still differ, return to the responsible object and verify the saved result.

Resource Pools Data Differs from Another Page ​

Symptom:

Counts or states differ from an associated page.

Possible Causes:

  • The pages use different filters, aggregation rules, or update times.
  • The change is still synchronizing, or role-based data scopes differ.

Resolution:

  1. Align filters and aggregation rules on both pages.
  2. Check update times and wait for synchronization.
  3. Compare object details instead of summary counts only.

How to Troubleshoot a Resource Pools Failure ​

Symptom:

Submission fails or the state does not change for an extended period.

Possible Causes:

  • Required fields, field combinations, or object state do not meet submission rules.
  • An upstream dependency is invalid, the request failed, or the same action is already processing.

Resolution:

  1. Record the redacted object, time, and complete page message.
  2. Verify required fields, object state, and upstream dependencies.
  3. Confirm that no identical job is processing before one retry.

Notes ​

  • Before changing state, check tenant authorization, business authorization, scheduling policies, and existing deployments.
  • Do not put real accounts, credentials, internal locations, or customer data in documentation, screenshots, tickets, or chat records.
  • Authorization, deployment, deletion, publication, state, or billing changes require an auditable record and recovery plan.

Next Steps ​

  1. Go to Tenant-Cloud Auth or Business-Region Auth to verify resource pool visibility scope.
  2. Go to Policies to confirm scheduling rules after enabling or disabling.
  3. Go to Access Overview to review resource pool status and resource checklist display.