Master Credentials & Endpoints Directory
📌 What is this for? (Quick Summary)​
In simple words: This is the master phone book and key ring for our entire system. It lists all the internet addresses (endpoints), database tokens, AWS Cognito account numbers, and
.envconfiguration keys that the apps need to connect and talk to each other. Keep this confidential.
CONFIDENTIAL • For authorized engineering team members only.
1. Cloud Endpoints Directory​
| Service / Resource | Value / Endpoint | Protocol / Region |
|---|---|---|
| API Gateway (BFF Router) | https://npig3gpgck.execute-api.ap-south-1.amazonaws.com/api | HTTPS (ap-south-1) |
| Cognito User Pool ID | ap-south-1_IXNCZVwj4 | ap-south-1 |
| Cognito App Client ID | 5eup0104notrn3fn4415u3fq3b | Public SPA |
| AWS Account ID | 897421226959 | Mumbai (ap-south-1) |
| MediaMTX Video Server | https://cam.tutr.tech:8889 (WebRTC) / :8554 (RTSP) | TLS / WebRTC |
| Production 2D Dashboard | https://dashboard.tutr.tech | CloudFront / HTTPS |
| InfluxDB Cloud Endpoint | https://influxdb.tutr.tech | Org: TuTr, Bucket: telemetry |
| Edge Testbed IP | 3.108.234.172 (Go: :20006, Web: :5001) | AWS EC2 Linux |
2. InfluxDB Authentication Token​
- Organization:
TuTr - Bucket:
telemetry - Read/Write Query Token:
C2QDhajxjliitod_eO64Wxi20DRARqeVPbc9FhB8bRayr2k6Np-I7yF_nhmaDbUGhhznZzvA1CbFIPguodA-Gg==
3. Standard .env File Reference​
To configure any new client dashboard clone (2D or 3D), create a .env file in the project root:
# AWS API Gateway Backend Router Endpoint
VITE_MAIN_API_URL=https://npig3gpgck.execute-api.ap-south-1.amazonaws.com/api
# AWS Cognito Authentication (Production User Pool)
VITE_COGNITO_CLIENT_ID=5eup0104notrn3fn4415u3fq3b
VITE_USER_POOL_ID=IXNCZVwj4
VITE_REGION=ap-south-1
# MediaMTX WebRTC (WHEP) Camera Stream Server
VITE_CAMERA_BASE_URL=https://cam.tutr.tech:8889
4. Documentation Portal Hardcoded Credentials​
- Portal URL:
http://localhost:3000(orhttps://apidocs.tutr.tech) - Username:
tutr - Password:
Tutr@tech1