DevOps on AWS
Source control and delivery tooling.
26 documented options on Amazon Web Services. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.
Read this page as JSON or Markdown.
| Listing | Documented clouds | Deployment and infrastructure | Licensing | Installation | Operations and limitations |
|---|---|---|---|---|---|
| Argo CD | AWS | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for upstream Argo CD. Commercial management platforms and support offerings are separate. | Install the official release Kubernetes manifests into a cluster; upstream releases provide standard and high-availability installation manifests. | Customer manages Kubernetes capacity, repository and cluster credentials, RBAC, identity integration, network exposure, application policies, backups and supported-version upgrades.Scope and evidenceArgo CD runs in Kubernetes and needs credentials for the clusters and repositories it manages. Git hosting, identity providers, image registries and target applications may reside outside the account. The listing covers upstream Argo CD rather than commercial management services or the separate Argo Workflows product. Argo CD patches v3.6.2, v3.5.8, and v3.4.14 update the bundled regexp2 library for CVE-2026-77299. Apply the patch for the deployed minor line and check the application version bundled in any Helm chart or provider package.
Cloud evidence reviewed 2026-11-12 |
| Bitbucket Data Center | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Bitbucket Data Center term license; eligible existing customers must transition to the Bitbucket Hybrid License to continue self-managed use beyond March 28, 2029. | Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based single-node and clustered installation | Customer manages Kubernetes or hosts, Git and shared storage, Mesh where used, database, search, networking, TLS, identity, backups, monitoring and upgrades.Scope and evidenceThis entry covers self-managed Bitbucket Data Center. Atlassian documents EKS, AKS and GKE with its supported Helm chart; the older AWS Quick Start and Azure Resource Manager templates are no longer maintained. Bitbucket and Bamboo are exempt from the retirement of the other affected Data Center products. Continued self-managed use after March 28, 2029 requires the Bitbucket Hybrid License; without transitioning, existing subscription instances become read-only. Atlassian plans availability in early 2027 for eligible existing Bitbucket or Bamboo Data Center/Server customers. The license also includes cloud services, but Atlassian states that the self-managed environment can remain in place without a data transfer. Atlassian rates CVE-2026-21589 critical (9.3). All Bitbucket Data Center versions before the fixed 9.4.26, 10.2.8, or 10.5.1 releases are affected by unauthenticated access to specifically named files under the web application root. Upgrade immediately to a fixed or later version; if patching is delayed, restrict internet access and apply Atlassian's documented WAF or Bitbucket URL-rewrite mitigation to every application and mirror node. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.
Cloud evidence reviewed 2026-11-16 |
| CircleCI Server | AWS, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial CircleCI Server license required. | Official Terraform-assisted infrastructure setup and Helm installation on Amazon EKS or Google GKE | Customer manages Kubernetes, networking, object storage, databases, secrets, TLS, execution capacity, backups, upgrades and the CircleCI Server license.Scope and evidenceThis entry covers CircleCI Server, not CircleCI Cloud or cloud-connected self-hosted runners. EKS and GKE are the tested cloud environments; CircleCI labels Azure and DigitalOcean as untested. GKE Autopilot is unsupported. CircleCI Server currently supports GitHub Enterprise Cloud and GitHub Enterprise Server as version-control providers.
Cloud evidence reviewed 2026-11-16 |
| CloudBees CI on Modern Cloud Platforms | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial CloudBees CI license required. | CloudBees Helm chart on EKS, AKS or GKE | Customer provisions and operates Kubernetes, storage, networking, ingress, DNS, certificates and upgrades; CloudBees supports the licensed application within documented boundaries.Scope and evidenceThis entry covers CloudBees CI on modern cloud platforms, not plain Jenkins or a CloudBees-hosted service. CloudBees publishes separate EKS, AKS and GKE paths and a strict platform/version support matrix. Each standalone controller requires a valid license. CloudBees CI 2.580.2.38435 is the October 29 security release. Java 17 has been unsupported since 2.555.1.36485, so migrate controllers and agents to Java 21; Blue Ocean and Team controllers reached end of life in July 2026.
Cloud evidence reviewed 2026-11-17 |
| GitHub Enterprise Server | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial GitHub Enterprise license required. | Official virtual-machine image on AWS, Azure or Google Cloud | Customer provisions infrastructure and manages networking, storage, backups, upgrades, monitoring and high availability.Scope and evidenceThis entry covers GitHub Enterprise Server, not GitHub Enterprise Cloud. A valid license file is required. Review supported instance types, storage, backup utilities, upgrade paths and version support before deployment. GitHub Enterprise Server 3.22.4 fixes critical Active Storage file-read and remote-code-execution CVE-2026-66066, several high-severity Git vulnerabilities, and Brotli CVE-2026-111497. Upgrade to 3.22.4 or a later supported patch. GitHub Enterprise Server 3.22.5 adds support-bundle and backup metrics, defaults new AWS roots to gp3, updates system packages for security, and fixes operational issues. Follow the documented upgrade path and reapply custom firewall rules when required.
Cloud evidence reviewed 2026-11-14 |
| GitLab Self-Managed | AWS, Azure, Google Cloud, Oracle Cloud, Alibaba Cloud | Customer-operated Servers / containers | Open Source / Open Core Free and paid tiers | Linux package, container or Helm chart | Your team operates, upgrades and backs up the installation.Scope and evidenceGitLab documents AWS, Azure and Google Cloud installations. Oracle and Alibaba Cloud also publish deployment guides. These are documented deployment paths, not a promise of identical support or feature availability. Check operating system, edition and region requirements. GitLab 19.5.4, 19.4.6, and 19.3.8 patch critical CVE-2026-105437 in the bundled Git. Affected self-managed versions are 16.2 through versions before 19.3.8, 19.4 before 19.4.6, and 19.5 before 19.5.4. Upgrade immediately. Self-compiled deployments must also rebuild the Git binaries embedded in Gitaly and the Git installation referenced by git.bin_path, or use a distribution-patched Git 2.56.1 or later. GitLab 19.5.6, 19.4.8, and 19.3.9 address a high-severity cross-site scripting issue plus CI/CD and workspace authorization flaws. On November 20, GitLab issued CE/EE patches 19.6.1, 19.5.8, and 19.4.10 for CVE-2026-132825 and related Ruby flaws. GitLab recommends upgrading affected self-managed installations immediately. Official Linux packages and container images include patched Ruby. Source builds must rebuild the Ruby used by GitLab with 3.3.14 or 3.4.13, or a later patch in the same minor series.
Cloud evidence reviewed 2026-11-12 |
| HashiCorp Consul Enterprise | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Consul Enterprise license required for the selected validated design. | HashiCorp Validated Design Terraform modules for AWS, Azure or Google Cloud | Customer manages cluster nodes, TLS, ACLs, gossip keys, secret handling, snapshots, upgrades, service integrations and availability.Scope and evidenceThis entry covers Consul Enterprise, not HCP Consul and not the separately licensed Community Edition. The validated designs require a commercial license and production security material, including TLS certificates, ACL configuration and gossip encryption. Protect bootstrap tokens and snapshot storage and validate the selected module release before deployment. HCSEC-2026-49 and 50 cover a health-check registration authorization bypass and a consul-k8s cross-namespace ACL binding-rule bypass. Fixed builds are Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18.
Cloud evidence reviewed 2026-11-17 |
| HashiCorp Nomad Enterprise | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Nomad Enterprise license required for the selected edition; Community Edition uses separate source-available terms. | HashiCorp Validated Design Terraform modules where available or manual package and binary installation | Customer manages servers and clients, TLS, gossip encryption, ACLs, snapshots, networking, workload drivers, upgrades and availability.Scope and evidenceThis entry scopes Nomad Enterprise rather than the separately licensed Community Edition. HashiCorp's validated cloud design requires a production multi-node topology, enterprise license, TLS and gossip encryption, protected snapshots and provider-specific infrastructure. Confirm the current validated module release and supported operating systems before deployment. HCSEC-2026-51, 52, and 53 cover cross-namespace information disclosure plus symlink-based allocation-directory escape and host permission modification. Fixed Enterprise builds are 2.1.0, 1.11.12, and 1.10.18.
Cloud evidence reviewed 2026-11-17 |
| Jenkins | AWS, Azure | Customer-operated Servers / containers | Open Source / Open Core MIT License for Jenkins core; plugins and bundled dependencies have their own listed licenses. | Run the official Jenkins Docker image or supported server package and attach appropriately isolated build agents. | Customer manages controller and agents, plugins, secrets, job permissions, storage, backups and security updates.Scope and evidencePipeline code, agents and plugins can access external source hosts, registries and deployment targets. A controller installed in an account does not contain every pipeline integration. Jenkins weekly 2.591 enables Content Security Policy enforcement on the Jenkins UI by default. Test installed plugins and custom UI integrations before adopting this weekly release; compatibility is tracked upstream. Administrators can use report-only mode while resolving incompatibilities, but disabling enforcement removes the protection.
Cloud evidence reviewed 2026-11-12 |
| JFrog Artifactory Self-Hosted | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Open Source / Open Core Open-source Artifactory OSS; commercial Pro X, Enterprise X and Enterprise+ editions. | Helm chart, Docker or Docker Compose, or native OS package or archive | Customer operates the cluster or servers, database, filestore, backups, upgrades and availability configuration.Scope and evidenceThis entry covers self-hosted Artifactory, not JFrog SaaS. Edition capabilities differ substantially: Artifactory OSS is limited and does not include cloud object storage, while high availability and broader repository, security and platform capabilities require the applicable commercial entitlement. Production deployments should use an external PostgreSQL database and durable filestore. The separate Amazon ECS path is single-node, limited to 16 vCPUs and cannot connect to Xray or Distribution. CVE-2026-82329 is a critical unauthenticated authentication bypass under default configuration. JFrog lists fixed builds across maintained branches, including 7.161.20, 7.146.38, 7.133.29, 7.125.20, 7.117.28, and 7.111.21; move to a fixed or later supported build.
Cloud evidence reviewed 2026-11-17 |
| Jira Service Management Data Center | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Atlassian Data Center term license for eligible existing customers; new-customer sales ended March 30, 2026. Affected subscriptions expire March 28, 2029. | Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based Jira Data Center installation | Customer manages Kubernetes or hosts, the database, shared and local storage, load balancing, networking, TLS, identity, email, Marketplace apps, backups, monitoring and upgrades.Scope and evidenceThis entry covers Jira Service Management Data Center, not Atlassian Cloud. Atlassian supports its Kubernetes Helm chart and documents EKS, AKS and GKE as managed cluster options. The older AWS Quick Start and Azure Resource Manager templates are no longer supported or maintained. Atlassian states that affected Data Center subscriptions and associated Marketplace apps expire on March 28, 2029, after which the applications become read-only; evaluate the migration timeline before a new deployment. New customers cannot purchase this Data Center subscription after March 30, 2026. The remaining purchase/expansion window through March 30, 2028 is for existing Data Center customers; do not treat this listing as an unrestricted new-customer offering. Atlassian rates CVE-2026-21589 critical (9.3). All Jira Service Management Data Center versions before the fixed 5.12.40, 10.3.26, or 11.3.12 releases are affected by unauthenticated access to specifically named files under the web application root. Upgrade immediately to a fixed or later version; if patching is delayed, restrict internet access and apply Atlassian's documented WAF or Tomcat rewrite mitigation. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.
Cloud evidence reviewed 2026-11-16 |
| Jira Software Data Center | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Atlassian Data Center term license for eligible existing customers; new-customer sales ended March 30, 2026. Affected subscriptions expire March 28, 2029. | Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based single-node and clustered installation | Customer manages Kubernetes or hosts, the database, shared and local storage, load balancing, networking, TLS, identity, Marketplace apps, backups, monitoring and upgrades.Scope and evidenceThis entry covers Jira Software Data Center, not Jira Cloud. Atlassian supports its Kubernetes Helm chart and documents EKS, AKS and GKE as managed cluster options. The older AWS Quick Start and Azure Resource Manager templates are no longer supported or maintained, so they are not listed as current install methods. Atlassian states that affected Data Center subscriptions and associated Marketplace apps expire on March 28, 2029, after which the applications become read-only; evaluate the migration timeline before a new deployment. New customers cannot purchase this Data Center subscription after March 30, 2026. The remaining purchase/expansion window through March 30, 2028 is for existing Data Center customers; do not treat this listing as an unrestricted new-customer offering. Atlassian rates CVE-2026-21589 critical (9.3). All Jira Software Data Center versions before the fixed 9.12.40, 10.3.26, or 11.3.12 releases are affected by unauthenticated access to specifically named files under the web application root. Upgrade immediately to a fixed or later version; if patching is delayed, restrict internet access and apply Atlassian's documented WAF or Tomcat rewrite mitigation. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.
Cloud evidence reviewed 2026-11-16 |
| Octopus Server | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Proprietary Free tier or annual Professional and Enterprise licenses. | Windows MSI, Docker or Docker Compose, or the official Helm chart on Kubernetes | Customer operates the server or cluster, SQL database, persistent storage, backups, security, upgrades and availability configuration.Scope and evidenceThis entry covers self-hosted Octopus Server, not Octopus Cloud. Octopus Server requires SQL Server 2016 or later or Azure SQL and a license key, including for the Free tier. The Linux container is stateful and needs persistent storage and monitoring. Self-hosted releases trail the cloud product by at least one quarter; each self-hosted major.minor release receives critical patches and support for six months. Octopus advisories SA2026-19, SA2026-22, and SA2026-28 cover authentication-cookie forgery, OIDC subject spoofing, and delegated-role privilege escalation. The last issue has no mitigation; Octopus recommends current 2026.3.16117, with branch-specific fixed builds also documented.
Cloud evidence reviewed 2026-11-17 |
| PagerDuty Runbook Automation Self-Hosted | AWS | Customer-operated Servers / containers | Commercial Only Commercial PagerDuty Runbook Automation Self-Hosted license required; Rundeck Community is a separate Apache-2.0 edition. | Commercial RPM/DEB/WAR or official Docker image on customer AWS infrastructure; obtain a current licensed Helm artifact before using the older EKS recipe | Customer manages EKS or VMs, database, storage, networking, TLS, execution nodes, backups, upgrades and license delivery.Scope and evidenceCommercial Runbook Automation Self-Hosted is distinct from PagerDuty SaaS and Rundeck Community. The EKS tutorial’s linked commercial Helm directory returned 404; use current licensed package/container documentation and obtain a pinned chart if needed. Official Docker images before 6.3.0 require the scoped CA trust-store remediation.
Cloud evidence reviewed 2026-11-18 |
| Perforce P4 Server (Helix Core) | AWS, Azure, Google Cloud, DigitalOcean | Customer-operated Servers / containers | Commercial Only Proprietary P4 license; free within the published small-team limits, with commercial licensing and support above them. | Perforce quickstart images for AWS, Azure, Google Cloud or DigitalOcean; AWS also uses CloudFormation | Customer manages VM and OS security, depot and metadata storage, accounts, firewall, backups, logs, upgrades, capacity and any replication or edge topology.Scope and evidenceHelix Core is being renamed P4 in current documentation. The quickstarts establish single-server deployment, not an HA or disaster-recovery design. Confirm current user/workspace entitlements before production use.
Cloud evidence reviewed 2026-11-18 |
| Pulumi Cloud Self-Hosted | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Pulumi Enterprise subscription with the Self-Hosted deployment option | Official Pulumi programs for ECS or EKS, AKS or GKE | Customer operates backups, uptime, infrastructure and upgrades; Pulumi supplies the licensed application and deployment tooling.Scope and evidenceSelf-hosting is an Enterprise-only option. The installers bootstrap with a separate state backend because the self-hosted Pulumi service does not yet exist during its own deployment. Validate the supported database, storage and identity configuration for the selected release. The public October changelog removes trust in eight compromised eMudhra intermediate certificates and identifies a Go 1.27.3 API-service rebuild. Obtain and deploy the entitled API image containing the documented trust-store update, restart the service and verify its image/trust configuration. Review the separate OpenSearch 2.x-to-3.7.0 installer migration before redeployment.
Cloud evidence reviewed 2026-11-19 |
| Rancher Manager | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0; commercial SUSE subscriptions and support are separate. | Official Helm chart on a supported Kubernetes cluster | Customer manages the management cluster, ingress, certificates, backups, upgrades, downstream-cluster credentials and availability.Scope and evidenceThis entry covers self-managed Rancher Manager, not separate hosted offerings. Rancher documents EKS, AKS and GKE installation paths. GKE Autopilot is not supported for the Rancher server because required kube-system changes are restricted.
Cloud evidence reviewed 2026-11-14 |
| Red Hat Ansible Automation Platform Self-Managed | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Red Hat Ansible Automation Platform subscription required. | Containerized installer on RHEL with Podman or the OpenShift Operator | Customer manages the platform, execution capacity, infrastructure, secrets, backups and upgrades; Red Hat supplies subscribed software updates and support.Scope and evidenceThis entry covers Red Hat Ansible Automation Platform, not the managed cloud service and not upstream Ansible Core or AWX. Current 2.7 deployment models use the containerized RHEL installer or OpenShift Operator; the RPM installer was removed in 2.7. Validate supported RHEL or OpenShift versions, execution environments and subscription manifests before installation.
Cloud evidence reviewed 2026-11-17 |
| Red Hat OpenShift Container Platform | AWS, Azure, Google Cloud, IBM Cloud, Alibaba Cloud | Customer-operated Servers / containers | Commercial Only Commercial Red Hat OpenShift subscription. | OpenShift installation on AWS, Azure, Google Cloud or IBM Cloud; Assisted Installer Technology Preview on Alibaba Cloud | Customer manages cloud accounts, installer credentials, cluster machines, networking, identity, storage, registry, monitoring, backups, upgrades and Red Hat subscriptions.Scope and evidenceThis entry covers self-managed OpenShift Container Platform, not OpenShift Dedicated, ROSA, Azure Red Hat OpenShift or other managed services. The installer can provision infrastructure or integrate with customer-provisioned resources; review credential scope, subscription entitlements and lifecycle support before installation. The documented Alibaba Cloud Assisted Installer path is Technology Preview, outside Red Hat production SLAs and not recommended for production.
Cloud evidence reviewed 2026-11-15 |
| SonarQube Server Data Center Edition | Google Cloud, Azure, AWS | Customer-operated Servers / containers | Commercial Only Commercial Data Center Edition license. | Google Cloud Marketplace on GKE or DCE Helm chart; documented AKS deployment and AWS architecture adaptation | Customer manages the Kubernetes cluster, namespaces, database, persistent volumes, secrets, TLS, identity, load balancing, backups, autoscaling, upgrades and the SonarQube license.Scope and evidenceThis entry covers self-managed Data Center Edition. Google Cloud has a Marketplace path; Azure has a concrete AKS deployment example, while the AWS architecture requires adaptation. For 2026.1, use an external production database, compatible Helm values and an appropriate storage class on AKS; the documentation warns about Azure Fileshare permissions. Confirm chart and package versions independently. CVE-2026-114938 is reported to allow unauthenticated RCE in affected OpenJDK 17.0.6+ runtimes, including Java 21 and 25, on x86-64 CPUs with AVX-512 VBMI. Until Sonar publishes patched builds, set -XX:-UseBASE64Intrinsics for Web, Compute Engine, and Search; ARM is unaffected, and Sonar reported no evidence of exploitation.
Cloud evidence reviewed 2026-11-15 |
| Sonatype Nexus Repository Pro Self-Hosted | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Nexus Repository Pro license required for high availability and other Pro capabilities. | Official Helm chart for resilient or high-availability Kubernetes deployments, or supported standalone and Docker installation paths | Customer manages compute or Kubernetes, PostgreSQL, blob and node storage, ingress and load balancing, TLS, secrets, backups, monitoring, upgrades and license persistence.Scope and evidenceThis entry covers Nexus Repository Pro self-hosted deployments, not Nexus Repository Cloud or the unlicensed Community Edition. High availability requires Pro, an external PostgreSQL database and customer expertise in Kubernetes, Helm and cloud infrastructure. Sonatype states that its support expertise is strongest on AWS even though Azure and Google Cloud infrastructure are supported. Container deployments must persist both nexus-data and Java preferences so license state survives restarts. Nexus Repository 3.98.0 fixes seven November advisories covering Rut Auth privilege escalation, disabled or locked SSO users regaining access, exposed signing material, SQL injection in the optional reindex task, stored XSS, and group-member authorization bypass. After upgrading, remove unused Rut Auth capabilities and realms, confirm intended capabilities were administrator-created, and remove existing group members that group editors are not allowed to read; the upgrade does not clean these up. Review affected sign-ins and tasks, and rotate potentially exposed signing keys or passphrases. Nexus Repository 3.98.2, released November 18, 2026, includes Java4Shell mitigation for CVE-2026-114938 on the 3.98 line. Sonatype also identifies fixes for other maintained branches, including 3.97.4, 3.95.6, 3.94.4, 3.93.4 and 3.92.5; the November 19 notes separately document 3.90.7 and 3.88.2 backports. Use the fixed release for the installed supported branch, restart affected processes and verify the active Java runtime or mitigation; do not downgrade to an older branch to match a backport.
Cloud evidence reviewed 2026-11-16 |
| Spacelift Self-Hosted | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Spacelift Self-Hosted Enterprise subscription and license token required. | Official Terraform/OpenTofu reference architectures and Helm charts for EKS/ECS, AKS or GKE | Customer manages compute or Kubernetes, database and object storage, networking, secrets, workers, backups, scaling, upgrades and licensing.Scope and evidenceThis entry covers Spacelift Self-Hosted, not the Spacelift SaaS service. New features can reach SaaS before self-hosted releases; match the deployment artifacts and architecture to the licensed version.
Cloud evidence reviewed 2026-11-18 |
| SuperPlane Enterprise Self-Hosted | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial SuperPlane Enterprise license required for the documented Kubernetes deployment. | Vendor Terraform modules provision EKS, AKS or GKE, managed data services and the SuperPlane Helm release | Customer manages the cloud account, cluster, database, object storage, runner images and VMs, DNS, TLS, backups, upgrades and connected model or tool credentials.Scope and evidenceThis entry scopes only the Enterprise Kubernetes deployment on AWS, Azure and Google Cloud. The Apache-2.0 community engine and single-VM Compose installation are separate. Google Cloud public runner images are not yet published and must be built with Packer. Connected source-control, model and workflow services can move code or data outside the cluster according to their own configuration and terms.
Cloud evidence reviewed 2026-11-17 |
| SUSE Multi-Linux Manager 5.2 | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Open Source / Open Core Open-source product based on Uyuni with component open-source licenses; SUSE subscriptions, support, images and trademarks use separate commercial terms. | SUSE Multi-Linux Manager 5.2 container with mgradm on SL Micro 6.2 or SLES 15 SP7, or a SUSE-provided cloud VM image | Customer manages the cloud VM, private networking, DNS, storage, server and proxy containers, repository synchronization, backups, upgrades and registered systems.Scope and evidenceSUSE documents public-cloud installation tested on Amazon EC2, Google Compute Engine and Microsoft Azure. Keep the server on a restricted private network with working forward-confirmed reverse DNS and external persistent disks for repositories and database data. AWS supports PAYG and BYOS; Azure supports BYOS, while the public guide's GCP path is a tested customer-operated installation rather than a confirmed marketplace billing offer. Public-cloud proxies are BYOS-only.
Cloud evidence reviewed 2026-11-17 |
| SUSE Security (NeuVector) | AWS, Azure, Google Cloud, IBM Cloud, Alibaba Cloud, Oracle Cloud | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for NeuVector; Rancher Prime delivery and commercial support have separate subscription terms. | SUSE Security Helm chart or manifests on public-cloud Kubernetes | Customer manages Kubernetes, registry access, Helm values, storage, certificates, policies, upgrades, monitoring and cluster privileges.Scope and evidenceThis entry covers upstream NeuVector/SUSE Security deployment; subscription images/support can require commercial entitlements. SUSE names six public-cloud Kubernetes targets. Resolve the conflicting manager-redundancy guidance before HA design, and apply GKE Autopilot allowlists where required. Scan-policy/compliance functions do not certify the customer installation.
Cloud evidence reviewed 2026-11-18 |
| Terraform Enterprise | AWS, Azure, Google Cloud, IBM Cloud | Customer-operated Servers / containers | Commercial Only Commercial Terraform Enterprise license required. | Official HashiCorp Terraform modules for EC2, EKS, Azure VMs, AKS, GCE or GKE; Kubernetes or OpenShift workflow on IBM Cloud | Customer manages compute or Kubernetes, PostgreSQL and object storage, cache, networking, TLS, identity, worker images, backups, scaling, upgrades and licensing.Scope and evidenceThis entry covers Terraform Enterprise, the self-hosted distribution, not HCP Terraform. Match the selected runtime to the current compatibility matrix and review the module's IAM, managed-identity, database, object-storage and network requirements before applying it.
Cloud evidence reviewed 2026-11-15 |
Deployment evidence and category fit
Argo CD
Declarative continuous delivery for Kubernetes: compares deployed application state with Git-defined desired state and supports synchronization, health visibility and rollback operations.
Argo CD runs in Kubernetes and needs credentials for the clusters and repositories it manages. Git hosting, identity providers, image registries and target applications may reside outside the account. The listing covers upstream Argo CD rather than commercial management services or the separate Argo Workflows product. Argo CD patches v3.6.2, v3.5.8, and v3.4.14 update the bundled regexp2 library for CVE-2026-77299. Apply the patch for the deployed minor line and check the application version bundled in any Helm chart or provider package.
- Self-managed Argo CD through AWS EKS Blueprints ↗
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
AWS EKS Blueprints installs the Argo CD Helm chart and its components in the customer EKS cluster. This is distinct from the managed Amazon EKS capability. Configure administrator credentials, repository secrets, upgrades and application cleanup before cluster deletion.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
Bitbucket Data Center
Provides self-managed Git repository hosting, pull requests, code review, permissions and software-delivery integrations.
This entry covers self-managed Bitbucket Data Center. Atlassian documents EKS, AKS and GKE with its supported Helm chart; the older AWS Quick Start and Azure Resource Manager templates are no longer maintained. Bitbucket and Bamboo are exempt from the retirement of the other affected Data Center products. Continued self-managed use after March 28, 2029 requires the Bitbucket Hybrid License; without transitioning, existing subscription instances become read-only. Atlassian plans availability in early 2027 for eligible existing Bitbucket or Bamboo Data Center/Server customers. The license also includes cloud services, but Atlassian states that the self-managed environment can remain in place without a data transfer. Atlassian rates CVE-2026-21589 critical (9.3). All Bitbucket Data Center versions before the fixed 9.4.26, 10.2.8, or 10.5.1 releases are affected by unauthenticated access to specifically named files under the web application root. Upgrade immediately to a fixed or later version; if patching is delayed, restrict internet access and apply Atlassian's documented WAF or Bitbucket URL-rewrite mitigation to every application and mirror node. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.
- Bitbucket Data Center on EKS, AKS or GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
Atlassian documents Bitbucket Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments. Product-specific AWS and Azure pages also direct customers to the Helm path because the older templates are no longer maintained.
Cloud evidence reviewed 2026-11-16. Full listing and qualifications
CircleCI Server
Provides self-hosted continuous integration and delivery pipelines, execution environments, policy controls and build infrastructure.
This entry covers CircleCI Server, not CircleCI Cloud or cloud-connected self-hosted runners. EKS and GKE are the tested cloud environments; CircleCI labels Azure and DigitalOcean as untested. GKE Autopilot is unsupported. CircleCI Server currently supports GitHub Enterprise Cloud and GitHub Enterprise Server as version-control providers.
- CircleCI Server on Amazon EKS ↗
Vendor / upstream documentation · Reviewed 2026-11-16 · Version: 4.10. Vendor support commitment: not assessed; confirm the selected release and contract.
CircleCI documents preparing AWS networking, an EKS cluster, storage, permissions and other prerequisites before installing CircleCI Server with its Helm chart.
Cloud evidence reviewed 2026-11-16. Full listing and qualifications
CloudBees CI on Modern Cloud Platforms
Centrally managed enterprise continuous integration and delivery environment.
This entry covers CloudBees CI on modern cloud platforms, not plain Jenkins or a CloudBees-hosted service. CloudBees publishes separate EKS, AKS and GKE paths and a strict platform/version support matrix. Each standalone controller requires a valid license. CloudBees CI 2.580.2.38435 is the October 29 security release. Java 17 has been unsupported since 2.555.1.36485, so migrate controllers and agents to Java 21; Blue Ocean and Team controllers reached end of life in July 2026.
- CloudBees CI installation on EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
CloudBees provides product installation guides for Amazon EKS, Azure AKS and Google GKE, and its supported-platform matrix lists all three. The customer operates the Kubernetes cluster.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
GitHub Enterprise Server
Provides customer-operated source control, pull requests, collaboration and software delivery workflows as a licensed virtual appliance.
This entry covers GitHub Enterprise Server, not GitHub Enterprise Cloud. A valid license file is required. Review supported instance types, storage, backup utilities, upgrade paths and version support before deployment. GitHub Enterprise Server 3.22.4 fixes critical Active Storage file-read and remote-code-execution CVE-2026-66066, several high-severity Git vulnerabilities, and Brotli CVE-2026-111497. Upgrade to 3.22.4 or a later supported patch. GitHub Enterprise Server 3.22.5 adds support-bundle and backup metrics, defaults new AWS roots to gp3, updates system packages for security, and fixes operational issues. Follow the documented upgrade path and reapply custom firewall rules when required.
- GitHub Enterprise Server on AWS ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
GitHub documents launching its published appliance image on EC2 and attaching an EBS data volume in the customer's AWS account.
Cloud evidence reviewed 2026-11-14. Full listing and qualifications
GitLab Self-Managed
Source control and CI/CD on infrastructure you operate.
GitLab documents AWS, Azure and Google Cloud installations. Oracle and Alibaba Cloud also publish deployment guides. These are documented deployment paths, not a promise of identical support or feature availability. Check operating system, edition and region requirements. GitLab 19.5.4, 19.4.6, and 19.3.8 patch critical CVE-2026-105437 in the bundled Git. Affected self-managed versions are 16.2 through versions before 19.3.8, 19.4 before 19.4.6, and 19.5 before 19.5.4. Upgrade immediately. Self-compiled deployments must also rebuild the Git binaries embedded in Gitaly and the Git installation referenced by git.bin_path, or use a distribution-patched Git 2.56.1 or later. GitLab 19.5.6, 19.4.8, and 19.3.9 address a high-severity cross-site scripting issue plus CI/CD and workspace authorization flaws. On November 20, GitLab issued CE/EE patches 19.6.1, 19.5.8, and 19.4.10 for CVE-2026-132825 and related Ruby flaws. GitLab recommends upgrading affected self-managed installations immediately. Official Linux packages and container images include patched Ruby. Source builds must rebuild the Ruby used by GitLab with 3.3.14 or 3.4.13, or a later patch in the same minor series.
- GitLab Self-Managed cloud installation guides ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream installation index links full GitLab Self-Managed deployment on AWS, Azure and Google Cloud. Choose the Linux package, chart or reference architecture appropriate to the selected edition, scale and supported release; a GitLab Runner alone is not the GitLab application.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
HashiCorp Consul Enterprise
Automates service networking, health discovery and policy across deployment environments.
This entry covers Consul Enterprise, not HCP Consul and not the separately licensed Community Edition. The validated designs require a commercial license and production security material, including TLS certificates, ACL configuration and gossip encryption. Protect bootstrap tokens and snapshot storage and validate the selected module release before deployment. HCSEC-2026-49 and 50 cover a health-check registration authorization bypass and a consul-k8s cross-namespace ACL binding-rule bypass. Fixed builds are Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18.
- Consul Enterprise Terraform deployments on AWS, Azure and Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
HashiCorp provides validated Terraform deployment paths for Consul Enterprise in customer AWS, Azure and Google Cloud environments. Customers manage the deployed cluster, security material and backups.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
HashiCorp Nomad Enterprise
Schedules and operates application, batch and system workloads across customer infrastructure.
This entry scopes Nomad Enterprise rather than the separately licensed Community Edition. HashiCorp's validated cloud design requires a production multi-node topology, enterprise license, TLS and gossip encryption, protected snapshots and provider-specific infrastructure. Confirm the current validated module release and supported operating systems before deployment. HCSEC-2026-51, 52, and 53 cover cross-namespace information disclosure plus symlink-based allocation-directory escape and host permission modification. Fixed Enterprise builds are 2.1.0, 1.11.12, and 1.10.18.
- Nomad Enterprise validated cloud deployment on AWS, Azure and Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
HashiCorp's Validated Design documents production Nomad deployment on customer AWS, Azure and Google Cloud infrastructure. The operator supplies the Enterprise license and manages the resulting cluster.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
Jenkins
Automation server for continuous integration, build, test and delivery pipelines; agents and plugins provide workload-specific integrations.
Pipeline code, agents and plugins can access external source hosts, registries and deployment targets. A controller installed in an account does not contain every pipeline integration. Jenkins weekly 2.591 enables Content Security Policy enforcement on the Jenkins UI by default. Test installed plugins and custom UI integrations before adopting this weekly release; compatibility is tracked upstream. Administrators can use report-only mode while resolving incompatibilities, but disabling enforcement removes the protection.
- Jenkins installation on AWS ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The Jenkins project documents installing the Jenkins server on a customer EC2 instance, not merely deploying build output to AWS.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
JFrog Artifactory Self-Hosted
Artifact, package and container registry for software delivery pipelines.
This entry covers self-hosted Artifactory, not JFrog SaaS. Edition capabilities differ substantially: Artifactory OSS is limited and does not include cloud object storage, while high availability and broader repository, security and platform capabilities require the applicable commercial entitlement. Production deployments should use an external PostgreSQL database and durable filestore. The separate Amazon ECS path is single-node, limited to 16 vCPUs and cannot connect to Xray or Distribution. CVE-2026-82329 is a critical unauthenticated authentication bypass under default configuration. JFrog lists fixed builds across maintained branches, including 7.161.20, 7.146.38, 7.133.29, 7.125.20, 7.117.28, and 7.111.21; move to a fixed or later supported build.
- Artifactory Helm installation on EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
JFrog's current Artifactory Helm guide explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as cluster types and documents installation into the customer's cluster. Provider storage, database, ingress and support details vary by edition.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
Jira Service Management Data Center
Supports IT service management, incident response, change coordination and development-to-operations workflows.
This entry covers Jira Service Management Data Center, not Atlassian Cloud. Atlassian supports its Kubernetes Helm chart and documents EKS, AKS and GKE as managed cluster options. The older AWS Quick Start and Azure Resource Manager templates are no longer supported or maintained. Atlassian states that affected Data Center subscriptions and associated Marketplace apps expire on March 28, 2029, after which the applications become read-only; evaluate the migration timeline before a new deployment. New customers cannot purchase this Data Center subscription after March 30, 2026. The remaining purchase/expansion window through March 30, 2028 is for existing Data Center customers; do not treat this listing as an unrestricted new-customer offering. Atlassian rates CVE-2026-21589 critical (9.3). All Jira Service Management Data Center versions before the fixed 5.12.40, 10.3.26, or 11.3.12 releases are affected by unauthenticated access to specifically named files under the web application root. Upgrade immediately to a fixed or later version; if patching is delayed, restrict internet access and apply Atlassian's documented WAF or Tomcat rewrite mitigation. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.
- Jira Service Management Data Center on EKS, AKS or GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
Atlassian documents Jira Service Management Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments.
Cloud evidence reviewed 2026-11-16. Full listing and qualifications
Jira Software Data Center
Supports software-delivery planning, issue tracking, release coordination and integrations with development toolchains.
This entry covers Jira Software Data Center, not Jira Cloud. Atlassian supports its Kubernetes Helm chart and documents EKS, AKS and GKE as managed cluster options. The older AWS Quick Start and Azure Resource Manager templates are no longer supported or maintained, so they are not listed as current install methods. Atlassian states that affected Data Center subscriptions and associated Marketplace apps expire on March 28, 2029, after which the applications become read-only; evaluate the migration timeline before a new deployment. New customers cannot purchase this Data Center subscription after March 30, 2026. The remaining purchase/expansion window through March 30, 2028 is for existing Data Center customers; do not treat this listing as an unrestricted new-customer offering. Atlassian rates CVE-2026-21589 critical (9.3). All Jira Software Data Center versions before the fixed 9.12.40, 10.3.26, or 11.3.12 releases are affected by unauthenticated access to specifically named files under the web application root. Upgrade immediately to a fixed or later version; if patching is delayed, restrict internet access and apply Atlassian's documented WAF or Tomcat rewrite mitigation. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.
- Jira Data Center on EKS, AKS or GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
Atlassian documents Jira Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments. Atlassian supports the product and Helm chart, but not the underlying Kubernetes platform.
Cloud evidence reviewed 2026-11-16. Full listing and qualifications
Octopus Server
Continuous delivery, release orchestration and operational runbook automation.
This entry covers self-hosted Octopus Server, not Octopus Cloud. Octopus Server requires SQL Server 2016 or later or Azure SQL and a license key, including for the Free tier. The Linux container is stateful and needs persistent storage and monitoring. Self-hosted releases trail the cloud product by at least one quarter; each self-hosted major.minor release receives critical patches and support for six months. Octopus advisories SA2026-19, SA2026-22, and SA2026-28 cover authentication-cookie forgery, OIDC subject spoofing, and delegated-role privilege escalation. The last issue has no mitigation; Octopus recommends current 2026.3.16117, with branch-specific fixed builds also documented.
- Octopus Server container on AWS ECS or EKS ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
Octopus explicitly lists Amazon ECS and EKS among supported underlying technologies for the Server Linux container. This is the server application in customer-operated AWS infrastructure.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
PagerDuty Runbook Automation Self-Hosted
Provides operations automation, job orchestration, access control and integrations for delivery and incident workflows.
Commercial Runbook Automation Self-Hosted is distinct from PagerDuty SaaS and Rundeck Community. The EKS tutorial’s linked commercial Helm directory returned 404; use current licensed package/container documentation and obtain a pinned chart if needed. Official Docker images before 6.3.0 require the scoped CA trust-store remediation.
- Runbook Automation Self-Hosted on AWS ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
PagerDuty documents a customer-operated HA architecture using AWS load balancing, RDS and S3; a separate guide deploys the product to customer EKS.
Cloud evidence reviewed 2026-11-18. Full listing and qualifications
Perforce P4 Server (Helix Core)
Provides centralized version control and a high-volume repository for source code, binaries and digital assets used by development teams.
Helix Core is being renamed P4 in current documentation. The quickstarts establish single-server deployment, not an HA or disaster-recovery design. Confirm current user/workspace entitlements before production use.
- P4 Server on AWS ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
Perforce documents a customer AWS deployment using EC2 and a CloudFormation quickstart.
Cloud evidence reviewed 2026-11-18. Full listing and qualifications
Pulumi Cloud Self-Hosted
Provides a customer-operated Pulumi control plane for infrastructure delivery, state, policy, access and deployment workflows.
Self-hosting is an Enterprise-only option. The installers bootstrap with a separate state backend because the self-hosted Pulumi service does not yet exist during its own deployment. Validate the supported database, storage and identity configuration for the selected release. The public October changelog removes trust in eight compromised eMudhra intermediate certificates and identifies a Go 1.27.3 API-service rebuild. Obtain and deploy the entitled API image containing the documented trust-store update, restart the service and verify its image/trust configuration. Review the separate OpenSearch 2.x-to-3.7.0 installer migration before redeployment.
- Pulumi Cloud Self-Hosted on AWS ECS or EKS ↗
Vendor / upstream documentation · Reviewed 2026-11-19 · Scope: Pulumi Enterprise Self-Hosted. Vendor support commitment: not assessed; confirm the selected release and contract.
Pulumi lists production self-hosting options for AWS ECS and EKS and links official deployment programs that create the application in the customer's AWS environment.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
Rancher Manager
Provides centralized provisioning, access control and lifecycle management for Kubernetes clusters.
This entry covers self-managed Rancher Manager, not separate hosted offerings. Rancher documents EKS, AKS and GKE installation paths. GKE Autopilot is not supported for the Rancher server because required kube-system changes are restricted.
- Rancher Manager on Amazon EKS ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream guide installs the Rancher server with Helm into an EKS cluster controlled by the customer.
Cloud evidence reviewed 2026-11-14. Full listing and qualifications
Red Hat Ansible Automation Platform Self-Managed
Enterprise configuration, provisioning and operations automation across infrastructure and applications.
This entry covers Red Hat Ansible Automation Platform, not the managed cloud service and not upstream Ansible Core or AWX. Current 2.7 deployment models use the containerized RHEL installer or OpenShift Operator; the RPM installer was removed in 2.7. Validate supported RHEL or OpenShift versions, execution environments and subscription manifests before installation.
- Self-managed Ansible Automation Platform in named public clouds ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
Red Hat documents self-managed Ansible Automation Platform deployments on infrastructure hosted in AWS, Azure and Google Cloud. The customer operates the RHEL or OpenShift environment and supplies the subscription.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
Red Hat OpenShift Container Platform
Provides platform engineering, build, deployment and operations workflows for applications across customer-managed clusters.
This entry covers self-managed OpenShift Container Platform, not OpenShift Dedicated, ROSA, Azure Red Hat OpenShift or other managed services. The installer can provision infrastructure or integrate with customer-provisioned resources; review credential scope, subscription entitlements and lifecycle support before installation. The documented Alibaba Cloud Assisted Installer path is Technology Preview, outside Red Hat production SLAs and not recommended for production.
- Self-managed OpenShift Container Platform on AWS, Azure or Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
Red Hat's current installation overview explicitly distinguishes self-managed OpenShift Container Platform and documents installer- and user-provisioned installation paths on AWS, Microsoft Azure and Google Cloud using customer accounts and credentials.
Cloud evidence reviewed 2026-11-15. Full listing and qualifications
SonarQube Server Data Center Edition
Provides high-availability self-managed code-quality and security analysis integrated with source-control and CI workflows.
This entry covers self-managed Data Center Edition. Google Cloud has a Marketplace path; Azure has a concrete AKS deployment example, while the AWS architecture requires adaptation. For 2026.1, use an external production database, compatible Helm values and an appropriate storage class on AKS; the documentation warns about Azure Fileshare permissions. Confirm chart and package versions independently. CVE-2026-114938 is reported to allow unauthenticated RCE in affected OpenJDK 17.0.6+ runtimes, including Java 21 and 25, on x86-64 CPUs with AVX-512 VBMI. Until Sonar publishes patched builds, set -XX:-UseBASE64Intrinsics for Web, Compute Engine, and Search; ARM is unaffected, and Sonar reported no evidence of exploitation.
- SonarQube DCE cloud architecture and AWS chart guidance ↗
Vendor / upstream documentation · Reviewed 2026-11-15 · Scope: Data Center Edition · Version: 2026.1 architecture; select a compatible Helm chart. Vendor support commitment: not assessed; confirm the selected release and contract.
Sonar explicitly says its DCE Kubernetes disaster-recovery architecture can be adapted to AWS with modifications. The upstream DCE Helm chart separately documents AWS ingress migration settings. This is an architecture adaptation path, not an AWS one-click package or a support commitment.
Cloud evidence reviewed 2026-11-15. Full listing and qualifications
Sonatype Nexus Repository Pro Self-Hosted
Provides a self-managed repository for packages, containers and other build artifacts used by software-delivery pipelines.
This entry covers Nexus Repository Pro self-hosted deployments, not Nexus Repository Cloud or the unlicensed Community Edition. High availability requires Pro, an external PostgreSQL database and customer expertise in Kubernetes, Helm and cloud infrastructure. Sonatype states that its support expertise is strongest on AWS even though Azure and Google Cloud infrastructure are supported. Container deployments must persist both nexus-data and Java preferences so license state survives restarts. Nexus Repository 3.98.0 fixes seven November advisories covering Rut Auth privilege escalation, disabled or locked SSO users regaining access, exposed signing material, SQL injection in the optional reindex task, stored XSS, and group-member authorization bypass. After upgrading, remove unused Rut Auth capabilities and realms, confirm intended capabilities were administrator-created, and remove existing group members that group editors are not allowed to read; the upgrade does not clean these up. Review affected sign-ins and tasks, and rotate potentially exposed signing keys or passphrases. Nexus Repository 3.98.2, released November 18, 2026, includes Java4Shell mitigation for CVE-2026-114938 on the 3.98 line. Sonatype also identifies fixes for other maintained branches, including 3.97.4, 3.95.6, 3.94.4, 3.93.4 and 3.92.5; the November 19 notes separately document 3.90.7 and 3.88.2 backports. Use the fixed release for the installed supported branch, restart affected processes and verify the active Java runtime or mitigation; do not downgrade to an older branch to match a backport.
- Supported Nexus Repository Pro high-availability infrastructure ↗
Vendor / upstream documentation · Reviewed 2026-11-16 · Scope: Nexus Repository Pro. Vendor support commitment: not assessed; confirm the selected release and contract.
Sonatype explicitly lists AWS, Azure and Google Cloud as supported providers for Nexus Repository Pro HA and names EKS, AKS and GKE together with provider-specific databases, storage and blob services.
Cloud evidence reviewed 2026-11-16. Full listing and qualifications
Spacelift Self-Hosted
Provides self-hosted infrastructure-as-code runs, policy, state, integrations and private workers.
This entry covers Spacelift Self-Hosted, not the Spacelift SaaS service. New features can reach SaaS before self-hosted releases; match the deployment artifacts and architecture to the licensed version.
- Spacelift in customer AWS, Azure or GCP infrastructure ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
Spacelift explicitly documents a customer-maintained self-hosted product for AWS, Azure and GCP and links provider-specific reference architectures.
Cloud evidence reviewed 2026-11-18. Full listing and qualifications
SuperPlane Enterprise Self-Hosted
Coordinates coding agents, source control, CI, review and verified software-delivery work.
This entry scopes only the Enterprise Kubernetes deployment on AWS, Azure and Google Cloud. The Apache-2.0 community engine and single-VM Compose installation are separate. Google Cloud public runner images are not yet published and must be built with Packer. Connected source-control, model and workflow services can move code or data outside the cluster according to their own configuration and terms.
- SuperPlane Enterprise on EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
SuperPlane documents Terraform-created EKS, AKS and GKE clusters with managed PostgreSQL, object storage and Helm releases in the customer's account. Enterprise licensing is required; Google Cloud runner images must currently be built by the operator with Packer.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
SUSE Multi-Linux Manager 5.2
Automates Linux provisioning, patching, configuration, monitoring, inventory and compliance operations across managed systems.
SUSE documents public-cloud installation tested on Amazon EC2, Google Compute Engine and Microsoft Azure. Keep the server on a restricted private network with working forward-confirmed reverse DNS and external persistent disks for repositories and database data. AWS supports PAYG and BYOS; Azure supports BYOS, while the public guide's GCP path is a tested customer-operated installation rather than a confirmed marketplace billing offer. Public-cloud proxies are BYOS-only.
- SUSE Multi-Linux Manager public-cloud installation on EC2, Azure and GCE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
SUSE states that its public-cloud requirements and procedures were tested on Amazon EC2, Microsoft Azure and Google Compute Engine. The customer operates the instance, DNS, private networking and durable storage; billing and image availability differ by provider.
- SUSE Multi-Linux Manager BYOS and PAYG public-cloud models ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
The public-cloud guide documents BYOS on AWS and Azure and PAYG on AWS. This evidence qualifies procurement models; it does not extend PAYG availability to Azure or Google Cloud.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
SUSE Security (NeuVector)
Adds runtime security, vulnerability scanning and policy enforcement to customer Kubernetes delivery environments.
This entry covers upstream NeuVector/SUSE Security deployment; subscription images/support can require commercial entitlements. SUSE names six public-cloud Kubernetes targets. Resolve the conflicting manager-redundancy guidance before HA design, and apply GKE Autopilot allowlists where required. Scan-policy/compliance functions do not certify the customer installation.
- SUSE Security on six named public-cloud Kubernetes services ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
SUSE explicitly names AWS EKS, Azure AKS, Google Cloud, IBM Cloud Kubernetes, Alibaba Cloud and Oracle Cloud and links full Kubernetes/Helm application deployment. Confirm tested platform versions and privileges. GKE Autopilot requires allowlists; AWS ECS is no longer supported in the requirements guide.
Cloud evidence reviewed 2026-11-18. Full listing and qualifications
Terraform Enterprise
Provides self-hosted infrastructure-as-code runs, workspaces, policy controls, private registry and team workflows.
This entry covers Terraform Enterprise, the self-hosted distribution, not HCP Terraform. Match the selected runtime to the current compatibility matrix and review the module's IAM, managed-identity, database, object-storage and network requirements before applying it.
- Official Terraform Enterprise modules and provider guidance ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
HashiCorp lists official Terraform Enterprise modules for AWS EC2 and EKS, Azure VMs and AKS, and Google GCE and GKE, together with provider-specific deployment guidance for customer environments.
Cloud evidence reviewed 2026-11-15. Full listing and qualifications
Deployment and procurement checks
- Private offers
- AWS Marketplace private offers can contain negotiated pricing and terms for a buyer account. Confirm the product delivery model and your agreement; commitment credit is not established by a directory badge. Provider source ↗ · Reviewed 2026-11-14
- Private connectivity
- PrivateLink provides private endpoints to supported services and resources across VPC/account boundaries. Confirm that the selected product exposes a compatible endpoint service. Provider source ↗ · Reviewed 2026-11-14
- Cross-account operations
- Use an IAM role with scoped permissions and a third-party external ID where applicable. Review the trust principal, support access and revocation separately from installation access. Provider source ↗ · Reviewed 2026-11-14
- Government environments
- AWS GovCloud (US) is a distinct isolated-region environment. A commercial-region product deployment does not establish availability or certification there. Provider source ↗ · Reviewed 2026-11-14
For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.
Plan this deployment
Account boundary: AWS account. Access: IAM roles and policies. Network: VPC.
Provider documentation ↗ · Guidance reviewed 2026-11-10. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.
Compare this category across clouds · Search these listings · Compare 2–4 listings