IP Addresses for Import and Export Integrations

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 Integrations

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 Integrations

When 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.

{
  "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.