How to Access the Console for an App Platform Component
Validated on 27 Nov 2024 • Last edited on 20 Jun 2025
App Platform is a Platform-as-a-Service (PaaS) offering that allows developers to publish code directly to DigitalOcean servers without worrying about the underlying infrastructure.
The console of an App Platform component is an in-browser command-line terminal whose shell context is a running container instance for a given resource. You can connect to the console of your app’s components (services and workers) to run commands in the component’s container.
By running commands in the console, you can see the active processes that are running inside the container, browse its local file system, monitor resource usage, observe system logs, and more. Connecting to the console is useful for troubleshooting issues, performing maintenance tasks, and running other one-off commands.
This is similar to other container workflows involving logging into the virtualized environment. For example, with containers that have a bash
shell, you can achieve the same effect locally by running docker exec -it CONTAINER_ID /bin/bash
.
You can access the console for a component using the DigitalOcean Control Panel, API or the official CLI, doctl.
Access a Component’s Console Using the API
Access a Component’s Console Using the CLI
Access a Component’s Console Using the Control Panel
To access a component’s console from the control panel, click your app, then click the Console tab. In the Console tab, select the component that you want access to open its console.

Access a Specific Instance
App Platform components can have multiple running instances. Whenever your app deploys or scales (automatically or manually), it creates a new instance. When accessing the app’s console, App Platform automatically connects you to the first available instance. However, you may want to access the console of another specific instance to debug an issue, using the DigitalOcean API or CLI. For example, if that instance is handling a significantly different workload.
To get a list of an app’s running compute instances:
Run the following doctl
command (requires version v1.129.0 or newer):
doctl apps list-instances $app_id
Use the following API call:
curl -X GET \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
"https://api.digitalocean.com/v2/apps/$app_id/instances"
This returns an array of component instances, each with an ephemeral instance_name
property and instance_alias
property mappable to the app’s insights. You can then use an instance’s name to get an exec URL:
Run the following doctl
command (requires version v1.129.0 or newer):
doctl apps console $app_id $component_name $instance_name
Use the following API call:
curl -X GET \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
"https://api.digitalocean.com/v2/apps/{app_id}/deployments/{deployment_id}/components/{component_name}/exec?instance_name={instance_name}"
This returns an exec URL, which you can use to access the instance’s console using the CLI or API. We recommend using Aptfile to install tools.
Because instances are ephemeral, do not make any changes to them that need to persist or create any scripts that rely on them.