So, we have a Splunk Enterprise running on an ec2 instance and we want to ssl secure the splunk web url. So for this we first got a name domain (eg."name.domain.com" ) from aws route53 and then got an aws ssl certificate for this domain. Next, we created a load balancer with a target group(target-1) HTTP at port 80 to the ec2 instance. And a second target group(target-2) HTTPS at port 443 to the same ec2 instance but without the load balancer. Then, we have two listeners to the load balancer:
1. HTTPS 443 listener with the aws ssl certificate that we got from aws. This listener is forwarding to the target group target-1
With these changes and modifications , when I type url "https://name.domain.com" on the web browser it opens the apache test page and the page is secured 🙂 . But when I type https://name.domain.com:8000 to open splunk web, it shows in browser " This site cant provide a secure connection". 😞
I think the problem is that, in the apache config files it cannot locate the SSLCertificateFile as I just provided the domain.name.crt there thinking it will somehow get the ssl crt and key files from the browser but it doesnt. Maybe , I have to put manually the ssl files in the specified locations. But, for aws created ssl certificates there is no way to export the .crt and .key files for ssl. So, what do I use for the fields SSLCertificateFile and SSLCertificatekey in the apache config files???? Please help????