Hosting
The application runs on AWS Elastic Beanstalk, which takes care of the servers. This way your attention stays on the application itself.
AWS infrastructure for your SaaS application
We set up your application on AWS with hosting, a filter for harmful traffic, automatic blocking of scanners and ready-made reports from the logs. The AWS account stays yours.
When your application already has users, an outage or an attack costs you time and trust. This page explains in plain words what we set up on Amazon Web Services (AWS) and what changes for you in practice: fewer surprises, a clear picture for whoever manages it, and no dependence on us to keep your access.
AWS infrastructure for your SaaS application What we set up
Each piece in plain words, together with its name on AWS.
What it does | AWS service |
|---|---|
Hosts the application and keeps it running | AWS Elastic Beanstalk |
A filter that stops harmful traffic before it reaches the application | AWS WAF |
A small automatic program that spots scanners and blocks them | AWS Lambda |
Ready-made queries on the logs | Amazon CloudWatch Logs Insights |
The filter
AWS WAF is a filter in front of the application. It limits how many requests each visitor can send, and it can limit traffic by country. It also applies sets of rules maintained by AWS, and it blocks requests for files that no visitor needs. Some places, such as complex sign-up forms, need exceptions so that real users get through normally. We set them with care.
The scanners
Automatic tools keep trying addresses, such as hidden settings files or admin pages of software that you may not even use. A small AWS Lambda program reads the logs every few minutes, recognises this behaviour and blocks the sender. Each time the sender comes back, the block lasts longer. See how it was done in a real project in the AWS infrastructure case.
The reports
Amazon CloudWatch Logs Insights keeps saved queries: which requests failed, which were redirected, which addresses look suspicious, what was blocked. Even someone who is not an engineer can open a report and read it.
AWS infrastructure for your SaaS application How we work
We start with a short conversation about your application: where it runs today, who uses it, and which parts are public and which are private. Then we agree on what will be set up. We build the infrastructure inside your own AWS account. We check that real users get through normally and that the rules block what they should. At the end we show you everything we set up and how the reports are read. If the application has not been built yet, we can take it on as a SaaS platform project. The two services combine easily.
The infrastructure lowers the everyday risk. It also shows you clearly what is happening, so you can react fast when something needs attention.
AWS infrastructure for your SaaS application What stays with you
The AWS account belongs to you, together with everything we set up inside it. You keep the access, and we work with the access you give us. You decide who changes settings, and you receive the AWS bill directly. You also keep the reports, together with the knowledge of how to read them. If you want us to keep supporting you, that is done with a separate, clear agreement.
AWS infrastructure for your SaaS application Who it is for
It is for teams that have a SaaS application running or are getting ready to launch one. They get a reliable level of protection without hiring an infrastructure specialist. It is also for businesses with an online application that finally want to make use of their logs. The service offers technical protection. Official certifications or legal statements for a system are issued by specialised bodies.
The owner of iwebforyou is AWS Certified, and the official badge can be verified through AWS. To see how the infrastructure fits your application, start a conversation about your project.
Trademark notice: Amazon Web Services, AWS and related marks are trademarks of Amazon.com, Inc. or its affiliates.
AWS infrastructure for your SaaS application Frequently asked questions
Do I need to already have an AWS account?
No. We guide you to create an account in your own name, so you are the owner from day one. If you already have an account, we work inside it.
Does the filter affect real users?
The filter is set up so that real users get through normally. That is why we test with real sign-in and sign-up flows. We add exceptions where a legitimate action looks unusual to the filter. After launch, the reports show what was blocked, so any mistake is found and fixed quickly.
Do you set up infrastructure for an application built by someone else?
Usually yes. First we study how the application is built and where it runs. Then we tell you what is possible. If changes are needed for it to run properly on Elastic Beanstalk, we tell you before the work starts.
Is the service the same as a security audit?
No. The service builds protection and visibility around the application. Checking every weakness inside the code is a separate job. See how our quality and security checks work.
Next step: AWS infrastructure for your SaaS application
Start your project
Send a project request, or check your current website for free. We read every message ourselves.