Multi-Cloud Deployment
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.
More from wgpsec/redc-template
terraform-provider-docs
Look up official Terraform provider documentation before writing or debugging any Terraform resource, data source, or provider configuration. Use this skill whenever you encounter a Terraform error, need to write a new resource block, are unsure about argument syntax or valid values, need to check resource attribute constraints, or want to understand provider-specific behaviors. Consult the docs first instead of guessing Terraform arguments from memory — it consistently saves multiple debug cycles.
1aws security hardening
AWS security hardening guide for red team infrastructure. Use this skill whenever the user is deploying to AWS, configuring IAM policies, setting up VPCs or security groups, asking about SSH access, encryption, key rotation, or any AWS security question. Also apply when the user mentions EC2 instances, EBS volumes, S3 buckets, or AWS networking — even if they don't explicitly ask about "security", because every AWS deployment should follow these hardening practices by default.
1cloud cost optimization
Strategies for minimizing cloud infrastructure costs in red team deployments. Use this skill whenever the user asks about pricing, budgets, cost estimates, instance sizing, spot instances, or resource cleanup. Also apply when the user is choosing instance types, discussing how long to keep infrastructure running, asking about billing alerts, or planning a deployment where cost is a concern — even if they don't explicitly mention "cost" or "budget". Proactively reference this skill when generating templates to suggest cost-saving alternatives.
1terraform best practices
Terraform IaC best practices for cloud infrastructure deployments. Use this skill whenever the user is writing Terraform code, creating templates, generating .tf files, asking about state management, modules, variables, security groups, or any infrastructure-as-code question. Also use when reviewing or debugging Terraform configurations, discussing provider setup, or planning multi-resource deployments — even if the user doesn't explicitly mention "Terraform" but is clearly working with .tf files or HCL syntax.
1deployment troubleshooting
Diagnose and fix Terraform deployment errors in RedC scenarios. Use this skill whenever the user encounters an error during deployment — whether it's a Terraform init failure, authentication error, resource creation failure, network timeout, state conflict, or cloud-init problem. Also use when the user pastes an error message, says "deployment failed", asks why something isn't working, or reports that instances are unreachable after creation. This skill covers the most common failure modes across all cloud providers supported by RedC.
1