consul-aws
syncs the services in an AWS CloudMap namespace to a Consul datacenter.
Consul services will be created in AWS CloudMap and the other way around.
This enables native service discovery across Consul and AWS CloudMap.
This project is versioned separately from Consul. Supported Consul versions for each feature will be noted below. By versioning this project separately, we can iterate on AWS integrations more quickly and release new versions without forcing Consul users to do a full Consul upgrade.
Download a pre-compiled, released version from the Consul-AWS releases page.
Extract the binary using unzip
or tar
.
Move the binary into $PATH
.
To compile from source, please see the instructions in the contributing section.
consul-aws
can sync from Consul to AWS CloudMap (-to-aws
), from AWS CloudMap to Consul (-to-consul
) and both at the same time.
No matter which direction is being used consul-aws
needs to be connected to Consul and AWS CloudMap.
In order to help with connecting to a Consul cluster, consul-aws
provides all the flags you might need including the possibility to set an ACL token.
consul-aws
loads your AWS configuration from .aws
, from the instance profile and ENV variables - it supports everything provided by the AWS golang sdk.
A default AWS region is not assumed.
You can specify this with the standard AWS environment variables or as part of your static credentials.
Apart from that a AWS CloudMap namespace id has to be provided. This is how consul-aws
could be invoked to sync both directions:
$ ./consul-aws sync-catalog -aws-namespace-id ns-hjrgt3bapp7phzff -to-aws -to-consul
To build and install consul-aws
locally, Go version 1.21+ is required.
You will also need to install the Docker engine:
Clone the repository:
$ git clone https://github.com/hashicorp/consul-aws.git
To compile the consul-aws
binary for your local machine:
$ make dev
This will compile the consul-aws
binary into dist/$OS/$ARCH/consul-aws
as well as your $GOPATH
.
To create a docker image with your local changes:
$ make dev-docker
If you just want to run the tests:
$ make test
Or to run a specific test in the suite:
go test ./... -run SomeTestFunction_name
Note: To run the sync integration tests, you must specify INTTEST=1
in your environment and AWS credentials.
You must also have a Consul server running locally.
consul-aws
is compatible with supported versions of Consul.
See long-term support docs for more information.