Add a feature in AppRunner service which is similar to ECS_CONTAINER_STOP_TIMEOUT in the ECS service that to ensure running asynchronous operations are finished.

[Mallamu]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request What do you want us to build? We want a feature to be available in AppRunner service which is similar to "ECS_CONTAINER_STOP_TIMEOUT" in the ECS service that ensures that the asynchronous operation is finished.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. For now, we can use ECS service as alternative approach.

Additional context Anything else we should know? In ECS, when a task is stopped, a SIGTERM signal is sent to each container’s entry process, usually PID 1. After a timeout has lapsed, the process will be sent a SIGKILL signal. By default, there is a 30 second delay between the delivery of SIGTERM and SIGKILL signals. This value can be adjusted by updating the ECS task parameter stopTimeout, or with EC2 Container Instances by setting the ECS agent environment variable ECS_CONTAINER_STOP_TIMEOUT. Processes that don’t exit before the timeout expires will be terminated abruptly upon receipt of the SIGKILL signal.” As mentioned in https://aws.amazon.com/blogs/containers/graceful-shutdowns-with-ecs/. We want similar feature in AppRunner service.

Attachments If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

[amitgupta85]

Could you please tell us what maximum timeout value you are looking for?