AWS Route53 Catalog

I Tried AWS Route53 (External DNS) from Rancher’s Catalog and noticed that the service “assumable” is for Route53 alone, calls other DNS providers (in rancher catalog)…

Is this normal? Why would a catalog dedicated for Route53, be calling other provider’s API?

UPDATE: Just got a conversation with Darren about this and was confirmed that it’s only reading env file but not querying any external endpoints.