Description of problem:

In our docs for v4.16 in the sections below pages

https://docs.openshift.com/container-platform/4.16/machine_management/creating-infrastructure-machinesets.html

and 

https://docs.openshift.com/container-platform/4.16/post_installation_configuration/configuring-multi-arch-compute-machines/creating-multi-arch-compute-nodes-aws.html#creating-multi-arch-compute-nodes-aws

Maybe more. I have found that the MachineSet Definition example is referring SecurityGroup Tags that no longer exist. 

Since v4.15 the SecurityGroup that the installer was creating for the nodes was ${Cluster-ID}-${node-role}-sg 

Since v4.16 this is changed and now the installer creates 2 SecurityGroups like below:

${Cluster-ID}-node and ${Cluster-ID}-lb.

This will result in an error that the controller cannot find such SecurityGroups and can be a problem that will result in the newly added MachineSet creation to fail. 

This can cause Support Case increase so i think that it is important to be fixed in the docs and to reflect the below filters:

          securityGroups:
          - filters:
            - name: tag:Name
              values:
              - <infrastructure_id>-node
          - filters:
            - name: tag:Name
              values:
              - <infrastructure_id>-lb

Version-Release number of selected component (if applicable):

v4.16

How reproducible:

Easy

Steps to Reproduce:

    1. Create a new Machine Set following the v4.16 documentation 
    2. Machine Set will fail to deploy with error taht cannot find the Security Group defined
    3.
    

Actual results:

The Machine Set is Failing to be successfully created    

Expected results:

The Machine Set should be successfully created 

Additional info:

Relevant installer code if i understand correctly here:
- v4.15 https://github.com/openshift/installer/blob/release-4.15/pkg/asset/machines/aws/machines.go
- v4.16 https://github.com/openshift/installer/blob/release-4.16/pkg/asset/machines/aws/machines.go