<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:10px"><div id="yui_3_16_0_ym19_1_1462251453092_3587"><span>Hi</span></div><div id="yui_3_16_0_ym19_1_1462251453092_3587"><span><br></span></div><div id="yui_3_16_0_ym19_1_1462251453092_3587" dir="ltr"><span id="yui_3_16_0_ym19_1_1462251453092_3815">Please advise on the approach to deploying KC where the Admin GUI and APIs are not exposed.</span></div><div id="yui_3_16_0_ym19_1_1462251453092_3587" dir="ltr"><br></div><div id="yui_3_16_0_ym19_1_1462251453092_3587" dir="ltr">We want to control what is exposed onto the internet and what is available within the organisation.</div><div id="yui_3_16_0_ym19_1_1462251453092_3587" dir="ltr">The flows are exposed but the admin gui / api are only accessible within the organisation.</div><div id="yui_3_16_0_ym19_1_1462251453092_3587" dir="ltr"><br></div><div id="yui_3_16_0_ym19_1_1462251453092_3587" dir="ltr">Currently we're considering filtering at the load balancer essentially whitelisting traffic.</div><div id="yui_3_16_0_ym19_1_1462251453092_3587" dir="ltr">The admin GUI is accessed internally within the organisation.</div><div id="yui_3_16_0_ym19_1_1462251453092_3587" dir="ltr"><br></div><div id="yui_3_16_0_ym19_1_1462251453092_3587" dir="ltr">Alternatively is there a way to config off admin ui & api and only deploy this into production? With the admin deployed internally?</div><div></div><div id="yui_3_16_0_ym19_1_1462251453092_3728"> </div><div class="signature" id="yui_3_16_0_ym19_1_1462251453092_3729">Regards
Tom Connolly.</div></div></body></html>