-
Notifications
You must be signed in to change notification settings - Fork 14
DC3: Procedure/template to add private cert on ALB (instead of AWS CA cert) - requiring .NET keystore addition on orchestrator VM #35
Comments
Ok, the feature request is to give the option to provide the ARN for the private cert hosted in ACM at deploy time (via parameter)? |
More than that I already added a parameter to pass in a private cert ARN that gets put on the ALB |
procedure: moving to private cert https://docs.uipath.com/orchestrator/docs/setting-orchestrator-to-use-a-private-key-certificate get rdp going - one to the orch box, add ssm role, open security groups temp to 0.0.0.0/0 incoming, reboot, run normal ssm cli with instance id c |
getting the certificate exported from AWS biometric:~ michaelobrien$ aws acm export-certificate --certificate-arn arn:aws:acm:us-west-2:453279094200:certificate/59305329-b576-4e1f-9b31-065652912e5c --region=us-west-2 --passphrase fileb://passphrase | jq -r '"(.Certificate)(.CertificateChain)(.PrivateKey)"' An error occurred (ValidationException) when calling the ExportCertificate operation: Certificate ARN: arn:aws:acm:us-west-2:453279094200:certificate/59305329-b576-4e1f-9b31-065652912e5c is not a private certificate todo create a private one - forgot this one is AWS CA signed |
each private CA is US400/month - first 30 days free for this demo aws ssm start-session --target i-0247a7f6436907a96 --document-name AWS-StartPortForwardingSession --parameters "localPortNumber=55678, portNumber=3389" --region us-west-2 machine dns for private cert ip-10-0-41-75.us-west-2.compute.internal |
add uipath procedure to move private cert
do this before
3 drives 2 and 4
The text was updated successfully, but these errors were encountered: