Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
App Runner is similar to Elastic Beanstalk (EB) in that it offers a wrapper around the underlying EC2 infrastructure and can provide a one-click deployment.
However it has some differences with EB. It is far more streamlined, abstracting away a lot of the networking side of things. This is useful if you have a relatively straightforward app (like we do).
Another big difference is that App Runner is designed first and foremost for containers, whereas in EB they are just one of the deployment options.
The final major advantage to App Runner is that it uses a pay-as-you-go pricing model. For low traffic applications such as the MCM this is a huge advantage as you are only charged when the app is in use.
I've got a test deployment through the CLI but there are some issues I'd like to confirm before migrating the production app over: