Support: 1-800-961-4454
Sales Chat
1-800-961-2888

Protect Servers Using Bastion Hosts And Isolated Cloud Networks

We know that the public internet can be a scary place for servers. Log files of servers attached to public addresses show regular port scans and URL snooping and are a constant reminder that your hosts are one misconfiguration away from catastrophe.

To help you avoid disaster and thwart potential threats, we’ve created a handy guide to walk you through the creation of bastion hosts and isolated cloud networks.

What’s a bastion host? It’s a choke point that only offers authorized users access to the hosts behind it. It’s like a gatekeeper: it won’t let anyone in who isn’t on the guest list.

And with Rackspace Cloud Networks, you can create Rackspace Cloud Servers that do not have a public IP and attach only to an isolated Class A, B or C network that only your Cloud Servers can talk to.

This increases the security of your infrastructure servers and adds an extra layer of defense.

For a deep, technical dive into protecting your infrastructure servers with bastion hosts and isolated cloud networks, check out our guide on the Rackspace DevOps blog.

And, remember, Cloud Networks is currently being rolled out to Rackspace customers. You may already have access, and if you don’t, you can request access now.

About the Author

This is a post written and contributed by Brandon Philips.

Brandon Philips is part of a small team of Rackers getting the Rackspace Cloud Monitoring Agent ready for launch. The Agent will help customers monitor the internals of their servers and application. You can check out his site at http://ifup.org, find him at local San Francisco meetups and check out his code at https://github.com/philips.


More

Leave a New Comment

(Required)


Racker Powered
©2014 Rackspace, US Inc.