Update Route53 the right way, with a text config file that you can version. Use your existing revision control & user permissions, then let the tool convert your human-understandable config into all the right AWS jargon.
npm install -g sync53
Usage: sync53 [options] [command]
Commands:
import [options] [<zones>...] Import DNS information from Route53
check <config> Validate <config>
diff <config> [<zones>...] Diff Route53 against <config>
commit <config> [zones...] Commit <config> to Route53
clean <config> [<zones>...] List stale records in Route53
Options:
-h, --help output usage information
-V, --version output the version number
-v, --verbose Verbose output
--silent Silent output (only errors)
--proxy <proxy> URL to proxy requests through
-k, --key <key> AWS Access Key
-s, --secret <secret> AWS Secret
If you define the AWS_ACCESS_KEY_ID
&
AWS_SECRET_ACCESS_KEY
in your environment you won't need to constantly specify them on the CLI.
zones...
is available to optionally filter the zones being imported/exported, it does exact matching for now.
Running sync53 import -o <file>
will give you a local JSON (with comment support) config file.
{
"zones" : {
"example.com" : {
// Records below that don't specify a `ttl` property will inherit this one
"ttl" : "5 minutes",
"records" : {
// Simplest possible record, single resources IP
"example.com" : {
"A" : "127.0.0.1"
},
// Records with multiple entries use an array
"multiple.example.com" : {
"A" : [
"127.0.0.2",
"127.0.0.3",
"127.0.0.4"
],
"ttl" : "10 days"
},
// Simple aliases to records in the same zone use a bare `alias` property
// Since aliases can't be differentiated from a resource an
// explicit type field is required
"alias.example.com" : {
"type" : "A",
"alias" : "example.com"
},
// Multiple records for a single DNS entry are coalesced into an array
"latency.example.com" : [{
...
}, {
...
}]
}
},
"otherdomain.com" : { ... },
"anotherone.net" : { ... }
}
}
(Other examples of available config options are available in the examples folder)
Changes made to this local config can then be written back to Route53 using sync53 commit
.
Tracked in the issues
The MIT License (MIT)
Copyright (c) 2014 Patrick Cavit
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
sync53's People
Forkers
me2dsync53's Issues
Examples in README
The readme needs some examples now that the config format is settling down.
import could save out most-common TTL at the top level
It would make a more streamlined config for people, and shouldn't be hard to do as a final step in the import
process.
Support for Health Checks
Need to figure out how to support health checks and what that means for everything.
Standardize on diff2 instead of diff
Having two diffing solutions is weird.
Unify error handling
Right now it's a weird mishmash of thrown errors, async error strings being turned into thrown errors, and lord knows what else. Should standardize on a way to handle that stuff that looks a bit nicer and is more consistent.
Limit ChangeBatches & batch them if necessary
Route53 has a hard cap on the number of changes allowed in a single ChangeBatch. We should check that client-side & batch them up into multiple calls if necessary.
Support for CloudFront aliases
Right now only in-zone aliases are supported, need to investigate what a cloudfront alias even looks like.
commit should use diff2 and only send changed records
It doesn't hurt to send everything, but it is a little gross.
read-config step should validate the read config automatically
To ensure that we never start operating on an invalid config. This is already true for broken (non-parseable) configs, but should also be true for configs that are of the wrong format as validated by joi
.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.