The administration topics help you set up, administer, and manage your DC/OS cluster.


DC/OS can be installed on any cluster of physical or virtual machines.


This document provides instructions for upgrading a DC/OS cluster from version 1.7 to 1.8. If this upgrade is performed on a supported OS with all prerequisites fulfilled, this upgrade should preserve the state of running tasks on the cluster. This document reuses portions of the Advanced DC/OS Installation Guide.

    Identity and Access Management

    You can enable authentication in your datacenter with DC/OS oauth. Authentication is managed through the DC/OS web interface. The Admin Router enforces access control.

    Finding a Public Agent

    After you have installed DC/OS with a public agent node declared, you can navigate to the public IP address of your public agent node.

      Removing an Agent

      To shut down and safely remove an agent node follow these steps.


        DC/OS cluster nodes generate logs that contain diagnostic and status information for DC/OS core components and DC/OS services.


        Monitoring the health of all the pieces that make up DC/OS is vital to datacenter operators and for troubleshoooting hard-to-diagnose bugs. You can monitor the health of your cluster components from the DC/OS UI component health page. The component health page displays information from the system health API, which monitors the core DC/OS components.

        Accessing the Cluster

        You can access your DC/OS cluster via SSH or by using DC/OS Tunnel from the CLI to set up a SOCKS proxy, an HTTP proxy, or a VPN.

        Securing communication with TLS

        You can set up secure HTTPS communication using a custom server certificate with your DC/OS cluster by setting up a proxy between the Admin Router and user agent requests coming in from outside of the cluster.

        Securing Your Cluster

        This topic discusses the security features in DC/OS and best practices for deploying DC/OS securely.

          Managing AWS

          The DC/OS AWS CloudFormation template is optimized to run DC/OS, but you might want to change the number of agent nodes based on your needs.


            DC/OS applications lose their state when they terminate and are relaunched. In some contexts, for instance, if your application uses MySQL, or if you are using a stateful service like Kafka or Cassandra, you’ll want your application to preserve its state. Configure Mesos mount disk resources to enable users to create tasks that can be restarted without data loss. Learn how to create stateful applications.

            Virtual Networks

            The DC/OS virtual network feature is an out-of-the-box virtual networking solution that provides an IP-per-container for Mesos and Docker containers alike. The DC/OS virtual network uses CNI (Container Network Interface) for the Mesos Containerizer and Docker libnetwork for the Docker Containerizer.


            We recommend starting with a fresh cluster to ensure all defaults are set to expected values. This prevents unexpected conditions related to mismatched versions and configurations.