The human-centric platform for production ML & AI

Outerbounds

Hello! I've been using metaflow for the past year and it's been working great :slightly_smiling_face:
I'm using the <https://github.com/outerbounds/terraform-aws-metaflow|terraform-aws-metaflow> module to set up my environment.

Earlier this week I changed the database instance type from  `db.t2.small` --&gt; `db.t3.small` as the support is ending for the t2 instances. With this change I also pulled in some changes to the `aws_lambda_function.db_migrate_lambda` resource.

It went from  python runtime "python3.7" -&gt; "python3.12" and what I believe is the latest source code hash.

After this change, I'm not able to see any logs in the metaflow UI anymore under stdout. Looking in the console I can see there is a 504 error
`Failed to load resource: the server responded with a status of 504 ()`

Is anyone aware of this being a known issue in the latest version?

Actually, I can't see any invocations of the lambda. This seems to be the change I'm catching in my latest terraform plan
<https://github.com/outerbounds/terraform-aws-metaflow/pull/88>

Is it really necessary to run the `db_migrate_lambda` after that?

This is the image being pulled for the *metadata_service* and *ui_backend*: `metaflow_metadata_service:v2.3.0`

FYI, this resolved itself without any action. Still not sure what the issue was but it's working now :shrug: