Cloud & Infrastructure
A secure, repeatable AWS environment,
built and operated by InterCloud.
Customers receive a secure account structure, repeatable deployments and monitoring that reports a problem before users are affected. InterCloud runs its own products on AWS with Terraform, containers and GitHub Actions, and builds the same foundation for you.
AWS Solutions
A Secure Foundation on AWS
The foundation is the same for a new migration to AWS and for an existing account that has grown without a plan: separated environments, identity-based access and all resources defined in code.
Landing zone
Keep environments separated and every action on record. A multi-account structure with AWS Organizations, centralized logging and audit trails, guardrails that define what each account may do, and a network design with private subnets for the data and application tiers.
Identity and secrets
Remove long-lived keys from your environment. IAM roles and SSO take their place, with least-privilege policies for people and pipelines, and application secrets held in a managed store and rotated without redeployment.
Managed data services
Recover data to a chosen point in time. Managed PostgreSQL with automated backups and point-in-time recovery, object storage with lifecycle rules, and caches and queues provisioned as code together with the application.
Edge and delivery
Protect public applications at the edge and run several on one domain. Cloudflare in front of AWS for DNS, TLS, WAF and DDoS protection, with routing rules that allow several applications to share one domain.
Backups and disaster recovery
Know that a restore works before it is needed. Backup schedules and retention periods agreed per system, restore procedures tested on a regular basis, and a written recovery plan that defines the order in which services are restored and who decides to invoke it.
Cost management
Keep cloud spending visible and reviewed every month. Tagging standards, budgets with alerts and a monthly cost review. Right-sizing, scheduling of non-production environments and reserved capacity are applied once usage patterns are known.
Container & Serverless
The Right Runtime for Each Workload, Operated the Same Way
Application services run as Docker containers on Amazon ECS, the platform behind InterCloud's own products. Each service has its own task definition, health checks, autoscaling rules and a private connection to the services it depends on, and images are built and scanned in the pipeline.
Scheduled jobs, file processing, notifications and event-driven integrations are better suited to serverless functions and managed queues. These services require no idle servers, and both capacity and cost follow actual usage.
The platform is chosen per workload and the deployment model is kept consistent, so that an engineer who knows one service can operate all of them.
- Amazon ECS with autoscaling, health checks and zero-downtime rolling updates
- Container images built, scanned and versioned in CI, stored in a private registry
- Serverless functions and managed queues for event-driven and scheduled work
- Kubernetes where an existing platform or team standard requires it
DevOps & CI/CD
A Repeatable Path From Commit to Production
The pipeline protects the product. Every change takes the same path, and releases become routine events that can be carried out during working hours.
- 1
Infrastructure as code
All AWS resources are defined in Terraform, reviewed as pull requests and applied by the pipeline. Environments are reproducible, drift is visible and no configuration depends on manual changes in a console.
- 2
Build and test
GitHub Actions runs type checks, linting, unit and integration tests and dependency scanning on every pull request. Container images are built once and promoted through the environments unchanged.
- 3
Deploy safely
Blue/green or rolling deployments on ECS with health checks, so that a faulty release does not receive traffic and a rollback is a single step. Database migrations run as versioned scripts with a tested reverse path.
- 4
Observe and improve
Deployment events are correlated with metrics and alerts in SnowTrack, so that a regression can be linked to the change that caused it. Post-incident reviews are fed back into tests and runbooks.
Monitoring & Operations
Monitoring and Operations From Go-Live
Monitoring is set up during the build phase. Infrastructure, application and business-level signals are collected in SnowTrack, our observability platform, with dashboards per service and alerts routed to the people on call.
Alerts are tuned to the agreed service level, and each alert has a runbook attached so that the person who receives it knows what to do. Alert noise is reviewed and reduced every month.
Under a managed operations agreement, InterCloud assumes on-call responsibility: patching, capacity management, incident response and a monthly report covering availability, incidents and changes. Alternatively, we hand over the setup and train your team.
- Infrastructure, application and service monitoring in SnowTrack
- Alert routing, on-call schedules and runbooks for every alert
- Centralized logs and traces with retention per compliance requirement
- Patch management, capacity reviews and a monthly operations report
- Overview
- Infrastructure
- Applications
- Services
- Logs
- Alerts
- Incidents
- Reports
System Overview
99.9%
3
42
A review of your AWS environment
For a new AWS environment or a review of an existing account, we can show you what a well-run environment looks like and the steps required to reach it.