Deployment of Gamelift Container Fleet fails with error about ManagedCapacityConfiguration

Question

Since today, when attempting to deploy a CloudFormation template defining a Gamelift Contianer fleet, the deployment fails at the final stage of fleet creation.

The full error I am seeing is as follows:

Failed resources:
container-fleet-stack-dev | 15:25:42 | CREATE_FAILED        | AWS::GameLift::ContainerFleet | container-fleet-1 (containerfleet1) Resource handler returned message: "Unauthorized input 'ManagedCapacityConfiguration' provided (Service: GameLift, Status Code: 400, Request ID: d138ae30-c498-48ce-9435-44bd76c6ac1f) (SDK Attempt Count: 1)" (RequestToken: 63042174-7c7d-fffe-160f-4fc8764aa910, HandlerErrorCode: AccessDenied)
❌  container-fleet-stack-dev failed: ToolkitError: The stack named container-fleet-stack-dev failed creation, it may need to be manually deleted from the AWS console: ROLLBACK_COMPLETE: Resource handler returned message: "Unauthorized input 'ManagedCapacityConfiguration' provided (Service: GameLift, Status Code: 400, Request ID: d138ae30-c498-48ce-9435-44bd76c6ac1f) (SDK Attempt Count: 1)" (RequestToken: 63042174-7c7d-fffe-160f-4fc8764aa910, HandlerErrorCode: AccessDenied)

This is how the scaling/capacity is defined in the synthesized template:

"InstanceType": "m6g.medium",
    "Locations": [
     {
      "Location": "eu-west-1",
      "LocationCapacity": {
       "DesiredEC2Instances": 1,
       "MaxSize": 5,
       "MinSize": 1
      }
     },
     {
      "Location": "us-east-1",
      "LocationCapacity": {
       "DesiredEC2Instances": 1,
       "MaxSize": 5,
       "MinSize": 1
      }
     },
     {
      "Location": "eu-central-1",
      "LocationCapacity": {
       "DesiredEC2Instances": 1,
       "MaxSize": 5,
       "MinSize": 1
      }
     }
    ],
    "LogConfiguration": {
     "LogDestination": "S3",
     "S3BucketName": {
      "Ref": "gameliftcontainerlogbucket8F9715A5"
     }
    },
    "NewGameSessionProtectionPolicy": "FullProtection",
    "ScalingPolicies": [
     {
      "EvaluationPeriods": 1,
      "MetricName": "PercentAvailableGameSessions",
      "Name": "TargetBasedScalingPolicy",
      "PolicyType": "TargetBased",
      "TargetConfiguration": {
       "TargetValue": 50
      }
     }
    ],

There is no mention of ManagedCapacityConfiguration anywhere.

The template worked fine until today. Is this an AWS issue?

SG · Accepted Answer

This was caused by the recent operational issue affecting eu-west-1, which was described as impacting containers and adjacent workflows. The issue is no longer occuring now that its been resovled.

re:Post Agent · Answer

Based on the error message you're seeing, it appears that there's an issue with the "ManagedCapacityConfiguration" parameter in your GameLift Container Fleet deployment, even though it's not explicitly defined in your template.

This error suggests one of two possibilities:

1. There might be an internal AWS service issue where the GameLift service is incorrectly interpreting your scaling configuration as a ManagedCapacityConfiguration parameter.

2. There could be a recent change in the GameLift service that affects how container fleet scaling is configured, and your template might need to be updated to align with these changes.

Since you mentioned that this template was working fine until today, and you're not explicitly defining ManagedCapacityConfiguration anywhere, this does suggest a potential issue on the AWS side.

For your scaling configuration, you're using a target-based scaling policy with PercentAvailableGameSessions as the metric and a target value of 50, which is a valid configuration. Your location capacities are also properly defined with desired, minimum, and maximum EC2 instances.

I would recommend:

1. Checking the AWS GameLift service health dashboard or recent announcements for any known issues
2. Contacting AWS Support to report this issue, providing them with the error message and request ID
3. As a temporary workaround, you might try deploying with a different scaling policy type or configuration to see if that resolves the issue

Since this appears to be a sudden change in behavior for a previously working template, it's reasonable to suspect a service-side issue.  
**Sources**  
[AWS::GameLift::ContainerFleet TargetConfiguration - AWS CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-gamelift-containerfleet-targetconfiguration.html)  
[AWS::GameLift::ContainerGroupDefinition - AWS CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-gamelift-containergroupdefinition.html)

Deployment of Gamelift Container Fleet fails with error about ManagedCapacityConfiguration

Add your answer

Relevant content