[optional] --check-interval=1m / CHECK_INTERVAL How often should we check AWS RDS for changes (examples: 30s, 1h, 1h10m, 1d)
[optional] --consul-service-prefix / CONSUL_SERVICE_PREFIX Prefix your Consul service name with this string.
[optional] --consul-service-suffix / CONSUL_SERVICE_SUFFIX Suffix your Consul service name with this string.
[optional] --instance-filter key=value / INSTANCE_FILTER Service dependent key/value for filtering on instance properties - Can be used multiple times as CLI argument
[optional] --tag-filter key=value / TAG_FILTER Service dependent key/value for filtering on instance tags - Can be used multiple times as CLI argument
[optional] --on-duplicate-service=ignore-skip-last / ON_DUPLICATE_SERVICE What to do if duplicate services are found in RDS (e.g. multiple instances with same DB name or consul_service_name tag and same RDS Replication Role. (quit, ignore, ignore-skip-last)
Service: RDS
Will every check-interval check AWS RDS for changes in the topologies and instances and update the Consul service catalog accordingly
RDS : Config
[optional] --consul-node-name=rds / CONSUL_NODE_NAME Name the Consul catalog node that all checks will belong to
[optional] --consul-master-tag=master / CONSUL_MASTER_TAG The Consul Service tag to use for RDS master instances
[optional] --consul-replica-tag=replica / CONSUL_REPLICA_TAG The Consul service tag to use for RDS replica instances
[optional] --rds-tag-cache-time=30m / RDS_TAG_CACHE_TIME The time RDS tags should be cached (examples: 30s, 1h, 1h10m, 1d)