Note
This documentation is for a prior release of Kinetica. For the latest documentation, click here.
Kinetica in AWS is automatically configured to optimize performance in the cloud environment. Noteworthy configuration features include:
- SSL enabling of native APIs and applications including Workbench & Reveal
- Role-Based Access Control (RBAC) for database objects & operations
- SQL planner with Rule-Based Optimization (RBO), fully distributed operations, and parallel query processing
- Multi-head ingest & egress
- Distributed graph servers
- Machine Learning (ML)
- User-Defined Functions (UDFs)
- Full-Text Search
- OpenGL & Level-of-Detail rendering (for GPU-based AWS deployments)
- A Disk Cache tier (DISK0), sized proportionally to the provisioned AWS deployment; and an unlimited Cold Storage tier (COLD0)
- Kinetica Distributed File System (KiFS), which hosts data files for fast database import/export
- System events, viewable through the AWS management interface
- System alerts, configurable through the AWS management interface
Features that are not part of the existing Kinetica in AWS deployments:
- Intra-cluster host failover
- Inter-cluster failover
- Vector Tile Service (VTS)
- System auditing
Default Ports
The default ports used for communication with Kinetica and various important services follow.
| Port | Function |
|---|---|
| 80 | The non-secure listener for Kinetica application & connection traffic; will redirect automatically to the secure listener on port 443 |
| 443 | The listener for applications (Workbench, Reveal, etc.) and connections (APIs, JDBC, etc.) |
| 5432 | The listener for PostgreSQL Wire Protocol connections |
| 9002 | Table monitor publishing server port. Users of database table monitors will need the ability to connect to this port to receive data generated via the table monitor. |
