hashicorp/demo-consul-cloud-map
1
0
Fork 0
mirror of https://github.com/hashicorp/demo-consul-cloud-map synced 2026-04-05 18:52:16 +00:00
Code Issues Projects Releases Packages Wiki Activity
No description
145 commits 1 branch 0 tags 8.6 MiB
  • Smarty 47%
  • HCL 45.6%
  • Makefile 5.2%
  • Shell 2.2%
Find a file
Exact
Rosemary Wang 69fd10a331 Update toggle
2019-12-03 16:49:59 -08:00
consul_config Revert "Fix API on AWS" 2019-12-03 15:20:00 -08:00
diagrams Fixed API on AWS 2019-12-02 09:12:11 -08:00
templates Update API with error rate 2019-11-22 15:08:35 -05:00
.gitignore Update with docs 2019-11-19 12:44:48 -05:00
api.tf Add toggles 2019-12-01 11:57:58 -08:00
cloud-map.tf Update with api-on-aws service 2019-11-21 16:16:51 -05:00
consul-server.tf Update to use EIP as output and add WAN security group 2019-11-20 10:35:18 -05:00
database.tf Rename everything and pass datacenter to API configuration 2019-11-18 15:22:33 -05:00
delete-cloud-map.sh Add deletion for cloud map 2019-11-12 11:28:38 -05:00
Makefile Update key before testing 2019-12-01 18:07:44 -08:00
network.tf Update to allow mesh gateway traffic 2019-11-20 17:12:47 -05:00
outputs.tf Update web_aws toggle 2019-11-22 16:10:52 -05:00
README.md Remove docs, update premise on README.md 2019-11-21 17:08:59 -05:00
shared-services.tf Move shared services VM into 3rd subnet 2019-11-18 16:19:28 -05:00
terraform.tf Update with hashicorp organization and workspace 2019-11-12 12:52:44 -05:00
tester.tf Add toggle for enabling web on AWS 2019-11-22 08:42:46 -05:00
toggles.tf Update toggle 2019-12-03 16:49:59 -08:00
variables.tf Move toggles out of variables 2019-11-22 16:32:29 -05:00
web.tf Use consul proxy for api 2019-12-01 12:02:14 -08:00

README.md

Consul Service Mesh

is a distributed networking layer to connect, secure and observe services across AWS and corporate datacenter.

Here, we'll demonstrate how we can use Consul Service Mesh to automate and scale service networking and security within a corporate datacenter and into AWS, using AWS Cloud Map.

Pre-Requisites

Premise

Our organization has been in the process of refactoring select applications and hosting them into AWS. We have the following general architectural approach:

  • Minimize downtime due to refactor during migration.
  • Use an AWS managed service, when possible.

We decided to start on a particularly challenging 3-tier application in our datacenter, complete with web, API, and database.

  1. We cannot migrate web since it behaves as a thick client application and our users would be disrupted by a new UI without proper communication and testing.
  2. We cannot migrate database in order to better assess the data and PII stored on it.

As a result, we decide to migrate the API first.