A Consul Service Mesh Integration Case Study With Presto
summary
A case study that integrates Presto with Consul Connect by adding a tiny Presto plugin that consumes Consul Connect native integration and uses mutual TLS plus an authorization call to Consul intentions, leaving the control plane untouched. The pipeline runs locally under Nomad with MinIO and a Hive metastore, shows Presto coordinator plus two workers serving SELECTs from TPCH-generated data, enforces ACLs via a proxy that denies or allows per-intention, and concludes the approach is secure, scalable, and implemented in a few lines of plugin code.
AI-written summary · about
chapters (17)
- 0:00Introduction and platform question
- 3:15Presto and Consul as core components
- 5:28Introducing the presenters
- 6:12Agenda and key personas
- 9:46Managing change and simplicity
- 11:15Consul Connect integration basics
- 12:41Challenges with opinionated systems
- 14:08Consul Connect native integration
- 15:35Integrating Presto with Consul
- 18:01Architecture improvements and PR
- 19:05Working with bleeding edge
- 19:27Secure Presto demo setup
- 21:57Granting access via intentions
- 23:07Final Presto demo walkthrough
- 24:37Denying access and policy control
- 25:01Key takeaways and simplicity
- 26:30Open source and enterprise options
related talks
49mEnterprise service networking with HashiCorp Consul and AWS (PRT238)
44mStretching the Service Mesh Beyond the Clouds
15mLightning Talk: Automate and Secure Consul Service Mesh on AWS ECS
49mPresto in the Cloud
36mGlobal Visibility and Control for Consul
25mConsul Terraform Sync - Awesome Use Cases
40mBuilding a Modern Infrastructure Stack
22mConsul Product Updates and Vision - HashiConf 2022