https://github.com/lynkerintel/lcsb-bootstrap-old

Bootstrap for Lynker Cloud Sandbox

https://github.com/lynkerintel/lcsb-bootstrap-old

Science Score: 13.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
  • DOI references
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (9.7%) to scientific vocabulary
Last synced: 4 months ago · JSON representation

Repository

Bootstrap for Lynker Cloud Sandbox

Basic Info
  • Host: GitHub
  • Owner: LynkerIntel
  • Language: HCL
  • Default Branch: develop
  • Size: 27.3 KB
Statistics
  • Stars: 0
  • Watchers: 4
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Created 12 months ago · Last pushed 11 months ago
Metadata Files
Readme

README.md

lcsb-boostrap

Repo for bootstrapping Lynker's Cloud Sandbox Parity Account

This project - sets up an S3 bucket with a specific bucket policy using Terraform - creates DynamoDB for state locking. This is always named "{var.environment}-terraform-state-lock

For the LCSB it also:

  • builds a VPC that tries to conform to the target environment while being independent enough to allow work to be done freely.

Requirements

  • Terraform installed on your machine. OpenTofu works.
  • AWS account with appropriate permissions

Setup Instructions

  1. Clone the repository: git clone <repository-url> lcsb-bootstrap cd lcsb-bootstrap

  2. Initialize Terraform: terraform init

  3. Configure variables: Update the variables.tf file with your desired bucket name, AWS account ID, and role ARNs or create a lcsb.tfvars

Configurable items are:

  • owner for who gets to destroy this, if desired
  • region for the AWS region to use
  • environment for the name of this target environment
  • bucket_name which must often be overridden unless you use_env_in_bucket_name
  • use_env_in_bucket_name if you want the environment name to be prepended to the state bucket name
  • role_name_regex is the regex to use to search for the role that should be allowed to write to the state bucket. The system uses the first returned result, so this should return exactly one.
  • subnet_map is a map(map(string)). The top level is the AZ name to build a subnet. For each subnet, if there is a public key in the submap, then it should point to the CIDR of a public network. Same for a private key and private network.

These all have reasonable defaults. For elements that are not "production" LCSB, the environment should be changed to something else and the bucket name adjusted, if desired.

  1. Plan the deployment: terraform plan

  2. Apply the configuration: terraform apply

  3. Check outputs: After applying, you can see the outputs for the bucket name and ARN.

Cleanup

To remove all resources created by this project:

First, you must change all instances of prevent_destroy = true to prevent_destroy = false in the lifecycle configurations.

Then you can terraform destroy

Notes

Ensure that your AWS credentials are configured properly in your environment for Terraform to access your AWS account.

Owner

  • Name: Lynker Intel
  • Login: LynkerIntel
  • Kind: organization

GitHub Events

Total
Last Year