> [!CAUTION]
> **Caution:** This documentation covers Edge for Private Cloud 4.17.05, which is no longer supported. Google does not provide security patches, bug fixes, or technical support for this version. The current supported version is 4.54.00. See the [Edge for Private Cloud documentation](https://docs.apigee.com/private-cloud/latest/overview) for the current version, or [All versions](https://docs.apigee.com/private-cloud/versions) to compare releases.

*Edge for Private Cloud v. 4.17.05*

You can install Edge for the Private Cloud on a single host machine as part of a demo or proof
of concept installation. This type of installation is referred to as an Edge "all-in-one"
installation. The host machine can be a standalone machine or a VM that meets the system
prerequisites listed below.

> [!NOTE]
> **Note:** A single machine install is meant for a getting started and prototyping environments, not for production. A full production installation of Edge requires multiple machines. See [Installation
> Topologies](https://docs.apigee.com/private-cloud/v4.17.05/installation-topologies) for examples of production installations.

After you install Edge for the Private Cloud on the host machine, you can optionally
install:

- Developer Services portal on its own host machine
- API BaaS on its own host machine

## Licensing

Each installation of Edge requires a unique license file that you obtain from Apigee. If you
do not yet have a license, contact Sales [here](https://pages.apigee.com/contact-sales-reg.html).

## System requirements for Edge

The following table lists the system requirements for installing Edge on a single host
machine:

| **Requirement** | **Description** | **Test** |
|---|---|---|
| **Access to Apigee RPM repo** | Ensure access to <https://software.apigee.com> Ensure you received a username/password from Apigee for the repo: - If you are a prospect evaluating Apigee, please contact Apigee Sales [here](https://pages.apigee.com/contact-sales-reg.html). - If you are an existing Apigee customer, please contact your Apigee representative. | curl -v <https://software.apigee.com> returns HTTP 200 |
| **Access to your backend services** | Ensure access to your backend services | curl -v http://***backend*** to check access to your backend services |
| **License key** | Check for an email from Apigee with license key attached | Ensure license key deployed to host machine |
| **OS Version** | Supported OS version as listed at [Supported software and supported versions](https://docs.apigee.com/release/supported-software). | cat /etc/redhat-release returns the OS version |
| **Java version** | Supported Java versions: - Oracle JDK 1.8 - OpenJDK 1.8 | java -version returns the installed Java version If required Java version not found, Edge installer downloads and installs it. |
| **CPU cores** | 2 minimum | lscpu returns number of CPUs cat /proc/cpuinfo returns CPU Information |
| **RAM** | 8 GB minimum | cat /proc/meminfo returns memory information |
| **Diskspace** | 100 GB minimum | df -h returns the disk space. df -h /opt returns the disk space for /opt, the Edge install directory |
| **Hostname** | Hostname set to IP address of host | hostname -i returns the IP address of host |
| **Network** | External Internet access required. For RedHat OS, access to RHEL yum repository. | yum repolist returns available repos. For RedHat, check the availability of repos from /etc/yum.repos.d/redhat-rhui.repo |
| **ports, iptables, firewalld** | Ensure that ports 8080, 9000, 9001, and 9002 can accept incoming packets. | This requirement is dependent on your OS and OS configuration. There are several commands you can use to view the current settings: iptables -nvL **Linux 6.x** : service iptables status **Linux 7.x** : sysctl firewalld status If necessary, you can stop iptables or firewalld |
| **SELinux** | Disable SELinux, or set it to permissive mode, during install. Re-enable after install if necessary | Temporarily set SELinux to permissive mode: **On a Linux 6.x operating system:** echo 0 \> /selinux/enforce To re-enable after installing Edge: echo 1 \> /selinux/enforce **On a Linux 7.x operating system:** setenforce 0 To re-enable after installing Edge: setenforce 1 To permanently disable SELinux, see [Install the Edge apigee-setup utility](https://docs.apigee.com/private-cloud/v4.17.05/install-edge-apigee-setup-utility). |
| **System user access** | User performing install requires: - sudo access or root access - ability to add users on host machine | sudo whoami should return root |
| **SMTP Server** | Access to SMTP server to send emails to new Edge users. |   |

## System requirements for Developer Services
portal

You can install the Edge Developer Services portal on a machine different than the one you
used to install Edge. Make sure you have satisfied the following requirements before you install
the portal:

| **Requirements** | **Description** | **Test** |
|---|---|---|
| **Access to Apigee RPM repo** | Ensure access to <https://software.apigee.com> Ensure you received a username/password from Apigee for the repo. | curl -v <https://software.apigee.com> returns HTTP 200 |
| **Edge installed on the host** | Ensure that you have already installed Edge on the host machine | See *System requirements for Edge* above. |
| **Port** | Ensure port 8079 is available and accessible | netstat -nlptu \| grep 8079 |

## System requirements for API BaaS

You can install API BaaS on the single host machine, different than the one you used to
install Edge. Make sure you have satisfied the following requirements before you install API BaaS
on the host:

| **Requirements** | **Description** | **Test** |
|---|---|---|
| **Access to Apigee RPM repo** | Ensure access to <https://software.apigee.com> Ensure you received a username/password from Apigee for the repo. | curl -v <https://software.apigee.com> returns HTTP 200 |
| **All Edge requirements** | Ensure that the host machine meets all the requirements listed above for Edge | See *System requirements for Edge* above. |
| **ports, iptables, firewalld** | Ensure that ports 2551, 8080, 9000, 9200-9400 can accept incoming packets. | This step is dependent on your OS and OS configuration. There are several commands you can use to view the current settings: iptables -nvL **Linux 6.x** : service iptables status **Linux 7.x** : sysctl firewalld status If necessary, you can stop iptables or firewalld |