Chef 360 SaaS system requirements

Confirm that your organization, users, and nodes meet these requirements before you sign up for Chef 360 SaaS and start enrolling nodes. After reviewing this page, you’ll know whether your browser access, network connectivity, and licensing meet the prerequisites for a SaaS tenant.

Chef 360 SaaS is hosted and operated by Progress. Unlike an on-prem deployment, you don’t provision servers, storage, or a Kubernetes cluster. Progress manages that infrastructure for you. Your requirements are limited to the access and connectivity needed to reach your tenant and to enroll the nodes you want Chef 360 Platform to manage.

Before you begin

• Confirm that your organization has a Chef 360 Platform subscription or evaluation entitlement.
• Identify the users who need access to the Chef 360 Platform user interface.
• Identify the nodes you plan to enroll and manage through your SaaS tenant.

Requirements

Licensing and entitlement

A valid Chef 360 Platform subscription or evaluation entitlement is required to sign up for and use Chef 360 SaaS. Unlike an on-prem deployment, no separate server license file is required because Progress operates the platform on your behalf.

Browser access

Users need a supported web browser to sign in to the Chef 360 Platform user interface at your tenant URL.

Node network connectivity

Each node you enroll must be able to reach your Chef 360 SaaS tenant over the network. The same node-side connectivity requirements that apply to an on-prem deployment also apply to SaaS.

Ports

Open the following default ports for outbound connections.

Connection requirements

• Nodes must be accessible through SSH or WinRM:
  • Linux nodes must be enrolled using SSH.
  • Windows nodes must be enrolled using WinRM.
• Nodes must have a public DNS name or public IP address.
• A node’s IP address can’t be 127.0.0.1 (localhost).
• A node’s CIDR address must not overlap with the Chef 360 Platform services’ CIDR range. The default CIDR ranges for Chef 360 Platform services are 10.244.0.0/16 and 10.96.0.0/12.
• The node’s ports for RabbitMQ and the nginx API gateway must be open to Chef 360 Platform. Chef 360 Platform must also allow inbound connections to these ports from the node.
• For nodes running Windows Server 2016, download and manually install curl. After installation, ensure the curl executable is added to the system’s PATH environment variable.

SSH connection requirements

• Port 22 must be open.
• The user must have sudo privileges.
• The user must authenticate using an ed25519 or RSA (2048-bit) key without a passphrase.
• If you’re enrolling a node with a username and password, disable sudo password prompts for the SSH user account on that node.

WinRM connection requirements

• Ports 5985 (HTTP) and 5986 (HTTPS) must be open.

• Configure WinRM by running the following commands:

  winrm quickconfig   # Select 'Yes' when prompted
  winrm set winrm/config/service/Auth '@{Basic="true"}'
  winrm set winrm/config/service '@{AllowUnencrypted="true"}'
  netsh advfirewall firewall add rule name="WinRM-HTTP" dir=in localport=5985 protocol=TCP action=allow
  netsh advfirewall firewall add rule name="WinRM-HTTPS" dir=in localport=5986 protocol=TCP action=allow
  

DNS and infrastructure

Because Chef 360 SaaS is hosted by Progress, you don’t need to provision or configure DNS records, storage, or Kubernetes infrastructure for the platform itself. You only need to ensure your users and nodes can reach the tenant URL provided by your account team.

Check whether this applies

Use this checklist to confirm your organization is ready to sign up for Chef 360 SaaS:

• Your organization has a valid subscription or evaluation entitlement.
• The users who need access have a supported browser and can reach the internet.
• The nodes you plan to enroll can open outbound connections on ports 443, 31050, and 31000 (and 22/80 if used).
• The nodes you plan to enroll meet the SSH or WinRM connection requirements above.
• You’ve identified who will request tenant access on behalf of your organization.

If you can check all of the above, you’re ready to continue to sign-up.

Next steps

• Sign up for Chef 360 SaaS to request tenant access and sign in.
• After your tenant is ready, see Enroll nodes to bring nodes under management.

Need access to this capability?

Chef 360 SaaS access requires a valid product subscription or evaluation entitlement. Review the Chef 360 Platform product page to learn more and connect with the marketing or account team about access.