This repository is dedicated to demonstration purpose for boundary.
Disclaimer: The repository is here for demonstration purpose. Meaning: No best practice and a lot of review.
For the demonstration, we will based on AWS deployment EC2 single node.
This our boundary stack. Take a look below to have more information on the Terraform stack.
Run this command : $ terraform apply
When your terraform stack is deploy, do the following steps:
- Get the
boundary endpoint
: Go to the Terraform output and grab theboundary_endpoint
. This is the endpoint to our Boundary. You can also retrieve this output with the following Terraform command:terraform output -raw boundary_endpoint
- Get the
boundary password
: Go to AWS management console, in the EC2 service, select your EC2 instance (e.g. boundary-dev) then click on the button Actions-> Monitor and troubleshoot-> Get system log. Find for " Password: " and grab the password. - Put the URL into your web browser.
- The username is
admin
and the password is theboundary_password
you get in the step 2.
The AWS system log take around 5min to be available.
Well done. You can now use Boundary.
If you want to try with a Postgresql target, follow the README.md.
You can also test the HashiCorp Learn - Boundary getting start.
Run this command : $ terraform destroy
You see something wrong ? You want extra information or more ?
Contact me: [email protected]
Name | Version |
---|---|
terraform | >= 1.0 |
aws | ~> 3.50 |
Name | Version |
---|---|
aws | 3.63.0 |
random | 3.1.0 |
template | 2.2.0 |
No modules.
Name | Type |
---|---|
aws_autoscaling_group.instance | resource |
aws_db_instance.boundary | resource |
aws_db_subnet_group.boundary | resource |
aws_iam_instance_profile.session_manager | resource |
aws_iam_role.session_manager | resource |
aws_iam_role_policy.boundary | resource |
aws_iam_role_policy_attachment.session_manager | resource |
aws_internet_gateway.gw | resource |
aws_kms_key.recovery | resource |
aws_kms_key.root | resource |
aws_kms_key.worker | resource |
aws_launch_template.instance | resource |
aws_route_table.public | resource |
aws_route_table_association.public | resource |
aws_security_group.db | resource |
aws_security_group.instance | resource |
aws_security_group_rule.allow_controller_sg | resource |
aws_subnet.private | resource |
aws_subnet.public | resource |
aws_vpc.boundary | resource |
random_password.db_master_pass | resource |
aws_ami.amazon_latest | data source |
aws_availability_zones.available | data source |
aws_iam_policy_document.instance-assume-role-policy | data source |
aws_instance.boundary | data source |
template_file.boundary_install | data source |
Name | Description | Type | Default | Required |
---|---|---|---|---|
app | Your application name. | string |
"boundary" |
no |
db_instance_class | The database instance size & type. | string |
"db.t2.micro" |
no |
db_name | The database name. | string |
"boundary" |
no |
db_storage | The database storage in GB. | number |
20 |
no |
db_username | The admin username for the database. | string |
"boundary" |
no |
env | Environment variable for the application. | string |
"dev" |
no |
instance_type | The EC2 instance size and type. | string |
"t3.small" |
no |
owner | The owner of the application or the owner of the deployed stack. | string |
"Terraform" |
no |
region | n/a | string |
"eu-west-1" |
no |
vpc_cidr | The CIDR to use for the VPC. | string |
"10.0.0.0/16" |
no |
Name | Description |
---|---|
ami_version_id | n/a |
boundary_endpoint | n/a |
subnets_private | n/a |
vpc_id | n/a |