Help Naming a Puppet Enterprise Server on AWS - Bounty

24 views
Skip to first unread message

Gil Motta

unread,
Apr 4, 2019, 12:12:41 PM4/4/19
to Puppet Users
Hello All,

I am a beginner with PE.

I created an Ubuntu 18.04 VM on Amazon AWS.

I have the public IP address as 54.100.1.200 and the public name as ec2-54-100-1-200.compute-1.amazonaws.com

I have the local server name as 'ip-172-26-6-65.ec2.internal'

from a remote location, I tried connecting to the console so I typed:


and every time it gets redirected to: 


and then an error.

this 'ip-172-26-6-65.ec2.internal' cannot be resolved as it is not on the Internet. It is NOT public.

I need help telling the PE to use the Static IP 54.100.1.200 when redirecting so it looks like https://54.100.1.200


but I don't have a clue how to do this.

I also would like to include an alt DNS name as NH.cargohold.net as I own that domain.

So I can later tell my agents to use either the AWS name or my NH.cargohold.net.

I have been struggling with PE for 5 days, the add said it would be done in 20 minutes but PE is not plug and play.

I will give you some BTC or LTC for helping me with this and successfully connecting my two remote agents as a template.

If you send an email please mention PUPPET in the subject.

Thanks a lot,
Gil Motta


martin...@puppet.com

unread,
Apr 6, 2019, 7:32:14 PM4/6/19
to Puppet Users
HI Gil.

The default behaviour of PE when attempting to access the console on Port 80 (http) is to redirect to port 443 (https) the reason for this is the Puppet console does not actually serve on Port 80, part of this is the built in NGINX instance rewrites the URL.
To avoid this you could go directly to  https://54.100.1.200

Or you can reconfigure the rewrite url  


or disable the redirect entirely: so you must fo to HTTPS:


Do you have an active PE licence? if so you can reach out to Puppet Support for this sort of thing.

Thanks
Reply all
Reply to author
Forward
0 new messages