Our cloud engineering team wears many hats, with different roles taking on different pieces of the nationwide gBlock™ Cloud falling to different staff members, but everyone pulling their weight on a wide variety of projects simultaneously.
Our new blog series digs into the daily life of our technology staff, focusing on their challenges, routines, and goals, to provide insight for those who are eying the IT field, or customers and friends who may be curious what goes on behind the scenes at a cloud data center.
This week, we talk to Senior Cloud Technologist Josh Larsen, who has moved around in different roles for Green House Data for over six years. As Cloud Technologist, his job largely entails forecasting and planning for large-scale cloud projects across our entire environment.
The B Corp movement continues to grow and spread throughout the world, with more and more companies of all sizes and industries looking towards B Corp Certification as a guide towards sustainability, positive relationships with employees and stakeholders, community involvement, and overall impact.
Green House Data is proud to announce that our recertification last year placed us among the Best for the World: Changemakers list, which honors organizations that significantly improved their B Impact certification rating.
It seems like every week some piece of your stack has a security advisory or a new version. While only the critical vulnerabilities or bugs might need immediate installation, inevitably you’ll be juggling dozens of versions, trying to decide which system requires a update and which you’ve already patched.
There are a few official and unofficial places to keep you in the loop on software lifecycle management, and by regularly using them in addition to your own tracking tools or spreadsheets, you can keep your IT environment safe and up-to-date.
With proliferating security tools, in addition to more systems and users taking advantage of cloud resources, IT perimeter security is feels more difficult to enforce with each passing day.
Use this checklist to quickly cover your IT perimeter and network security protocols and make sure nothing is slipping through the cracks.
When planning a cloud migration, don’t forget to plan ahead for IP address changes that could affect your workloads and the way they interact with internal and external network traffic.
Cloud providers and data centers have a limited pool of IP addresses that they own, and they often re-use previously assigned IPs in order to maximize them. You can’t simply move your existing IP addresses along with your services. Rather, you’ll receive a dynamically assigned internal and external IP address.
To complicate matters, you could lose those dynamically assigned IPs if you stop your cloud instance (but usually only if you stop and deallocate the VM resources — most providers will keep your IP assigned to you if your machine is paused/stopped but still reserved within the overall resource pool). Luckily, there are a few ways to keep IPs relatively static in the cloud.