Deprecation of LOC Services in Shared Accounts

Overview

As part of LOC migration to separate AWS accounts we need your help to ensure all services connecting to LOC have connected to multi account instances so that we're save to decommission infra on tvlk-dev and tvlk-prod.

Impact

If you use any of the following backend services (through RPC, SNS, and more) or public API, you are impacted by this project. If you don't connect to any of these services and APIs, you are not impacted by this project.

Backend services:

locgs
locgi
locrich
locwh
locgepa (formerly usrgepa)

Public API:

All API under *.loc.traveloka.com domain

This also includes LOC dashboard od.loc.traveloka.com

Plan

12 March 2021 : Confirming no more usage on tvlk-prod LOC services
15 March 2021 : Decommissioning tvlk-dev infra & turning off tvlk-prod infra
22 March 2021 : Decommissioning tvlk-prod infra

What do you need to do?

For connections to LOC backend services, make sure your service has been listed on this document and notify @Edo Fanuel or @Yosef so that we can allow inbound connection from our side
For connections to LOC public APIs, you will need to change your code to use new staging endpoint (see this document for the new endpoints). Production endpoint is the same with the exception of locrapi.loc.traveloka.com moving to location.loc.traveloka.com

Should you have any further questions / concerns, please let us know on #loc-multiaccount-migration. Thanks!