- Newest
- Most votes
- Most comments
Hello there,
Based on the new information and documents provided, let's try to troubleshoot the issue you're facing with AWS App Runner service update.
-
Review Your Dockerfile or Build Specifications: Check if there are any changes or errors in your Dockerfile or build specifications that might cause the update to fail. The new image being pulled from ECR needs to be correctly configured for your service.
-
AWS Service Updates: Check if there have been recent updates to AWS App Runner or other AWS services you use, that could be affecting the update process.
-
Health Check Configuration: Ensure your health check path and port are correctly configured for your new image. Though your logs suggest successful health checks, a misconfiguration here might affect the update process.
-
Networking or Permissions: Verify if there have been any changes in the networking setup or permissions that might affect your service from being updated.
Further to these specific steps, you can also try the following general troubleshooting steps:
-
Host Header: Verify that your Host Header is correctly pointing to the service URL in the HTTP request, as per the documentation.
-
Custom Domain's CAA Records: If you're using a custom domain, ensure that the CAA records for the domain include 'amazon.com'. You can check this with the DiG tool. If 'amazon.com' is not included in the CAA records, you need to correct this in your domain records.
-
Service Status: Use the AWS CLI to verify the status of your service with the command: aws apprunner describe-service --service-arn <your-service-arn> replacing '<your-service-arn>' with your App Runner service ARN.
-
DNS Records & Certificates: In case you're using custom domains, make sure to check your CNAME records in your DNS server. If these CNAME records were removed, App Runner won't be able to validate your DNS records and renew the certificate for your custom domain. If the certificate has expired, you should disassociate and then reassociate your custom domain with your App Runner service.
If all of these don't resolve the issue, consider checking if you've reached a resource quota or if there are underlying issues with AWS services. Remember to delete the service after it fails, as it will still count towards your service quota even though it isn't usable.
I hope these steps help you in identifying the root cause and resolving the issue with your App Runner service update.
Relevant content
- asked a year ago
- asked 8 months ago
- asked 8 months ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Thanks for your response, I ll review every detail mentioned and let you know if anything else happens. Thanks!