# Can the endpoint URL be separated from the admin console for security?

**URL:** <https://forum.openreplay.com/t/can-the-endpoint-url-be-separated-from-the-admin-console-for-security/86>\
**Category:** 🛠️ Deployment\
**Tags:** session-replay, deployment\
**Created:** [April 19, 2024, 9:53am UTC](https://forum.openreplay.com/t/can-the-endpoint-url-be-separated-from-the-admin-console-for-security/86 "2024-04-19T09:53:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![brenbrend](https://avatars.discourse-cdn.com/v4/letter/b/97f17d/32.png) [@brenbrend](https://forum.openreplay.com/u/brenbrend)\
**Post date:** [April 19, 2024, 9:53am UTC](https://forum.openreplay.com/t/can-the-endpoint-url-be-separated-from-the-admin-console-for-security/86/1 "2024-04-19T09:53:20Z")

</div>

We want to set up OpenReplay in AWS where our SaaS product streams events to a public endpoint, but the admin console for session replay is secured behind a VPC.

However it seems the default deployment on EC2 in AWS results in a single URL [https://openreplay](https://openreplay).[mydomain].com for both the events endpoint and the admin console.

How could I secure the admin console separately to the events endpoint? eg.

[https://openreplay-events](https://openreplay-events).[mydomain].com  
[https://openreplay-admin](https://openreplay-admin).[mydomain].com (must be on VPN to access)

?

If that’s not possible then how could I secure the events URL in the gateway without exposing the admin console to the public? eg.

[https://openreplay](https://openreplay).[mydomain].com/post-events → routed via public gateway  
[https://openreplay](https://openreplay).[mydomain].com/\* → accessible on VPN

---

<div class="post-metadata">

**Author:** ![rajesh](https://avatars.discourse-cdn.com/v4/letter/r/8e7dd6/32.png) [@rajesh](https://forum.openreplay.com/u/rajesh)\
**Post date:** [April 21, 2024, 4:03am UTC](https://forum.openreplay.com/t/can-the-endpoint-url-be-separated-from-the-admin-console-for-security/86/2 "2024-04-21T04:03:21Z")

</div>

You should be able to do blacklist the openreplay endpoint using following

```auto
openreplay -e

```

```auto
frontend:
  ingress:
    annotations:
      nginx.ingress.kubernetes.io/whitelist-source-range: 49.36.X.X/32

```