## Assign an AWS IAM instance profile per team

AWS Private Locations now support mapping IAM instance profiles per team with `iam-instance-profiles-by-team-id`, so you no longer have to share a single wide-scope profile across every team:

```hocon
control-plane {
  locations = [
    {
      id = "<location-id>"
      type = "aws"
      iam-instance-profile = "<default-profile>" # (optional)
      iam-instance-profiles-by-team-id {
        "team_00000000000000000000000000" = "<team-specific-profile>"
      }
    }
  ]
}
```

When a run's team has no entry in `iam-instance-profiles-by-team-id`, the Control Plane falls back to `iam-instance-profile`.

## Tag AWS instances with the team and test that triggered the run

AWS instances provisioned by Private and Managed locations are now tagged with `Gatling:TeamId`, `Gatling:TeamName` and `Gatling:TestId`, in addition to the existing reserved tags. Use them to attribute AWS cost and usage to the team and test that triggered a run with your own cost-allocation tooling.