has anyone experienced an issue with a fully manually created ECS Cluster where the instance during it's creation does not have network access, but does later on ? I went through every bit of my config:
• Security Group allow eggress anywhere
• the instance is in the private subnet, which routing table for outbound traffic points to the NAT
• The NAT Gateway is in public subnet
• the pub subnet does have an IG
Additionally I created a jumbox and while the stack fails to create (no network so no cfn-signal installed by cloud-init and sent to Cloud formation for the autoscaling group). Once the instance is up, and without changing anything I log in to that specific and can successfully reach internet... confirming that the setup is right.
I am thinking that the instance comes up before the NAT is attached or a specific rule added to routing table or Security group. Any pointer would be welcomed