Compute
EC2 instances or containers (ECS/EKS), sized to the workload, with autoscaling when traffic is not flat. Lightsail exists for smaller sites that want a simpler envelope.
- EC2 / Lightsail
- Containers (ECS/EKS)
- Autoscaling when you need it
Host a site, an application or a database on AWS infrastructure that TiCON Cloud (TICON System Limited) provisions and invoices in taka. Bangladesh does not have an AWS Region; the usual regions for this work are ap-south-1 (Mumbai) and ap-southeast-1 (Singapore). Scale is elastic: a single server today, a fleet behind a load balancer later, without a forklift onto a different vendor. This is the learn page. The buy page is where configurations and an order conversation live.
Last updated 23 September 2026
“Cloud hosting” is three things that get sold as one: compute that can grow, storage and a CDN, and a database you do not patch yourself. On AWS those are EC2 or containers, S3 plus CloudFront, and RDS, Aurora or DynamoDB.
EC2 instances or containers (ECS/EKS), sized to the workload, with autoscaling when traffic is not flat. Lightsail exists for smaller sites that want a simpler envelope.
S3 for objects, snapshots for disks, CloudFront for the edge. Reseller CloudFront bandwidth is up to 40% below list — from TiCON's facts file, not from a sample invoice on this page.
Managed RDS or Aurora when you want automated backups and Multi-AZ; DynamoDB when the access pattern is key-value at scale.
A hosting price table that is not tied to a real SKU becomes fiction within a quarter. Ops has not supplied a sourced “from” list, so this page does not invent one. You get a quote in taka after we know the workload, or an indicative monthly run-rate from the BDT calculator.
What drives the number: instance size and hours, storage gigabytes, database engine, and egress — especially if you stream or ship software. CloudFront is often the line that surprises OTT and download-heavy sites; it is also the line with the largest published reseller gap (up to 40%). Compute and storage sit in the 15–35% range versus AWS list.
VAT and AIT on a local invoice are NBR matters. The calculator uses a mid-market FX print for illustration; it is not TiCON's invoice policy. Neither this page nor the calculator is a tax document.
A local VPS in Dhaka and an AWS instance in Mumbai are both “a server.” They are not the same product. The comparison is about failure domains, growth, and the invoice — not about a made-up taka-per-month column. A local public cloud (Brilliant Cloud from Intercloud) is a third product: in-country bits, narrower catalogue. Fair comparison: /blog/aws-vs-local-cloud-bangladesh.
| Criterion | Shared hosting / cPanel | Local VPS (Dhaka DC) | AWS via TiCON Recommended |
|---|---|---|---|
| Where the machine sits | A shared host's data centre, often undisclosed to you in practice | A Bangladeshi facility — useful when a regulator wants bits in-country | An AWS Region, usually Mumbai or Singapore; no AWS Region in Bangladesh |
| Growth | You hit a plan ceiling and ticket for an upgrade | You resize or buy another VPS; still one building | Autoscaling, extra AZs, GPU or a fleet, without changing vendor |
| Invoice | Local, often annual, in taka | Local, in taka | Local taka invoice from TiCON for AWS usage; no AWS dollar card required |
| When it is the wrong choice | Anything that needs isolation, a real database SLA, or burst traffic | Global audience, GPU, or a need to fail out of one building | A hard in-country residency rule that an AWS Region cannot meet — talk residency first |
No ping times and no “from ৳X/month” figures. Latency belongs in a dated measurement; prices belong in a quote.
Users in Dhaka reach Mumbai or Singapore, not a local AWS Availability Zone. This page does not publish ping or traceroute figures. Those need a dated measurement from a Bangladeshi ISP, which is still an open input.
For many websites and APIs the difference is acceptable. For a trading UI or a voice path, you measure. CloudFront and a local CDN or edge can pull cacheable bytes closer; they do not move the origin into Bangladesh. If a regulator requires data in-country, AWS-as-origin may be the wrong design, or only part of the design. That conversation is on the data-residency page, and it needs primary circulars before anyone quotes a circular number.
TLS, WAF, IAM and automated backups are the default control set we put on a hosted workload. They are not a substitute for a residency ruling.
A site on cPanel or a single office server can move. The method is a small migration: copy content, stand up TLS, cut DNS, keep a rollback. It is the 6 R's in miniature — usually rehost, sometimes replatform onto RDS — not a six-month programme.
Move a site from shared hosting onto AWS
About 5 days
Typical for a brochure or app site. A platform rewrite is a different quote.
Say what it is
CMS or custom app, PHP/Node/.NET, database engine, expected traffic, and whether you need us to operate it afterwards.
Stand up the landing
We provision compute (or Lightsail), storage, TLS, backups, and the database if it is leaving the shared host. Billing is already on the taka invoice.
Copy and test
Content and data copy onto the new host. You test on a staging hostname before DNS moves.
Cut DNS, keep rollback
Lower TTL beforehand, switch the record, watch. The old host stays up until you are sure. Then we decommission it so you stop paying twice.
You can take the keys and run the instance under reseller billing, or you can have 24×7 operations on top. GPU instances for training or rendering are in the catalogue; they are quoted, and they should be stopped when idle because they are expensive when they sit.
Yes. TiCON hosts on AWS for Bangladeshi companies, usually in Mumbai or Singapore, and invoices in taka. There is no AWS Region in Bangladesh. Ping times are not published on this page.
It scales with compute, storage and egress. There is no price table here until a sourced “from” list exists. Use the BDT calculator for an estimate, then ask for a quote. CloudFront is up to 40% below list; compute and storage typically 15–35%.
Yes. Servers, storage and database usage arrive on one taka invoice. You do not need an AWS dollar card. Settle with TiCON, typically by bank transfer.
Yes, as an option. Fully managed is the managed-cloud scope. Self-managed under reseller billing is the other option. You can start self-run and add operations later.
No. A local VPS is one machine in one building, invoiced by that host. This page is AWS capacity with a local taka invoice. The buy page is the order conversation for sizes.
Yes. GPU instances are provisioned to the job and billed in taka. Stop them when idle. There is no public GPU price column on this page.
Yes. Copy, TLS, DNS cutover, rollback. A larger estate belongs on the migration page. Typical brochure-site moves are days, not months — still quoted, not a published SKU.