TEL AVIV, August 11, 2020 (GLOBE NEWSWIRE) —
DoiT International, a leading provider of proprietary cloud optimization and operations software and cloud expertise, announced today that it has been named as an Amazon Web Services (AWS) Partner Network (APN) Immersion Day Partner, recognizing the company’s eligibility to conduct APN Immersion Days.
The traditional AWS Immersion Day workshops are customizable day-long, in-person, or online workshops to help customers navigate through different areas of AWS. This in-depth approach helps technical experts learn how to best leverage AWS to unlock business potential and meet key objectives. AWS Immersion Day workshops are available in many solution areas, such as database migration, containers, machine learning (ML), and serverless services.
APN Immersion Days offer APN Advanced and Premier Consulting Partners access to workshop content and tools developed by AWS Solutions Architects and packages it for APN Partners to use exclusively with their customers. With this announcement, DoiT International can now deliver APN Immersion Days.
As an APN Immersion Day Partner, DoiT International Cloud Architects will be able to provide its customers with an exclusive technical workshop experience. Customers will have access to curated field-tested content, sound architectural principles, and a guided tour of AWS products and services.
This announcement follows DoiT International being named as an AWS Well-Architected Partner in February 2020, recognizing DoiT International has the expertise to deliver AWS Well-Architected reviews for existing workloads or new applications based on AWS’s best practices and guidelines. The extensive certification efforts for both distinctions were led by Doron Offir, DoiT International’s Director of Cloud Engineering.
“DoiT is proud to have been named as an APN Immersion Day Partner,” said DoiT International’s CEO and Co-Founder, Yoav Toussia-Cohen. “We are excited to provide APN Immersion Day training to clients and prospects at no extra cost, just one of the many additional benefits that we are proud to offer our clients.”
About DoiT International
DoiT International is a leading global cloud consulting company and strategic partner of Google Cloud Platform and member of the Amazon Web Services (AWS) Partner Network (APN). We tackle complex problems of scale for our customers, using our expertise in resolving problems, machine learning, algorithms, complexity analysis, and system design.
Founded in 2011, DoiT International has offices in Tel Aviv, San Francisco, Santa Clara, New York, Austin, London, Paris, Berlin, Los Angeles, Melbourne, and with plans to expand Chicago and Seattle in 2020. For more information, please visit www.doit.com.
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