Video

Scaling Securely: How PlaxidityX Optimizes AWS, Google Cloud & Azure with DoIT

As cybersecurity threats in the automotive industry grow, PlaxidityX is building a next-generation multi-cloud security platform to protect vehicles inside and out. But scaling across AWS, GCP, and Azure while ensuring cost efficiency and compliance presents major challenges.
  • 🚀 Scaling a multi-cloud SaaS: Balancing uptime, security, and costs while integrating services like Cognito, Lambda, and RDS.
  • 🌏 Expanding into China: Overcoming complex regulatory hurdles with DoIT’s expert guidance.
  • ⚠️ Preventing costly cloud mistakes: Real-time Slack notifications helped stop runaway S3 costs, saving thousands of dollars.
  • 📊 Bridging tech & finance: DoIT’s reports help both engineering and leadership teams track costs and optimize infrastructure.
  • 🤝 Hands-on, expert support: Unlike other providers, DoIT offers personalized, in-depth support to solve complex challenges.
Watch now to see how PlaxidityX and DoIT are working together to secure the future of automotive cybersecurity.

Subscribe to updates, news and more.

6 Responses

  1. 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?

  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 – 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

  3. 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