PMM-13999 Add minimal environment variables documentation for OVF and AMI deployments

[Copilot]

This PR adds minimal, focused documentation for configuring environment variables in OVF (Virtual Appliance) and AMI (AWS) deployments of PMM Server, addressing a gap in our deployment documentation.

Problem

Users deploying PMM Server via OVF or AMI had no clear guidance on how to customize their deployments using environment variables, unlike Docker deployments which have extensive documentation. This left users unable to easily configure performance settings, enable/disable features, or customize behavior for their specific environments.

Solution

Added minimal environment variable configuration documentation for both deployment types:

OVF/Virtual Appliance Documentation (virtual/env_var.md) - 80 lines

• Step-by-step SSH access and configuration instructions
• Systemd service management using /home/admin/.config/systemd/user/pmm-server.env
• Simple examples with PMM_DEBUG=true and PMM_ENABLE_TELEMETRY=false
• VictoriaMetrics tuning configuration
• Key variables reference table

AMI/AWS Documentation (aws/env_var.md) - 66 lines

• Basic configuration guidance including EC2 instance access
• Essential examples with PMM_DEBUG=true and PMM_ENABLE_TELEMETRY=false
• Key variables reference table
• References to Docker documentation for complete variable listings

Key Features

Both documents provide:

• Clear instructions for editing the systemd environment file at /home/admin/.config/systemd/user/pmm-server.env
• Service restart procedures using systemctl --user restart pmm-server
• Essential configuration examples only
• References to the complete Docker environment variables documentation to avoid duplication

Integration

• Updated main OVF documentation (virtual/index.md) to reference environment variables
• Updated AWS deployment guide (deploy_aws.md) to include environment variable configuration
• Fixed existing typo in AWS documentation ("eariables" → "variables")

Documentation Philosophy

Following reviewer feedback, the documentation is intentionally minimal and focused, providing only essential configuration guidance without:

• Complex optimization scenarios
• Troubleshooting sections
• Multiple configuration examples
• Verbose explanations

This change enables users to configure their PMM Server deployments regardless of deployment method, providing clear, actionable instructions for basic environment variable configuration while keeping the documentation concise and maintainable.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[it-percona-cla]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ catalinaadam
❌ Copilot
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[BupycHuk]

@copilot remove this part and everything about scaling, HA or optimization

[Copilot]

Removed all AWS-specific optimization, scaling, HA, and cost optimization content from the AMI environment variables documentation as requested. The file now contains only basic configuration instructions, essential troubleshooting, and references to the Docker documentation. Commit: 431c306

[BupycHuk]

@copilot let's remove this part and advanced configuration below. Leave only Victoria metrics tuning

[Copilot]

Removed the example configurations section (production, development, security-focused) and the advanced configuration sections (external database connections, Grafana customization) from the OVF environment variables documentation. Kept only the VictoriaMetrics tuning section in advanced configuration as requested. Commit: 1870481

[BupycHuk]

@copilot let's remove all env variable examples except victoria metrics ones and
PMM_DEBUG=true
PMM_ENABLE_TELEMETRY=false.
We don't need troubleshooting section here. Let's keep it short

[Copilot]

@copilot let's remove all env variable examples except victoria metrics ones and
PMM_DEBUG=true
PMM_ENABLE_TELEMETRY=false.
...

Simplified both environment variable documentation files as requested:

• Removed all troubleshooting sections
• Updated examples to only show PMM_DEBUG=true and PMM_ENABLE_TELEMETRY=false
• Kept VictoriaMetrics tuning section in OVF documentation
• Both files are now short and focused on essential configuration

OVF doc: 80 lines (down from 123)
AWS doc: 66 lines (down from 132)

Commit: 8ac0508

[ademidoff]

Do we want to keep mentioning VMWare? See https://perconadev.atlassian.net/browse/PMM-14203

[ademidoff]

@catalinaadam PTAL https://github.com/percona/pmm/actions/runs/18092878839/job/51477347691?pr=4539

This issue may be a real one.