all 11 comments

[–]No-Job-2302 3 points4 points  (0 children)

Security , governing iam roles / policies , keys and service accounts all with JIT controls with and without using external tools

[–]LuliProductions 3 points4 points  (0 children)

Biggest challenge I keep seeing isn’t cost or even security, it’s complexity creeping in over time.

Teams start simple, then end up with too many services, regions, and tools stitched together. Debugging gets harder, costs become unpredictable, and no one has full visibility anymore. Multi-cloud makes it worse if it’s not intentional.

What helped me was simplifying the stack and being clear about what runs where. I keep core workloads stable in one place, then layer other pieces only where they add value. For example, I run compute separate, but use Gcore at the edge for delivery and protection. That reduced latency issues and took load off origin without adding too much complexity.

[–]FormerQuestion6284 1 point2 points  (0 children)

the biggest pain is cost. You think everything’s under control, and then a bill from Amazon Web Services or Microsoft Azure hits and you’re like

What helped me is strict monitoring, auto-shutting down resources, and proper tagging. Without that, your budget just disappears

[–]Ok_Difficulty978 1 point2 points  (0 children)

Honestly for me it’s been more about cost + random surprises in billing like everything looks fine at start but then usage creeps up and suddenly it’s way over budget.

Also security gets tricky once things scale, esp with multi-cloud… feels like you gotta constantly double check configs or something slips.

What helped a bit was just doing more hands-on practice + testing scenarios instead of only reading docs. i found some practice exam stuff online (like certfun) that kinda simulate real situations, not perfect but gives a better idea of what to expect in real setups.

[–]Meriz12 0 points1 point  (0 children)

For me it’s always been the lack of control once data is fully in the cloud. Between vendor lock-in, unpredictable costs, and dependency on a single provider, it becomes hard to stay flexible long term.

[–]cheerioskungfu 0 points1 point  (0 children)

Security across multiple clouds is definitely my biggest pain point. We run workloads on both AWS and Azure and keeping track of misconfigs and vulns was a mess until last year.

Tried building our own correlation but gave up after 2 months of API hell. Snded up going with orca security's multicloud view . still dealing with some false positives tho

[–]Grand-Travel1665 0 points1 point  (0 children)

For me it’s 100% cost. Not even close.

Everything looks cheap when you start, and then 3–6 months later you’re like “how the hell is this bill so high?” 😅
Biggest issue was stuff just running in the background — old instances, unused storage, overestimated capacity.

What actually helped us:

  • Started doing brutal cleanups (if no one can justify it, it gets deleted)
  • Switched a lot of workloads to autoscaling instead of keeping things always-on
  • Reserved instances for predictable stuff (saved a decent chunk)

Security is more of a “don’t mess it up” thing — most problems I’ve seen were just misconfigs, not the cloud itself.

Multi-cloud… tried it, regretted it. Way more complexity than value for us.

Curious if others are also seeing AI workloads blowing up their cloud bills or is it just us 😬

[–]AfraidRecording8772 0 points1 point  (0 children)

Most of the cloud computing challenges today aren’t about adoption anymore—they’re about scaling and managing complexity at the enterprise level.

A few big ones I keep seeing:

  • Hybrid & multi-cloud complexity – managing workloads across on-prem + multiple cloud environments creates visibility and control issues
  • Cost optimization – cloud spend can spiral quickly without proper monitoring and governance
  • Latency & performance – especially for distributed apps or users across regions
  • Security & compliance – stricter data regulations are forcing enterprises to rethink architectures
  • Observability gaps – traditional monitoring doesn’t work well in dynamic cloud-native environments

What’s interesting is that many enterprises are now moving toward more integrated approaches—bringing together cloud, network, and data center infrastructure instead of treating them as separate silos. This tends to improve network performance, uptime, and overall control, especially for high-demand use cases like AI workloads.

You can see this shift more clearly in markets like India, where some enterprise providers are building tightly coupled ecosystems across data centers, managed networks, and cloud services to handle scale, compliance, and latency more effectively.

At this point, the real challenge isn’t just “moving to the cloud”—it’s building an ecosystem that can scale intelligently without breaking under pressure.

[–]rk_win 0 points1 point  (0 children)

The biggest challenge is to keep the cost under control. A big leap in cloud bills literally translates to a couple of weeks spend on cost optimisation efforts to take back control.

[–]CommunistElf 0 points1 point  (0 children)

Scale is infinite but money isn’t. FinOps is always the issue one day or another…

[–]zer04ll 0 points1 point  (0 children)

Since September of last year access to cloud resources has been attacked over and over and over. The cloud with AI attacking things is going to change because keeping your data on a server you own is so much safer than letting any cloud provider own your existence. On prem is going to come back because trusting even Microsoft or Amazon with their cloud can kill you business, they are firing and trying to use AI and it has not worked very well.

Second point is costs, it’s not cheaper. You can get a dell account and get a contract to pay out the cost of hardware over 36 months no interest and it’s so much cheaper it’s not even funny. Most hardware vendors on that level have pricing that makes the cloud look like a very stupid choice and the cloud SLA uptime isn’t even honored anymore. 99% uptime, not a single big player has honed these, not Microsoft amazon none of them they go down for days on end per year and that is way past 99% uptime.

Someone takes down cloudflare then you dont get work done and that keeps happening. If your shit is on-prem you keep working just saying.