Trying to run the boundary-reference-architecture deployment for aws, and I’ve been struggling for days.
- I guess I was supposed to know how to configure my
~/.aws/credentialsfile, but I didn’t. I work with multiple aws instances and terraform wasn’t hitting the one I wanted. If there is documentation about getting that right, I haven’t seen it. I got that working but wasted a lot of time getting there.
- I had a problem with line endings when I cloned the repo to my Windows 10 machine (detailed here). Again, it’s good now but took a while.
- I was using the Windows
boundary.exefile instead of the Linux binary (that same issue actually came up in the thread mentioned above, but of course I only found that thread after solving it myself).
terraform apply -target module.awscompletes, I get an error that the ACM Certificate is valid in the future. It also fails to create the Load Balancer, but I assume that is because of the certificate failure. Re-running
terraform applysolves both of those.
So now it completes successfully, but it doesn’t look like everything worked. The
boundary-controller service is up and running (although the output from the
install.sh script reported an
Unable to capture a lock on the database error, does that matter?). The
boundary-worker service does not exist, even though I can see the output from it installing and there are no errors in that. If I try to manually run the install script (via ssh), I get an error, but it at least creates the service.
ubuntu@ip-x-x-x-x:~$ sudo systemctl status boundary-worker Unit boundary-worker.service could not be found. ubuntu@ip-x-x-x-x:~$ sudo ~/./install.sh worker The system user `boundary' already exists. Exiting. chown: cannot access '/etc/boundary-worker.hcl': No such file or directory Created symlink /etc/systemd/system/multi-user.target.wants/boundary-worker.service → /etc/systemd/system/boundary-worker.service. ubuntu@ip-x-x-x-x:~$ sudo systemctl status boundary-worker ● boundary-worker.service - boundary worker Loaded: loaded (/etc/systemd/system/boundary-worker.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2021-09-13 18:01:07 UTC; 16s ago Process: 2795 ExecStart=/usr/local/bin/boundary server -config /etc/boundary-worker.hcl (code=exited, status=3) Main PID: 2795 (code=exited, status=3) Sep 13 18:01:07 ip-x-x-x-x systemd: Started boundary worker. Sep 13 18:01:07 ip-x-x-x-x boundary: Error parsing config file: open /etc/boundary-worker.hcl: no such file or directory Sep 13 18:01:07 ip-x-x-x-x systemd: boundary-worker.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED Sep 13 18:01:07 ip-x-x-x-x systemd: boundary-worker.service: Failed with result 'exit-code'.
I’m all out of ideas here. Can anyone help me?