# Custom subdomain on Akto on AWS

[Akto](https://www.akto.io/) creates a load balancer for your akto dashboard. You can put this dashboard behind your organization's subdomain for easier access across teams. Moreover, adding SSL certificate make the dashboard more secure.

## To configure HTTPS and add SSL certificate to akto dashboard load-balancer

1. Navigate to AWS dashboard > EC2 > load balancers and select the akto dashboard load balancer.

<figure><img src="https://2916937215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRc4KTKGprZI2sPWKoaLe%2Fuploads%2Fgit-blob-a9e5222fbf3dea387c5f1115e42ef7cc37fee6e3%2Faws-ssl-1.png?alt=media" alt="Navigate to load balancers and select akto dashboard load balancer"><figcaption></figcaption></figure>

2. Go to `Listeners and rules` and select the `HTTP:80` rule.

<figure><img src="https://2916937215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRc4KTKGprZI2sPWKoaLe%2Fuploads%2Fgit-blob-52bf36e1a98b2d160ee56e238bab08c72b00ff8a%2Faws-ssl-2.png?alt=media" alt="Select HTTP 80 rule"><figcaption></figcaption></figure>

3. Click on `Edit listener`

<figure><img src="https://2916937215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRc4KTKGprZI2sPWKoaLe%2Fuploads%2Fgit-blob-bbdcba19a00bbd403117fc5776c83432c28326c3%2Faws-ssl-3.png?alt=media" alt="Click on edit listener"><figcaption></figcaption></figure>

4. Change protocol from `HTTP` to `HTTPS`.

<figure><img src="https://2916937215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRc4KTKGprZI2sPWKoaLe%2Fuploads%2Fgit-blob-7eec7823966db158d98710fdaa3b2aaceb850b6c%2Faws-ssl-4.png?alt=media" alt="Change protocol to HTTPS"><figcaption></figcaption></figure>

5. Add your SSL certificate to the listener.

<figure><img src="https://2916937215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRc4KTKGprZI2sPWKoaLe%2Fuploads%2Fgit-blob-07267a817eeccb101fb7467e3c1316ba816d168d%2Faws-ssl-5.png?alt=media" alt="Add SSL cert"><figcaption></figcaption></figure>

6. Click on save changes. The protocol should be changed by this. To make it reachable by the load balancer we would edit its security group.

<figure><img src="https://2916937215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRc4KTKGprZI2sPWKoaLe%2Fuploads%2Fgit-blob-af83821b6a1d863cc042f606125bed57af38c39f%2Faws-ssl-6.png?alt=media" alt="Save changes"><figcaption></figcaption></figure>

7. On the same page, click on security and click on the associated security group.

<figure><img src="https://2916937215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRc4KTKGprZI2sPWKoaLe%2Fuploads%2Fgit-blob-e7e0c01685ef5a40a44178a47e4d320a0998aa50%2Faws-ssl-7.png?alt=media" alt="Go to the associated security group"><figcaption></figcaption></figure>

8. Click on edit inbound rules.

<figure><img src="https://2916937215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRc4KTKGprZI2sPWKoaLe%2Fuploads%2Fgit-blob-cc7e9b5599c686fc544b6f653e56410f1df3a037%2Faws-ssl-8.png?alt=media&#x26;token=dd77b76b-cff9-4c54-9796-19f1f9e7f94e" alt="Edit inbound rules"><figcaption></figcaption></figure>

9. Change the type of protocol from HTTP to HTTPS and save the inbound rule of the security group.

<figure><img src="https://2916937215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRc4KTKGprZI2sPWKoaLe%2Fuploads%2Fgit-blob-b23084da172262f8b4b5795093537cd2ebe6025a%2Faws-ssl-9.png?alt=media&#x26;token=43c5bb0f-7808-40a8-a97b-d05e8efedb8c" alt="Set type to HTTPS"><figcaption></figcaption></figure>

10. You should now be able to access akto dashboard's load-balancer IP on HTTPS and it should give an invalid SSL certificate error, because the certificate belongs to your organization and would have been mapped to your organization's domain name.

<figure><img src="https://2916937215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRc4KTKGprZI2sPWKoaLe%2Fuploads%2Fgit-blob-6e3b4599828b0d7aab590fa40851906136a46172%2Faws-ssl-10.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2916937215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRc4KTKGprZI2sPWKoaLe%2Fuploads%2Fgit-blob-7fe321dceaf590e7e22d838a70b180ce936d92ed%2Faws-ssl-11.png?alt=media" alt=""><figcaption></figcaption></figure>

## To configure custom subdomain for akto dashboard load-balancer

1. Navigate to Route 53 on the AWS dashboard. Go to hosted zones.

<figure><img src="https://2916937215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRc4KTKGprZI2sPWKoaLe%2Fuploads%2Fgit-blob-be16eb6d3300ed4218f2eeca9be937df1ddcd0bf%2Faws-ssl-12.png?alt=media" alt="Go to route 53"><figcaption></figcaption></figure>

2. Select the hosted zone in which you want to route akto dashboard and click on create record.

<figure><img src="https://2916937215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRc4KTKGprZI2sPWKoaLe%2Fuploads%2Fgit-blob-c2b6b1789c3badbc5eb4e80bbee3a177278eaad1%2Faws-ssl-13.png?alt=media" alt="Create a new record in a hosted zone"><figcaption></figcaption></figure>

3. Select the record name as `akto` and record type as `A - Routes traffic to an IPv4 address and some AWS resources`. Then toggle the alias button.

<figure><img src="https://2916937215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRc4KTKGprZI2sPWKoaLe%2Fuploads%2Fgit-blob-3f4fee1397fe624b83c7b0470ddac78ae6b73d94%2Faws-ssl-14.png?alt=media&#x26;token=de81de68-49a3-483e-8cec-f7f6a7529886" alt=""><figcaption></figcaption></figure>

4. Select on `Application and classic load balancer` in the endpoints menu.

<figure><img src="https://2916937215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRc4KTKGprZI2sPWKoaLe%2Fuploads%2Fgit-blob-3fdc44b57896f1ae4cac95b5d88ea3359439d637%2Faws-ssl-15.png?alt=media&#x26;token=16bfd272-1938-4a99-8418-2c3bc9c13ce3" alt="Select on application and classic load balancer"><figcaption></figcaption></figure>

5. Select the region in which the load balancer is deployed.

<figure><img src="https://2916937215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRc4KTKGprZI2sPWKoaLe%2Fuploads%2Fgit-blob-fe1a265575c1eca36e42b451e189af536380b60b%2Faws-ssl-16.png?alt=media" alt="Select region"><figcaption></figcaption></figure>

6. Choose akto dashboard's load balancer in the menu and click on `Create records`.

<figure><img src="https://2916937215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRc4KTKGprZI2sPWKoaLe%2Fuploads%2Fgit-blob-5020c99bc997282bd287ae7d7177c28ae9ef1429%2Faws-ssl-17.png?alt=media&#x26;token=bf9913a2-aa6e-4a78-9483-baee2f166ec1" alt="choose your LB and create records"><figcaption></figcaption></figure>

Now, you have added a custom subdomain and SSL certificate to your akto deployment on AWS.
