Frustrated attempt to create my first EC2 instance AND connect to it. Launching it with defaults went fine, but connecting kept timing out, and after going through all the troubleshooting it is still timing out. Stopped, for now.
Jeremy Cherfaspublished this
@jack Amen to that!
I went for a default security group and then went through all the checks, so I am at a loss. Will try again when my brain has cooled down.
, Jun 30 2019 on micro.blog
@jeremycherfas Amazon makes the simple things just difficult. The AWS way!
, Jun 30 2019 on micro.blog
@jsanchez True ... But there is also a set and forget aspect to it, once you have it working. At least, that has been my experience with S3. This is the first time I have tried to use EC2.
, Jun 30 2019 on micro.blog
@jeremycherfas that’s totally true, what’s the reason that you want to use EC2? :-)
, Jul 02 2019 on micro.blog
@jsanchez Blindly following a recipe I don’t fully understand. May try again with a later Ubuntu that allows web access too.
, Jul 02 2019 on micro.blog
@jeremycherfas That happens to me sometimes and is usually due to a missing security group rule. I find AWS issues to be mind-bogglingly hard to track down. They write millions of words of documentation but for some reason I can never find the answer I'm looking for.
jack, Jun 30 2019 on micro.blog