EFA 5.0 Install script and AWS connectivity issue

[cordeos]

We are setting up an experimental project with two linked/sync'd EFA 5.0 machines - one on-premise and the other in AWS. On premise works ok, but it seems the standard EFA setup causes issues with AWS SSH connectivity. Likely due to the creation of new login accounts and SSH keys. We also had the same problem with our on-premise installation. Since we already have an entire server setup and hardening process, it would be nice if the EFA5.0 installer had a "Simple" and "Advanced" option choice at the beginning. The advanced would skip any OS-level changes (IP, user, SSH keys, etc).

[cordeos]

This issue is not an issue. Fixed with an update of SSH keys and can access AWS LS/EC2 installations.
Would be nice if there was a cut-down installer or script option which assumes ipv4, ipv6 and shell user (and keys) are already set up outside of the eFa installation process.