Amazon AWS DevOps Linux

5 steps to setup SSH PROXY VIA WITH PUTTY

Depending on your setup and where you are deploying your solution, you may have to jump via multiple servers before you can get access to your internal server. This quick guide will help you understand how you can leverage PUTTY to Proxy via multiple SSH hosts.

Here is the example: let say that you are on your house or outside your cloud provider and you need to access the private SSH server in the image. That server has an IP address that is private so it can’t be access from the internet. And there is only one server available from the internet. You can use that server as a SSH Proxy server so you can access the internal one via your SSH proxy server.

Here is what you need:

  1. Install Putty suite completely not only the putty.exe
  2. Have a Public Key configure on your Servers and have the Keys available.

5 Steps to configure SSH Proxy with Putty

  1. Open Putty and create a new connection. Type the IP address or DNS Name of your Private SSH Server. On our Lab that will be any IP address or Private DNS. Type a name to save the session later. Do not save it yet.

  2. Click the Connection  Data. Type the name in the Auto-login username field.

  3. Click Connection Proxy. Type the IP Address or DNS server that is available externally or in the internet. Click Local for the Proxy Type and change the port to 22. Type your username that will be use to connect to the remote server. In the Telnet command or local proxy command type: plink %user@%proxyhost -nc %host:%port

  4. Click Connection à SSH àAuth. Click Allow agent forwarding and then put your public key.

  5. Go back up to the Session screen and click Save. Then Open.

That’s it. You are now connected to your Private IP server via a public SSH Server.

Let me know how you use this tutorial.

Amazon AWS Beanstalk Carlos Vargas Technology

AWS Elastic Beanstalk S3 Bucket and Access Denied

After working with AWS for a while , I decided to clean up some of my old deployments. After removing one of my Elastic Beanstalk application deployments it left a bucket in S3. So I tried to delete it and I got Access Denied.


After a little digging and some reading, I found the way to remove it.

Steps to remove left over Elastic Beanstalk S3

1. Login to your S3 console

2. Click the bucket that you need to delete

3. Click the bucket policy button

4. In the bucket policy editor. Look for the “Effect”: “Deny”, statement

5. Change the “Deny” statement to “Allow”. Press Save and then OK.

6. Now you should be able to right click your bucket and delete the bucket

7. Old Elastic Beanstalk S3 bucket removed