Detach traveloka.com Route53 Private Zone from tvlk-prod VPC (Part 2)

On [1] Site-Infra team has detached traveloka.com route53 private zone from prod VPC.

The private zone had to be re-attached to VPC, since multiple services still use content-api.traveloka.com to access content services.

Based on [2], only few apr services still need to be released to remove dependency to content-api.traveloka.com. This is scheduled to be finished today.

Remaining Records

Currently traveloka.com private zone contain the following records

Re-detach traveloka.com private zone

Site-Infra team plan to re-detach traveloka.com private zone on:

Friday, 2018-08-31T1030:30:00 (UTC+7)

Impact

After private zone is detached, instances in tvlk-prod VPC that need to resolve records in traveloka.com domain will do so via our public DNS zone hosted on Cloudflare. If you use public DNS records to access internal services, do upgrade your application to use .main.tvlk.cloud records to reduce number of network hops, latency and costs.

References

[1] https://tvlk.slack.com/files/U0HKPPK8D/FCHMPQA6S/Detach_traveloka_com_Route53_Private_Zone_from_tvlk-prod_VPC
[2] https://docs.google.com/spreadsheets/d/1375OIfHtFsaPkzMhNLJIwXnKydciPn0q8g1rgLWjhtc/edit#gid=1109867493
On [1] Site-Infra team has detached traveloka.com route53 private zone from prod VPC.

The private zone had to be re-attached to VPC, since multiple services still use content-api.traveloka.com to access content services.

Based on [2], only few apr services still need to be released to remove dependency to content-api.traveloka.com. This is scheduled to be finished today.

Remaining Records

Currently traveloka.com private zone contain the following records

Re-detach traveloka.com private zone

Site-Infra team plan to re-detach traveloka.com private zone on:

Friday, 2018-08-31T1030:30:00 (UTC+7)

Impact

After private zone is detached, instances in tvlk-prod VPC that need to resolve records in traveloka.com domain will do so via our public DNS zone hosted on Cloudflare. If you use public DNS records to access internal services, do upgrade your application to use .main.tvlk.cloud records to reduce number of network hops, latency and costs.

References

[1] https://tvlk.slack.com/files/U0HKPPK8D/FCHMPQA6S/Detach_traveloka_com_Route53_Private_Zone_from_tvlk-prod_VPC
[2] https://docs.google.com/spreadsheets/d/1375OIfHtFsaPkzMhNLJIwXnKydciPn0q8g1rgLWjhtc/edit#gid=1109867493