• 💡 Why Basti?
• ⚙️ How it works
• 💻 Installation
• 🏄 Basic usage
  • ☝️ Initialize connection target
  • ✌️ Connect to the target
  • 🎉 Use the target on localhost
  • Cleanup (optional)
• 🧶 Reference documentation
• 💠 Custom connection targets
• 🎛️ Advanced initialization options
  • Resource tags
  • Bastion instance type
  • Assign public IP address
• 🦾 Automatic mode
• 📝 Configuration file
• 💫 Infrastructure as code (IaC)
• 🏢 Basti in teams and organizations
  • Minimal IAM permissions
  • Usage audit
  • Shared configuration
• 🔐 Security
  • Network
  • Access control
  • Software
• ❤️ Development
  • Build
  • Run
  • Test
• License

With Basti, you can securely connect to RDS, Aurora, Elasticache, or any other AWS resources in private VPC subnets from a local machine or a CI/CD pipeline almost for free!

AWS Session Manager is a fantastic tool! But Basti makes it even better:

• 🦾 With Session Manager, you need to oversee an EC2 bastion instance for connecting to managed resources such as RDS or Elasticache. Basti handles bastion instance setup, shutdown, and updates for you!

• 💅 Basti provides a convenient way to store and reuse connection configuration across your team.

• 📶 Basti improves stability of the Session Manager sessions by automatically restarting failed or expired sessions.

• 🏰 Basti sets up a so called bastion EC2 instance in the connection target's VPC.

• 🧑‍💻 The bastion instance is used with AWS Session Manager port forwarding capability to make the target available on your localhost.

• 💵 Basti takes care of keeping the bastion instance stopped when it's not used to make the solution cost as low as ≈ 0.01 USD per hour of connection plus ≈ 0.80 USD per month of maintaining the instance in a stopped state.

• 🔒 Security completely relies on AWS Session Manager and IAM policies. The bastion instance is not accessible from the Internet and no SSH keys are used.

Using homebrew

brew install basti

Using npm

npm install --global basti

Other, NodeJS-independent, installation options are coming soon!

Basti uses AWS SDK and relies on credentials to be configured in your system. You can use any of the methods supported by AWS SDK to configure credentials.

💡 You can expect Basti to work if you can use AWS CLI in your terminal.

First, initialize your connection target. It could be an RDS instance, an Elasticache cluster or any other target residing in a VPC. The following command will set up all the infrastructure required to start a connection. You only need to do this once.

basti init

You will be prompted for a target to initialize and a public VPC subnet to create the bastion EC2 instance in.

Now, you can start the connection. This command will establish a secure port forwarding session and make the target available on your localhost.

basti connect

You will be prompted for the target to connect to as well as the local port to forward the connection to.

Finally, you can use the target same way as it was running on your localhost and port you specified in the previous step.

psql -h localhost -p 5432

💡 psql, the PostgreSQL client, is used as an example here. Basti can be used to connect to any type of database or other services as long as the communication is done over TCP.

You can remove all the resources created by Basti in you AWS account.

basti cleanup

The list of resources will be displayed and you will be prompted to confirm the cleanup.

Please, refer to the reference documentation for the full description of Basti CLI options and the configuration file.

Basti provides first class support for RDS instances, Aurora clusters, and Elasticache clusters. However, you can use Basti to connect to any other target in your AWS VPC (e.g. DocumentDB instance, EC2 instance, etc.).

To connect to a custom target, select the Custom option when prompted for a target to initialize or connect to. You will be prompted for the target's VPC, IP address and port.

🤝 Feel free to open an issue or a pull request if you want to extend the list of natively supported targets

The basti init command has a number of advanced options that can be used to customize the bastion instance and other resources created by Basti.

💡 Please, refer to the reference documentation for the full list of options.

You can specify tags to be applied to the bastion instance and other resources created by Basti. This can be done in three ways:

1. By entering the tags in the advanced options section of the interactive mode.
2. By passing the --tag option. This option accepts tag name and value separated by an equal sign. For example, --tag Project=my-project This option can be used multiple times to specify multiple tags.
3. By passing the --tags-file option. This option accepts a path to a JSON file with tags. The option can be used multiple times to specify multiple files.

Example of a tags file:

{
  "Project": "my-project",
  "Environment": "production"
}

Tags with the same name will be overwritten in the order they are specified. Tags specified with the --tag option will always overwrite tags specified in the tags file.

💡 If your tags contain special characters, it might be easier to use interactive mode or the --tags-file command than escaping the characters in the --tag option.

You can specify the EC2 instance type to be used for the bastion instance using the --bastion-instance-type option or by entering it in the advanced options section of the interactive mode. The default instance type is t2.micro, but it's subject to change in the future.

By default, the bastion instance is created with a public IP address to enable seamless outbound-only connection to AWS services from a public VPC subnet. Please, refer to the AWS documentation for more details on the Session Manager requirements.

You can disable the public IP address using the --bastion-assign-public-ip false option or in the advanced options section of the interactive mode.

☝️ When the public IP address is disabled, you will need to manually ensure that the AWS Session Manager connectivity requirements are met. This can be done with the help of VPC endpoints, NAT gateways, or other means.

💡 Disabling public IP address can be useful when setting up the bastion instance in a private subnet.

Using interactive mode is convenient when you're getting used to Basti. However, in Continuous Integration and Continuous Delivery (CI/CD) pipelines, you will probably want to disable interactivity and pass all the options as command line arguments:

basti connect --rds-instance your-instance-id --local-port your-port

Use basti <command> --help to see all the available options for basti connect and other commands.

To continue executing the script after the connection is established, you can use Basti in conjunction with the wait-on utility and the & shell operator:

