Re:Troubles with the AWS web console
by baseballMan on Saturday September 07, 2019 @09:08AM
(#20903544)
CloudWatch log filters are pretty bad too. I basically just use ctrl + f now in cw logs to find what I'm looking for.
Emit your logs in JSON for structural search and use CloudWatch Logs Insights. It's actually really very good these days--we have an ELK cluster because the team is used to the Kibana interface but I rarely if ever use it.
Re:Troubles with the AWS web console
by cloakandswagger on Saturday September 07, 2019 @11:45AM
(#20904477)
I haven't had this problem. For simple string searches CloudWatch returns exactly what I'm looking for, even for partial word matches, and for more complicated queries there is the excellent Insights feature.
Re:Troubles with the AWS web console
by scarface74 on Saturday September 07, 2019 @09:20AM
(#20903583)
Oh yeah. They are horrible. I agree completely. For C#, I use Serilog for logging to both a Cloudwatch sink and a ElasticSearch sink. Before I’ve used a Mongo sink.
Re:Troubles with the AWS web console
by nostrebored on Saturday September 07, 2019 @02:33PM
(#20905638)
Cross account setups from the console are generally not allowed.
Re:Troubles with the AWS web console
by scarface74 on Saturday September 07, 2019 @03:47PM
(#20906063)
You can assign cross account permissions for S3, sharing AMIs, sharing KMS keys, SNS permissions, etc.
CodePipeline is pretty bad too. There is no way you can create a cross account code pipeline from the console.