My main use case for AWS App Runner is to deploy lightweight backend services and APIs, primarily in Node.js and Python, without managing infrastructure like Kubernetes or ECS. Managing Kubernetes is a real challenge, so AWS App Runner helped me overcome that. A recent project where I used AWS App Runner for a Node.js or Python backend involved a microservice built in FastAPI that needed to be deployed quickly with auto-scaling and HTTPS. Instead of setting up ECS and EKS, we pushed the container image to ECR and connected it to AWS App Runner. It automatically handled deployment, scaling, and load balancing.
Senior Java Consultant at a comms service provider with 1,001-5,000 employees
Real User
Top 5
Mar 21, 2025
I use AWS App Runner as a development platform. I create a service locally with Docker containers, and then I'm able to start it up to test. If I need to make a backup, I just put it on a different port to test different configurations. Once I have my services working, a team handles the DevOps for production deployment.
I think the solution is growing in size. It's like a multi-tier website that wants to provide some microblogging data being collected personally, but it does so in different tiers. The first one is closest to AWS. Another one is encrypting and decrypting data so that it is not very easy to eavesdrop. This user interface is in a web browser and shows textual information with a few analytics graphs. It's still kind of an experimental thing. It's probably in this condition because I'm not selling or monetizing the product. It's a very good illustration of how you customize your expectations of the services you're developing and try them on the different implementations of the AWS compute services because they're changing. There is something new every two years or so, and it's evolving.
AWS App Runner is primarily used for deploying and scaling web applications and APIs, known for its seamless integration with GitHub, automatic scaling, and serverless nature.
AWS App Runner allows efficient deployment and scaling of web applications and APIs by offering automatic scaling without complex configurations. It smoothly integrates with other AWS services and simplifies the transition from development to production. Users value its serverless nature, reducing operational...
My main use case for AWS App Runner is to deploy lightweight backend services and APIs, primarily in Node.js and Python, without managing infrastructure like Kubernetes or ECS. Managing Kubernetes is a real challenge, so AWS App Runner helped me overcome that. A recent project where I used AWS App Runner for a Node.js or Python backend involved a microservice built in FastAPI that needed to be deployed quickly with auto-scaling and HTTPS. Instead of setting up ECS and EKS, we pushed the container image to ECR and connected it to AWS App Runner. It automatically handled deployment, scaling, and load balancing.
I use AWS App Runner as a development platform. I create a service locally with Docker containers, and then I'm able to start it up to test. If I need to make a backup, I just put it on a different port to test different configurations. Once I have my services working, a team handles the DevOps for production deployment.
I think the solution is growing in size. It's like a multi-tier website that wants to provide some microblogging data being collected personally, but it does so in different tiers. The first one is closest to AWS. Another one is encrypting and decrypting data so that it is not very easy to eavesdrop. This user interface is in a web browser and shows textual information with a few analytics graphs. It's still kind of an experimental thing. It's probably in this condition because I'm not selling or monetizing the product. It's a very good illustration of how you customize your expectations of the services you're developing and try them on the different implementations of the AWS compute services because they're changing. There is something new every two years or so, and it's evolving.