Error with the service "awslogsd" about aws-cf-templates HOT 5 CLOSED

UPDATE:

I have found that the service is called "awslogs" rather than "awslogsd" so I have updated the service name on "vpc-ssh-bastion.yaml"

2021-02-20 09:57:31,546 [INFO] enabled service awslogs
2021-02-20 09:57:31,546 [DEBUG] Restarting awslogs due to change detected in dependency
2021-02-20 09:57:31,547 [DEBUG] Using service runner: /sbin/service
2021-02-20 09:57:33,585 [INFO] Restarted awslogs successfully

Now it is erroring on "mariadb"
2021-02-20 09:57:36,374 [ERROR] mariadb is not available to be installed
2021-02-20 09:57:36,374 [ERROR] Error encountered during build of config: Yum does not have mariadb available for installation

Why is this happening?

from aws-cf-templates.

Hi @ian-tait

Do you use the latest version of the templates without modifications? As far as I remember, the service name was renamed from awslogs to awslogsd in Amazon Linux 2 a while ago.

mariadb is 100% not part of our template.

from aws-cf-templates.

Hi Michael,

I am using the latest version with some slight changes around tags and naming.
Currently using the latest EC2 "ami-047a51fa27710816e" in us-east-1

Mariadb is part of the bastion build, as see here:
https://github.com/widdix/aws-cf-templates/blob/master/vpc/vpc-ssh-bastion.yaml
Line 432, as it installs packages using cfn-init yum.

from aws-cf-templates.

Oh, know I remember. It installs the mysql client to connect to RDS instances :)

I just created a bastion ssh stack in us-east-1 and it worked. it also worked 3 days ago when the test suite ran. can you try to spin up an unmodified template to reproduce your issue? Can you share the parameters of the stack?

from aws-cf-templates.

Hi Michael,

After picking through my code, it would seem I found the issue with the AMI; somehow, I was using an older image of an Amazon Linux 1(AL1) machine. Hence the reason for "awslogs" and not "awslogsd". I still haven't figured out how that came about.
I ended up double-checking after my last update, and it was at that point I found I was using the wrong one.

By using the right AMI, this too fixed the issue with the MariaDB. It would appear that this was not available in the repos for AL1 machines.

Not too sure how I got myself in such a mess with my testing but thank you for helping me out.

Thank you
Ian

from aws-cf-templates.