Hello team, as you guys might remember, time to time there have been discussions around ECS’s 8192 character limit on

ContainerOverrides

object. I have noticed that earlier you guys attempted to patch it up by compressing the amount of information metaflow sends compulsorily, but another case where this limit is breached is if the user input itself is large enough. In our case we stumbled upon this issue when we started use a json payload which can a couple of KBs large sometimes. This combined with information that metaflow already attaches makes the

ContainerOverride

object again exceed the hard 8192 limit 😕 As a short term workaround we are exploring passing input params through a persistent storage like s3/dynamo but I am just wondering if this is something metaflow team would consider supporting natively? So a blob-like or json-like input param type that is passed through a dynamodb/s3 layer implementaiton-wise. Perhaps then, in fact, all payloads can be passed as such uplifting this restriction forever?