Skip to content

Fix: cloudwatch imds v2 agent execution failed with hooks#79

Open
Frtrillo wants to merge 3 commits into
rennokki:masterfrom
Frtrillo:fix-cloudwatch2
Open

Fix: cloudwatch imds v2 agent execution failed with hooks#79
Frtrillo wants to merge 3 commits into
rennokki:masterfrom
Frtrillo:fix-cloudwatch2

Conversation

@Frtrillo

Copy link
Copy Markdown

Command execution wasn't processed at correct time so it couldn't fetch the laravel_logs.json settings to execute the command
Fix issues: #77, #74

@Frtrillo

Copy link
Copy Markdown
Author

okay can confirm its working and fixed

@rennokki

rennokki commented Oct 7, 2022

Copy link
Copy Markdown
Owner

@Frtrillo Can you add a comment in the topside of each file to reference each-other to not forget to uncomment the other one?

@stephan-v

Copy link
Copy Markdown

It seems that if you don't write to etc/amazon-cloudwatch-agent.d this would be solved. Rather just write to etc.

I used this file as a base example so in my case I am also using append-config instead of fetch but that seems to work.

That also seems to be more preferabel because I am also using CloudFormation functions like this:

"log_group_name": "`{"Fn::Join":["/", ["/aws/elasticbeanstalk", { "Ref":"AWSEBEnvironmentName" }, "var/app/current/storage/logs"]]}`",

And don't think you can use that inside shell scripts. I don't have a whole lot of experience with this but maybe something you could look into.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants