本文属于机器翻译版本。若本译文内容与英语原文存在差异，则一律以英文原文为准。

# 示例：对多账户应用程序进行建模
<a name="next-gen-modeling-example-multiacccount"></a>

此示例展示了如何在下一代 Resilience Hub 中对一个拥有 10 个账户的 30 项服务的大型电子商务平台进行建模。

**为多账户应用程序建模**

1. **在中央账户中创建系统。**

   首先创建一个代表整个电子商务平台的单一系统。在您的中央治理账户中创建系统并启用跨账户共享：

   ```
   aws resiliencehubv2 create-system \
     --name "acme-ecommerce" \
     --description "Acme Corp e-commerce platform" \
     --sharing-enabled
   ```

1. **在他们各自的账户中创建服务。**

   每个团队都在自己的账户中创建自己的服务，并引用中央系统 ARN：

   ```
   # In account A (auth team)
   aws resiliencehubv2 create-service \
     --name "auth-service" \
     --regions '["us-east-1", "us-west-2"]' \
     --permission-model '{"invokerRoleName": "AWSResilienceHubAssessmentRole"}' \
     --associated-systems '[{"systemArn": "arn:aws:resiliencehub:us-east-1:111111111111:system/acme-ecommerce:abc123"}]'
   
   # In account B (checkout team)
   aws resiliencehubv2 create-service \
     --name "checkout-service" \
     --regions '["us-east-1", "us-west-2"]' \
     --permission-model '{"invokerRoleName": "AWSResilienceHubAssessmentRole"}' \
     --associated-systems '[{"systemArn": "arn:aws:resiliencehub:us-east-1:111111111111:system/acme-ecommerce:abc123"}]'
   ```

1. **向每项服务添加输入源。**

   每个团队都会添加自己的资源发现配置：

   ```
   # Auth team adds their CloudFormation stack
   aws resiliencehubv2 create-input-source \
     --service-arn "arn:aws:resiliencehub:us-east-1:222222222222:service/auth-service:def456" \
     --resource-configuration '{"cfnStackArn": "arn:aws:cloudformation:us-east-1:222222222222:stack/auth-prod/..."}'
   
   # Checkout team adds their EKS cluster
   aws resiliencehubv2 create-input-source \
     --service-arn "arn:aws:resiliencehub:us-east-1:333333333333:service/checkout-service:ghi789" \
     --resource-configuration '{"eks": {"clusterArn": "arn:aws:eks:us-east-1:333333333333:cluster/checkout-cluster", "namespaces": ["checkout"]}}'
   ```

1. **定义用户旅程。**

   在按业务能力对服务进行分组的中央账户中创建用户旅程：

   ```
   aws resiliencehubv2 create-user-journey \
     --system-arn "arn:aws:resiliencehub:us-east-1:111111111111:system/acme-ecommerce:abc123" \
     --name "Path to purchase" \
     --description "Customer browses, adds to cart, and completes checkout"
   ```

1. **应用弹性策略。**

   创建策略并将其与服务关联：

   ```
   # Create a policy
   aws resiliencehubv2 create-policy \
     --name "mission-critical" \
     --availability-slo '{"target": 99.99}' \
     --multi-az '{"rtoInMinutes": 5, "rpoInMinutes": 1, "disasterRecoveryApproach": "ACTIVE_ACTIVE"}' \
     --multi-region '{"rtoInMinutes": 30, "rpoInMinutes": 5, "disasterRecoveryApproach": "WARM_STANDBY"}'
   
   # Associate with a service
   aws resiliencehubv2 update-service \
     --service-arn "arn:aws:resiliencehub:us-east-1:333333333333:service/checkout-service:ghi789" \
     --policy-arn "arn:aws:resiliencehub:us-east-1:111111111111:policy/mission-critical:xyz"
   ```

1. **进行评估。**

   开始对每项服务进行故障模式评估，以确定弹性差距：

   ```
   aws resiliencehubv2 start-failure-mode-assessment \
     --service-arn "arn:aws:resiliencehub:us-east-1:333333333333:service/checkout-service:ghi789"
   ```

可以逐步添加服务——从最关键的服务开始，然后随着时间的推移添加更多服务。控制台中的系统级视图在单个画布中显示跨账户的所有服务。