Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non HTTP/S ports open for public inbound connection #3001

Closed
vaclavdobsicek opened this issue Apr 20, 2023 · 1 comment
Closed

Non HTTP/S ports open for public inbound connection #3001

vaclavdobsicek opened this issue Apr 20, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@vaclavdobsicek
Copy link

Describe the bug

Lambda has open ports 3306, 22 and 5432 for INBOUND connection.

To Reproduce

Deploy Laravel Vapor to AWS

Steps to reproduce the behavior:

  1. Visit Lambda - Configuration - VPC

Expected behavior

There should be only port 80 and 443 open and idealy with SG of API Gateway, not for 0.0.0.0/0

Environment

  • Vapor Framework version: not sure
  • Vapor Toolbox version: not sure
  • OS version: N/A

Additional context

image

@vaclavdobsicek vaclavdobsicek added the bug Something isn't working label Apr 20, 2023
@vzsg
Copy link
Member

vzsg commented Apr 20, 2023

I'm afraid if this is about Laravel Vapor, then this is the wrong repository to open an issue against.
This is the repo for the Server-side Swift framework Vapor.

@0xTim 0xTim closed this as not planned Won't fix, can't repro, duplicate, stale Apr 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants