Cloud-Administrator werden: Was sich ändert, wenn du aus dem Rechenzentrum kommst

# Azure
az login
az account show --output table
az account list --output table
az group list --output table

# AWS: Anmeldung ueber IAM Identity Center statt ueber Zugriffsschluessel
aws configure sso
aws sts get-caller-identity
aws ec2 describe-regions --query 'Regions[].RegionName' --output text

# Azure Resource Graph: alle virtuellen Maschinen mit Groesse und Region
az graph query -q "Resources
  | where type =~ 'microsoft.compute/virtualmachines'
  | project name, location, properties.hardwareProfile.vmSize" --output table

# AWS: laufende Instanzen samt Typ und Zone
aws ec2 describe-instances \
  --filters "Name=instance-state-name,Values=running" \
  --query 'Reservations[].Instances[].[InstanceId,InstanceType,Placement.AvailabilityZone]' \
  --output table

az group create --name rg-lab --location germanywestcentral

az network vnet create --resource-group rg-lab --name vnet-lab \
  --address-prefixes 10.20.0.0/16 \
  --subnet-name snet-app --subnet-prefixes 10.20.1.0/24

az vm create --resource-group rg-lab --name vm-app01 \
  --image Ubuntu2404 --size Standard_B2s \
  --vnet-name vnet-lab --subnet snet-app \
  --public-ip-address "" --generate-ssh-keys

aws ec2 create-vpc --cidr-block 10.30.0.0/16 \
  --tag-specifications 'ResourceType=vpc,Tags=[{Key=Name,Value=vpc-lab}]'

aws ec2 create-subnet --vpc-id vpc-0123456789abcdef0 --cidr-block 10.30.1.0/24

aws ec2 create-security-group --group-name sg-app \
  --description "App-Schicht" --vpc-id vpc-0123456789abcdef0

aws ec2 run-instances --image-id ami-0123456789abcdef0 \
  --instance-type t3.small --subnet-id subnet-0123456789abcdef0 \
  --security-group-ids sg-0123456789abcdef0 \
  --tag-specifications 'ResourceType=instance,Tags=[{Key=Umgebung,Value=lab},{Key=Kostenstelle,Value=4711}]'

terraform {
  required_providers {
    azurerm = {
      source  = "hashicorp/azurerm"
      version = "~> 4.0"
    }
  }
}

provider "azurerm" {
  features {}
}

resource "azurerm_resource_group" "lab" {
  name     = "rg-lab"
  location = "germanywestcentral"

  tags = {
    umgebung     = "lab"
    kostenstelle = "4711"
  }
}

terraform init
terraform plan -out=tfplan      # zeigt vorher, was passieren wuerde
terraform apply tfplan          # fuehrt genau diesen Plan aus

terraform destroy               # raeumt die Uebungsumgebung vollstaendig ab

# Azure ohne Zustandsdatei, direkt gegen die Ressourcenverwaltung
az deployment group create --resource-group rg-lab \
  --template-file main.bicep --parameters umgebung=lab

SCOPE=$(az group show --name rg-lab --query id -o tsv)
GRUPPE=$(az ad group show --group 'team-app' --query id -o tsv)

az role assignment create \
  --assignee-object-id "$GRUPPE" \
  --assignee-principal-type Group \
  --role "Virtual Machine Contributor" \
  --scope "$SCOPE"

az role assignment list --scope "$SCOPE" --output table

# AWS: was kostet gerade welcher Dienst?
aws ce get-cost-and-usage \
  --time-period Start=2026-07-01,End=2026-08-01 \
  --granularity MONTHLY --metrics UnblendedCost \
  --group-by Type=DIMENSION,Key=SERVICE

# Azure: bestehende Budgets pruefen
az consumption budget list --output table

# Uebungsumgebung vollstaendig entfernen
az group delete --name rg-lab --yes --no-wait
terraform destroy