Multiple ports
- Dominant language
- No language data
- Stars
- 301
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
**Community Note**
* Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
As of now it only seems possible to expose one port from an app runner service. But there are many instances where you might want to expose several ports. For example having rest api on one port and gRPC on different port. Or in our case running an otel collector that exposes the health check on a different port from the receiver. It would be very useful is app runner supported this.
**Describe alternatives you've considered**
If you need multiple ports there really are no alternatives.
Contributor guide
Research direction
Start by reviewing issue #214 and the AWS App Runner roadmap context. Confirm the requested behavior: one service should expose multiple ports, such as separate REST and gRPC endpoints or an OpenTelemetry health check. Done means the feature is defined and available for App Runner services, with its supported configuration and limitations documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100