Deployment Guide
Qinfinite provides two deployment options to meet different customer requirements for data residency, control, and compliance.
Deployment Options
| Aspect | Qinfinite Cloud | Customer Cloud |
|---|---|---|
| Hosting | Qinfinite-managed AWS account | Customer's own cloud account (AWS, Azure) |
| Setup time | Less than 4 hours | Approximately 40 hours |
| Data residency | Qinfinite cloud environment | Customer's cloud environment |
| Management | Fully managed by Qinfinite | Setup and maintenance by Qinfinite professional services |
| Communication | HTTPS, Port 443 | HTTPS, Port 443 |
Option 1: Qinfinite Cloud Deployment
In this model, the Qinfinite instance is provisioned and managed by the Qinfinite team. A Remote Agent is deployed inside the customer network to securely collect data from infrastructure and applications.
How It Works
- Qinfinite provisions a dedicated instance on Qinfinite Cloud (SaaS)
- A Remote Agent is deployed in the customer network with access to infrastructure and applications
- The Remote Agent communicates outbound to Qinfinite Cloud over HTTPS
- All data is encrypted in transit and at rest
Data Security
- Data location: Data resides within the Qinfinite cloud environment with enterprise-grade security measures
- Encryption in transit: TLS 1.2 or above for all communications
- Encryption at rest: AES-256 encryption for all stored data
Advantages
- Quick setup -- Platform up and running in under 4 hours
- Qinfinite expertise -- Managed by the Qinfinite team for optimal performance and security
- Scalability -- Seamless resource expansion as usage grows
- Data security -- Encryption in transit and at rest included by default
RACI Matrix
| Activity | Qinfinite | Customer |
|---|---|---|
| Access to Remote Agent Host | Responsible | |
| Remote Agent Installation | Responsible | |
| Configure Remote Agent | Responsible | Assist |
| Required Firewall Port Opening | Responsible | |
| Setup Qinfinite Instance on Qinfinite Cloud | Responsible | |
| Configure Customer Application/Infra in Qinfinite | Responsible | Assist |
| Initiate Auto Discovery | Responsible | |
| Build Knowledge Graph | Responsible | |
| Validate Knowledge Graph | Assist | Responsible |
Option 2: Customer Cloud Deployment
In this model, the Qinfinite instance is set up within the customer's own cloud account. The customer grants necessary privileges to the Qinfinite professional services team, who handles setup and ongoing maintenance.
How It Works
- Customer provides a cloud account (AWS, Azure) with necessary privileges
- Qinfinite professional services installs and configures the platform
- A Remote Agent is deployed in the customer network for on-premise system access
- All data remains within the customer's cloud environment
Data Security
- Data location: The Qinfinite instance and all customer data reside within the customer's own cloud account
- Encryption: Adheres to the customer's security standards for transit and at-rest encryption
Advantages
- Customer control -- Full ownership of cloud environment and data
- Professional services expertise -- Efficient setup by the Qinfinite team
- Data privacy and compliance -- Data remains within customer's cloud, adhering to internal policies
- Scalability and flexibility -- Scale resources based on usage needs
RACI Matrix
| Activity | Qinfinite | Customer |
|---|---|---|
| Access to Qinfinite Host (Customer IaaS) | Responsible | |
| Qinfinite Platform Installation and Configuration | Responsible | |
| Qinfinite Deployment | Responsible | |
| Access to Remote Agent Host | Responsible | |
| Remote Agent Installation | Responsible | |
| Required Firewall Port Opening | Responsible | |
| Configure Customer Applications/Infrastructure in Qinfinite | Responsible | Assist |
| Initiate Auto Discovery | Responsible | |
| Build Knowledge Graph | Responsible | |
| Validate Knowledge Graph | Assist | Responsible |
Remote Agent
The Qinfinite Remote Agent (RA) is deployed in the customer network to securely collect data from infrastructure and applications.
Specifications
| Parameter | Requirement |
|---|---|
| Number of Remote Agents | Minimum 1 (varies based on the number of LANs where applications are hosted) |
| Number of VMs | Minimum 2 (for high availability) |
| VM OS | Ubuntu 22.04 LTS, RHEL 8, RHEL 9, or Amazon Linux 2 (Architecture: x86-64) |
| vCPU | 4 (minimum) |
| RAM | 32 GB (minimum) |
| Disk | 100 GB (Root Volume) + 100 GB (Data Volume) |
| Supported Protocols | TCP, HTTPS, SFTP, SNMP, SSH, REST |
| Connection to Qinfinite | HTTPS / TLS 1.2 & 1.3 |
Network Requirements
- The Remote Agent requires an outbound HTTPS connection to communicate with the Qinfinite platform
- The agent pulls data from customer systems -- no inbound connections are required from Qinfinite to the customer network
- Customer must whitelist the Qinfinite domain for outbound communication