無法使用 PuTTY 連接到 Amazon EC2 實例

Question

我已經能夠使用免費Amazon Web Services EC2連接到Amazon Web Services EC2並使用它運行R程序。 現在我正在嘗試使用帶有 Spot 請求的實例。 實例已創建並正在運行，並且兩個狀態檢查都正常。 但是， PuTTY不會連接。 PuTTY仍將使用相同的步驟和相同的key pair連接到免費實例。

誰能建議我做錯了什么？ 如果此信息可能有用，這里是這兩個實例的詳細信息。 我隱藏了Instance IDs 、 IPs 、 Owner ID和Reservations ，並提供了一個假key pair名稱。

以下是我無法使用PuTTY連接的 Spot 實例的描述詳細信息：

Instance ID: i-XXXXXa30498b1b9ca
Public DNS (IPv4): ec2-XX-XXX-XXX-XXX.us-east-2.compute.amazonaws.com
Instance state: running
IPv4 Public IP: XX.XXX.XXX.XXX
Instance type: r4.xlarge
IPv6 IPs: -
Elastic IPs:
Private DNS: ip-XXX-XX-XX-XX.us-east-2.compute.internal
Availability zone: us-east-2b
Private IPs: XXX.XX.XX.XX
Security groups: default. view inbound rules. view outbound rules
Secondary private IPs
Scheduled events: No scheduled events
VPC ID: vpc-ce0c17a6
AMI ID: ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20191002 (ami-0d5d9d301c853a04a)
Subnet ID: subnet-b3f881c9
Platform: -
Network interfaces: eth0
IAM role: -
Source/dest. Check: True
Key pair name: mykeyb
T2/T3 Unlimited: -
Owner: XXXXXXXXXXXX
EBS-optimized: False
Launch time: November 26, 2019 at 5:43:37 PM UTC-5 (1 hour)
Root device type: ebs
Termination protection: False
Root device: /dev/sda1
Lifecycle: spot
Block devices: /dev/sda1
Monitoring: basic
Elastic Graphics ID: -
Alarm status: None
Elastic Inference accelerator ID: -
Kernel ID: -
Capacity Reservation: -
RAM disk ID: -
Capacity Reservation Settings: Open
Placement group: -
Partition number: -
Virtualization: hvm
Reservation: r-XaecaXXbfXacXXXXX
AMI launch index: 0
Tenancy: default
Host ID: -
Affinity: -
State transition reason: -
State transition reason message: -
Stop - Hibernation behavior: Disabled
Number of vCPUs: 4

以下是我可以使用PuTTY連接的免費實例的描述詳細信息：

Instance ID: i-ZZdZZZZZ41cZZZZZZ
Public DNS (IPv4): ec2-X-XXX-XXX-XX.us-east-2.compute.amazonaws.com
Instance state: running
IPv4 Public IP: X.XXX.XXX.XX
Instance type: t2.micro
IPv6 IPs: -
Elastic IPs:
Private DNS: ip-XXX-XX-XX-XXX.us-east-2.compute.internal
Availability zone: us-east-2b
Private IPs: XXX.XX.XX.XXX
Security groups: launch-wizard-5. view inbound rules. view outbound rules
Secondary private IPs:
Scheduled events: No scheduled events
VPC ID: vpc-ce0c17a6
AMI ID: ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20191002 (ami-0d5d9d301c853a04a)
Subnet ID: subnet-b3f881c9
Platform: -
Network interfaces: eth0
IAM role: -
Source/dest. check: True
Key pair name: mykeyb
T2/T3 Unlimited: Disabled
Owner: XXXXXXXXXXXX
EBS-optimized: False
Launch time: November 22, 2019 at 12:16:56 AM UTC-5 (less than one hour)
Root device type: ebs
Termination protection: False
Root device: /dev/sda1
Lifecycle: normal
Block devices: /dev/sda1
Monitoring: basic
Elastic Graphics ID: -
Alarm status: None
Elastic Inference accelerator ID: -
Kernel ID: -
Capacity Reservation: -
RAM disk ID: -
Capacity Reservation Settings: Open
Placement group: -
Partition number: -
Virtualization: hvm
Reservation: r-XXaXXXdfXXXXfXXXX
AMI launch index: 0
Tenancy: default
Host ID: -
Affinity: -
State transition reason: -
State transition reason message: -
Stop - Hibernation behavior: Disabled
Number of vCPUs: 1

Answer 1

您的兩個 EC2 實例上的安全組不同。 安全組是防火牆規則集。 您需要允許 Spot 實例的入站端口 22 (SSH)。 考慮到兩個實例位於同一 VPC 中，您可以執行此操作的一種簡單方法是將launch-wizard-5安全組添加到 Spot 實例。 或者創建一個具有等效入口規則集的新安全組，並將其添加到 Spot 實例。