How can I configure my local rMC to manage appliances beyond my firewall, like in Amazon EC2?
By setting up a target for Amazon EC2 in rMC, your local rBuilder can upload, launch, and manage your appliance in Amazon EC2. This is the target setup described in Section 2.3, “Set Up a Target for rBuilder”. But, there is one catch: appliance updates By default, your deployed appliances check their original rBuilder repository for updates. The network address for that repository is taken from the first part of the label on which your appliance is built. For example, if your rBuilder is at rb.example.com, and your appliance (with a unique name of app) was generated from the label app.rb.example.com@corp:devel-1, then your deployed appliances will look for updates at the network address app.rb.example.com. Because of DNS rules about resolving network addresses like this, the appliance may be unable make it past your firewall to find the repository.
