CloudWeave
Plateforme d'orchestration IaC gérant 200+ ressources cloud avec provisioning automatique, drift detection, cost optimization et compliance as code.
Client
Cloud service provider
Stack
Fonctionnalités
Infos
Les noms de domaine affichés sont purement illustratifs. Par souci de confidentialité, les vrais domaines des projets ne peuvent être divulgués.
Infrastructure Dashboard
STACKS
8
6 healthy
RESOURCES
142
across 3 providers
MONTHLY COST
$4,280
↑ 3% vs last month
DRIFT DETECTED
2
resources
LAST DEPLOY
2h ago
production
Stacks
production-vpc
production-k8s
production-rds
staging-infra
monitoring-stack
dns-global
ci-runners
dev-sandbox
By Provider
Recent Activity
Stacks › production-k8s
production-k8s
AWS • eu-west-1 • 35 resources • Last apply 2h ago
LAST PLAN — Run #247
cloudweave plan
Refreshing state... [35 resources]
aws_eks_cluster.main: Refreshing...
aws_eks_node_group.workers: Refreshing...
aws_iam_role.eks_role: Refreshing...
aws_security_group.eks_sg: Refreshing...
kubernetes_namespace.apps: Refreshing...
kubernetes_deployment.api: Refreshing...
kubernetes_service.api_lb: Refreshing...
No changes. Infrastructure is up-to-date.
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.
RESOURCES (35)
+ 20 more resources
CONFIGURATION
RUN HISTORY
Resources (142)
Modules Registry
vpc-network
Complete VPC with public/private subnets, NAT, and VPN
eks-cluster
Production-ready EKS cluster with managed node groups and autoscaling
rds-postgres
RDS PostgreSQL with Multi-AZ, automated backups, and monitoring
s3-bucket
S3 bucket with encryption, versioning, lifecycle, and replication
iam-roles
IAM roles and policies following least privilege principle
cloudflare-dns
Cloudflare DNS zone with records, page rules, and WAF
gke-cluster
GKE Autopilot cluster with Workload Identity
monitoring-stack
Prometheus + Grafana + AlertManager on Kubernetes
cert-manager
cert-manager with Let's Encrypt and DNS01 challenge
eks-cluster
v3.1.0 • AWS • Published 2 weeks ago
# Usage
module "eks" {
source = "cloudweave/eks-cluster/aws"
version = "3.1.0"
cluster_name = "production"
cluster_version = "1.28"
vpc_id = module.vpc.vpc_id
subnet_ids = module.vpc.private_subnet_ids
node_groups = {
workers = {
instance_types = ["m6i.xlarge"]
min_size = 3
max_size = 10
desired_size = 5
}
}
}
Policy as Code
TOTAL POLICIES
24
PASSING
21
87.5%
FAILING
2
action required
ADVISORY
1
non-blocking
Security
4/5 passingS3 buckets must not have public access
All storage resources must have encryption enabled
Resources must not use the default VPC
IAM users must have MFA enabled
IAM policies must not use wildcard (*) actions
Cost
2/3 passingEC2 instances must not exceed m6i.2xlarge
All resources must have team, env, and cost-center tags
Elastic IPs must be associated with a resource
Reliability
2/3 passingRDS instances must be Multi-AZ in production
All databases must have automated backups
EKS node groups must have min 3 nodes
# policy: mfa-iam-users
rule mfa_required {
resource "aws_iam_user" {
condition = has_mfa_device == true
severity = "critical"
message = "IAM user must have MFA enabled"
}
}
Violation: aws_iam_user.deploy_bot in stack prod-vpc
User "deploy_bot" does not have MFA configured. This is required for all IAM users per security policy.