本文為英文版的機器翻譯版本，如內容有任何歧義或不一致之處，概以英文版為準。
# AWS FIS 實驗範本範例
如果您使用 AWS FIS API 或命令列工具來建立實驗範本，您可以在 JavaScript 物件標記法 (JSON) 中建構範本。如需實驗範本元件的詳細資訊，請參閱 [AWS FIS 實驗範本元件](experiment-templates.md)。
若要使用其中一個範例範本建立實驗，請將其儲存至 JSON 檔案 （例如 `my-template.json`)，以您自己的值取代*斜體*的預留位置值，然後執行下列 [create-experiment-template](https://docs.aws.amazon.com/cli/latest/reference/fis/create-experiment-template.html) 命令。
```
aws fis create-experiment-template --cli-input-json file://my-template.json
```
**Topics**
+ [根據篩選條件停止 EC2 執行個體](#stop-instances-filters)
+ [停止指定數量的 EC2 執行個體](#stop-instances-count)
+ [執行預先設定的 AWS FIS SSM 文件](#cpu-fault-injection)
+ [執行預先定義的 Automation Runbook](#run-automation-runbook)
+ [具有目標 IAM 角色的 EC2 執行個體上的調節 API 動作](#inject-api-throttle)
+ [Kubernetes 叢集中 Pod 的壓力測試 CPU](#stress-test)
+ [指定 Kinesis Data Streams 數量的佈建輸送量例外狀況](#throughput-kinesis)
+ [實驗角色許可範例](#permissions-example)
## 根據篩選條件停止 EC2 執行個體
下列範例會停止指定區域中所有執行中的 Amazon EC2 執行個體，並在指定的 VPC 中具有指定的標籤。它會在兩分鐘後重新啟動它們。
```
{
"tags": {
"Name": "StopEC2InstancesWithFilters"
},
"description": "Stop and restart all instances in us-east-1b with the tag env=prod in the specified VPC",
"targets": {
"myInstances": {
"resourceType": "aws:ec2:instance",
"resourceTags": {
"env": "prod"
},
"filters": [
{
"path": "Placement.AvailabilityZone",
"values": ["us-east-1b"]
},
{
"path": "State.Name",
"values": ["running"]
},
{
"path": "VpcId",
"values": [ "vpc-aabbcc11223344556"]
}
],
"selectionMode": "ALL"
}
},
"actions": {
"StopInstances": {
"actionId": "aws:ec2:stop-instances",
"description": "stop the instances",
"parameters": {
"startInstancesAfterDuration": "PT2M"
},
"targets": {
"Instances": "myInstances"
}
}
},
"stopConditions": [
{
"source": "aws:cloudwatch:alarm",
"value": "arn:aws:cloudwatch:us-east-1:111122223333:alarm:alarm-name"
}
],
"roleArn": "arn:aws:iam::111122223333:role/role-name"
}
```
## 停止指定數量的 EC2 執行個體
下列範例會停止具有指定標籤的三個執行個體。 AWS FIS 會選取要隨機停止的特定執行個體。它會在兩分鐘後重新啟動這些執行個體。
```
{
"tags": {
"Name": "StopEC2InstancesByCount"
},
"description": "Stop and restart three instances with the specified tag",
"targets": {
"myInstances": {
"resourceType": "aws:ec2:instance",
"resourceTags": {
"env": "prod"
},
"selectionMode": "COUNT(3)"
}
},
"actions": {
"StopInstances": {
"actionId": "aws:ec2:stop-instances",
"description": "stop the instances",
"parameters": {
"startInstancesAfterDuration": "PT2M"
},
"targets": {
"Instances": "myInstances"
}
}
},
"stopConditions": [
{
"source": "aws:cloudwatch:alarm",
"value": "arn:aws:cloudwatch:us-east-1:111122223333:alarm:alarm-name"
}
],
"roleArn": "arn:aws:iam::111122223333:role/role-name"
}
```
## 執行預先設定的 AWS FIS SSM 文件
下列範例使用預先設定的 AWS FIS SSM 文件，在指定的 EC2 執行個體上執行 CPU 故障注入 60 秒，[AWSFIS-Run-CPU-Stress](actions-ssm-agent.md#awsfis-run-cpu-stress). AWS FIS 會監控實驗 2 分鐘。
```
{
"tags": {
"Name": "CPUStress"
},
"description": "Run a CPU fault injection on the specified instance",
"targets": {
"myInstance": {
"resourceType": "aws:ec2:instance",
"resourceArns": ["arn:aws:ec2:us-east-1:111122223333:instance/instance-id"],
"selectionMode": "ALL"
}
},
"actions": {
"CPUStress": {
"actionId": "aws:ssm:send-command",
"description": "run cpu stress using ssm",
"parameters": {
"duration": "PT2M",
"documentArn": "arn:aws:ssm:us-east-1::document/AWSFIS-Run-CPU-Stress",
"documentParameters": "{\"DurationSeconds\": \"60\", \"InstallDependencies\": \"True\", \"CPU\": \"0\"}"
},
"targets": {
"Instances": "myInstance"
}
}
},
"stopConditions": [
{
"source": "aws:cloudwatch:alarm",
"value": "arn:aws:cloudwatch:us-east-1:111122223333:alarm:alarm-name"
}
],
"roleArn": "arn:aws:iam::111122223333:role/role-name"
}
```
## 執行預先定義的 Automation Runbook
下列範例會使用 Systems Manager、AWS-PublishSNSNotification 提供的 Runbook 將通知發佈至 Amazon SNS。 [PublishSNSNotification](https://docs.aws.amazon.com/systems-manager-automation-runbooks/latest/userguide/automation-aws-publishsnsnotification.html) 角色必須具有將通知發佈至指定 SNS 主題的許可。
```
{
"description": "Publish event through SNS",
"stopConditions": [
{
"source": "none"
}
],
"targets": {
},
"actions": {
"sendToSns": {
"actionId": "aws:ssm:start-automation-execution",
"description": "Publish message to SNS",
"parameters": {
"documentArn": "arn:aws:ssm:us-east-1::document/AWS-PublishSNSNotification",
"documentParameters": "{\"Message\": \"Hello, world\", \"TopicArn\": \"arn:aws:sns:us-east-1:111122223333:topic-name\"}",
"maxDuration": "PT1M"
},
"targets": {
}
}
},
"roleArn": "arn:aws:iam::111122223333:role/role-name"
}
```
## 具有目標 IAM 角色的 EC2 執行個體上的調節 API 動作
下列範例會針對目標定義中指定的 IAM 角色 (IAM) 發出的 API 呼叫，調節 動作定義中指定的 100% API 呼叫。
**注意**
如果您想要以屬於 Auto Scaling 群組的 EC2 執行個體為目標，請改用 **aws：ec2：asg-insufficient-instance-capacity-error** 動作，並以 Auto Scaling 群組為目標。如需詳細資訊，請參閱[aws:ec2:asg-insufficient-instance-capacity-error](fis-actions-reference.md#asg-ice)。
```
{
"tags": {
"Name": "ThrottleEC2APIActions"
},
"description": "Throttle the specified EC2 API actions on the specified IAM role",
"targets": {
"myRole": {
"resourceType": "aws:iam:role",
"resourceArns": ["arn:aws:iam::111122223333:role/role-name"],
"selectionMode": "ALL"
}
},
"actions": {
"ThrottleAPI": {
"actionId": "aws:fis:inject-api-throttle-error",
"description": "Throttle APIs for 5 minutes",
"parameters": {
"service": "ec2",
"operations": "DescribeInstances,DescribeVolumes",
"percentage": "100",
"duration": "PT2M"
},
"targets": {
"Roles": "myRole"
}
}
},
"stopConditions": [
{
"source": "aws:cloudwatch:alarm",
"value": "arn:aws:cloudwatch:us-east-1:111122223333:alarm:alarm-name"
}
],
"roleArn": "arn:aws:iam::111122223333:role/role-name"
}
```
## Kubernetes 叢集中 Pod 的壓力測試 CPU
下列範例使用 Chaos Mesh 對 Amazon EKS Kubernetes 叢集中的 Pod CPU 進行壓力測試一分鐘。
```
{
"description": "ChaosMesh StressChaos example",
"targets": {
"Cluster-Target-1": {
"resourceType": "aws:eks:cluster",
"resourceArns": [
"arn:aws:eks:arn:aws::111122223333:cluster/cluster-id"
],
"selectionMode": "ALL"
}
},
"actions": {
"TestCPUStress": {
"actionId": "aws:eks:inject-kubernetes-custom-resource",
"parameters": {
"maxDuration": "PT2M",
"kubernetesApiVersion": "chaos-mesh.org/v1alpha1",
"kubernetesKind": "StressChaos",
"kubernetesNamespace": "default",
"kubernetesSpec": "{\"selector\":{\"namespaces\":[\"default\"],\"labelSelectors\":{\"run\":\"nginx\"}},\"mode\":\"all\",\"stressors\": {\"cpu\":{\"workers\":1,\"load\":50}},\"duration\":\"1m\"}"
},
"targets": {
"Cluster": "Cluster-Target-1"
}
}
},
"stopConditions": [{
"source": "none"
}],
"roleArn": "arn:aws:iam::111122223333:role/role-name",
"tags": {}
}
```
下列範例使用 Litmus 對 Amazon EKS Kubernetes 叢集中的 Pod CPU 進行壓力測試一分鐘。
```
{
"description": "Litmus CPU Hog",
"targets": {
"MyCluster": {
"resourceType": "aws:eks:cluster",
"resourceArns": [
"arn:aws:eks:arn:aws::111122223333:cluster/cluster-id"
],
"selectionMode": "ALL"
}
},
"actions": {
"MyAction": {
"actionId": "aws:eks:inject-kubernetes-custom-resource",
"parameters": {
"maxDuration": "PT2M",
"kubernetesApiVersion": "litmuschaos.io/v1alpha1",
"kubernetesKind": "ChaosEngine",
"kubernetesNamespace": "litmus",
"kubernetesSpec": "{\"engineState\":\"active\",\"appinfo\":{\"appns\":\"default\",\"applabel\":\"run=nginx\",\"appkind\":\"deployment\"},\"chaosServiceAccount\":\"litmus-admin\",\"experiments\":[{\"name\":\"pod-cpu-hog\",\"spec\":{\"components\":{\"env\":[{\"name\":\"TOTAL_CHAOS_DURATION\",\"value\":\"60\"},{\"name\":\"CPU_CORES\",\"value\":\"1\"},{\"name\":\"PODS_AFFECTED_PERC\",\"value\":\"100\"},{\"name\":\"CONTAINER_RUNTIME\",\"value\":\"docker\"},{\"name\":\"SOCKET_PATH\",\"value\":\"/var/run/docker.sock\"}]},\"probe\":[]}}],\"annotationCheck\":\"false\"}"
},
"targets": {
"Cluster": "MyCluster"
}
}
},
"stopConditions": [{
"source": "none"
}],
"roleArn": "arn:aws:iam::111122223333:role/role-name",
"tags": {}
}
```
## 指定 Kinesis Data Streams 數量的佈建輸送量例外狀況
下列範例會針對 100% 具有指定標籤的最多五個 Kinesis Data Streams 請求擲出佈建輸送量例外狀況。 AWS FIS 會隨機選取要影響的串流。5 分鐘後會移除故障。
```
{
"description": "Kinesis stream experiment",
"targets": {
"KinesisStreams-Target-1": {
"resourceType": "aws:kinesis:stream",
"resourceTags": {
"tag-key": "tag-value"
},
"selectionMode": "COUNT(5)"
}
},
"actions": {
"kinesis": {
"actionId": "aws:kinesis:stream-provisioned-throughput-exception",
"description": "my-stream",
"parameters": {
"duration": "PT5M",
"percentage": "100",
"service": "kinesis"
},
"targets": {
"KinesisStreams": "KinesisStreams-Target-1"
}
}
},
"stopConditions": [
{
"source": "none"
}
],
"roleArn": "arn:aws:iam::111122223333:role/role-name",
"tags": {},
"experimentOptions": {
"accountTargeting": "single-account",
"emptyTargetResolutionMode": "fail"
}
}
```
## 實驗角色許可範例
下列許可可讓您對影響 50% 請求的特定串流執行 `aws:kinesis:stream-provisioned-throughput-exception`和 `aws:kinesis:stream-expired-iterator-exception`動作。
```
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "kinesis:InjectApiError",
"Resource": "*"
"Condition": {
"ForAllValues:StringEquals": {
"kinesis:FisActionId": [
"aws:kinesis:stream-provisioned-throughput-exception",
"aws:kinesis:stream-expired-iterator-exception"
],
"kinesis:FisTargetArns": [
"arn:aws:kinesis:us-east-1:111122223333:stream/stream-name"
],
},
"NumericEquals": {
"kinesis:FisInjectPercentage": "50"
}
}
},
{
"Action": [
"kinesis:DescribeStreamSummary",
],
"Resource": "*",
"Effect": "Allow"
}
]
}
```