AWS EC2 server disappear after provisioning

How long after you provision did it disappear? Does this happen every time?

I gave it a new try with the same result today. It is removed from forge when the "building" is done. But the server is up and running in EC2 so I guess there are no errors on Amazons side.

How do you do when setting up an EC2? I'm using my Access Key ID and the Secret Access Key, obv it is working enough to create the server, but not to keep it in forge?

I guess it was a misunderstanding of VPC from me. When I choose "Create New" instead of using the default one forge seems to get access to the server it created and the provisioning went just fine.

I am having the same problem. I have tried both "create new" vpc and used existing. Any idea whats wrong?

Solved the problem when creating via VPS in forge istead.

I'm still having this issue. Not sure if we gave it the wrong policy? I messaged support for help, but found this hear with no solid answer. Anyone?

If using the default VPC, the default security group is applied. That security group may not have port 22/ssh enabled. That was my issue (creating a new VPC would create a new security group that would allow ssh).

So if creating a new VPC isn't ideal (I prefer not to have a ton of VPCs when not needed), try opening port 22 for the default security group.

Had this issue lately, the problem for me was missing to add the internet gateway of the VPC to the subnet Route Table on AWS

This was happening to me as well. I was using the default VPC which was using the default security group and it seems that the security group only accepts traffic coming from another resource with the same security group applied to it.

I've updated the rules in the SG allowing incoming traffic from anywhere and it worked.

I hope this helps someone else with the same problem.