amazon-cloudwatch-agent VS amazon-linux-2023

cloudWatch - IAM Policy CloudWatchAgentServerPolicy for AWS Cloudwatch Agent.

$ ssh ec2-user@sumpserver The authenticity of host 'sumpserver (xx.xx.xx.xx)' can't be established. ED25519 key fingerprint is SHA256:abdcABCD1234... Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added 'sumpserver' (ED25519) to the list of known hosts. , #_ ~\_ ####_ Amazon Linux 2023 ~~ \_#####\ ~~ \###| ~~ \#/ ___ https://aws.amazon.com/linux/amazon-linux-2023 ~~ V~' '-> ~~~ / ~~._. _/ _/ _/ _/m/' [ec2-user@ip-xx-xx-xx-xxx ~]$

, #_ ~\_ ####_ Amazon Linux 2023 ~~ \_#####\ ~~ \###| ~~ \#/ ___ https://aws.amazon.com/linux/amazon-linux-2023 ~~ V~' '-> ~~~ / ~~._. _/ _/ _/ _/m/'

I wouldn't bet on it given the support lifetimes and release strategy they're trying to follow with AL2023. If you have packages that are in EPEL that you'd like to see in AL2023, file an issue https://github.com/amazonlinux/amazon-linux-2023/issues

They seem to indicate they plan to add it, but no timeframe: https://github.com/amazonlinux/amazon-linux-2023/issues/57

I just tore through the dnf list, not seeing an obvious replacement for a imap/pop server. There is an open request to include dovecot if you want to add your upvote. https://github.com/amazonlinux/amazon-linux-2023/issues/70

We were pretty aggressive with what we removed initially, with the idea being that it's a whole lot easier to add something after the fact than it is to take something out. There is a request to re-add dovecot on GitHub, please feel free to add more context to that or just give it a thumbs-up.