Connecting to Your AWS Linux Instance from MacOS Using PuTTY for Mac

Connecting to Your ( Amazon Elastic Compute Cloud ) AWS Linux Instance from MacOS Using PuTTY for Mac.

After you launch your instance, you can connect to it and use it the way that you’d use a computer sitting in front of you.

Note

After you launch an instance, it can take a few minutes for the instance to be ready so that you can connect to it. Check that your instance has passed its status checks – you can view this information in the Status Checks column on the Instances page.

The following instructions explain how to connect to your instance using PuTTY for Mac, a SSH client for Windows that has been ported to MacOS. If you receive an error while attempting to connect to your instance.

Prerequisites

Before you connect to your Linux instance using PuTTY, complete the following prerequisites:

  • Install PuTTY
    Download and install PuTTY from the PuTTY for Mac store. If you already have an older version of PuTTY for Mac installed, we recommend that you download the latest version. Be sure to install the entire suite.
  • Get the ID of the instance
    You can get the ID of your instance using the Amazon EC2 console (from the Instance ID column). If you prefer, you can use the describe-instances (AWS CLI) or Get-EC2Instance (AWS Tools for Windows PowerShell) command.
  • Get the public DNS name of the instance
    You can get the public DNS for your instance using the Amazon EC2 console (check the Public DNS (IPv4) column; if this column is hidden, choose the Show/Hide icon and select Public DNS (IPv4)). If you prefer, you can use the describe-instances (AWS CLI) or Get-EC2Instance (AWS Tools for Windows PowerShell) command.
  • (IPv6 only) Get the IPv6 address of the instance
    If you’ve assigned an IPv6 address to your instance, you can optionally connect to the instance using its IPv6 address instead of a public IPv4 address or public IPv4 DNS hostname. Your local computer must have an IPv6 address and must be configured to use IPv6. You can get the IPv6 address of your instance using the Amazon EC2 console (check the IPv6 IPs field). If you prefer, you can use the describe-instances (AWS CLI) or Get-EC2Instance (AWS Tools for Windows PowerShell) command. For more information about IPv6, see IPv6 Addresses.
  • Locate the private key
    Get the fully qualified path to the location on your computer of the .pem file for the key pair that you specified when you launched the instance.
  • Enable inbound SSH traffic from your IP address to your instance
    Ensure that the security group associated with your instance allows incoming SSH traffic from your IP address. The default security group does not allow incoming SSH traffic by default.

Starting a PuTTY Session

Use the following procedure to connect to your Linux instance using PuTTY. You need the .ppk file that you created for your private key. If you receive an error while attempting to connect to your instance, see Troubleshooting Connecting to Your Instance.

To start a PuTTY session
  1. (Optional) You can verify the RSA key fingerprint on your instance using the get-console-output (AWS CLI) command on your local system (not on the instance). This is useful if you’ve launched your instance from a public AMI from a third party. Locate the SSH HOST KEY FINGERPRINTS section, and note the RSA fingerprint (for example, 1f:51:ae:28:bf:89:e9:d8:1f:25:5d:37:2d:7d:b8:ca:9f:f5:f1:6f) and compare it to the fingerprint of the instance.
    Copy
    aws ec2 get-console-output --instance-id instance_id

    Here is an example of what you should look for:

    -----BEGIN SSH HOST KEY FINGERPRINTS-----
    ... 1f:51:ae:28:bf:89:e9:d8:1f:25:5d:37:2d:7d:b8:ca:9f:f5:f1:6f ...
    -----END SSH HOST KEY FINGERPRINTS-----

    Note that the SSH HOST KEY FINGERPRINTS section is only available after the first boot of the instance.

  2. Start PuTTY (from the Start menu, choose All Programs > PuTTY > PuTTY).
  3. In the Category pane, select Session and complete the following fields:
    1. In the Host Name box, enter user_name@public_dns_name. Be sure to specify the appropriate user name for your AMI. For example:
      • For an Amazon Linux AMI, the user name is ec2-user.
      • For a RHEL AMI, the user name is ec2-user or root.
      • For an Ubuntu AMI, the user name is ubuntu or root.
      • For a Centos AMI, the user name is centos.
      • For a Fedora AMI, the user name is ec2-user.
      • For SUSE, the user name is ec2-user or root.
      • Otherwise, if ec2-user and root don’t work, check with the AMI provider.
    2. (IPv6 only) To connect using your instance’s IPv6 address, enter user_name@ipv6_address. Be sure to specify the appropriate user name for your AMI. For example:
      • For an Amazon Linux AMI, the user name is ec2-user.
      • For a RHEL AMI, the user name is ec2-user or root.
      • For an Ubuntu AMI, the user name is ubuntu or root.
      • For a Centos AMI, the user name is centos.
      • For a Fedora AMI, the user name is ec2-user.
      • For SUSE, the user name is ec2-user or root.
      • Otherwise, if ec2-user and root don’t work, check with the AMI provider.
    3. Under Connection type, select SSH.
    4. Ensure that Port is 22.
    
       PuTTY configuration - Session
  4. In the Category pane, expand Connection, expand SSH, and then select Auth. Complete the following:
    1. Choose Browse.
    2. Select the .ppk file that you generated for your key pair, and then choose Open.
    3. (Optional) If you plan to start this session again later, you can save the session information for future use. Select Session in the Category tree, enter a name for the session in Saved Sessions, and then choose Save.
    4. Choose Open to start the PuTTY session.
    
       PuTTY configuration - Auth
  5. If this is the first time you have connected to this instance, PuTTY displays a security alert dialog box that asks whether you trust the host you are connecting to.
  6. (Optional) Verify that the fingerprint in the security alert dialog box matches the fingerprint that you previously obtained in step 1. If these fingerprints don’t match, someone might be attempting a “man-in-the-middle” attack. If they match, continue to the next step.
  7. Choose Yes. A window opens and you are connected to your instance.
    Note

    If you specified a passphrase when you converted your private key to PuTTY’s format, you must provide that passphrase when you log in to the instance.

