-
Access your BOSH director
- Through a VPN
- Through a jumpbox
- Expose Director on a Public IP (not recommended)
bosh.yml
: Base manifest that is meant to be used with different CPI configurations[aws|azure|docker|gcp|openstack|softlayer|vcloud|vsphere|virtualbox]/cpi.yml
: CPI configuration<cloud>/cloud-config.yml
: Simple cloud configsjumpbox-user.yml
: Adds userjumpbox
for SSH-ing into the Director (see Jumpbox User)uaa.yml
: Deploys UAA and enables UAA user management in the Directorcredhub.yml
: Deploys CredHub and enables CredHub integration in the Directorbosh-lite.yml
: Configures Director to use Garden CPI within the Director VM (see BOSH Lite)config-server.yml
: Deploys config-server (seecredhub.yml
)syslog.yml
: Configures syslog to forward logs to some destinationlocal-dns.yml
: Enables Director DNS beta functionalitymisc/proxy.yml
: Configure HTTP proxy for Director and CPIruntime-configs/syslog.yml
: Runtime config to enable syslog forwarding
See tests/run-checks.sh for example usage of different ops files.
Please ensure you have security groups setup correctly. i.e:
Type Protocol Port Range Source Purpose
SSH TCP 22 <IP you run bosh CLI from> SSH (if Registry is used)
Custom TCP Rule TCP 6868 <IP you run bosh CLI from> Agent for bootstrapping
Custom TCP Rule TCP 25555 <IP you run bosh CLI from> Director API
Custom TCP Rule TCP 8443 <IP you run bosh CLI from> UAA API (if UAA is used)
SSH TCP 22 <((internal_cidr))> BOSH SSH (optional)
Custom TCP Rule TCP 4222 <((internal_cidr))> NATS
Custom TCP Rule TCP 25250 <((internal_cidr))> Blobstore
Custom TCP Rule TCP 25777 <((internal_cidr))> Registry if enabled