hashicorp/boundary-reference-architecture

View on GitHub

Example reference architecture for a high availability Boundary deployment on AWS.

Stars: 217
Forks: 105
Open beginner issues: 0
Indexed issues: 19

Dominant language: HCL
License: MPL-2.0
Last GitHub push: Feb 20, 2026
Latest indexed: Sep 17, 2026
Contributing guide: Contributing guide
Code of conduct: Code of conduct
Beginner labels: No beginner labels indexed
PR merge metrics: No merged PRs in 30d

Open All

19 open issues indexed

Uncertain what to specify in public_cluster_addr for k8s running in private subnet Open

hashicorp/boundary-reference-architecture#35 · 2 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
How to access PostreSQL on AWS Open

question

hashicorp/boundary-reference-architecture#41 · 3 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
terraform plan failure using Azure deployment Open

hashicorp/boundary-reference-architecture#45 · 4 comments · 1 reaction · 0 assignees · Indexed Sep 17, 2026
Fix jq string on Kubernetes Deployment instructions Open

bug

hashicorp/boundary-reference-architecture#51 · 2 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
AWS Deployment doesn't use HTTPS -- Provide warning in the documentation Open

documentation

hashicorp/boundary-reference-architecture#52 · 5 comments · 1 reaction · 0 assignees · Indexed Sep 17, 2026
Why are the NAT gateways in private subnets...? Open

question

hashicorp/boundary-reference-architecture#53 · 1 comment · 1 reaction · 0 assignees · Indexed Sep 17, 2026
Error parsing KMS HCL: At 6:19: Unknown token: 6:19 IDENT file Open

question

hashicorp/boundary-reference-architecture#58 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Azure deployment needs updating. Open

bug

hashicorp/boundary-reference-architecture#73 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Unable to use the GCP reference architecture Open

bug

hashicorp/boundary-reference-architecture#74 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Getting error while following kubernetes deployment document Open

hashicorp/boundary-reference-architecture#76 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
AWS - connection refused error while running terraform apply Open

hashicorp/boundary-reference-architecture#87 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Azure - Unsupported argument Open

hashicorp/boundary-reference-architecture#89 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
EKS deployment failed: Disabling IPC_LOCK, please use --privileged or --cap-add IPC_LOCK Open

hashicorp/boundary-reference-architecture#90 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 17, 2026
AWS "host_set_ids" is not expected here Open

hashicorp/boundary-reference-architecture#91 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Error while following the boundary-reference-architecture/deployment/docker_cts/compose/cts/sync-tasks/boundary/ Open

triage

hashicorp/boundary-reference-architecture#93 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
AWS Deploy - terraform apply error - Invalid Configuration for Read-Only Attribute Open

hashicorp/boundary-reference-architecture#96 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Is this repository still considered to follow best practices? Open

hashicorp/boundary-reference-architecture#102 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Investigate TLS Open

hashicorp/boundary-reference-architecture#107 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Security Groups open to 0.0.0.0 Open

hashicorp/boundary-reference-architecture#108 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

hashicorp/boundary-reference-architecture

Get new issues in your inbox