Multi-Cloud Deployment Guide

RedC's core strength is deploying infrastructure across multiple clouds simultaneously. This skill covers the practical knowledge needed to work across providers — from authentication setup to region selection to cross-cloud consistency patterns. Understanding these differences matters because each cloud has its own authentication model, naming conventions, and regional availability, and getting any of these wrong means a deployment that fails at plan time.

Provider Authentication

Each cloud provider authenticates differently. Set these environment variables before running RedC, or configure them in RedC's credential profiles.

Provider	Required Environment Variables	Notes
AWS	`AWS_ACCESS_KEY_ID` + `AWS_SECRET_ACCESS_KEY`	Or use `~/.aws/credentials` profile
Azure	`ARM_SUBSCRIPTION_ID` + `ARM_TENANT_ID` + `ARM_CLIENT_ID` + `ARM_CLIENT_SECRET`	Service principal recommended
GCP	`GOOGLE_APPLICATION_CREDENTIALS` (path to JSON)	Service account key file
Alibaba Cloud	`ALICLOUD_ACCESS_KEY` + `ALICLOUD_SECRET_KEY`	China mainland requires real-name verification
Tencent Cloud	`TENCENTCLOUD_SECRET_ID` + `TENCENTCLOUD_SECRET_KEY`	SecretId, not AccessKey
Huawei Cloud	`HW_ACCESS_KEY` + `HW_SECRET_KEY`	Regional endpoints differ from global
Volcengine	`VOLCENGINE_ACCESS_KEY` + `VOLCENGINE_SECRET_KEY`	ByteDance cloud platform

Note the naming inconsistency — AWS uses "access key", Tencent uses "secret id", GCP uses a JSON file. This is a common source of confusion. When helping users configure credentials, pay attention to which provider they're targeting.