Cross-Cloud without Crossed Fingers: Surviving Azure, AWS, and GCP with PowerShell
summary
PowerShell becomes the anchor: a small module called PS Cumulus normalizes cloud resources across Azure AWS and GCP into eight fields (name provider region status size createdAt tags metadata), returns PowerShell objects, and exposes about 11 public commands for listing and querying instances, disks, storage and networks. The demo is partly mocked but works, uses each provider’s native sessions and tokens, avoids IAM and has no write commands (read only for now, eventual start/stop only), and treats Terraform as a separate provisioning tool.
AI-written summary · about
chapters (10)
- 0:00Multi-cloud challenges
- 1:54Why multi-cloud environments are difficult
- 3:41PowerShell as unifier
- 5:24PS Cumulus design
- 7:08Live demo of PS Cumulus
- 10:58Normalizing cloud data
- 12:20Supported commands
- 14:05Terraform vs operations
- 15:30PS Cumulus purpose
- 16:10Q&A
related talks
46mPowerShell on AWS CloudShell
43mUsing PowerShell From a Browser to Manage Cloud Resources
47mIt’s PowerShell In the Cloud – Welcome to Azure Cloud Shell
45mMulti-Cloud & On-Premise, Let's Cross Borders! Get the Best of Both Worlds
41mManaging a Hybrid Infrastructure with PowerShell
43mPowerShell For Every System
42mPowerShell Guide to Terraform
46m0-60 with PowerShell on AWS