Which Environment Variables Are Protected When Creating a Debug Training Job?

Constraints on Custom Environment Variables

1. Variables starting with MA_
   • Purpose: Used internally by ModelArts for managing service configuration, resource allocation, and other core functions.
   • Constraints: You must not set these manually. Modifying them may cause service initialization failures or unexpected behavior.
2. Specific key variables
   • ENABLE_HTTPS
     • Purpose: Controls whether the service uses HTTP or HTTPS. This is managed automatically by the platform.
     • Constraints: Manually setting this variable triggers security validation and may cause initialization errors.

Solution

1. Check your custom image: Remove any MA_‑prefixed variables or ENABLE_HTTPS settings from the Dockerfile or build scripts.
2. Check your job configuration: Remove related environment variable settings from the console or API configuration.
3. Create a new job: Save the updated configuration and recreate the training job.