Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

image.png

Hi Prefect team, I’m noticing what I think is a bug in the Prefect UI. Running AWS ECS tasks that were correctly configured and previously running fine on push work pools, I’m now seeing the below.

When I look under the relevant code in `prefect_aws` I see that the `profile_name` property is marked as *optional*, as so

```    profile_name: Optional[str] = Field(
        default=None, description="The profile to use when creating your session."
    )```
Is this intended behavior?

I am in a similar boat and just started seeing this

This started happening about 5 minutes ago — if <@U03JL7YD78T> is seeing it I suspect it’s a general problem

FYI I just tried to amend my `aws_credentials` objects by specifying a profile name. This worked but triggered a further and not-so-easily resolved issue.

Since I don’t use session tokens this is a non starter.

Seems to be working again out of no where

Hi Harrison and Robert. This was a bug that’s now resolved. Thank you for flagging it to us! 