Here is another thread where the same error was present. They seemed to get around it by specifying the
--override
elsewhere. But removing the
--override
from the above invocation leads to boto3 permissions errors.
r
Ryan Peden
04/18/2023, 10:08 PM
I suspect this is because env is set to
None
in your
ecs-block
block right now.
If you use the UI to set env to
{}
, and then try your deployment command again, does it work?
It looks like the default for
env
is supposed to be an empty dict, which would prevent this from happening.
But I just created a new ECS block and my env was None, which I believe will cause the problem you saw right about here when it tries to look up
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.