3 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Sorry for the delay. This problem was solved immediately by deleting the virtual machine. By mistake I had created an OS linux aws with pytorch nvidia pre-installed on a micro instance. So I think the admin had blocked me.
beantwortet vor einem Monat
0
I initially created groups for the virtual machine. Then I assigned the standard group. I deleted the old groups. Maybe something went wrong. Now I see that the VM has been deleted, and so has the associated flexible IP. I'll try again but I won't use public IPs. Thank you
beantwortet vor 2 Monaten
0
Is there a security group associated with the EC2 instance that allows inbound ICMP ? https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/security-group-rules-reference.html#sg-rules-ping
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 7 Monaten
Ensure you are in the correct region, as the EC2 wouldn't be deleted without your knowledge. Releasing an Elastic IP is also a manual process.
If the new EC2 is provisioned without a public IP then it won't be accessible from outside the VPC, unless something like VPN or Direct Connect is in place.