hashicorp / hashicorp/boundary-reference-architecture
AWS - connection refused error while running terraform apply
- Dominant language
- HCL
- Stars
- 217
- Forks
- 105
- PR merge metrics
- No merged PRs in 30d
Description
I have followed the steps in the Readme file for deploying to AWS. After performing the last step "terraform apply", I am encountering the below error. I tried to debug this and resolve it but was unable to find any solution. Please help.
│ Error: error calling read scope: error performing client request during Read call: Get http://DNS:9200/v1/scopes/global: dial tcp :9200: connect: connection refused
│
│ with module.boundary.boundary_scope.global,
│ on boundary/scopes.tf line 1, in resource "boundary_scope" "global":
│ 1: resource "boundary_scope" "global" {
Contributor guide
Research direction
Start with the AWS deployment steps in the README and the failing terraform apply output. Inspect boundary/scopes.tf, especially the boundary_scope.global resource and its configured endpoint, then reproduce the connection-refused error. Done means terraform apply can read the global scope without the refused connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, terraform
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100