10/22 4/25 800MM Big Six* USA Technology Company CapEx *Apple, NVIDIA, Microsoft, Alphabet, Amazon (AWS only), & Meta Platforms Source: Capital IQ (3/25), Morgan Stanley 2014 2024 CapEx, $B +63% $212B deepest, and deploy it widest. *Hyperscalers (large data center operators) are Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform (GCP), Alibaba Cloud, Oracle Cloud Infrastructure (OCI) Amazon, & Meta Platforms / Facebook. Only AWS CapEx & revenue shown for Amazon (i.e. excludes Amazon retail CapEx). AWS CapEx estimated per Morgan Stanley – equals AWS net additions to property & equipment

machineIt's a VM. Classic EC2 instance in de‐ fault setting. Resources: EC2SecurityGroup: Type: AWS:: EC2:: SecurityGroup Properties: GroupName: Launch-wizard-13 GroupDescription: So that's the story about secured SSH server.Simple fix Resources: EC2SecurityGroup: Type: AWS:: EC2:: SecurityGroup Properties: GroupName: Launch-wizard-13 GroupDescription: be maintained – bastion host become single point of failure solution two - ssm – to be precise AWS System Manager Session Manager – sessions based on secure bi-directional channel – traffic is encrypted

虚拟机和容器相互访问 Linkerd 1.* 天然支持 Envoy 天然支持 Istio 开始准备支持，后 来实质性取消，基 本只有k8s好用 Linkerd 2.0 只支持k8s AWS app mesh 支持虚拟机，而且 可以虚拟机和容器 相互访问 ServiceMesh主流产品对虚拟机的支持情况Part 3：ServiceMesh灵魂拷问三：要不要支持虚拟机？ Linkerd 3：ServiceMesh灵魂拷问三：要不要支持虚拟机？ Linkerd 1.* Envoy AWS App Mesh Google Traffic Director Istio Linkerd 2.* 支持 支持 不支持 第二个转折做何解？ App Mesh：我原以为只有我这长相的会背叛革 命，想不到你这浓眉大眼的家伙也背叛革命了。 AWS App Mesh Google Traffic DirectorPart Google在ServiceMesh标准化上表现异常：而标准化是供应商不锁定的基石 Part 4：ServiceMesh灵魂拷问四：说好的供应商不锁定呢？ AWS：我原以为只有我这长相的会背叛革命， 想不到你这浓眉大眼的家伙也背叛革命了。 AWS Google SMI出来之前： • Istio迟迟未贡献给CNCF • Istio API 是私有API，未见有标准化动作 • Envoy xDS

enabled AWS EC2 �→ now uses IMDSv2 as the default information, see documentation. 2.2.1.7 Security • BR supports AWS IMDSv2 #16443 @pingyu When deploying TiDB on Amazon EC2, BR supports AWS Instance Metadata Service Version 2 (IMDSv2). You can configure example result is as follows: 154 export TIDB_HOST='{host}' # e.g. gateway01.ap-northeast-1.prod.aws. �→ tidbcloud.com export TIDB_PORT='4000' export TIDB_USER='{user}' # e.g. xxxxxx.root export TI

enabled AWS EC2 �→ now uses IMDSv2 as the default information, see documentation. 2.2.1.7 Security • BR supports AWS IMDSv2 #16443 @pingyu When deploying TiDB on Amazon EC2, BR supports AWS Instance Metadata Service Version 2 (IMDSv2). You can configure example result is as follows: 149 export TIDB_HOST='{host}' # e.g. gateway01.ap-northeast-1.prod.aws. �→ tidbcloud.com export TIDB_PORT='4000' export TIDB_USER='{user}' # e.g. xxxxxx.root export TI

400GB SSD tikv-server x3 c5d.4xlarge 16 vCPU 32 GB mem 400GB SSD tidb-server x3 All tests are done in AWS TiDB environment: TiKV configuration modifications: https://gist.github.com/c4pt0r/b0c39f9da9360af2fb2c41ace274b30e dm-worker dm-worker Demo 1. Launch an empty TiDB cluster 2. Import data to AWS Aurora (TPC-H sample data) a. http://download.pingcap.org/tispark-sample-data.tar.gz 3. Deploy DM a `dm-master` 4. Launch `dm-master` 5. Launch `dm-worker` 6. use `dmctl` create a synchronization task (AWS Aurora->TiDB) a. Sample task: https://gist.github.com/c4pt0r/bcbf645ab475e5a603ad3d79d95c1757 7. Run

example result is as follows: 127 export TIDB_HOST='{host}' # e.g. gateway01.ap-northeast-1.prod.aws. �→ tidbcloud.com export TIDB_PORT='4000' export TIDB_USER='{user}' # e.g. xxxxxx.root export TI The example result is as follows: export TIDB_HOST='{host}' # e.g. gateway01.ap-northeast-1.prod.aws. �→ tidbcloud.com export TIDB_PORT='4000' export TIDB_USER='{user}' # e.g. xxxxxx.root export TI The example result is as follows: export TIDB_HOST='{host}' # e.g. gateway01.ap-northeast-1.prod.aws. �→ tidbcloud.com export TIDB_PORT='4000' export TIDB_USER='{user}' # e.g. xxxxxx.root export TI

example result is as follows: 124 export TIDB_HOST='{host}' # e.g. gateway01.ap-northeast-1.prod.aws. �→ tidbcloud.com export TIDB_PORT='4000' export TIDB_USER='{user}' # e.g. xxxxxx.root export TI The example result is as follows: export TIDB_HOST='{host}' # e.g. gateway01.ap-northeast-1.prod.aws. �→ tidbcloud.com export TIDB_PORT='4000' export TIDB_USER='{user}' # e.g. xxxxxx.root export TI The example result is as follows: export TIDB_HOST='{host}' # e.g. gateway01.ap-northeast-1.prod.aws. �→ tidbcloud.com export TIDB_PORT='4000' export TIDB_USER='{user}' # e.g. xxxxxx.root export TI

example result is as follows: 124 export TIDB_HOST='{host}' # e.g. gateway01.ap-northeast-1.prod.aws. �→ tidbcloud.com export TIDB_PORT='4000' export TIDB_USER='{user}' # e.g. xxxxxx.root export TI The example result is as follows: export TIDB_HOST='{host}' # e.g. gateway01.ap-northeast-1.prod.aws. �→ tidbcloud.com export TIDB_PORT='4000' export TIDB_USER='{user}' # e.g. xxxxxx.root export TI The example result is as follows: export TIDB_HOST='{host}' # e.g. gateway01.ap-northeast-1.prod.aws. �→ tidbcloud.com export TIDB_PORT='4000' export TIDB_USER='{user}' # e.g. xxxxxx.root export TI