Default AWS accounts unusable for KKP?

We created a fresh AWS account to test KKP. After installing KKP 2.23 into it, we started to create the first usercluster, also on AWS, in the same account.

However the nodes never joined the usercluster. We found out that this is because we had not enabled `Assign Public IP` when creating the MachineDeployment via the KKP dashboard. Once we enabled this, new machines could successfully join the cluster.

Our VPC followed the current documentation (i.e. `Enable DNS Hostnames` was enabled).

It's unfortunate that KKP's default settings result in a broken cluster.

Start by reviewing the AWS MachineDeployment settings in the KKP dashboard and the current documentation for Assign Public IP and VPC DNS Hostnames. Reproduce the first usercluster setup described in the issue, then determine whether the documented defaults or the dashboard behavior need correction; done means a fresh AWS account can create a joining usercluster without an undocumented setting.

Written by the indexing model from the issue text.