Configuring the Bastion Feature

The Bastion creates a direct communication link to your applications from within the sandbox. In the Application YAML, define the connection protocol (SSH, RDP or both). In the Blueprint YAML, define the Bastion's initial state and availability. CloudShell Colony provides an initial state of "enabled-on." You can change its state to "Enabled-off" or "Disabled" in the Blueprint YAML file. 

In the Application’s YAML file do the following:

1. Under the source section, image sub-section, define the operating system’s username.
2. Under the debugging section, define the connection protocol as one of the following: SSH | RDP | SSH, RDP.

For example: 

source:
  os_type: linux
  image:
    ami:
      - id: ami-f90a4880
        region: eu-west-1
        username: ubuntu
debugging:
  connection_protocol: SSH

NOTE: CloudShell Colony does not require a password definition since the connection is done using a secured certificate that is generated when the instance is created and stored in your cloud account.

In the Blueprint’s YAML file do the following:

• Under the debugging section, define the Bastion's availability state:
  • enabled-on: (Default) Bastion will be deployed and remain powered on
  • enabled-off: Bastion will be deployed and then powered off. Can be powered on easily by the user.
  • disabled: Bastion will not be deployed, and debugging links will not be available for this blueprint.

For example: 

debugging:
  bastion_availability: enabled-on

NOTE: If the Bastion is enabled-on, the UI displays different buttons in the Debugging tab, from which you can control the state.