To provide you with dedicated AWS accounts and increase agility of the engineering product teams, Site-infra needs your help getting rid of an ancient technical debt blocking our progress in creating decentralized Multi-Account Infrastructure Platform.
Legacy use of traveloka.com domain for resolution of private IPs inside our shared production network (e.g. mongodata01.traveloka.com) is blocking communication to products/services running in dedicated AWS accounts.
This means you won't be able to reach public APIs of products hosted in dedicated accounts (e.g. api.txt.traveloka.com) from a server running in shared production network until we completely stop all use of traveloka.com domain to resolve private IP addresses. To reiterate: ALL production use of domain traveloka.com to resolve private IPs must stop before we can start building services/products in new AWS accounts.
I have drafted an implementation plan and created a tracking spreadsheet to help us with implementation. I hope the effort required on your part is minimal, but I also fear this will take at least some time to complete. I have drawn up a rough timeline, but I expect I will be able to make it more realistic with your feedback and comments.
Best regards!