You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ERROR] InvalidChangeBatch: An error occurred (InvalidChangeBatch) when calling the ChangeResourceRecordSets operation: [RRSet with DNS name ........ is not permitted in zone ......]
#38
Closed
emiioan opened this issue
Aug 2, 2021
· 4 comments
Hello tried the code you provided as example but records are not created. Lambda logs:
[ERROR] InvalidChangeBatch: An error occurred (InvalidChangeBatch) when calling the ChangeResourceRecordSets operation: [RRSet with DNS name . is not permitted in zone ...]
Traceback (most recent call last):
File "/var/task/autoscale.py", line 144, in lambda_handler
process_record(record)
File "/var/task/autoscale.py", line 136, in process_record
process_message(json.loads(record['Sns']['Message']))
File "/var/task/autoscale.py", line 132, in process_message
update_record(zone_id, ip, hostname, operation)
File "/var/task/autoscale.py", line 87, in update_record
route53.change_resource_record_sets(
File "/var/runtime/botocore/client.py", line 357, in _api_call
return self._make_api_call(operation_name, kwargs)
File "/var/runtime/botocore/client.py", line 676, in _make_api_call
raise error_class(parsed_response, operation_name)
The text was updated successfully, but these errors were encountered:
emiioan
changed the title
[ERROR] IndexError: list index out of range Traceback (most recent call last): File "/var/task/autoscale.py", line 144, in lambda_handler process_record(record)
[ERROR] InvalidChangeBatch: An error occurred (InvalidChangeBatch) when calling the ChangeResourceRecordSets operation: [RRSet with DNS name ........ is not permitted in zone ......]
Aug 2, 2021
I had that error, too. The module mismatches foo.id, foo.name and foo.arn at some places. Check the generated policy, I think you'll find a wrong ARN like arn:aws:route53::: arn:aws:route53:::foo/bar. (When you have fixed that, you'll find the next mistake where the module expects a zone id but the module's description says you need an ARN. (sorry, I mismatched this with a different error.)
Hi @emiioan, it looks like the problem here is that you're not creating a fully qualified domain name inside of the asg:hostname_pattern tag, which is preventing the Route 53 record from being created. Here is an example of how this would work -
It's worth noting as well that #instanceid is interpolated by the lambda function to the instance_id of the AWS instance that is created. I will update the documentation to make this more clear.
Hello tried the code you provided as example but records are not created. Lambda logs:
code:
The text was updated successfully, but these errors were encountered: