Managing API keys and data spaces across multiple Adobe Commerce instances
Multiple Adobe Commerce instances under the same account can share API keys and data spaces when configured through the Commerce Services Connector. If the same data space is used across instances, it can cause data mixing and inconsistent behavior across environments.
To resolve the issue, assign a unique data space to each instance.
Description description
Environment
- Adobe Commerce (all deployment methods)
- Services: Live Search, Catalog Service, Payment Services
- Scenario: Multiple Adobe Commerce instances under the same parent account using shared API keys
- Versions: All versions
Issues/Symptoms
- Commerce instances display overlapping or mixed data
- Multiple instances select the same Production or Testing data space
- Commerce Services Connector shows shared data spaces across instances
- Instance data appears shared across environments
Root cause
API keys and data spaces belong to the parent account instead of to individual instances. Selecting the same data space across multiple instances causes shared data processing and leads to data mixing.
Resolution resolution
To resolve this issue, follow the steps below:
- Review all Commerce instances associated with the same account and verify the selected data space in each instance using the Commerce Services Connector.
- Assign a unique data space to every instance based on its environment.
- Use a dedicated Production data space for production instances and separate Testing data spaces for non-production environments.
- Avoid selecting the same data space across multiple instances to maintain proper data separation.
- Request additional data spaces through Adobe Support when needed. If you need additional data spaces for a new instance, submit a Support ticket to request additional Production and Testing data spaces.
Example scenario
The account owner creates multiple API keys and data spaces:
- Instance A (Production) uses Production API key and selects the Production data space.
- Instance B (New installation) uses a different API key but selects the same Production data space.
As a result, both instances share the same data space, causing data mixing and inconsistent behavior across environments.
To avoid this, ensure each instance uses a separate data space.
Related reading
For more information, refer to the official documentation: