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.

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.


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.

SSHing into Nodes

These instructions explain how to set up an SSH connection to your DC/OS cluster from an outside network. If you are on the same network as your cluster or connected by using VPN, you can instead use the dcos node ssh command. For more information, see the dcos node section of the CLI reference.


    You can opt-out of the provided authentication by disabling it for your cluster. To disable authentication, add this parameter to your config.yaml file during installation (note this requires using the CLI or advanced installers):


      To continuously improve the DC/OS experience, we have included a telemetry component that reports anonymous usage data back to us. We use this data to monitor the reliability of core DC/OS components, installations, and to find out which features are most popular. There are two sections that have the telemetry component implemented:

        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.


            This document provides instructions for upgrading a DC/OS cluster from version 1.6 to 1.7. 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.

              Finding a public agent IP

              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.

                User Management

                Users are granted access to DC/OS by another authorized user. A default user is automatically created by the first user that logs in to the DC/OS cluster.


                  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.