https://outerbounds.com/ logo
Join Slack
Powered by
Hello Outerbounds Team! I'm having problem to get ...
# ask-metaflow
r
Hello Outerbounds Team! I'm having problem to get the step functions created by Metaflow in our Metaflow UI: • I have added in our AWS Stack the metaflow cloud formation with everything enabled except Sagemaker. • the cluster is working well. I can see my step functions being created and running with no problem with the builtin DAG of AWS Step Functions • I don't see any error on the metaflow services spin out in my ECS either. -> However I can't see any of them in my Metaflow UI that i can access successfully and seems to work well (no http request are failing) Some context: • Im not sure if the metaflow configuration i have is ok though when im creating/executing the flow 
... step-functions create/trigger
. See in the thread my config constants im setting • Also how metaflow service is retrieving the step functions info in general behind the scene? Thank you very much for your help!
✅ 1
{
"METAFLOW_BATCH_JOB_QUEUE": "",
"METAFLOW_DATASTORE_SYSROOT_S3": "",
"METAFLOW_DATATOOLS_SYSROOT_S3": "",
"METAFLOW_DEFAULT_DATASTORE": "s3",
"METAFLOW_ECS_S3_ACCESS_IAM_ROLE": "",
"METAFLOW_EVENTS_SFN_ACCESS_IAM_ROLE": "",
"METAFLOW_ECS_FARGATE_EXECUTION_ROLE": "",
"METAFLOW_SFN_DYNAMO_DB_TABLE": "",
"METAFLOW_SFN_IAM_ROLE": "",
"METAFLOW_SFN_EXECUTION_LOG_GROUP_ARN": "",
"METAFLOW_SERVICE_URL": ""
}
a
are you able to use the metaflow client to list your step functions executions from your laptop?
Also, are only the step functions flows are missing in the UI?
r
I cant see anything yet:
I will try to use the client, thank you for the tip!
yes i can see the list
Copy code
Run('HelloFlow/1683934077136657')
Run('HelloFlow/1683934053129859')
Run('HelloFlow/1683934046901631')
Run('HelloFlow/1683934035076308')
Run('HelloFlow/1683934021271435')
Run('HelloFlow/1683933931042944')
is there a constant missing such as the METAFLOW_INTERNAL_SERVICE_URL ? my understanding is that its overriding the METAFLOW_SERVICE_URL. So in my config.json i don't set the url 
"METAFLOW_SERVICE_INTERNAL_URL": "<http://XXX-NLB-XXXX-XXX.elb.us-east-1.amazonaws.com/>
, only 
"METAFLOW_SERVICE_URL": "<https://XXX.execute-api.us-east-x.amazonaws.com/api/>"
and i didnt set actually 
METAFLOW_SERVICE_HEADERS
Ok its set now but didnt fix, still not having the flows in the UI.
Ok my issue was the service headers i didnt set properly with the right api key. All good now! thank you!
among us party 1
At the end for your info, it was not just that: you need actually after deploying the stack to enter the api key in the usage plans of the gateway. I don't know if i miss that in the documentation.
3 Views
Open in Slack
PreviousNext
Powered by