Browse through the questions and answers listed below or filter and sort to narrow down your results.
Can't create or deploy a service on App Runner since it can't pull a private ECR image
Hey! I'm having an issue with App Runner. When I'm trying to create a service with an image from a private ECR repository it fails because apparently it can't pull the image. Pulling images from public ECR works fine. When I try to create a service I choose to create the AppRunnerECRAccessRole for me. Then when it tries to deploy for the first time, it tries to pull the image. Then it does nothing for around 45 minutes. Then it fails with a message that it apparently can't pull the image. The error message is confusing since the role was created automatically and looking at the policy it looks fine to me. Both ECR repository and App Runner service are in the same region (eu-west-1). Deployment logs: 2021-11-21T14:02:26.613+01:00 Starting to pull your application image. 2021-11-21T14:42:09.236+01:00 Failed to pull your application image. Be sure you configure your service with a valid access role to your ECR repository. Event log: 11-21-2021 02:02:46 PM Successfully created pipeline for automatic deployments. 11-21-2021 02:02:26 PM Service status is set to OPERATION_IN_PROGRESS. 11-21-2021 02:02:26 PM Service creation started.
App Runner Scaling for background service
We have started using App Runner to run out container based application. Some of the services are just background jobs meaning there will be no incoming requests to those services specifically. According to the information on how App Runner scales I read this: > AWS App Runner monitors the number of concurrent requests sent to your application and automatically adds additional instances based on request volume. If your application receives no incoming requests, App Runner will scale the containers down to a provisioned instance, a **cpu throttled instance** ready that is ready to serve incoming requests within milliseconds. I understand that with the background process auto scaling will probably not work but we are ok with setting a minimum manually so that we have enough instances. What worries me though is the part that says a "cpu throttled instance". My question is: 1. Does the fact that the instance get CPU throttled mean that I will not get proper instances and App Runner is not capable of running a service that does not serve http requests? 2. Assuming question 1 is that the instances will work fine and not be throttled, is there an actual way to get auto scaling on such a service?
AWS App Runner Stuck
Hi I've tried starting up an app runner service using a custom Docker container, and it seems to be stuck. My log messages are as follows: **08-21-2021 10:51 PM \[AppRunner] Successfully created pipeline for automatic deployments.** **08-21-2021 10:51 PM \[AppRunner] Service status is set to OPERATION_IN_PROGRESS.** **08-21-2021 10:51 PM \[AppRunner] Service creation started.** Unfortunately, these were created 40 minutes ago at the time of writing and I can't see any update from here. I tried using the aws console to delete the running service, but I get the following error message: **An error occurred (InvalidStateException) when calling the DeleteService operation: Service cannot be deleted in the current state: OPERATION_IN_PROGRESS.** I can't do anything, e.g. update env variables, use the console to delete etc. Is there anything else I can do as it looks stuck. Has anyone else had this issue before? Simmy
AppRunner Service stuck in "Operation in progress"
I have a AppRunner "dev-xyz-webapp-apprunner" service which I updated (changed configuration) which triggered an update. Unfortunatelly, it failed so it rollbacked. But it has been rollbacking for almost 24 hours now so it seems to be stuck. I can't do anything through the AWS web console, no actions (pause, resume, delete) are available because status is "Operation in progress". I tried with AWS CLI (aws apprunner delete-service) and received the following error which is normal I suppose: An error occurred (InvalidStateException) when calling the DeleteService operation: Service cannot be deleted in the current state: OPERATION_IN_PROGRESS. I want to delete it, any suggestions?
Health check on custom port number fails.
I attempted to define a new App Runner web api service running on port 5000. The creation fails the health check step, but the failure message states port 8080 which is the default port number on the setup screen. Is it truly using port 8080 for the health check or is the error message string using the default port always? The event prior states health check will occur on port 5000. Log: 06-20-2021 09:34 PM \[AppRunner] Health check on port '8080' failed. Service is rolling back. Check your configured port number. For more information, read the service's logs. 06-20-2021 09:28 PM \[AppRunner] Performing health check on path '/' and port '5000'. 06-20-2021 09:28 PM \[AppRunner] Provisioning instance and deploying image. 06-20-2021 09:28 PM \[AppRunner] Successfully pulled image from ECR. 06-20-2021 09:25 PM \[AppRunner] Service status is set to OPERATION_IN_PROGRESS. 06-20-2021 09:25 PM \[AppRunner] Service creation started. Edited by: SamSan on Jun 24, 2021 7:57 AM