StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I found it to be a 2-step process. This assumes that you've already set up a keypair to access EC2 instances in the relevant region.</p> <h1>Configure Security Group</h1> <ol> <li>In the AWS console, open the EC2 tab.</li> <li>Select the relevant region and click on Security Group.</li> <li>You should have an <code>elasticbeanstalk-default</code> security group if you have launched an Elastic Beanstalk instance in that region.</li> <li><p>Edit the security group to add a rule for SSH access. The below will lock it down to only allow ingress from a specific IP address.</p> <pre><code>SSH | tcp | 22 | 22 | 192.168.1.1/32 </code></pre></li> </ol> <h1>Configure the environment of your Elastic Beanstalk Application</h1> <ol> <li>If you haven't made a key pair yet, make one by clicking Key Pairs below Security Group in the ec2 tab.</li> <li>In the AWS console, open the Elastic Beanstalk tab.</li> <li>Select the relevant region.</li> <li>Select relevant Environment</li> <li>Select Configurations in left pane.</li> <li>Select Instances.</li> <li>Under "EC2 key pair:", select the name of your keypair in the <code>Existing Key Pair</code> field. </li> </ol> <p>Once the instance has relaunched, you need to get the host name from the AWS Console EC2 instances tab, or via the API. You should then be able to ssh onto the server.</p> <pre><code>$ ssh -i path/to/keypair.pub ec2-user@ec2-an-ip-address.compute-1.amazonaws.com </code></pre> <p>Note: For adding a keypair to the environment configuration, the instances' termination protection must be off as Beanstalk would try to terminate the current instances and start new instances with the KeyPair. </p> <p>Note: If something is not working, check the "Events" tab in the Beanstalk application / environments and find out what went wrong.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload