Infrastructure, Security, and Configuration Guide
Welcome to your dedicated private cloud environment. This guide outlines how we host, protect, and route traffic to your application instance using an Instance-Based Architecture within Amazon Web Services (AWS).
Unlike standard software-as-a-service (SaaS) systems where multiple companies share the same servers and databases, your organization receives a completely isolated, single-tenant environment.
1. What is an Instance-Based Account?
An instance-based account means your software runs on its own dedicated virtual infrastructure. Your data, application code, and processing power are entirely separated from all other clients.
Key Business Benefits:
Zero Co-Mingling of Data: Your databases and file storage are structurally isolated. There is no physical or logical path for another client's system to interact with yours.
Predictable Performance: Your system does not suffer from the "noisy neighbor" effect. 100% of the allocated server processing power, memory, and database speed belong exclusively to your users.
Custom Maintenance Windows: Because your system is standalone, updates, patches, and maintenance can be scheduled around your specific business hours rather than a global pool.
2. Secure Subdomain Routing
Your isolated environment is mapped directly to a dedicated web address of your choice, typically a subdomain of your primary corporate domain:
yourcompany.medialakeapp.com
How Traffic Flows Securely:
When your team visits this address, a highly secure, automated routing process takes place:
Encrypted Handshake: Connection is established via strict HTTPS using TLS 1.3 encryption. Your traffic is encrypted from the moment it leaves a user's browser until it reaches your cloud perimeter.
Web Application Firewall (WAF): Before hitting your servers, incoming requests pass through a dedicated security layer that filters out malicious traffic, bots, and potential cyber threats.
Private Load Balancing: A dedicated load balancer receives the clean traffic and routes it to your application servers. These servers live inside a Private Subnet—meaning they are completely invisible and inaccessible directly from the public internet.
3. Data Protection & Security Matrix
We employ a defense-in-depth approach to ensure your private cloud remains resilient and compliant.
Encryption at Rest: All data written to your dedicated databases or cloud storage drives is encrypted automatically using industry-standard AES-256 bit encryption.
Continuous Backups: Full system and database snapshots are taken automatically every 24 hours and retained securely. These backups are also encrypted and isolated.
High Availability: Your application is distributed across multiple AWS Availability Zones (isolated physical data centers within the region). If one data center experiences an infrastructure failure, your traffic automatically reroutes to the surviving zone instantly with no data loss.
4. Next Steps & Onboarding Setup
To activate your environment, our engineering team needs to link your preferred subdomain to the private cloud infrastructure.
We will provide you with a CNAME (Canonical Name) record. Your internal IT or network administrator will simply need to add this single record to your company’s DNS management console (such as GoDaddy, Cloudflare, or Route 53).
Example Configuration:
Type:CNAME
Host/Name:app(or your preferred prefix)
* Value/Target:dedicated-lb-12345.amazonaws.com
Once this record is published, your private instance will go live under your corporate identity.