Genially: Resizing infrastructure in AWS
Genially is a online tool for creating interactive content aimed at a wide range of audiences, from corporations or media to educational entities or designers. At the beginning of 2020, it was the winner of the Global Edtech Startups Awards (GESA) for the Best Startup of the Future at an event held in London attended by around 2.500 companies from around the world.
Currently has a community of 5 over millions of users distributed in all countries of the world. Its client portfolio includes companies such as Telefónica, Santillana, Porsche, Danone and Michelin.
What challenge did the company face?
Genially listed some points for improvement that had been dragging on and that were now beginning to become potential problems. Among the most worrying points for them were:
Oversized architecture
autoscaling
Solution implemented
As part of our solution AWS Onboarding Program 4 Startups by apser, we made a audit of the entire deployed infrastructure, addressing it according to the different services involved:
During the audit process, potential improvements were detected in each of the services, as well as recommendations to be implemented following the best practices of AWS WAF (Well-Architected Framework).
On the other hand, certain security problems of the architecture were reflected in a document that would serve as a guide for the implementation of all the improvements detected.
Results
We are currently still working with Genially in the assessment phase of our SHERPA accompaniment program.
However, significant improvements have been made to the configuration of the AWS services that form the core of the Genially tool: AWS Elastic Beanstalk and AWS S3.
AWS Beanstalk makes use of different environments to manage all the requests received by the users. The different environments, mounted on a monolithic infrastructure with dozens of servers running, even with an Autoscaling Group, were not working correctly, which led to the implementation of some improvements:
As for the AWS S3The most significant work was to improve the security policies associated with buckets (bucket policies) to make them more restrictive.
Next steps
Once the modifications have been made to the configuration of the different AWS services with the aim of Improve the performance and operation of the infrastructureas well as a Eliminating security vulnerabilities detected, the improvements detected during the phase will be implemented. assessment making use of the best practices of the services involved.
Why Apser
apser is the AWS Advanced Consulting Partner specialized in private companies, public sector, ISVs and non-profit organizations.
Other success stories
Service center
