Daniel Lipovetsky

We would not need to interpose cloud-init, if the user-data did not contain the sensitive data (bootstrap token). See https://github.com/kubernetes-sigs/cluster-api/issues/5294 and https://github.com/kubernetes-sigs/cluster-api/issues/9631

/triage accepted /priority important-soon

> Imagine before we supported say EFA networking, if a user wanted to use that, what would stop them building and adding their own EC2 instances to the workload cluster?...

Also from office hours discussion: Users define Pod Disruption Budgets to ensure that their Pods are not _voluntarily_ deleted. A scale-in of a MachinePool, if it uses the "providers refresh",...

/triage accepted /priority important-soon

This change must be validated e2e. I've already tested it using my own AWS account, so I'm confident it will pass e2e. /test pull-cluster-api-provider-aws-e2e

/cc @randomvariable You know this area. Tagging you, in case you have questions/concerns about this change.

I'd like to backport this to supported release branches, too.

/retest

Last e2e failure was due to reaching EventBridge resource quota. From the [manager log](https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api-provider-aws/4746/pull-cluster-api-provider-aws-e2e/1754115651997274112/artifacts/clusters/bootstrap/controllers/capa-controller-manager/capa-controller-manager-6b8f8b488c-bft66/manager.log): ``` E0204 12:33:36.396548 1 awscluster_controller.go:309] "non-fatal: failed to set up EventBridge" err="unable to create rule: LimitExceededException:...