apply https to my server!!

I don't know what sort of load balancer you're using (Classic, Application, Network) but all of them can be configured with a HTTPS listener. Then you will need a certificate - this can be provided by AWS Certificate Manager as seen in these instructions.

thank you for your answer!! i solve it by changing target group of listener 443 from waiting port 443 to waiting 80 port. it takes too long time for me. target group concepts recently applied.....

You need to create an HTTPS listener to the load balancer to be able to listen to port 443 (https) This document has step by step how to do it https://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-https-listener.html

Hello, SSL transmission terminates at the load balancer, the traffic from the load balancer to the server is usually unencrypted. It can be encrypted if required using certificates.

Could you please check the following

1. If the targets are healthy under Target Group?
2. If the security groups are configured to allow HTTPS to the load balancer?
3. Does it work if we remove HTTPS from the load balancer and allow HTTP in the Security Groups?

It appears that there is no listener/the target is not healthy when we ping arabbit.link

ping arabbit.link
PING arabbit.link (18.218.3.123): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2

DNS seems fine

dig arabbit.link

; <<>> DiG 9.10.6 <<>> arabbit.link
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39787
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;arabbit.link.			IN	A

;; ANSWER SECTION:
arabbit.link.		223	IN	A	18.218.3.123

;; Query time: 8 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Jan 27 20:00:05 AEDT 2022
;; MSG SIZE  rcvd: 57