Fully backwards compatible in terms of credential mechanisms (environment variables, shared credentials file, EC2 metadata). If a custom AWS IAM policy is in use it needs to be updated with permissions for the route53:ListHostedZonesByName action.