Connecting to Your Linux Instance Using SSH

After you launch your instance, you can connect to it and use it the way that you’d use a computer sitting in front of you.

Note

After you launch an instance, it can take a few minutes for the instance to be ready so that you can connect to it. Check that your instance has passed its status checks – you can view this information in the Status Checks column on the Instances page.

The following instructions explain how to connect to your instance using an SSH client. If you receive an error while attempting to connect to your instance, see Troubleshooting Connecting to Your Instance.

Prerequisites

Before you connect to your Linux instance, complete the following prerequisites:

  • Install an SSH client
    Your Linux computer most likely includes an SSH client by default. You can check for an SSH client by typing ssh at the command line. If your computer doesn’t recognize the command, the OpenSSH project provides a free implementation of the full suite of SSH tools. For more information, see http://www.openssh.com.
  • Install the AWS CLI Tools
    (Optional) If you’re using a public AMI from a third party, you can use the command line tools to verify the fingerprint. For more information about installing the AWS CLI, see Getting Set Up in the AWS Command Line Interface User Guide.
  • Get the ID of the instance
    You can get the ID of your instance using the Amazon EC2 console (from the Instance ID column). If you prefer, you can use the describe-instances (AWS CLI) or Get-EC2Instance (AWS Tools for Windows PowerShell) command.
  • Get the public DNS name of the instance
    You can get the public DNS for your instance using the Amazon EC2 console (check the Public DNS (IPv4) column; if this column is hidden, choose the Show/Hide icon and select Public DNS (IPv4)). If you prefer, you can use the describe-instances (AWS CLI) or Get-EC2Instance (AWS Tools for Windows PowerShell) command.
  • (IPv6 only) Get the IPv6 address of the instance
    If you’ve assigned an IPv6 address to your instance, you can optionally connect to the instance using its IPv6 address instead of a public IPv4 address or public IPv4 DNS hostname. Your local computer must have an IPv6 address and must be configured to use IPv6. You can get the IPv6 address of your instance using the Amazon EC2 console (check the IPv6 IPs field). If you prefer, you can use the describe-instances (AWS CLI) or Get-EC2Instance (AWS Tools for Windows PowerShell) command. For more information about IPv6, see IPv6 Addresses.
  • Locate the private key
    Get the fully qualified path to the location on your computer of the .pem file for the key pair that you specified when you launched the instance.
  • Enable inbound SSH traffic from your IP address to your instance
    Ensure that the security group associated with your instance allows incoming SSH traffic from your IP address. The default security group does not allow incoming SSH traffic by default. For more information, see Authorizing Inbound Traffic for Your Linux Instances.

Purchase Putty 8.5.1 now and have Telnet SSH FTP SCP on your Mac made easy!

Advertisements

Q4Wine 1.3.2 has been released for Linux and Mac OSX

Q4Wine is a Qt GUI for Wine. It will help you manage wine prefixes and installed applications. It currently supported on Linux, FreeBSD and Mac OS X platforms.

Q4Wine was initially written by Alexey S. Malakhov aka John Brezerk. General idea comes from WineTools scripts which were initially written by Frank Hendriksen.

General features are:

  • Can export Qt color theme into wine colors settings;
  • Can easy work with different wine versions at same time;
  • Easy creating, deleting and managing prefixes (WINEPREFIX);
  • Easy controlling for wine process;
  • Autostart icons support;
  • Easy cd-image use;
  • You can extract icons from PE files (.exe .dll);
  • Easy backup and restore for managed prefixes;
  • Winetricks support;
  • And more: Explore it!;

Changelog for 1.3.2:

Fixed:

  • [regression, bisected] Icon information is not displayed correctly BUG-80;
  • Winetricks does not update BUG-77;
  • First startup wizard (quick mount profile): profile strings are initially empty if fuseiso is not installed BUG-81;
  • Download (latest) Winetricks from GitHub BUG-82;
  • Correct proxy-related environment variables in Winetricks plugin BUG-83;
  • Use env command in the command line to download Winetricks BUG-83;
  • Support proxy username/password in Winetricks plugin BUG-83;
  • Treat aarch64 as 64 bit platform and put libraries in lib64 directory BUG-85;

