Video

How DoiT Strengthened Monstarlab’s Cloud Management and Transparency

Juraj Longauer on Monstarlab’s Cloud Transformation with DoiT

Juraj Longauer, Director of Cloud at Monstarlab, shares how the global digital consultancy transformed its cloud management and transparency by partnering with DoiT. Facing challenges with cloud accountability and uncontrolled costs, Monstarlab turned to DoiT for a strategic overhaul.

Over a short period, DoiT’s Cloud Navigator and FinOps framework revolutionized Monstarlab’s cost attribution, spending patterns, and resource optimization.

Juraj discusses the impact of DoiT’s comprehensive assessments, innovative cost attribution tools, and the resulting improvements in cloud service maturity and operational efficiency.

This collaboration not only streamlined Monstarlab’s cloud operations but also significantly enhanced their cost management capabilities, enabling the company to focus on delivering top-notch digital transformation solutions. Discover how DoiT’s expertise set the stage for Monstarlab’s continued success with AWS, Azure, and future Google Cloud workloads.

Subscribe to updates, news and more.

4 Responses

  1. ec2 instance connect appears to be locked down to SSH and RDP protocols (ports 22 and 3389 only), meaning you can’t use it for databases in the way this post suggests. You still need to ssh to some instance then connect to the DB from there – the advantage is you don’t need to expose that ec2 instance publicly.

    If you go through the above guide, you’ll just get the following error:

    awscli.customizations.ec2instanceconnect.websocket – ERROR – {“ErrorCode”:”InvalidParameter”,”Message”:”The specified RemotePort is not valid. Specify either 22 or 3389 as the RemotePort and retry your request.”}

    did you actually try the above out successfully?

    also discussed here: https://repost.aws/questions/QU_h42-ck0R-alITadXrrXSQ/rds-configuration

  2. ec2 instance connect appears to be locked down to SSH and RDP protocols (ports 22 and 3389 only), meaning you can’t use it for databases in the way this post suggests. You still need to ssh to some instance then connect to the DB from there. If you go through the above guide, you’ll just get the following error: awscli.customizations.ec2instanceconnect.websocket – ERROR – {“ErrorCode”:”InvalidParameter”,”Message”:”The specified RemotePort is not valid. Specify either 22 or 3389 as the RemotePort and retry your request.”} did you actually try the above out successfully? also discussed here: https://repost.aws/questions/QU_h42-ck0R-alITadXrrXSQ/rds-configuration

Leave a Reply

Your email address will not be published. Required fields are marked *

Related videos

Schedule a call with our team

You will receive a calendar invite to the email address provided below for a 15-minute call with one of our team members to discuss your needs.

You will be presented with date and time options on the next step