Hey Y'all, I've been running the flow as a separate ECS task using the ECS infrastructure block; however, we need to provide AWS credentials; is there a way to avoid this and run the task through the block using a custom IAM role created for Prefect?

Hi Vishnu, this is a great question for #C048K0MGHNK. It looks like the credentials provided to the ECS task is optional and as long as your task arn is using the custom IAM role permissions you should be able to do this.

@Kalise Richmond Thank you for responding; I saw that it was optional, but I still got an error; the problem was that I attached the perfect policy to the Task execution role, which controls the permissions of the task when it launches; it turns out that if I attach that perfect policy to the Task role, it works!