Dec 022017

Whoa…AWS is not joking when saying that in AWS Simple Queue Service the order is not guaranteed. I send in this (in exactly that order):

100, 101, 102, 103, 104, 105, 106, 107, 108, 109

and I receive this:

108, 102, 106, 101, 105, 109, 100, 103, 104, 107


 Posted by at 21:26  Tagged with:
Nov 052017
AWS - Route53 and your own IP

AWS is functionally very nice, but the docs are…improvable. Thus the need for me to write down things which should be simple but are not:

Updating DNS Records

Very easy to do in the GUI. Tricky the first time you try this from the aws CLI.

I got a delegated zone aws.XXX. (I own XXX and i delegated aws.XXX. to AWS Route53) and when I boot my (special) EC2 instance, I’d like it to update the DNS record accordingly.

Here the needed batch file (stored in the file “dnsupdate.json”)

  "Comment": "Updating my EC2 instance DNS record", 
  "Changes": [ 
      "Action": "UPSERT", 
      "ResourceRecordSet": { 
        "Name": "", 
        "Type": "A", 
        "TTL": 300, 
        "ResourceRecords": [ 
            "Value": "" 

Pitfall 1: “Name” is the full FQDN. Get your current IP via


Then update via aws CLI:

aws route53 change-resource-record-sets --hosted-zone-id Z1KXXXXXXXXXX \
--change-batch file:///home/ec2-user/dnsupdate.json

Pitfall 2: The batch file location MUST NOT be the simple “dnsupdate.json” but it MUST BE “file://absolute/path/to/the/file.json”. Otherwise you get the totally unhelpful error message

aws route53 change-resource-record-sets --hosted-zone-id Z1KXXXXXXXXXX \
--change-batch dnsupdate.json                        

Error parsing parameter '--change-batch': Expected: '=', received: 'EOF' for input: