KB-1582 How to allow traffic from Appian Cloud based on IPs

Purpose

This article provides source IPs by region for traffic originating from Appian Cloud. Some examples include invoking a web service or connecting to a data source. For details on SMTP server IPs, refer to the documentation.

Adding trusted IPs to the allow list only helps determine if the traffic is coming from the Appian Cloud infrastructure as a whole. It does not help identify that traffic is coming from a specific Appian Cloud site.

Instructions

To restrict source traffic from a single Appian Cloud site, Appian strongly recommends the use of VPN tunnel integration. Doing so will negate the need for adding IP addresses to an allow list.

The recommended best practice is to add the entire set of IP ranges in a region to the allow list.

NOTE: IPs are typically added as new availability zones become available. As such, these changes generally do not impact existing customer configurations. Appian will update this document from time to time with these additions. In the event that changes are introduced that would impact existing customer configurations, Appian will update this article in advance of these changes. Customers that require immediate visibility into changes can enable notifications on this article by clicking “More” -> “Turn Notifications On”, which can be found at the end of the article. The last reviewed date can also be found at the end of the article.

Region

IPs

Jakarta

108.137.105.140

108.137.160.196

108.137.17.48

108.137.105.200

108.137.125.194

108.136.66.243

Bahrain

157.175.112.214

157.175.118.201

157.175.16.32

15.184.45.16

15.184.73.104

15.184.94.120

Cape Town

13.244.84.90

13.244.51.11

13.245.58.64

13.244.187.171

13.244.215.58

13.244.226.2

Frankfurt

52.57.200.142

52.29.179.127

52.58.4.167

18.157.232.83

18.157.244.91

18.157.246.109

GovCloud (US East)

18.253.151.83

18.253.155.40

18.253.161.224

18.252.132.43

18.254.191.247

18.254.194.149

GovCloud (US West)

96.127.33.171

96.127.33.83

52.61.75.116

52.61.141.205

52.61.165.64

52.61.9.217

Ireland

54.229.33.30

54.229.32.187

54.229.33.31

54.170.239.72

54.228.31.150

54.247.146.71

London

35.177.153.88

52.56.95.43

52.56.57.70

18.135.112.100

18.135.112.128

18.135.112.181

Milan

15.161.117.167

15.161.83.168

15.161.169.119

15.161.195.64

15.161.248.215

35.152.44.2

Montreal

52.60.99.138

52.60.94.241

15.223.58.8

15.223.139.127

99.79.11.148

99.79.98.210

Mumbai

13.233.30.20

13.235.170.135

35.154.253.168

13.234.250.247

65.1.37.209

65.1.38.88

Northern California

50.18.192.70

54.215.175.68

13.52.127.92

52.8.211.193

52.9.236.55

Northern Virginia

184.72.123.171

54.236.230.226

54.236.230.220

54.236.102.234

18.214.90.73

54.157.94.67

54.80.53.225

Ohio

52.14.52.152

52.14.72.54

52.14.68.142

3.17.170.7

3.21.211.74

3.23.245.203

Oregon

35.167.217.93

35.167.89.183

35.167.191.61

35.161.209.55

44.241.218.41

52.33.126.168

Paris

52.47.193.68

52.47.132.163

52.47.109.115

15.236.137.203

15.236.169.250

15.237.147.217

Sao Paulo

54.207.3.4

54.207.1.49

54.232.55.78

52.67.119.73

54.207.192.184

54.94.17.25

Seoul

13.124.97.200

15.164.158.203

52.78.140.120

3.35.247.76

3.36.135.226

54.180.209.143

Singapore

13.250.232.54

54.254.138.249

54.254.138.246

13.228.250.99

18.138.18.191

54.254.55.137

Stockholm

13.48.94.228

13.53.105.142

13.53.105.192

13.49.190.42

13.49.94.220

13.51.22.144

Sydney

52.63.251.183

54.252.132.145

54.252.130.176

13.237.129.206

3.106.112.168

3.24.15.63

Tokyo

3.113.196.145

52.193.143.182

52.196.184.139

52.192.201.207

54.248.54.3

54.95.243.181

UAE

3.29.75.206

51.112.0.175

51.112.68.45

Zurich

16.63.188.214

16.63.48.38

16.63.63.153

S3 VPC Endpoints

Customers using an S3 endpoint in AWS will additionally need to allow the below VPC Endpoint IDs based on their region.

Region	VPC Endpoint IDs
Jakarta	vpce-06429f85815af8964
Bahrain	vpce-03cc2b1d682a71b61
Cape Town	vpce-0240e43cfdaa7c095
Frankfurt	vpce-012b68e5ff3b97dbe
GovCloud (US East)	vpce-040ffd93e984f119f
GovCloud (US West)	vpce-088b89cc2b12e12b5
Ireland	vpce-036e3325f7e224837
London	vpce-07930232302fb4b8a
Milan	vpce-0680cfb29ed61db23
Montreal	vpce-07690c01f3eccef27
Mumbai	vpce-0108245544683380a
Northern California	vpce-0eadc11670ae028d9
Northern Virginia	vpce-0d1fb4d9322c93aa3
Ohio	vpce-03904ab496e952139
Oregon	vpce-0eb9ba21b0cc3688d
Paris	vpce-0c281fc8f19900ba2
Sao Paulo	vpce-086c542ec9661876a
Seoul	vpce-0395c066740e18a88
Singapore	vpce-0a15e37c2f0f991cd
Stockholm	vpce-027cbcc1998b6ee55
Sydney	vpce-0cffe1605b6af8c52
Tokyo	vpce-034fdee416a67751a
UAE	vpce-0fe70b95ce651f962
Zurich	vpce-0a06b91ad4f9e9bbc

PCI customers will also need to allow the below endpoint.

Northern Virginia

vpce-0debabaff048dc700

DynamoDB VPC Endpoints

Customers using a DynamoDB endpoint in AWS will additionally need to allow the below VPC Endpoint IDs based on their region.

Region	VPC Endpoint IDs
Jakarta	vpce-0a2edfefd98ae1cd3
Bahrain	vpce-02517ca8d08e6e0cf
Cape Town	vpce-04f9fb867aeee5031
Frankfurt	vpce-000b26fc9339ea99c
GovCloud (US East)	vpce-0bb9cd26c52bb402d
GovCloud (US West)	vpce-06d66da2e890d41a0
Ireland	vpce-0b910a30ef63a95c0
London	vpce-0b6c5f905da0f8efa
Milan	vpce-0c1e259c9c22fe8bf
Montreal	vpce-09d4b7814d391497b
Mumbai	vpce-098e266da86f89f60
Northern California	vpce-00c178823d60ae56f
Northern Virginia	vpce-010c209ec37834e3e
Ohio	vpce-0ce720212165746c7
Oregon	vpce-0df59396fe8568c6f
Paris	vpce-08265e399214609bc
Sao Paulo	vpce-0ba009a5018e13cd2
Seoul	vpce-0eabee28573bf10a6
Singapore	vpce-0d5390c4841cc4850
Stockholm	vpce-0c755dd572bf35ad7
Sydney	vpce-03ecdc01a602d91b2
Tokyo	vpce-0ac938e6ec4110981
UAE	vpce-0ac84e00d0765dd48
Zurich	vpce-06fb5fc5ddd4e122f

PCI customers will also need to allow the below endpoint.

Northern Virginia

vpce-0f487a2460f173149

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: April 2024