Is a Hybrid AWS and GCP Setup Worth the Complexity?

Before going hybrid, it's best to clarify your company's needs clearly. Talk to stakeholders about whether a multi-cloud strategy is necessary for contractual, reputational, or financial reasons. This way, when you present your design, you can either justify it with solid business rationale or simplify things based on feedback.

You should only pursue multi-cloud strategies if the benefits genuinely outweigh the additional complexities. That could mean finding unique capabilities in one cloud that the other doesn’t provide, which can reduce risks or costs in specific use cases.

Honestly, multi-cloud setups are often more expensive due to the overhead in maintenance. It's crucial to factor in egress costs when you're moving data between clouds. Sometimes, sticking with one provider for all your needs is simpler and more cost-effective.

The question is whether you can afford to lose one cloud without affecting your production. If AWS experiences another major outage, is your setup resilient enough to keep running? Consider how critical the GCP components are for your workloads. The complexity needs to be justified against the importance of these connections.

It sounds like you might be complicating things a bit. Relying on two cloud providers can create dependencies that make your setup less robust. A truly resilient multi-cloud strategy should ideally allow your systems to function independently if one provider goes down, otherwise, you're just doubling your risk.