3 ms·
We've (Epio) been using Route53 for 6 months or so now, and have had zero problems with it. The main problem is, as others have said, that the only way to inter
by andrewgodwin 15y ago
We've (Epio) been using Route53 for 6 months or so now, and have had zero problems with it. The main problem is, as others have said, that the only way to interact with it is via the (somewhat cumbersome) API.
We got round this by writing our own Python command-line tool using Boto, which sadly I have yet to release...
- kelleyk 15y agoI've been using the wonderful cli53 (available on GitHub here: https://github.com/barnybug/cli53 https://github.com/barnybug/cli53). All I have to type is "cli53 import example.com --file example.bind --replace --wait" and it'll replace all of the records for example.com with what's in the BIND file, and the --wait makes it poll Amazon until the "pending changes" go through.
- andrewgodwin 15y agoAh, now that looks useful - thanks! And it supports AAAA records, thankfully.
- sayhello 15y agoYou can use a web-based ui here: https://www.interstate53.com/ https://www.interstate53.com/ It is free, pretty well done and they haven't stolen my AWS credentials yet.
- zackfern 15y agoI'm a developer at the company who makes Interstate53, and I have to say your comment made me smile. I assure you we're not logging any credentials and strive to keep our users happy. It's been a really fun project.