📄️ AWS
Provision an AWS CodeBuild project that runs JS Recon against any URL. Surface exposed endpoints, client-side vulnerabilities, and leaked source maps automatically on demand or on a schedule.
📄️ GCP
Provision a GCP Cloud Build trigger that runs JS Recon against any URL. Upload results to a GCS bucket automatically.
📄️ Azure
Provision an Azure Container App Job that runs JS Recon against any URL. Upload results to Azure Blob Storage automatically.
📄️ DigitalOcean
Provision a DigitalOcean Droplet that runs JS Recon against any URL. Upload results to DigitalOcean Spaces automatically.
📄️ IBM Cloud
Provision an IBM Code Engine Job that runs JS Recon against any URL. Upload results to IBM Cloud Object Storage automatically.
📄️ Oracle Cloud
Provision an OCI Container Instance that runs JS Recon against any URL. Upload results to OCI Object Storage automatically.
📄️ Alibaba Cloud
Provision an Alibaba Cloud ECI container group that runs JS Recon against any URL. Upload results to OSS automatically.
📄️ Common Reference
Every per-provider JS Recon Terraform module — AWS, GCP, Azure, DigitalOcean, IBM Cloud, Oracle Cloud, Alibaba Cloud — shares the same core scan-control inputs, the same set of output files, and the same break-condition and version-pinning mechanics. This page documents that shared surface once; each provider page documents only what's actually specific to that cloud (compute resource, storage backend, scheduling mechanism, and any provider-only inputs).