But the payback for all that heaviness is the ability to administer Windows Server graphically. Let’s face it, Windows Server is heavy - much heavier than Linux (as the folks I hung out with at AWS re:Invent last week kept telling me). If, like me, you are a Mac user who has responsibility for managing a large number of Windows Server instances running on EC2 in AWS (or in a data center, should you be so unlucky as to have to run on physical hardware), you know that Remote Desktop Protocol (RDP) is the key to, well, everything. (If you are also interested in a technique to secure RDP connections without having to open TCP 3389, please see this post about Remote Desktop Gateway.) If you have a problem make sure you run the chmod command as the PEM file needs to have restricted permissions.Remote Desktop Manager running natively on Mac OS X (click to enlarge) This will permanently add the key to your profile and then Transmit should connect correctly. Then go to the Terminal and change directory to the ~/Documents/ec2-keys/ folder in this case and run : chmod 700. I usually put them in ~/Documents/ec2-keys/.pem. This allows using SSH from the terminal to manage the instance. During the EC2 setup you should have saved your PEM key file to your local machine.
The user will be ec2-user with no password. Enter either your instance name given to you by AWS, elastic ip, or the domain used to access it.
Then make sure to select sFTP as your protocol. This example is for connecting Amazon Linux EC2 from a Mac so your mileage may vary.Ĭlick the to add a new site to Transmit:
0 kommentar(er)
