Hi everyone! I'm new to the cloud, and we're transitioning from on-prem hypervisors to Azure. We've got several branches in rural areas and are looking to reduce the overhead of managing hardware. I've convinced my team that a lift and shift approach isn't the way to go. We're running legacy applications on Windows servers, and I believe we should explore PaaS or instance-based solutions.
For our first project, I'm considering deploying Keeper Automator, which helps manage approvals through SSO with CA for secure sign-ins and also manages new employee vault provisioning via SSH. There are lots of deployment methods available—app containers, app services, Docker/Compose, and so on—so I'm a bit overwhelmed. I'm leaning towards either an app service or a Docker instance since we want to maintain privacy within a VNET.
However, given that we're in the financial sector, we'll need thorough ingress inspections for compliance, which complicates things. I'm worried that app services might be too costly for our needs since we only require operation during business hours. Would a Docker instance be a better fit? Also, as a complete newbie to Docker, is it essential for this type of setup, or would it be overkill? I'd love to hear how you seasoned pros would tackle this challenge!
4 Answers
It’s definitely a daunting task, but just remember you're in a testing phase! As long as you secure whatever you implement, you’re good to go. Have you considered using Azure's container service since it can simplify the management aspect? Also, engaging with the Azure subreddit could provide you with some valuable tips from users facing similar challenges.
You’re on the right track! Avoiding a lift and shift is wise. Containers do have a reputation for being complicated, especially when you’re just getting your feet wet. But don't overlook them! If you decide to go with Docker, it’s definitely Linux-based, which has its advantages. It lets you create really flexible and lightweight environments. Just make sure to implement security measures, especially in your regulated environment. Play around in a test environment and see how it fits your needs before going live!
It sounds like you're in a bit deep, but it's great that you want to explore your options! If you're moving something like Keeper Automator to Azure, I’d suggest looking into an app service first. While it might seem pricey, it could save you time in the long run with setup and management since they handle scaling and maintenance for you. It’s usually straightforward and suits business-hour operations well. But yeah, definitely check with Keeper Automator for deployment recommendations based on your specific needs.
You're absolutely right, lift and shift often leads to more headaches than solutions. If you're unsure about which route to go, don't hesitate to reach out to Keeper Automator’s support for their insights—they might have defined paths based on your use case. Plus, keep experimenting—it’s all part of the learning process! By the way, Azure does have options for running containers without needing a complete Linux server if you're looking for alternatives.
Thanks for the encouragement! I’m definitely planning to test everything thoroughly before making any big moves.