Cloud Admin UI Settings

The Cloud Admin UI provides a web interface to manage your Commerce Cloud project, environments, settings, and deployments.

Where to Find Project Settings

Access project-level settings from the main project dashboard:

• User Management: Add/remove users and manage access permissions
• Project Variables: Configure environment variables available across all environments
• General Settings: Project name, region, and configuration

Manage team access to the Cloud project:

• Add new users with email addresses
• Set permission levels (Admin, Contributor, Viewer)
• Remove user access
• Manage SSH key access

Configure variables that apply to all environments:

• Set environment-specific configuration
• Store API keys and credentials securely
• Configure application settings
• Available across all branches/environments

The Environments page shows your project's environment tree:

• Visual tree structure of all branches/environments
• Active vs inactive environments
• Parent-child relationships
• Environment status indicators

Environment Tree Structure

For Starter:

• master (production)
• staging
• integration branches

For Pro:

• master (production)
• staging
• integration (base)
• development branches

Each environment provides multiple access methods:

• Web URL: Direct link to frontend
• SSH Access: Command-line access to environment
• Admin Panel: Link to Magento admin
• Database Access: MySQL connection details

Log Locations

Logs are stored in different locations depending on environment tier:

Starter & Pro Integration Environments

Access via SSH to the environment.

Pro Staging & Production

Important for Pro: You must log into all three nodes to access logs across the cluster.

Accessing Logs

• SSH into the environment
• Navigate to log directory
• Use commands like tail, less, or grep
• Download logs for local analysis if needed

Common Log Files

• deploy.log - Deployment process logs
• system.log - Magento system logs
• exception.log - PHP exceptions
• debug.log - Debug information
• error.log - Server error logs

The Environment Control Panel provides basic actions for each environment:

• View Logs: Access deployment and application logs
• Restart Services: Restart web server, cache, etc.
• Clear Cache: Flush Magento and platform caches
• Redeploy: Trigger a new deployment
• Delete Environment: Remove inactive environments

Inside each environment's configuration, you can change settings:

Available Settings

1. Environment Status

• Enable or disable the environment
• Disabled environments don't consume resources
• Cannot access disabled environments via web

2. Outgoing Emails

• Disabled by default in all non-production environments
• Must explicitly enable for testing email functionality
• Prevents accidental customer emails from staging/integration

3. Search Engine Indexing

• Control whether search engines can index the environment
• Disable for staging/development to prevent duplicate content issues
• Enable only for production

4. HTTP Access Control

• Restrict access with username/password (HTTP Basic Auth)
• Ideally used on staging to prevent search engines and unauthorized access
• Add multiple username/password combinations
• Protects non-production environments

At the top of each branch/environment, there are 5 very important buttons:

1. 📋 Git/CLI Access

• Provides commands and git remote details
• Shows how to load project locally to your system
• Includes SSH connection string
• Git clone command with authentication

git clone <project-url>
magento-cloud checkout <environment>

2. 🌿 Branch (Create New Environment)

• Create a new branch (environment) from the current branch
• Only enabled if you have permission and available environments
• Creates child environment with copied data

3. 🔀 Merge

• Merges the current branch to its parent
• Integration → Staging
• Staging → Master
• Not available on master branch (no parent to merge to)
• Triggers automatic deployment to parent environment

4. 🔄 Sync

• Syncs code and/or data and files from parent
• Can sync code only, data only, or both
• Also available via magento-cloud CLI
• Useful for refreshing integration with production data

magento-cloud environment:synchronize

5. 💾 Backup (Snapshot)

• Creates a backup/snapshot of the environment
• Includes database and files
• Can restore from snapshots later
• Recommended before major changes

Branch vs Environment

The DevDocs and Admin UI use branch and environment interchangeably:

• Branch: Git branch in your repository
• Environment: A branch that is activated and publicly accessible via the web
• An environment is an enabled branch
• Inactive branches exist in git but don't have running environments

Three-Node Cluster

For Pro Staging and Production:

• Runs on three separate nodes for fault tolerance
• Must log into all three nodes to access complete logs
• Load balanced across nodes
• Higher availability and performance

• Magento Commerce Cloud Architecture
• Starter Architecture
• Pro Architecture
• Pro Develop and Deploy Workflow
• Cloud Project Management