Unexpected key 'enableFaultInjection' found in params

Question

suddenly,not able to deploy the task definition. It has "enableFaultInjection":false as default value but failing the deployment with the following error:

Error: Failed to register task definition in ECS: Unexpected key 'enableFaultInjection' found in params
Error: Unexpected key 'enableFaultInjection' found in params

Here is the screenshot of my task definition JSON:

![Enter image description here](/media/postImages/original/IMeJj7LJoGQtWq7spMPFBNEw)

Joel · Answer

You are likely using v1 of the ecs-deploy-task-defintion GitHub action, you should be using v2 as this was fixed there yesterday as well.

```
- name: Deploy Amazon ECS task definition
  uses: aws-actions/amazon-ecs-deploy-task-definition@v2
  with:
     task-definition: task-definition.json
```

oscarcrespo · Answer

this is a temporary solution that fixes this. Add it to your action script after getting task definition

```
 - name: Remove enableFaultInjection from task-definition.json
      shell: bash
      run: |
        jq 'del(.enableFaultInjection)' task-definition.json > task-definition-fixed.json
        mv task-definition-fixed.json task-definition.json
```

re:Post Agent · Answer

The error you're encountering suggests that there's an issue with the task definition JSON you're trying to deploy. The "enableFaultInjection" parameter is not a standard parameter in ECS task definitions, which is why you're seeing the "Unexpected key" error.

To resolve this issue, you should remove the "enableFaultInjection" field from your task definition JSON. This parameter is not recognized by ECS and is causing the deployment to fail.

Here are the steps you can take to fix this:

1. Edit your task definition JSON.
2. Remove the line containing "enableFaultInjection":false.
3. Save the updated task definition.
4. Try to deploy the task definition again.

If you're using some kind of infrastructure-as-code tool or template to generate this task definition, you may need to update that template to remove the "enableFaultInjection" parameter.

After removing this unexpected key, your task definition should deploy successfully, assuming there are no other issues with the configuration.

If you're wondering about the origin of this parameter, it's possible that it was inadvertently added during a copy-paste operation or through some automated process. It's not a standard ECS parameter, which is why it's causing the deployment to fail.

Remember to always validate your task definition JSON against the ECS task definition schema to catch these kinds of issues before attempting to deploy.  
**Sources**  
[ECS deployment task failed (deployed on EC2) | AWS re:Post](https://repost.aws/questions/QUvRR68auITZy6cbraAwl9kw/ecs-deployment-task-failed-deployed-on-ec2)  
[How to debug failed ECS deployment? | AWS re:Post](https://repost.aws/questions/QUWAcmJzxRQOSuDJ3GyCmTew/how-to-debug-failed-ecs-deployment)

Unexpected key 'enableFaultInjection' found in params

Relevant content