Video

Engineer-to-engineer with Diego Munoz

You know that success with the cloud starts with proper planning, but do you know as much about planning and structuring cloud data as Diego Munoz? (Hats off if you do. That’s impressive.)

Bringing a wealth of experience in systems infrastructure and communications to the DoiT CRE team, Diego takes a strategic and success-minded approach to cloud data architecture that helps him help customers define the right solution for their needs.

“The problems that I solve for my customers are usually with regard to proof of concept — to guide them through defining KPIs and bring them a roadmap in order to accomplish that,” he explains. “It’s still a new technology. That means in order to do it effectively, it’s very important to have the proper structure.”

Watch the full video to hear more from Diego about what excites and inspires him in his work as a senior cloud data architect and customer reliability engineer at DoiT.

Engineer to Engineer is a series of short videos introducing our renowned team of customer reliability engineers, or CREs. This team is responsible for the unparalleled service and support all DoiT customers receive, at no extra cost, around the clock and around the world.

Our senior-level cloud engineers and architects collectively have hundreds of certifications and years of experience working with our public cloud partners. Their expertise and commitment to a cloud-enabled future is on hand every day to help you achieve your goals.

Our customer satisfaction rate averages at 98%, with an average first reply time below 40 minutes and full resolution time in under two days. But don’t take our word for it — check out our live stats, unedited and available in real time at doit.com/stats to see what our customers have to say.

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