Forum Discussion

ibardarov's avatar
ibardarov
Data Storage
03-07-2023

How to move self hosted sisense on a single ec2 behind ALB?

Hello,

What are the steps to move Sisense behind an AWS ALB?

In the config I have

 

k8s_nodes:
 - { node: NODENAME, internal_ip: "10.102.20.166", external_ip: "4.5.6.7" }

 

I didn't restart sisense or re-installed it. Only added from single_config.yaml:application_dns_name
into Admin / Trusted Servers

I thought it would be enough to detach the IP from the ec2 instance, but I start having timeout outs when trying to access the dashboards.

 

POST  
scheme https
host hostname.devqa.com
filename /api/datasources/Bookings/jaql
 
Address

1.2.3.4:443
Status
504
Gateway Timeout
VersionHTTP/2
Transferred285 B (132 B size)
Referrer Policystrict-origin

I also tried to remove the external IP, but sisense doesn't allow empty external IP

single_config.yaml:

k8s_nodes:
 - { node: NODENAME, internal_ip: "10.102.20.166" }


$./sisense.sh single_config.yaml
Preparing System ...
Linux user: ec2-user
Validating Sudo permissions for user ec2-user ...
User ec2-user has sufficient sudo permissions
Detecting Host OS  ...
OS: Red Hat Enterprise Linux, Version: 8.3
Validating OS and its version
Can proceed with RKE process ...
Validating that namespace name is all lower case ...
Enter the password for user ec2-user and press [ENTER]: 
Using password for Ansible Installation ...
Verifying Python packages exist ...

Wrong syntax was found at : {"node":"NODENAME","internal_ip":"10.102.20.166"}
Please verify the following:
- external_ip: "null" must follow IPv4 structure x.x.x.x or be different from 127.0.0.0 and 0.0.0.0

Why I see timeout on 1.2.3.4:443  instead of 4.5.6.7 ?

But when I re-attached the 4.5.6.7 to the ec2 sisense everything works.

 

Linux

1 Reply

Replies have been turned off for this discussion
  • ibardarov's avatar
    ibardarov
    Data Storage
    03-15-2023

    We done it by setting internal and external IP the same. also the hostname.

    ## Uninstall the Sisense

    Change in the configuration

    uninstall_cluster: true
    uninstall_sisense: true

    ## Configure now ssl

    Change in the configuration

    k8s_nodes:
    - { node: hostname, internal_ip: "INTERNAL_IP", external_ip: "INTERNAL_IP" }

    Additionally to remove the ssl from sisense ec2 we did

    is_ssl: false
    ssl_key_path: ""
    ssl_cer_path: ""
    uninstall_cluster: false
    uninstall_sisense: false
     
    # Setup the ALB

    The listener should forward to the new instance on HTTP port 30845

    The healtchecks

    health_check {
    port = 30845
    protocol = "HTTP"
    matcher = "200,404"
    }