Video
Engineer-to-engineer with Logan Clemons
You have cloud challenges? We have Logan Clemons, cloud infrastructure expert, problem-solving enthusiast and key member of our CRE team at DoiT. With extensive experience with both AWS and Google Cloud services and technology, Logan approaches every new support ticket as an opportunity to learn and deliver.
“Most of the tickets that we receive are the problems that some of the smartest engineering teams in the world are having,” he explains. “And we get to work alongside them to try and solve them.
“So it’s incredibly satisfying to work with extremely varied and intelligent people on the problems that they’re struggling to solve, and it’s very satisfying to be able to solve the issues with them.”
Watch the full video to hear more from Logan about what excites and inspires him in his work as a DoiT cloud engineer and customer reliability engineer.
“Most of the tickets that we receive are the problems that some of the smartest engineering teams in the world are having,” he explains. “And we get to work alongside them to try and solve them.
“So it’s incredibly satisfying to work with extremely varied and intelligent people on the problems that they’re struggling to solve, and it’s very satisfying to be able to solve the issues with them.”
Watch the full video to hear more from Logan about what excites and inspires him in his work as a DoiT cloud engineer and customer reliability engineer.
6 Responses
Very useful guide.
The link to calculate the optimal amount of slots doesn’t work (“BQ SE max configuration.sql”), can you fix it please?
Not sure which link you are referring to…
The link is fixed.
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
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
Always curious to learn more about Cloud data