#aws (2024-12)

Yeah, our team has been using it for a few years. It’s very stable, we like the control and permission CodeArtifact allows, i.e who can consume the artifact at AWS account level…

The biggest workflow change for us when we first adopted CodeArtifact was how to build the docker image that reference library from CodeArtifact. Once we got that worked out… it has been running with minimum support ..

oh that’s awesome

im gonna give it a shot. we use github actions, so i’m assuming we just do an assume role to use artifacts from codeartifact

there are few ways to approach that, assuming role is one of them.

for our own use case, we want to allow anyone from the organization to use our library in codeartifact, we’ve set it up to allow any aws account as long as the AWS account is under a specific organization id

I see terraform-aws-sqs-cloudwatch-sns-alarms - [wip] Terraform module for creating alarms for SQS and notifying endpoints

Do you know what the tentative expected date is for this module release?

But I don’t see any recent updates in the above project, do we have any alternative solution?

@Andriy Knysh (Cloud Posse)

Just curious how they’re holding up… since I wanted to evaluate Leapp alternatives at some point

I use it, it’s been pretty good for me. Came from AWS-vault

i use the granted cli regularly, it’s been great