anchor.diff:  ### My instances don’t start the buildkite-agent
   
   Ensure your AMI has been [configured to auto-login as the ec2-user](#build-an-ami)
  -in the GUI. The buildkite-agent launchd job configuration requires an `Aqua`
  -session type to allow your pipelines to use Xcode and the iOS Simulator.
  +in the GUI. To allow your pipelines to use Xcode and the iOS Simulator the
  +Buildkite Agent launchd job configuration requires an `Aqua` session type.
  
positive.code: 
  ## Starting your Buildkite Agents
  
  Once you have successfully deployed the template, use the template Resources tab
  to find the Auto Scaling Group. Edit the Auto Scaling Group and set the Desired
  Capacity to the number of instances you require.
  
  The Auto Scaling Group will automatically provision Dedicated Hosts using the
  Host Resource Group and boot instances on them. The Launch Template’s `UserData`
  script will install, configure, and start the Buildkite Agent.
  
  Caveat the use of dynamic scaling policies on the Auto Scaling Group, instances
  are slow to boot and slow to terminate. Consider using Scheduled Scaling Rules.
  
  ## F.A.Q.
  
  ### My ASG doesn’t launch any instances
  
  
negative.code: 
  We have built a [CloudFormation template](https://github.com/buildkite/elastic-mac-for-aws)
  that configures an Auto Scaling group, Launch Template, and Host Resource Group
  suitable for maintaining a pool of EC2 `mac1.metal` instance based Buildkite
  Agents. These agents can be used to run Buildkite Pipelines that build Xcode
  based software projects for macOS, iOS, iPadOS, tvOS, and watchOS.
  
  As you must prepare and supply your own AMI for this template, macOS support has
  **not** been incorporated into the Elastic CI Stack for AWS.
  
  Using an Auto Scaling group for your instances ensures booting your macOS
  Buildkite Agents is repeatable, and provides automatic instance replacement when
  hardware failures occur.
  
  