(MAINT) Fix issue where an exception triggers another exception
(MAINT) Fix issue where an exception triggers another exception

This is a copy-paste bug. Route53 is a global service (it's DNS), unlike
all the other services which are scoped to region. This is rarely seen,
but a user managing a large number of records hit it a few times. This
should mean when the exception occurs a useful error message is produced
rather than getting Error: Failed to apply catalog: undefined local
variable or method `region' for.

zvymazal/puppetlabs-aws,daveseff/puppetlabs-aws,marksyme/puppetlabs-aws,gregohardy/puppetlabs-aws,rfletcher/puppet-aws,puppetlabs/puppetlabs-aws,gregohardy/puppetlabs-aws,DavidS/puppetlabs-aws,hundredacres/puppetlabs-aws,zleswomp/puppetlabs-aws,daveseff/puppetlabs-aws,puppetlabs/puppetlabs-aws,marksyme/puppetlabs-aws,zvymazal/puppetlabs-aws,DavidS/puppetlabs-aws,benpillet/puppetlabs-aws,benpillet/puppetlabs-aws,rfletcher/puppet-aws,hundredacres/puppetlabs-aws,zleswomp/puppetlabs-aws