@Marvin, I am use the prefect_aws python module to save an ECSTask as a Block. I have the below code to set the task_customisations, however, when I lookup the ECS Block in Prefect Cloud, no task_customisations=[], any idea? task_customisations=[ { "op": "add", "path": "/networkConfiguration/awsvpcConfiguration/securityGroups", "value": ["sg-xyz"] } ],

Based on the information I found, the

ECSTask

infrastructure runs your flow in an ECS Task. However, the ephemeral Prefect API won't work with ECS directly. You must have a Prefect server or Prefect Cloud set up. If you're not seeing the

task_customisations

in Prefect Cloud, it could be due to a few reasons: 1. There might be an issue with the way the

task_customisations

are being set in your code. Ensure that the

task_customisations

are correctly formatted and are being passed to the correct function or method. 2. There might be an issue with the Prefect Cloud interface not displaying the

task_customisations

. This could be a bug or a feature not yet implemented in the Prefect Cloud interface. 3. The

task_customisations

might not be getting saved correctly to Prefect Cloud. This could be due to an issue with the Prefect Cloud API or the way your code is interacting with it. To troubleshoot this issue, you could try the following: 1. Double-check your code to ensure that the

task_customisations

are being set correctly. 2. Try to retrieve the

task_customisations

programmatically using the Prefect Cloud API to see if they are being saved correctly. 3. Reach out to the Prefect community or support for help. They might be able to provide more insight into why the

task_customisations

are not appearing in Prefect Cloud. Here are some resources that might help: - Prefect Cloud Documentation - Prefect Infrastructure Concepts Please note that this is a general advice based on the information available and might not solve your specific issue.

Supposed to be

task_customizations

not

task_customisations