Description

• Customer is looking to roll out a strategic multi cloud Ansible Automation Platform with an automation mesh spanning AWS, Azure and On Premise Hosting. They have security constraints which limit their ability to allow SSH traffic to pass through their cloud interconnects and thus wish to use remotely installed/managed mesh nodes.
• Their thought process follows the upstream AWX documentation here - https://github.com/ansible/awx/blob/devel/docs/execution_nodes.md

Customer Explanation

• In conversations with RedHat, it was advised this is only available in the OpenShift deployment of AAP. We do not have approval nor the platform to deploy onto OpenShift and thus plan to deploy a controller stack in AWS. We are missing this feature and we may struggle to meet our requirement for a multi cloud strategic solution without this feature being enabled.

Define the value or impact to you or the business

• We will not be able to roll out a multi cloud, private and public, Ansible Automation Platform and thus may have to deploy multiple versions of AAP in each cloud environment. This will dramatically reduce the value of the proposition we are offering to the DWP as the main driver behind our rollout is multi cloud management of services. We will struggle to get the buy in without this solution.