As AWS provides multiple services, those can be utilized to host the websites or web-app. following are the best-fit use-case with respect to services.
Table Of Contents
Website Hosting at AWS
Using Lightsail
Pros:-
- The cost is combined with outbound data transfer and is cheaper than ec2 setup
- less overhead at database management, backup policies management
- The Load Balancer included but up to five instances
Limitation:-
- A limited number of instances or you can say, computer family
Best Fit For:-
- Websites built on common applications like WordPress, Joomla, Drupal, Magento
- Websites built on popular development stacks like LAMP, LEMP, MEAN, Node.Js
- Websites that are unlikely to scale beyond 5 servers
- Customers who want to manage their own web server and resources
- Customers who want one console to manage their web server, DNS, and networking
Using Amplify
Best Fit For:-
Single-page Website that utilizes the services in the background or Server-less Applications
- Websites built with Single pages app frameworks such as React JS, Vue JS, Angular JS, and Nuxt.
- Websites built with static site generators such as Gatsby JS, React-static, Jekyll, and Hugo.
- Progressive web apps or PWAs
- Websites that do not contain server-side scriptings, like PHP or ASP.NET
- Websites that have serverless backends.
Using S3
For static website [html+css+js] without need of a processing engine
Pros :-
- Highly scalable
- Durable
- High availability
- No worry about storage, backup, load, or managing infrastructure
Limitation:-
- Only Static content without the need of a processing engine [html+css+javascript]
- Apply HTTPS
Use Case:-
- Websites that do not contain server-side scriptings, like PHP or ASP.NET
- Websites that change infrequently with few authors
- Websites need to scale for occasional intervals of high traffic
- Customers who do not want to manage infrastructure
Using Ec2
Best Fit For:-
If we want to utilize resource optimized instances [memory or compute]
- Websites that use multiple web servers across at least two data centers
- Websites that need to scale using load balancing, autoscaling, or external databases
- Websites that require sustained high CPU utilization
- Customers who need maximum control and flexibility for their web server configuration and administration