I got my blog here for a long time. Moving from stand-alone into Docker containers, moving those from AWS to GC to Linode servers, and now to AWS again. At least for the time being.
The new part is that the new blog won’t be WordPress anymore, but in order to carry over the old blog, I simply copied it via the awesome HTTrack
The new location also changes the domain: https://harald.aws.qw2.org/wordpress/index.html
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
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:
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 ec2.aws.XXX. accordingly.
Here the needed batch file (stored in the file “dnsupdate.json”)
{
"Comment": "Updating my EC2 instance DNS record",
"Changes": [
{
"Action": "UPSERT",
"ResourceRecordSet": {
"Name": "ec2.aws.XXX.",
"Type": "A",
"TTL": 300,
"ResourceRecords": [
{
"Value": "34.207.167.92"
}
]
}
}
]
}
Pitfall 1: “Name” is the full FQDN. Get your current IP via
curl http://169.254.169.254/latest/meta-data/public-ipv4
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: dnsupdate.json ^