Organizations and Environments
In this document, you will learn how AISIX Cloud organizes managed gateway resources by organization and environment, and how those scopes affect live traffic.
Overview
Organizations and environments define the two main Cloud scopes in AISIX Cloud. The organization establishes who owns the Cloud account and its shared administration. The environment establishes which managed gateway or gateways receive projected configuration.
This separation keeps account administration separate from traffic behavior. Members, billing, and provider credentials belong to the organization. Models, caller API keys, policies, and cache policies belong to the environment that serves traffic.
For live traffic, the environment is usually the scope that matters first. A saved environment resource affects live traffic only when it belongs to the environment attached to the target managed gateway.
Members, billing, shared administration, and provider credentials.
Holds resources for a development gateway.
Holds resources for a production gateway.
Scope Model
AISIX Cloud can manage more than one gateway and more than one set of gateway resources. Organizations and environments make it clear which team owns the account and which managed gateway receives each environment-scoped resource.
Organization Scope
An organization is the top-level ownership boundary in AISIX Cloud. It is the scope for members, billing, shared administration, and provider credentials.
Use organization scope to reason about account ownership and shared administration. It is usually not the first scope to check when a saved gateway resource does not affect live traffic.
Environment Scope
An environment is the unit that groups gateway resources and projects them to the attached managed gateway or gateways.
Environment scope turns saved Cloud state into live gateway behavior. A resource can exist in AISIX Cloud and still not affect the gateway you are testing if it belongs to another environment.
When a resource does not affect traffic as expected, confirm first that the resource belongs to the same environment as the target managed gateway. For provider keys, also confirm that the provider key is allowed in that environment.
Next Steps
You have now seen how AISIX Cloud resource scope is organized. Continue with Resource Projection for how environment resources reach the gateway.