Skip to content
  • New: asasii S2 handheld barcode scanner. 1D and 2D, IP52 rated.View S2
  • asasii POS is live and deploying to Malaysian retailers.See asasii POS
  • asasii BSC: supply chain software for multi-outlet operators.See asasii BSC
  • Browse the full asasii hardware line: terminals, printers, scanners, payment, drawers.View hardware
idataraya
idataraya

Cloud Architecture.

Cloud infrastructure designed around your operational model.

We design and deploy cloud architecture on AWS, Google Cloud, and Azure. We pick the right services for your workload, not the ones with the best marketing. Landing zones, networking, IAM, cost controls, and operational tooling, built for Malaysian businesses that need production-grade infrastructure without a six-month procurement cycle.

  • Multi-cloud architecture across AWS, Google Cloud, and Azure
  • Landing zone design with IAM, networking, and security baselines
  • Cost optimization and reserved capacity planning
  • Infrastructure as code with Terraform and Pulumi
landing-zone · ap-southeastApplied
  • VPC3 AZ · /16
  • IAMbaseline
  • GuardrailsSCP · CIS
  • Cost alertsconfigured
Region utilization · workloadsCPU intensity · 6 services × 5 regions
sintkosydfrauseapiworkerdbcachebatchedge
Singapore hot · Frankfurt idle · rebalancing plan drafted
landing-zone · ap-southeast-1Applied
  • Account treeorg · 4 OUs
  • Networking3 AZ · /16
  • GuardrailsSCP · CIS
  • Cost alertsbudgets
tagging policy · required keysMaterialized
ownerteamrequired rows
environmentenumdev|stg|prod rows
cost_centercoderequired rows
data_classenumpub|int|conf|rstr rows
Enforced in IaC · no bypass

The right cloud.

Cloud architecture isn't about picking a vendor. It's about matching services to workloads, controlling costs, and building infrastructure your team can operate without calling us every week.

Landing zone deployed as code, not clicked in a console.

Account structure, VPC, IAM baseline, and guardrails defined in Terraform or Pulumi. Apply the same plan to AWS Organizations, GCP projects, or Azure subscriptions and get an auditable foundation out of it.

landing-zone · ap-southeast-1Applied
  • Account treeorg · 4 OUs
  • Networking3 AZ · /16
  • GuardrailsSCP · CIS
  • Cost alertsbudgets

Every resource tagged, every account traceable.

Ownership, environment, and cost-center tags applied at provision time, enforced by policy. When the bill arrives, each line has a team behind it.

tagging policy · required keysMaterialized
ownerteamrequired rows
environmentenumdev|stg|prod rows
cost_centercoderequired rows
data_classenumpub|int|conf|rstr rows
Enforced in IaC · no bypass

Cost you see before the bill arrives.

Budget alerts, reserved capacity planning, and monthly reviews so spend never surprises the CFO. Hot data stays fast, cold data drops into the tier that makes sense.

Spend · month to date
prod · computeSLO RM 18,000RM 14,210
prod · storageSLO RM 4,200RM 3,080
stg · computeSLO RM 2,500RM 2,380
egress · cross-regionSLO RM 800RM 920
Reviewed weekly · 3% under plan

Drift caught in CI, not in production.

Every plan runs before apply, every apply runs through a pipeline. If someone edits a resource in the console, the next drift check flags it and the team that owns it knows why.

terraform runs · this week
apply · prod-network #142reviewed · 2 approvers
4m 18s
apply · prod-eks #78canary
6m 02s
drift-check · prod-iammanual edit flagged
1m 12s
plan · stg-storage #41awaiting review
queued
All change via pipeline

Cloud infrastructure your team can operate.

  • Landing zone

    Production-ready account structure with IAM, networking, and security baselines, deployed as code on AWS, Google Cloud, or Azure.

  • Infrastructure code

    Terraform or Pulumi modules for every resource, stored in your repository with CI/CD pipelines for plan, apply, and drift detection.

  • Cost framework

    Tagging strategy, budget alerts, reserved capacity recommendations, and a monthly review cadence to keep spend aligned with usage.

  • Operations runbook

    Incident response procedures, scaling playbooks, and disaster recovery steps, written for the team that operates the infrastructure day to day.

Ready to talk about cloud architecture?

Book a discovery call. We will walk through how this fits your business, scope, timeline, and what you will get at the end.