title: Allow Elasticbeanstalk application to access EC-2 instance without using a VPC
body: <p>Currently I have an application which is running on a normal Ubuntu EC-2 instance as well as an elasticbeanstalk environment running a Tomcat Web Application. There is a server on the EC-2 instance which must be accessible from the elasticbeanstalk application at all times.</p>
  
  <p>The issue here is that I cannot associate the elasticbeanstalk application with a Security Group, I have tried adding an options.config file to the .ebextensions folder in the root web project containing the following:</p>
  
  <pre><code>  option_settings:
     - namespace: 'aws:autoscaling:launchconfiguration'
     - option_name: SecurityGroups
     - value: 'sg-XXXXXX'
  </code></pre>
  
  <p>But this doesn't work. The EC-2 instance always has a static IP-address, however, the instances accessing the EC-2 server is changing inside of AWS. I read that if two services are assigned to the same security group they will be able to communicate with eachother. The issue with that approach is that I cannot even change the security group of the elasticbeanstalk application whatsoever.</p>
  
  <p>I cannot allow global access to the server either, it must be specific to the elasticbeanstalk environment only.</p>
  
  <p>Due to circumstances I cannot dig into right now, we won't be able to launch the instances in a VPC for the moment, but we need the services running regardless.</p>
  
  <p>I cannot find any decent documentation on how to achieve any of this, if any of you have a hunch I'd be more than happy to receive any suggestions or directions as to how to solve this issue.</p>