blue-article-76939
02/27/2026, 12:12 PMmetaflow dev up and dev shell on an AWS EC2 instance (Amazon Linux). From my local machine, I connected to the instance using SSH and configured SSH port forwarding for port 3000, so the Metaflow UI is opening correctly at <http://localhost:3000>.
However, when I run a Metaflow flow file inside the virtual environment, the executed runs are not appearing in the UI. When I started the dev environment, Tilt showed <http://localhost:10350/>.
I think this may be related to metadata configuration or metadata provider mode. How do I properly configure METAFLOW_SERVICE_URL in metaflow-dev so that my flow stores metadata in the Postgres-backed metadata service instead of local metadata?
How can I verify whether my flow is using the service metadata backend exposed through Tilt (port 10350), and how can I confirm that the metadata is being stored correctly and accessible to the UI?
Also, what is the recommended way to run Metaflow code so that executions are properly reflected in the Metaflow UI in the browser?hundreds-rainbow-67050
02/28/2026, 5:11 AMmetaflow-dev shell ?hundreds-rainbow-67050
02/28/2026, 5:13 AMMETAFLOW_PROFILE
"METAFLOW_DEFAULT_METADATA": "service",
"METAFLOW_SERVICE_URL": "<http://localhost:8080>",blue-article-76939
02/28/2026, 5:27 AMhundreds-rainbow-67050
03/01/2026, 3:43 AMblue-article-76939
03/01/2026, 6:05 AM