amazon-linux-2023 VS amazon-ecs-agent

$ aws ec2-instance-connect ssh --instance-id i-12345example --connection-type eice The authenticity of host '10.0.0.1 ()' can't be established. ED25519 key fingerprint is SHA256:abcdefg. This key is not known by any other names. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added '10.0.0.1' (ED25519) to the list of known hosts. , #_ ~\_ ####_ Amazon Linux 2023 ~~ \_#####\ ~~ \###| ~~ \#/ ___ https://aws.amazon.com/linux/amazon-linux-2023 ~~ V~' '-> ~~~ / ~~._. _/ _/ _/ _/m/' [ec2-user@ip-10-0-0-1 ~]$

$ 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

[4] https://github.com/aws/amazon-ecs-agent/issues/3129

Exactly. The ECS agent (https://github.com/aws/amazon-ecs-agent/) inside of the EC2 make requests to the AWS. To it work, it is necessary internet access (though Internet Gateway or a NAT Gateway) or the VPC endpoints (https://docs.aws.amazon.com/vpc/latest/privatelink/concepts.html#concepts-service-providers).

The approach I am going to take is to create an Apache Airflow workflow (DAG) and leverage an Apache Airflow operator, ECSOperator, which allows us to launch container based images. The container based images we launch will contain our ETL code, and this will be parameterised so that we can re-use this multiple times, changing the behaviour by providing parameters during launch (for example, different SQL queries). Finally, we will use ECS Anywhere, which uses the open source amazon-ecs-agent to simplify how we can run our containers anywhere - in the Cloud, on premises or on other Clouds.

... ... Ping ECS Agent registered successfully! Container instance arn: "arn:aws:ecs:eu-west-1:704533066374:container-instance/ecs-anywhere-ec2-mydcecsclusterBB109425-r7l2mKClssuV/8dfb8700d9a1460dad403a321db6b5b9" You can check your ECS cluster here https://console.aws.amazon.com/ecs/home?region=eu-west-1#/clusters/ecs-anywhere-ec2-mydcecsclusterBB109425-r7l2mKClssuV # ok ########################## ########################## This script installed three open source packages that all use Apache License 2.0. You can view their license information here: - ECS Agent https://github.com/aws/amazon-ecs-agent/blob/master/LICENSE - SSM Agent https://github.com/aws/amazon-ssm-agent/blob/master/LICENSE - Docker engine https://github.com/moby/moby/blob/master/LICENSE ##########################

It looks like they have added something for this in the latest ECS agent: https://github.com/aws/amazon-ecs-agent/releases/tag/v1.50.0