You can now purchase PuTTY for Mac as well Mariner Software products in our new online store.

 

WineTricks has seen a massive amount of improvements this year

WineTricks has seen allot of development recently, some of the notable changes are better IE 8 support, MetaTrader 4 support, Kindle improvements, Russian translation, A new self update function and a massive amount of other fixes and updates. The full changelog sense February 2016 and August 2016 is provided below with a download link to get the latest release.

Winetricks is an easy way to work around problems in Wine. It has a menu of supported games/apps for which it can do all the workarounds automatically. It also lets you install missing DLLs or tweak various Wine settings individually.

It can be used via gui or commandline, whichever you prefer; the commandline mode is particularly useful as a building block in fancier wine frontends and in automated regression testing.

The latest version can be downloaded here

Changelog between 20160724 and 20160802

add win2k8/win8/win81/win10 verbs

Changelog between 20160219 and 20160724

github-api-releases.py: fix for Debian’s python-magic
relase.sh: fix path to pgp signature file
test cleanups
opensymbol: update to latest
add win2k8/win8/win81/win10 verbs
winetricks: add initial embedded wine cmd support
tests: add some TODOs
tests/winetricks-test: avoid backtricks (“), use $()
winetricks: get rid of backticks(“), use $() instead
README.md: fix typo
tests/winetricks-test: add some basic .verb tests
README: add some .verb documentation
winetricks_handle_options: alphabetize case list
src/release.sh: fix path to github-api-releases.py
src/release.sh: specify the GPG key to use
src/release.sh: create local signed release tarball
github-api-releases.py: check in script, authored by Joseph Bisch
wmv9vcm: new verb
w_get_sha1sum(): only try to verify sha1sum for actual files
winetricks: miscellaneous spelling updates
winetricks: Add separate override just for d3dx10_43
kindle: update to version 1.16 (build 44025)
kindle: Fix bug reference number
winetricks.1: Change strings to proper case, wine to Wine, etc
w_try_ar(): use 7zip as a fallback if ar is missing
7zip: update to latest release
opensymbol: restore J flag to tar
w_try_ar: should be w_die, not w_fatal

winetricks: add a w_try_ar() function, give better warning if ar is missing
Override more vcrun2015 dlls for 32 bits prefix Fixes #650, tested with Python3.5.exe, on both 32/64 bits, wine 1.9.8/1.9.11.

w_wine_version: support wine-1.9.x
Update ev3 verb
adobeair: remove extra space in metadata
mt4: do not use checksum for mt4setup.exe which may change
winetricks: update Ukrainian translation
release.sh: allow overridding version
Update control
foobar2000: update to v1.3.10
update src/release.sh for github releases, also now updates manpage
update manpage
Makefile: update copyright
Makefile: winetricks now uses git, not svn

winetricks: remove python26_comtypes / python26_setuptools broken, old, and not actively supported upstream

winetricks: print winetricks and wine version in winetricks_init()
add .gitignore
jet40: restore original microsoft.com url
cmd: revert back to a microsoft.com URL (really, archive.org)
xna40: add Louis’ workaround from bug 30718

Self-update functionality for winetricks.

– With this patch it is possible to use “winetricks –self-update|–selfupdate” to automatically update the script with the last online version. Also, it is possible to rollback an update by running “winetricks –update-rollback”;
– Added checking to avoid running the command into dev versions of winetricks;
– Added message for users who run unprivileged and do not have the proper permissions to update winetricks.

w_download_to(): fix aria2c torify support
winetricks: add -t/–torify support
mt4: new verb (Meta Trader 4)
windowscodecs: initial 64-bit esupport
vcrun2015: also extract api-ms-win-crt-conio-l1-1-0.dll
vcrun2015: warn about win7 mode installations failing
winetricks: improve aria2 support (fixes 612)
winetricks-test: xna40 now completes without an error dialog
Makefile: default to a 32-bit prefix if WINEARCH is not set
emu8086: update download URL
ev3: add -q support
winetricks: introduce W_UNATTENDED_SLASH_QB to unify /qb handling
ev3: update download URL
xna40: needs dotnet45, not dotnet40
vcrun2003: fix url
winetricks: check each test scripts dependencies before running any tests
linkcheck.sh: cleanup temp files after running
baekmuk: update URL and some cleanups
opensymbol: update URL to jessie (stable)
openwatcom: update URL
kindle: needs taskset -c 0, not vcrun2008
shockwave: update sha1sum
ie8_kb2936068: exit code 194 is not an error
Preliminary Russian translation By Artem S. Tashkinov
A real albeit untidy help page the old redirect is hard to swallow
ie6: make ie6 an automated download again
w_download_manual_to(): verify sha1sum of manually downloaded files
ie6: use $W_PACKAGE instead of hardcoding
ie8-kb2936068: rename to ie8_kb2936068, avoid warning on OSX.
ev3/ie8-kb2936068: minor cleanups
ev3: new verb
ie8-kb2936068: new verb
cmd: update download URL
kindle: update to version 1.14.43019

The newest CodeWeavers coupon promo code is ( CXNOW ) save 30% off CrossOver Mac or Linux today!