The framepkg.exe runs under your account if you do a manual install locally, there is also a package where you can add credentials to your package. It contains the name and ip of the server to report to as well as the required encryption keys to communicate.
Once the package is installed you should be able to look at the logs in your programdata\mcafee\common framework\db or start cmdagent -s from c:\program files\mcafee\common framework
It should shed some light onto what is happening during communication.
Maybe you should also have an Agent Handler at the EC2 so you can see it through internet by its public IP address (configured under Agent Handler settings in ePO) and so all your computers should see it through WAN
ePO is touchy about its name and IP address. Specifically you shouldn't change them after ePO is installed. However, if you run into an issue where you have a different internal vs. external name then that should be easily addressed with the Agent Handler properties:
Just insert the needed name or address of the ePO server.
As far as becoming an MSP, you can easily do this. The only issue you have is with figuring out who has what machine. The easy method is to create a tag for each domain in use. The agent pulls the domain properties and then you can process those into a tag like this:
Then you apply that tag to a sort field so that machines will automatically fall into the correct groups:
As you can probably tell, I already do this for my computers. The only issue is for non-domain computers. You'll need to find another property to use in order to sort them into the right container.
moved to EPO group for better visibility.