The Requirement:

One such requirement came from Rizitek India Pvt. Ltd. They wanted to deploy an in-house Odoo ERP system, along with a Web API to support their mobile applications. The objective was straightforward:
• Host Odoo ERP on the cloud
• Provide secure Web API access for mobile applications
• Maintain reasonable performance
• Keep the infrastructure simple to manage
• Keep the monthly AWS budget around US$150
This is where Amazon Lightsail became an attractive solution.

Rizitek India Pvt. Ltd. needed a small but dependable cloud environment for its internal ERP operations.

The proposed application architecture consisted primarily of:

Odoo ERP + Database + Web API + Web Access

The infrastructure did not require a large multi-server architecture, Kubernetes, auto-scaling groups, or a highly distributed microservices environment.

The real requirement was much simpler:

A reliable cloud server capable of running Odoo and exposing APIs, without paying for enterprise-scale infrastructure.

For a small client, simplicity is itself an important architectural requirement.

Why Traditional AWS EC2 Can Become Complicated?

Amazon EC2 is extremely powerful and flexible. It allows organizations to select instance types, storage, networking, security groups, load balancers, elastic IPs, monitoring, backups, and many other services.

But that flexibility can also introduce complexity.

For a small deployment, an architecture such as:

Internet → Load Balancer → EC2 → Database → Storage

may be technically sound but unnecessarily expensive and operationally complex.

There are also additional considerations such as:

• Instance configuration
• EBS volumes
• Security groups
• Elastic IP
• Backup strategy
• Monitoring
• OS maintenance
• Network configuration
• Cost monitoring

For a small internal ERP deployment, many of these components may not provide enough additional value to justify their cost.

Enter Amazon Lightsail:

Amazon Lightsail is designed to simplify cloud infrastructure deployment.

Instead of configuring every infrastructure component independently, Lightsail provides a more straightforward server-oriented experience.

For a small business application, this makes it possible to think in terms of:

Application Server → Database → Internet

rather than designing an enterprise cloud architecture from day one.

For the Rizitek requirement, this was particularly attractive because the infrastructure needed to remain within an approximate $150/month budget.

Proposed Architecture

A practical architecture for the requirement can be represented as:

Internet
│
│
HTTPS / SSL
│
▼
┌─────────────────┐
│ Amazon Lightsail│
│     Server      │
└────────┬────────┘
│
┌────────┴────────┐
│                 │
▼                 ▼
Odoo ERP           Web API
│                 │
└────────┬────────┘
│
▼
PostgreSQL

The same infrastructure can serve two major purposes:

1. Odoo ERP for internal users
2. Web API for mobile applications

This keeps the initial architecture compact and easy to manage.

Odoo ERP Hosting:

Odoo is a powerful open-source ERP platform that can cover areas such as:

• CRM
• Sales
• Purchase
• Inventory
• Accounting
• HR
• Project management
• Manufacturing
• Reporting

For an organization using Odoo primarily for internal business operations, a dedicated cloud server can be sufficient, particularly when the number of concurrent users is moderate.

The Lightsail instance can host the Odoo application while PostgreSQL provides the underlying database.

The key is to size the server according to actual usage rather than designing for hypothetical future requirements.

Web API for Mobile Applications

The second important requirement was the Web API.

Mobile applications often need access to ERP information such as:

• Customer information
• Products
• Orders
• Inventory
• Employee information
• Attendance
• Transaction status
• Reports

Instead of allowing the mobile application to communicate directly with the Odoo database, the recommended approach is to expose controlled APIs.

Mobile App
│
│ HTTPS
▼
Web API
│
│ Authenticated requests
▼
Odoo / Business Logic
│
▼
PostgreSQL

This provides a much cleaner separation between the mobile application and the ERP database.

It also provides an opportunity to implement:

• Authentication
• Authorization
• API rate limiting
• Request validation
• Logging
• Audit trails
• Versioned APIs

Keeping Security in Mind

A small infrastructure does not mean security should be compromised.

At minimum, the deployment should include:

HTTPS:

All ERP and API traffic should use HTTPS.

For example:

https://erp.company.com
https://api.company.com

