Issue-365: Use amazon linux 2 AMI for ECS (if none specified)#377
Issue-365: Use amazon linux 2 AMI for ECS (if none specified)#377AndreyMarchuk wants to merge 11 commits intostelligent:developfrom
Conversation
|
@AndreyMarchuk sorry for the lazy question...have you tested this? Curious how much testing i need to do. I had assumed there would be work to update the UserData and CloudFormation::Init data in the template, but happy if this is all that was needed! |
|
While testing and checking awslogs stumbled upon new recommended CloudWatch agent: Pushed commit which includes new CloudWatch agent. I've tested on existing environment which used amazon linux (v1) by running |
|
I don't think it's safe to merge without additional testing. |
|
Awesome, i'll check it out. This looks great. One thought for you on the Public IP problem...are you allowing mu to manage the VPC or are you using a VPC target? If you are using a VPC target, then check if all the subnets you listed have |
|
Great pointer re: target subnets, indeed there was one with disabled IP auto-assign. |
|
RE: CloudWatch agent does not support %f (millisec) in timestamp...i'm fine if we lose millisecond in parsed timestamp. |
| 02_configure_cloudwatch_agent: | ||
| command: !Sub | | ||
| #!/bin/bash | ||
| sudo yum install -y https://s3.amazonaws.com/amazoncloudwatch-agent/amazon_linux/amd64/latest/amazon-cloudwatch-agent.rpm |
There was a problem hiding this comment.
The new CW agent is known to have issues with auto rotation of logs. Have you tested that ? The advantage of using the new unified agent is that it provides metrics and logging in one POST request, but are those metrics being used? It will just incur more cost in case it is left enabled without actually consuming them for alarms or monitoring.
cplee
left a comment
There was a problem hiding this comment.
can you remove all the # commented out code?
Issue #365