Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have the following scenario:
Since I can’t filter by name (fqdn) and I can’t filter for a single IP either, is there a way to make all the request that came from AWS Machines have only one IP or maybe use a third machine to serve as proxy for the calls for the AWS Machines and then attach a EIP on it.
Not really. Or at least, if there’s a way to do it, I’d love to hear about it. One of the biggest problems with beanstalk is its requirement to exist outside of VPCs, and thus, in arbitrary Amazon IP space. About the only workaround I’ve found for this after talking to AWS engineers is to forward traffic from them to something like a bastion server, and allow the bastion server to communicate with your data center firewall. Maybe there’s something I’m missing, but I know of no other way to get it working without some server in between the beanstalk instances and the data center; not if the IP of the server matters.