We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
-
Chapter 1 Platform Setup
-
Chapter 2 Operating the Platform
-
2.1SSH Access for your Cluster02:36
-
2.2Scaling up the Cluster05:30
-
Don't have an account?
Sign up and get a 30 day free trial. No credit card required.
SSH Access for your Cluster
Up until this point we have just learned how to configure, provision, and destroy our cluster. In this episode we will access the cluster by jumping into our bastion.
This episode assumes that you have correctly setup the ssh-keys in your infrastructure configuration.
Getting the right Address
To ssh into the bastion node, you'll need to find the node on your AWS console and select the public DNS address.
Copy the public IPv4 address and paste it in the command line:
$ ssh ubuntu@ec2-54-254-197-71.ap-southeast-1.compute.amazonaws.com
You should be able to jump into the bastion and jump to the bootstrap node from here.
Jumping into the Compute Node
All your containers are running inside your compute nodes, so to access them you'll need to jump in. We'll use the private ip address for this.
Head over to the node you want to jump into and copy the Private IPv4 address and type in:
$ ssh ubuntu@the-private-ip-address
You should be able to jump into the node. You can run the lxc list --all-projects
and you should see an output with the uplink node.
Instructor

Zack Siri
Founder
Zack is the creator of Opsmaru. He's worked as CTO in many companies across many industries, everything from hospitality to fin-tech.
He's currently building Opsmaru and loves help customers simplify their DevOps journey. He's happy to share his knowledge and experience to empower customers to get the most out of Opsmaru.