App Runner actions work very slow (2-10 minutes) and deployer provides incorrect error message

0

App Runner actions work very slow for me. create/pause/resume may take 2-5 minutes for simple demo image (public.ecr.aws/aws-containers/hello-app-runner:latest)

and create-service when image not found takes ~10 minutes:

example #1 - 5 min to deploy hello-app image

04-17-2022 05:59:55 PM [AppRunner] Service status is set to RUNNING.
04-17-2022 05:59:55 PM [AppRunner] Deployment completed successfully.
04-17-2022 05:59:44 PM [AppRunner] Successfully routed incoming traffic to application.
04-17-2022 05:58:33 PM [AppRunner] Health check is successful. Routing traffic to application.
04-17-2022 05:57:01 PM [AppRunner] Performing health check on port '8000'.
04-17-2022 05:56:51 PM [AppRunner] Provisioning instances and deploying image.
04-17-2022 05:56:42 PM [AppRunner] Successfully pulled image from ECR.
04-17-2022 05:54:56 PM [AppRunner] Service status is set to OPERATION_IN_PROGRESS.
04-17-2022 05:54:55 PM [AppRunner] Deployment started.

example #2 - 10 min when image not found

04-17-2022 05:35:41 PM [AppRunner] Failed to pull your application image. Be sure you configure your service with a valid access role to your ECR repository.
04-17-2022 05:25:47 PM [AppRunner] Starting to pull your application image.

example #3 - 10 min when image not found

04-17-2022 06:46:24 PM [AppRunner] Failed to pull your application image. Be sure you configure your service with a valid access role to your ECR repository.
04-17-2022 06:36:31 PM [AppRunner] Starting to pull your application image.

but 404 error should be detected immediately and fail much faster. because no need to retry 404 many times for 10 min, right?

additionally the error message Failed to pull your application image. Be sure you configure your service with a valid access role to your ECR repository is very confusing. it doesn't show image name and doesn't provide the actual cause. 404 is not related to access errors like 401 or 403, correct?

can App Runner actions performance and error message be improved?

  • I'm seeing long deploy times, as well. Roughly 5-10 minutes each for successful deploys.

No hay respuestas

No has iniciado sesión. Iniciar sesión para publicar una respuesta.

Una buena respuesta responde claramente a la pregunta, proporciona comentarios constructivos y fomenta el crecimiento profesional en la persona que hace la pregunta.

Pautas para responder preguntas