- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hi @REDACTEDUSER
Yes, this is a known issue in our backlog. See doc: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-gamelift-fleet.html#cfn-gamelift-fleet-******
When creating a new fleet, GameLift automatically sets this value to "1". Once the fleet is active, you can change this value.
It's tricky to fix this because it would be a backwards-incompatible change. For instance, some people may put down a very large number for these fields currently, and if we fix the behavior as the name intended, it would break those customers due to LimitExceededException.
In the meantime, it might be possible to use CloudFormation Custom Resources to trigger a lambda to update your fleet/location capacity upon creation. See: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/template-custom-resources.html
Ok gotcha. Missed that note in the docs.
I've decided to automate this from our deployment script when stack update completes (rather than figure out Custom Resources).
Thanks!
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- Wie kann ich mithilfe von CloudFormation Laufwerksbuchstaben Amazon EBS-Volumes in Windows zuordnen?AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 10 Monaten
- AWS OFFICIALAktualisiert vor 2 Jahren