Amazon web services Can'；t使用PuTTY连接到Amazon EC2实例

我已经能够使用免费层连接到Amazon Web Services EC2，并使用它运行

R

程序。现在，我尝试使用一个带有Spot请求的实例。实例已创建并正在运行，两个状态检查都正常。但是，

PuTTY

将无法连接

PuTTY

仍将使用相同的步骤和相同的

密钥对连接到自由实例

有人能指出我做错了什么吗？下面是这两个实例的详细信息，如果这些信息可能有用的话。我隐藏了
实例ID
、
IP
、
所有者ID
和
保留
的部分内容，并提供了一个假的
密钥对
名称

以下是我无法使用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

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

下面是我可以使用PuTTY连接到的免费实例的详细描述：

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

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

两个EC2实例上的安全组不同。安全组是一组防火墙规则。您需要允许入站端口22（SSH）连接到spot实例。考虑到两个实例都在同一VPC中，一种简单的方法是将
launch-wizard-5
安全组添加到spot实例中。或者使用一组等效的入口规则创建一个新的安全组，并将其添加到spot实例。
这不是编程问题。