You can use the IP addresses in this article to selectively open your firewalls (or public cloud equivalent, such as security groups in AWS) to allow the Treasure Data servers to reach your systems.
Data Connector IP addresses You whitelist these IP addresses to allow Treasure Data's input integrations to pull data from one of your systems. For example, to ingest data from your MySQL database.
Export Integration IP addresses You must whitelist the IP addresses that are listed in Export Integrations so that Treasure Data output integrations can push data from a query into one of your systems. For example, a Treasure Data query writes the query result to your MySQL database.
This topic contains:
- Tokyo Region Elastic IP Addresses
- US Region Elastic IP Addresses
- EU01 Region Elastic IP Addresses
- AP02 Region Elastic IP Addresses
- S3 Bucket Policy Configuration for Export and Import Integrations
52.198.232.201
52.198.68.179
13.112.195.14
52.194.115.251
54.249.135.6023.21.102.81
23.21.103.124
23.23.126.184
23.23.173.173
23.23.88.94
50.16.198.121
50.16.200.30
50.16.223.69
54.83.21.182
54.83.52.199
107.20.134.38
107.20.142.104
107.20.144.178
107.20.145.75
107.20.147.58
107.20.148.03.120.79.159
3.120.50.29
3.120.68.1552.79.160.42
54.180.65.243
15.165.210.14When your S3 bucket is in the same region as your Treasure Data endpoint, you must set a VPC ID to allow TD's access to the bucket and still restrict access.
| Region | VPC Value |
|---|---|
| TOKYO | vpc-e630c182 |
| US | vpc-df7066ba |
| EU01 | vpc-f54e6a9e |
| AP02 | vpc-00ca316f964009497 |
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "Treasure-Data-eu01-Result-Output",
"Action": [
"s3:AbortMultipartUpload",
"s3:PutObject"
],
"Effect": "Deny",
"Resource": [
"arn:aws:s3:::your-bucket",
"arn:aws:s3:::your-bucket/*"
],
"Condition": {
"StringNotEqualsIfExists": {
"aws:sourceVpc": "vpc-f54e6a9e"
}
},
"Principal": "*"
}
]
}Replace "arn:aws:s3:::your-bucket" and "arn:aws:s3:::your-bucket/*" with your actual S3 bucket's ARN.