OEM partner
AWS
Public cloud infrastructure
Amazon Web Services is one of the two public cloud platforms we build on for cloud migration, hosting and architecture work.
Part of our IT and digital services work.
EC2 compute — pick by deployment size
Within EC2 compute, here's roughly where each tier fits. Exact model and configuration are confirmed when you request a quote.
Small / dev-test
T-family burstable instances
Low, steady baseline compute that can burst for occasional spikes — good for small apps and dev/test.
Enterprise / production
M and C-family instances
General-purpose and compute-optimized instances for steady production workloads.
Data center / hybrid
AWS Outposts
AWS-managed infrastructure that runs in your own data center for strict latency or data-residency needs.
AWS product families we work with
EC2 compute
CloudVirtual server instances for general-purpose and specialized workloads.
- Instance types for general-purpose, compute- or memory-heavy workloads
- Scales up or down with actual demand instead of fixed hardware
- Pairs with auto-scaling for variable-traffic applications
Best for: Businesses moving server workloads off fixed on-premises hardware.
S3 and EBS storage
CloudObject and block storage for primary data, backups and archives.
- S3 for object storage — files, backups, static assets
- EBS for block storage attached directly to compute instances
- Tiered storage classes for cost-sensitive archival data
Best for: Businesses needing scalable storage without buying physical capacity.
Managed relational databases and data-warehouse analytics.
- Managed relational databases without manual patching and backups
- Data-warehouse-scale analytics for larger reporting workloads
- Reduces the database administration burden on internal staff
Best for: Businesses wanting managed databases instead of self-hosted ones.
Planning and executing migration from on-premises to AWS.
- Phased migration planning, not a single risky cutover
- Cost modeling before migration, not after the bill arrives
- Ongoing management once workloads are live on AWS
Best for: Businesses planning to move some or all infrastructure off-premises.
Why source AWS through Tanrova Rise
- We architect for your actual workload and budget, not the default service tier.
- Migration planned in phases with a working rollback plan, not a risky one-shot cutover.
- Ongoing cost and performance monitoring after go-live, not just a one-time migration project.
AWS — frequently asked questions
- Should we choose AWS or Microsoft Azure?
- Both are credible, mature platforms; the right one often comes down to what you're already using (Microsoft 365, on-prem Windows Server) and where your team's existing skills sit. We support both and will recommend based on your environment, not a fixed preference.
- How do you control AWS costs from growing unpredictably?
- Through right-sizing instances to actual usage, reserved or savings-plan pricing for predictable workloads, and ongoing cost monitoring after go-live — not just an architecture review at the start.
- Can we move to AWS gradually, or does it have to be all at once?
- Gradually, in most cases — a phased, hybrid approach (some workloads on AWS, some still on-premises during transition) is usually lower-risk than a single cutover, and we plan migrations that way by default.