Add more environment variables after reaching the limit of 200 environment variables
The article discusses the alternate storage options for adding more environment variables after reaching the limit of 200 variables in Adobe Experience Manager as a Cloud Service (AEMaaCS).
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS)
Issue/Symptoms
After reaching the limit of 200 variables, is it possible to add more environment variables. If not, are there any recommendations on alternative storage options for these variables?
Resolution resolution
If you have reached the current limit of 200 environment variables in Adobe Experience Manager as a Cloud Service (AEMaaCS), you won’t be able to add more directly.
However, if you have reached this limit and need to add more variables, consider the following strategies:
-
Optimize Existing Variables: Review and consolidate existing variables to free up space.
-
External Storage Solutions: Use external storage options like AWS S3, Azure Blob Storage, or Google Cloud Storage to store additional configurations.
-
Secrets Management Tools: Utilize tools like AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault for managing sensitive information.
-
Environment-Specific Configuration Files: Store configurations in separate files and load them at runtime.
Note: There is no other OOTB possibility to add more than 200 variables other than the options already presented.