SSL/TLS certificates should be configured and renewed automatically wherever practical.

Firewall Rules:

Only required ports should be exposed publicly.

Typical requirements might include:

80    HTTP
443   HTTPS
22    SSH – restricted access

Database ports such as PostgreSQL’s default port 5432 should not be exposed publicly.

Strong Authentication:

Administrative access should use strong credentials and preferably SSH keys rather than password-based authentication.

For the API, token-based authentication such as JWT or another appropriate authentication mechanism should be considered.

Why Lightsail Makes Sense for Small Clients:

The biggest advantage is not simply the server itself.

It is predictability.

For a small business, a cloud architecture should ideally provide:

Simple deployment + predictable cost + reasonable performance + manageable operations

Lightsail fits this model particularly well for smaller workloads.

Instead of building a large AWS architecture immediately, the organization can start with a straightforward server and evolve as requirements increase.

The $150/Month Target:

The most important constraint in the Rizitek project was the approximate US$150/month infrastructure budget.

This changes the architecture discussion considerably.

Instead of asking:

“What is the most powerful AWS architecture we can build?”

the better question becomes:

“What is the simplest architecture that reliably satisfies the business requirement within the budget?”

This is an important principle for small and medium businesses.

Cloud architecture should be requirement-driven, not technology-driven.

A possible monthly budget allocation could look conceptually like:

Actual AWS pricing depends on the selected Lightsail configuration, region, storage, transfer usage, and backup requirements, so the final deployment should be validated against current AWS pricing before implementation.

Start Small, Scale When Necessary:

One of the biggest mistakes in cloud architecture is over-engineering the first version.

A small organization does not necessarily need:

• Kubernetes
• Multiple application servers
• Load balancers
• Auto Scaling
• Multiple database clusters
• Complex CI/CD infrastructure
• Microservices everywhere

These technologies have their place, but they should be introduced when the business actually needs them.

For Rizitek, the initial architecture can remain simple.

Later, if the application grows, the architecture can evolve.

For example:

Stage 1

Lightsail
│
├── Odoo
├── API
└── PostgreSQL

Stage 2

Load Balancer
│
┌────┴────┐
▼         ▼
Odoo/API  Odoo/API
│
▼
PostgreSQL

Stage 3

Cloud Architecture
│
├── Load Balancer
├── Application Servers
├── Managed Database
├── Object Storage
├── CDN
├── Monitoring
└── Automated Backup

The architecture evolves with the business.

The Bigger Lesson: AWS Is Not Only for Large Enterprises:

There is sometimes a perception that AWS is suitable only for organizations running large applications.

That is not true.

The AWS ecosystem contains services for very different levels of scale.

For a small client, the right approach is often:

Keep the architecture simple.

For a growing organization:

Add managed services where they provide measurable value.

For a large enterprise:

Introduce distributed architecture, automation, high availability, scalability, and advanced security controls where required.

The technology should follow the business requirement.

Why This Approach Works for Small Clients:

For organizations like Rizitek India Pvt. Ltd., the objective isn’t to build the most sophisticated cloud architecture.

The objective is to build an infrastructure that is:

• Affordable
• Reliable
• Secure
• Easy to maintain
• Easy to troubleshoot
• Scalable enough for future growth

Amazon Lightsail provides a practical starting point for this type of deployment.

It allows a small organization to take advantage of AWS infrastructure without immediately inheriting the complexity associated with a large enterprise architecture.

Conclusion:

The Rizitek India Pvt. Ltd. requirement is a good example of how cloud architecture should be approached for small and medium-sized businesses.

The requirement was relatively simple:

Run an internal Odoo ERP + provide APIs for mobile applications + stay within approximately $150/month.

Instead of building an unnecessarily complex AWS environment, Amazon Lightsail provided a simpler path to achieving the requirement.

The important lesson is not that Lightsail is always the best AWS solution.

The lesson is:

Choose the architecture according to the workload, budget, security requirements, and expected growth—not according to how many AWS services you can deploy.

For a small client, a well-designed single-server cloud architecture can sometimes deliver significantly more business value than an over-engineered enterprise platform.

And when the business grows, AWS provides the flexibility to grow the architecture along with it.