Never mind, the solution was easy
Laravel Vapor Using Load Balancers if not in Vapor Network
We use Vapor extensively and We have a custom setup where we must be in the existing VPC and Subnets our Infrastructure team has demanded. on our vapor.yml we have those subnets listed and everything works fine, every deployment etc. We're however restricted to the 30 second constraints of the API Gateway and want to utilize the Load Balancers.
My initial assumption was we can't because we're outside the vapor network, within different VPC and subnets, is this not the case and there is still an option to attached a ALB to the Lambda functions vapor uses?
Any direction here or options would be fantastic. if this is possible, or if anyone has run into this case.
Please or to participate in this conversation.