> For the complete documentation index, see llms.txt.
Skip to main content

Check out Port for yourself ➜ 

Infrastructure and network security

Port hosts its infrastructure on Amazon Web Services (AWS). This page describes the architecture, network controls, and recovery processes that protect your service.

Architecture overview​

The diagram shows Port's cloud-hosted infrastructure, the components you host yourself, and the third-party services you connect. It also shows the protocol for each connection.

Port architecture diagram showing Port's AWS cloud-hosted infrastructure with microservices on EKS, data stores and Kafka, alongside customer hosted Port integrations and the Port agent, and the connections between them and third-party SaaS products

Notes:

  • Port's geographical tenants are separate: the US tenant uses us-east-1, and the EU tenant uses eu-west-1. You can choose which tenant to use.
  • Port application - AWS CloudFront exposes https://app.port.io and its US equivalent, https://app.us.port.io, globally through a content delivery network (CDN).
  • Port API gateway - Port hosts a commercial Traefik API gateway in its cloud network and exposes https://api.port.io and its US equivalent, https://api.us.port.io, through an AWS Application Load Balancer (ALB).
  • Amazon Relational Database Service (RDS), MongoDB, Kafka, and all other backends encrypt data using a Port-managed AWS Key Management Service (KMS) key (AES-256).
  • All resources, including databases, Kafka, and Amazon Elastic Kubernetes Service (EKS), span multiple availability zones (AZs).
  • The environment is multi-tenant: multiple accounts share the same backends, including databases and microservices, with complete logical segregation, role-based access control (RBAC), and token separation.
  • Kafka is publicly available. Each customer connects using dedicated credentials and has access control list (ACL) permissions to read dedicated Kafka topics.
  • Each customer has a dedicated Kafka topic with messages scoped to that customer. Messages follow a consistent format and include a signature you can validate using your secret credentials to confirm they originated from Port.
  • Customer-hosted Port integrations are part of the Ocean integration framework. They make outbound-only requests to Port's API gateway and populate your catalog in Port.
  • All HTTPS communication enforces Transport Layer Security (TLS) 1.2 or later. Port has a roadmap item to enforce TLS 1.3 across all HTTPS communication.
  • All HTTPS communication uses REST APIs.
  • All HTTPS communication uses port 443.
  • The depicted architecture requires no inbound connections to your environment.
  • You can use inbound connections as an alternative to the Port agent. In that case, Port routes one-way requests to your environment through a network address translation (NAT) gateway, using the following fixed static IP addresses: 44.221.30.248, 44.193.148.179, 34.197.132.205, 3.251.12.205, 34.252.219.131, and 54.75.236.107.

Physical access control​

AWS data centers use physical security and access controls, including:

  • Alarms.
  • Recorded closed-circuit television (CCTV) footage from server rooms.
  • Perimeter fencing.
  • Intrusion detection systems.
  • Biometrics and multi-factor authentication.

Port employees do not have physical access to AWS data centers, servers, network equipment, or storage.

Logical access control​

Port is the sole administrator of its AWS infrastructure. Only designated, authorized Port operations team members can configure it, on an as-needed basis, through a virtual private network (VPN) protected by multi-factor authentication.

Port uses a separate VPN for each environment and completely segregates test, staging, and production environments.

Intrusion detection​

Port uses Amazon GuardDuty as its intrusion detection system (IDS). GuardDuty uses signature-based and algorithm-based detection to identify traffic patterns similar to known attack methods.

Rate limiting and traffic control​

Port uses AWS WAF as its web application firewall, in addition to AWS's built-in denial-of-service (DoS) and distributed denial-of-service (DDoS) protections.

AWS WAF protects against known bot attacks and uses custom rules to enforce rate limiting and control unwanted traffic.

Business continuity and disaster recovery​

High availability​

Port uses redundant, appropriately provisioned servers throughout the service, including multiple load balancers, web servers, and replica databases. This redundancy maintains availability if a server fails. Port can also take servers out of operation for regular maintenance without affecting availability.

Business continuity​

Port maintains a formal business continuity plan (BCP) for extended service outages caused by unforeseen or unavoidable disasters. The plan aims to restore services as broadly as possible within a reasonable time frame.

Port documents disaster recovery policies and procedures for recovering or continuing vital technology infrastructure and systems. You can request Port's BCP policy.

Disaster recovery​

Port maintains encrypted backups in multiple AWS regions in accordance with its recovery point objectives. For a region-wide outage, Port has a documented protocol to deploy a duplicate environment in another AWS region.

The Port operations team performs an annual disaster recovery (DR) simulation to keep the process current with changes to Port.