Alternatives to Consul Enterprise in Atlas
The hosted Consul Enterprise in Atlas will be deprecated on March 7th, 2017. The functionality was not widely used, and there are strong alternatives available. As a user of Consul Enterprise, you must take action to replace its functionality with alternatives. Most importantly as a user of Consul auto-join, you must take action to remove -atlas-join from all Consul configurations and replace it with an alternative. Potential options are listed below.
For users on AWS the -retry-join-ec2 configuration options allow bootstrapping by automatically discovering AWS instances with a given tag key/value at startup. For users not on AWS the native -join and retry-join functionality can be used.
For users on GCP, the -retry-join-gce configuration options allow bootstrapping by automatically discovering GCP instances with a given tag at startup.
Note that the AWS and GCP join options do not apply to WAN-join which must be done with standard -join-wan options.
For users not on AWS or GCP, the native -join and retry-join functionality can be used.
The other features of Consul Enterprise, the UI and Alerts, have suitable open source alternatives.
For replacing alerts, we recommend the open source Consul alerts daemon. This is not maintained by HashiCorp, however there is active development from the community.
You received a bill last week for October usage of Consul Enterprise, that is your final bill. You will not be billed during the deprecation period. The features of Consul Enterprise are not going away, rather they will be packaged as a binary that can be run on private infrastructure. To keep up-to-date on the private version of Consul Enterprise, sign up here.
Please let us know if you have any questions at firstname.lastname@example.org.