basti connect --rds-instance your-instance-id --local-port your-port &
wait-on tcp:localhost:your-port

When working with multiple connection targets, it becomes convenient to store their configurations and other Basti settings in a dedicated configuration file. To facilitate this, Basti automatically searches for the configuration file in the current directory and its parent directories. The supported file names are .basti.yaml, .basti.yml, and .basti.json.

You can quickly start a connection defined in the configuration file by passing its name to the basti connect command:

basti connect your-connection

# - Connections are used with the `basti connect <connection>` command
# - Targets' fields are the same as the options for the `basti connect` command
connections:
  database-dev:
    target:
      rdsInstance: my-dev-database
      awsProfile: dev
    localPort: 5432

  database-prod:
    target:
      rdsInstance: my-prod-database
      awsProfile: prod
    localPort: 5432

  # Default AWS profile and region are used if not specified in the target
  redis-cache-dev:
    target:
      elasticacheRedisCluster: my-dev-cache
    localPort: 6379

  # Same target but with different local port
  custom-target-local:
    target: custom-target
    localPort: 4646

# Targets can be extracted and reused in multiple connections
# with different local ports
targets:
  custom-target:
    customTargetVpc: vpc-1234567890
    customTargetHost: 10.0.1.1
    customTargetPort: 4646
    awsProfile: prod
    awsRegion: us-east-1

💡 Please, refer to the reference documentation for the full list of configuration options.

Introducing, Basti CDK, an AWS CDK construct library that allows you to integrate Basti with your existing CDK-managed infrastructure.

Feel free to open an issue if you want to see Basti in Terraform or other IaC tools. Contributions are welcome 🤗

Basti was designed with organizational usage patterns in mind. The bastion instance and other infrastructure created by Basti is reused across all the users in your organization.

Basti commands require different sets of IAM permissions. basti init needs broad permissions to set up all the infrastructure required to start a connection. basti connect, on the other hand, requires only minimal permissions to start a connection. This means that the AWS account administrator can run the basti init command once and then grant the minimal permissions to the IAM users who need to start connections.

basti connect --custom-target-vpc your-vpc-id --custom-target-host your-target-host --custom-target-port your-target-port --local-port your-local-port

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "ec2:DescribeInstances",
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": "ec2:StartInstances",
      "Resource": "arn:aws:ec2:<your-region>:<your-account-id>:instance/<your-basti-instance-id>"
    },
    {
      "Effect": "Allow",
      "Action": "ec2:CreateTags",
      "Resource": "arn:aws:ec2:<your-region>:<your-account-id>:instance/<your-basti-instance-id>"
    },
    {
      "Effect": "Allow",
      "Action": "ssm:StartSession",
      "Resource": [
        "arn:aws:ssm:*:*:document/AWS-StartPortForwardingSessionToRemoteHost",
        "arn:aws:ec2:<your-region>:<your-account-id>:instance/<your-basti-instance-id>"
      ],
      "Condition": {
        "BoolIfExists": {
          "ssm:SessionDocumentAccessCheck": "true"
        }
      }
    }
  ]
}

Since Basti uses IAM for access control, the connection history, along with the responsible IAM user and all the connection details, can be audited using AWS CloudTrail by filtering on the "StartSession" event. Please, refer to the AWS CloudTrail documentation for more details.

A simple connections history can also be found in the AWS Session Manager history. See AWS Session Manager documentation for more details.

The Basti configuration file file can be shared across your organization, making it easy for all developers to connect to the project's cloud infrastructure. A recommended practice is to store the configuration file in the root of your project's repository. This ensures that the configuration is readily accessible to all team members, enabling quick and seamless connections to the required cloud resources.

Security is a top priority for Basti. The following sections describe the security measures taken by Basti.

The bastion EC2 instance reachability from the Internet is completely disabled with AWS Security Groups configuration. No ports are open for inbound traffic. The bastion instance is only accessible through AWS Session Manager.

Basti automatically adjusts the target's Security Group to allow inbound traffic from the bastion instance's Security Group.

AWS Session Manager, which is used by Basti to establish a port forwarding session, doesn't use SSH keys for access control. Instead, it relies on AWS IAM users and their permissions in your AWS account. This also means that AWS CloudTrail could be used to audit Basti usage.

Basti uses the latest Amazon Linux 2 - Kernel 5.10 AMI available at the initialization time (basti init command) for the bastion instance.

The bastion instance EBS volume is encrypted by default.

The bastion instance is being stopped when it's not used for some short period of time. These shutdowns are also used to update the bastion instance's software packages and OS kernel. By default, the updates happen once a day but not more often than the bastion instance is used.

First of all, thank you for your interest in contributing to Basti! 🎉

The following section describes how to run your local version of Basti CLI as you make changes to the code. Please, feel free to open an issue if you want to see Basti CDK development guide!

Before proceeding to development, it's recommended to run the full build. This requires Docker to be installed on your machine and may take a couple of minutes.

npm run build

Full Basti build consists of two parts:

1. Compiling Basti TypeScript code. The code has to be compiled after each change.

   npm run build-src
   
   # Or, if you want to automatically recompile on each change:
   npm run build-src-watch

2. Building non-NodeJS dependencies (AWS session-manger-plugin). This step is only required after the first checkout or in a rare case when the dependencies are updated.

   npm run build-deps

After the build is complete, you can run Basti:

npm run start -- <command> <options>

Alternatively, you can link-install the local version of Basti in your system and use it as you would usually use Basti:

# Link-install the local version of Basti
npm link

# Run Basti
basti <command> <options>

Before submitting a pull request, please make sure that all the tests and checks pass:

npm run test

Usage is provided under the MIT License. See LICENSE for the full details.