Closed MikeTheCanuck closed 6 years ago
There are/may be better ways to accomplish the upgrade steps indicated above, I will test them out in my account and document. Killing off the instance manually probably added to the issues we had after clearing up the instance that had memmory spce issues.
Once we are up on a newer image version, we will be able to change the cloudformation template to auto magically update when ever the template is run after the recommended image version has been updated:
Parameters:
ECSAMI:
Description: AMI ID
Type: AWS::SSM::Parameter::Value
The latest image is:
ami-d2f489aa amzn-ami-2018.03.a-amazon-ecs-optimized
Rest of check list items not needed. as soon as change set is executed on the cloudformation template change, the autoscaler will migrate the instance to the new AMI image. May need to manually re-balance depending on timing since the placement strategy option will not be available until we are on the latest AMI .
merge pull request 35 submitted.
Closing, resolved by mereged PR
Current AMI used by the EC2 hosts that are carrying the load of our ECS containers is one last updated 2016-09.
This is where the update needs to happen: https://github.com/hackoregon/hackoregon-aws-infrastructure/blob/master/infrastructure/ecs-cluster.yaml#L59
Intended Benefits
ToDo