- Newest
- Most votes
- Most comments
All ssh needs is a hostname that will resolve to the correct IP or an IP.
slogin ec2-user@<hostname> or slogin ec2-user@<ip address>
If the public IP of your instance is 12.34.56.78, then you should be able to log in with
slogin ec2-user@ec2-12-34-56-78.compute-1.amazonaws.com
If you set up a DNS entry for your static IP, you would just do...
slogini ec2-user@dnsentry.example.com
Yes.
ec2-<public ip with dash instead of period>.compute-1.amazonaws.com
Unless you have arranged for a PTR (reverse IP) dns entry to be setup (which you need if you're sending mail).
If you're not sending mail, then there's no real need for a PTR dns entry.
david
ec2-<public ip with dash instead of period>.compute-1.amazonaws.com
isn't working when trying to log into terminal via SSH!
the static-ip is working but not the public_dns_name.
I'm using a debian-instance!
Cheers!
Edited by: tendouser on Feb 8, 2019 4:33 PM
Relevant content
- asked 5 years ago
- asked 3 years ago
From https://docs.aws.amazon.com/vpc/latest/userguide/vpc-dns.html#vpc-dns-hostnames noting that there's regional differences in the instance's public DNS name.
A public (external) IPv4 DNS hostname takes the form ec2-public-ipv4-address.compute-1.amazonaws.com for the us-east-1 Region, and ec2-public-ipv4-address.region.compute.amazonaws.com for other Regions.