Current AMI: ami-08d090f841c8435e9
If I spin this ami up in AWS Console with the same InstanceProfile and SecurityGroup settings I can access fine via SSH or session_manager.
If I spin this ami up in packer with t2.large (it won’t connect at all) - times out (ssh or session_manager)
If I spin this ami up in packer with t3.large (it will show connection accepted over session_manager but then timeout) If I try to manually connect via SSM I can get in.
Not sure why changing the instance type would have any affect on this. I can use the same instance types in AWS Console and no issue. I’ve had ena_support = true and false but no difference.