Kostya Barchenkov from Luxury Escapes shares their positive experience working with DoiT, highlighting how the partnership significantly improved their holiday sales performance.
Initially skeptical about partnering with resellers, Luxury Escapes found great value in DoiT’s services during their challenging transition to AWS.
They particularly benefited from cost savings, enterprise-level support, and a thorough architectural review that prepared them for high demand during the Boxing Day sales, leading to doubled traffic without performance issues.
You have cloud challenges? We have Logan Clemons, cloud infrastructure expert, problem-solving enthusiast and key member of our CRE team at DoiT.
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?
How did a small-town internet service provider technician from Texas come to lead DoiT’s global client services team?
From cost optimization to cloud migration, machine learning and CloudOps,
we’re here to make the public cloud easy.
From cost optimization to cloud migration, machine learning and CloudOps, we’re here to make the public cloud easy.
Ready to get started?
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.
4 Responses
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