Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Currently customer's IT-security will not allow this product to be deployed inside their firewall to manage systems at Amazon: 

    Having systems connect back to inside their perimeter security is usually seen as breach of the security architecture. 

    A VPN actually makes it worse, because it moves the perimeter security to the cloud resource provider. 

This prohibits all major use-cases. Purely on-premise use-cases using RHEVM and/or VMWare may be feasible, but in my opinion for this case the RHEV-M user portal and Satellite/cobbler are more usable for now. Also, it leads to increased cost from a data transfer standpoint if data is not local within the provider.

This is a request to move to an architecture that allows update and entitlement of systems to occur in the cloud resource provider and have federation of the data into the on-premise system in a secure manner.

Due to the age of this BZ it is not currently scheduled for implementation. If there is more info for the feature and continued customer need, please reopen. Associating with customer cases will also help in prioritization.
Thank you