By using AWS re:Post, you agree to the Terms of Use

Questions tagged with AWS App Runner

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

What's the unit for AppRunner's CPU Utilization?

Looking at the CloudWatch metric AppRunner > Instance metrics > CPU Utilization, I see that my instance is reaching up to 1000 of an unknown unit. Well, the question here is simple - what is the unit for CPU Utilization? Here are my theories so far: - The official [docs page](https://docs.aws.amazon.com/apprunner/latest/dg/monitor-cw.html) on AppRunner metrics is not very helpful; their description is "The average CPU usage during one-minute periods." - The most obvious is percentage of CPU, but that should stop at 100%, so 1000% doesn't make much sense. - According to some other AWS products though, 100% = 1vCPU. This SageMaker [question](https://aws.amazon.com/premiumsupport/knowledge-center/sagemaker-cpu-gpu-utilization-100/) says 400% = 4 vCPUs. So 1000 would be 10 vCPUs. - But my instances are configured to use 1vCPU & 2 GB. So I'd still expect a max of 100, not 1000. Am I allowed to go above the max for brief amounts of time? Will I be charged extra if so? - Another theory is that this might be something to do with less than 1vCPU - like AWS Lambda's CPU throttling which lets you use less than 1vCPU. ie, 1000 = 1vCPU. - Finally, I might be doing something wrong. I'd be happy to share some details of my setup. I'm using maximum for aggregation statistic in Cloud Watch & only 1 instance is running. But to sum up - does anyone know what the unit is for AppRunner's CPU Utilization?
1
answers
0
votes
72
views
asked 5 months ago

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

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?
0
answers
0
votes
53
views
asked 6 months ago