awx VS sops

AWX Project ↗

However, when I try to add it is not allowing me to save nor it throws any error. I see one old pull request which seem to address this very issue but I find the issue still persists. https://github.com/ansible/awx/issues/8898

I ran into that (or something very similar) a few days ago. For me, I made a new Execution environment and used this image rather than the 'latest' one: quay.io/ansible/awx-ee:23.5.0 and now mine works. ref: https://github.com/ansible/awx/issues/14689

@elibogomolnyi The EKS reconnect support AWX jobs can't tolerate the EKS scale out & possible fix.

We're happy to announce that AWX Version 23.0.0 is now available! We're happy to announce that AWX Operator version 2.5.2 is now available!

AWX Project ↗ AWX

2023-07-11: AWX Office hours, 15:00 UTC

You can install AWX in a docker-compose environment as well: https://github.com/ansible/awx/blob/devel/tools/docker-compose/README.md

There is a web UI for Ansible called AWX

Mozilla SOPS (Secrets OPerationS) is an open-source command-line tool for managing and storing secrets. It uses secure encryption methods to encrypt secrets at rest and decrypt them at runtime. SOPS supports a variety of key management systems, including AWS KMS, GCP KMS, Azure Key Vault, and PGP. It's particularly useful in a DevOps context where sensitive data like API keys, passwords, or certificates need to be securely managed and seamlessly integrated into application workflows.

Encrypted secrets thanks to SOPS and Age

We do the exact same thing to keep track of some credentials we use sops[1] and AWS KMS to separate credentials by sensitivity, then use the git differ to view the diffs between the encrypted secrets

Definitely not best practice security-wise, but it works well

[1] https://github.com/getsops/sops

For anyone new to SOPS like I was - https://github.com/getsops/sops

I've found this is largely solved by strictly separating plain config and secrets, and then having secrets pull from GCP secret manager / vault / whatever.

You can then commit all the config (including the secret identifiers) and it all just works so long as you're authenticated with your secret storage system.

We do this for the live configuration as well in line with Gitops and find it to work well.

If you don't want to use a cloud secret manager you can also use something like https://github.com/getsops/sops to commit the encrypted secrets safely

Basically, the simpler the better --just encrypt your secrets and check them in to version control.

We use SOPS[0] for this, and have found it to be pretty nice.

[0]: https://github.com/getsops/sops

The answer is that secrets shouldn't be stored in the git repo at all, but somewhere safe like a password manager or Mozilla's SOPS which people seem to love.

Unfortunately, the SOPS project is in some sort of a limbo state and there has been quite a long period with limited maintenance and unclear position from Mozilla. Despite the project being accepted into the CNCF, it's still unclear what will happen with it going forward.

It looks like the software you're intending to use is oriented towards interacting with desktop Linux's keyring. While you can probably get this to work, I would recommend using something like sops as it's a more standardized way of storing secrets in configuration.