## HashiCorp ## Consul及Consul Connect介绍 Service Mesh Made Easy 劉宇雷-Hashicorp Solutions Engineer ## Agenda 1. 服務網格是什麼？簡要歷史回顧 2. 什麼是Consul，它如何工作？ 3. 演示: 如何在非容器化的環境下使用Consul的服務網格 4. 問&答 ## 簡要歷史回顧： 89e6/p19_1.jpg) Consul Connect Architecture 通過intentions實現 聲明式網絡安全互 聯  Consul Connect Architecture 基於PKI services, start using it for service discovery. ## Walk Turn on Consul Connect and secure traffic between services. ## ? Run Connect multiple datacenters, incorporate both Kubernetes and legacy environments

access to EC2 (for developers) ## Agenda – introduction – EC2 in native environment – 3-tier architecture intro – alternative methods of resource connection: – Bastion host - SSM – EC2 Instance Connect Classic EC2 instance in default setting. ## Resources: EC2SecurityGroup: Type: AWS:: EC2:: SecurityGroup Properties: GroupName: Launch-wizard-13 GroupDescription: Allow traffic to EC2 SecurityGroupIngress: _2.jpg) Resources: EC2SecurityGroup: Type: AWS:: EC2:: SecurityGroup Properties: GroupName: Launch-wizard-13 GroupDescription: Allow traffic to EC2 SecurityGroupIngress: - CidrIp: 3.145.12.1/32 IpProtocol:

启动 AMAZON CLOUDFORMATION 堆栈.....6 配置部署参数.....7 使用 APACHE ROCKETMQ.....13 APACHE ROCKETMQ 在 EC2 上部署所在目录说明：.....13 Nameserver :.....13 Broker:.....13 如何使用浏览器查看 APACHE ROCKETMQ 的 WEB CONSOLE 对 AMAZON WEB SERVICES 客户需要在 AMAZON WEB SERVICES 上使用 RocketMQ 的需求，我们开发了一键部署的方案，帮助客户快速的在自己的账号部署一个基于 EC2 的高可用的 RocketMQ 集群。 ## 架构 AMAZON CloudFormation 提供了一种创建和管理相关 AMAZON WEB SERVICES 资源的简便方法，并通过有序且可预 Nameserver 互为备份，三个 Broker Instance 每个 Broker Instance 上面启动三个 Broker 实例，每个 Broker 实例会在三个 Broker Instance 之间形成一个基于 Raft 的高可用 dledger 集群，如果其中一个 Broker 实例因故障无法提供服务，Raft 协议会自动在另外两个 Instance 中选择一个作为 Master 继续提供服

Full release notes Highlights: - 2.27.0 Introduced a new upgrade tool to help migrating your instance to a newer version. - The client and broker now use SLF4J for their logging API. - The broker details. If upgrading an existing broker instance rather than creating a new instance, some configuration etc updates will be necessary for the brokers existing instance /etc and /bin files. You can use the configuration files and scripts for an existing broker instance. The broker.xml and data are left in place as-is. You should back up your existing broker instance before running the command. The command can be

lost. Let's also imagine there are many consumers on the order queue - each representing an instance of an order processing component - these can be on different physical machines but consuming from XML Schemas used to validate ActiveMQ Artemis configuration files ## Creating a Broker Instance A broker instance is the directory containing all the configuration and runtime data, such as logs and data data files, associated with a broker process. It is recommended that you do not create the instance directory under $ \{ARTEMIS_HOME\} $ . This separation is encouraged so that you can more easily upgrade

lost. Let's also imagine there are many consumers on the order queue - each representing an instance of an order processing component - these can be on different physical machines but consuming from XML Schemas used to validate ActiveMQ Artemis configuration files ## Creating a Broker Instance A broker instance is the directory containing all the configuration and runtime data, such as logs and data data files, associated with a broker process. It is recommended that you do not create the instance directory under $ \{ARTEMIS\_HOME\} $ . This separation is encouraged so that you can more easily upgrade

lost. Let's also imagine there are many consumers on the order queue - each representing an instance of an order processing component - these can be on different physical machines but consuming from XML Schemas used to validate ActiveMQ Artemis configuration files ## Creating a Broker Instance A broker instance is the directory containing all the configuration and runtime data, such as logs and data data files, associated with a broker process. It is recommended that you do not create the instance directory under $ \{ARTEMIS\_HOME\} $ . This separation is encouraged so that you can more easily upgrade

lost. Let's also imagine there are many consumers on the order queue - each representing an instance of an order processing component - these can be on different physical machines but consuming from XML Schemas used to validate ActiveMQ Artemis configuration files ## Creating a Broker Instance A broker instance is the directory containing all the configuration and runtime data, such as logs and data data files, associated with a broker process. It is recommended that you do not create the instance directory under \($\{ARTEMIS\_HOME\}$ . This separation is encouraged so that you can more easily upgrade

AMAZON CLOUDFORMATION 堆栈 ..... 7 配置部署参数 ..... 8 使用 APACHE ROCKETMQ ..... 15 APACHE ROCKETMQ 在 EC2 上部署所在目录说明： ..... 15 Nameserver ..... 15 Broker ..... 16 如何使用浏览器查看 APACHE ROCKETMQ 的 WEB CONSOLE 具有低延迟，金融级高可用以及厂商中立的特点，目前广泛使用于国内外的互联网公司。针对亚马逊云科技客户需要在亚马逊云科技上使用 RocketMQ 的需求，我们开发了一键部署的方案，帮助客户快速的在自己的账号部署一个基于 EC2 的高可用的 RocketMQ 集群。 ## 架构 Amazon CloudFormation 提供了一种创建和管理相关 AMAZON WEB SERVICES 资源的简便方法，并通过有序且可预 Nameserver 互为备份，三个 Broker Instance 每个 Broker Instance 上面启动三个 Broker 实例，每个 Broker 实例会在三个 Broker Instance 之间形成一个基于 Raft 的高可用 dledger 集群，如果其中一个 Broker 实例因故障无法提供服务，Raft 协议会自动在另外两个 Instance 中选择一个作为 Master 继续提供服

lost. Let's also imagine there are many consumers on the order queue - each representing an instance of an order processing component - these can be on different physical machines but consuming from XML Schemas used to validate ActiveMQ Artemis configuration files ## Creating a Broker Instance A broker instance is the directory containing all the configuration and runtime data, such as logs and data data files, associated with a broker process. It is recommended that you do not create the instance directory under $ \ \{ ARTEMIS\_HOME \} $ . This separation is encouraged so that you can more easily