-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fargate support #15718
Comments
Hi @johnf, thanks for filing this. Could you elaborate what you'd want to see exactly? |
@andreiborza Below are two sections that I get in Lambda which would be handy in Fargate
Those are the main bits missing. If you could detect that this was running in a step function and provide the input to the function, that would be amazing. But I'm not sure if that is possible. This would be valuable for Fargate and Lambda. |
Thanks! Hm, these are directly supplied to a lambda function's context but I don't think fargate exposes these as easily. I'm not super familiar with fargate and step functions but from looking around it looks like you'd have to use the aws-sdk to fetch these. Something we're probably unlikely to add. You could try to do this yourself enhancing events in |
Problem Statement
I recently moved some step function steps from lambda to fargate. When errors occur, I'm missing the nice linkage to cloudwatch, etc.
Solution Brainstorm
I suspect code could be re-used from the lambda integration. If I had more time right now I'd explore it
The text was updated successfully, but these errors were encountered: