ECS exec Tasks, CLI Sign Up, Compliance enforcement, and major CLI experience improvements.
📇 ECS Exec commands integration
You can now use Runops to access running containers in AWS ECS, using the ECS exec feature recently launched by AWS. This means that you can get a shell inside ECS containers without bastion hosts or exposing your private network to the internet. The access happens trough the AWS internal infrastructure. You get the all the auditing capabilities of Runops along with the AWS Cloud Watch trails for every command. It's a great alternative to manage and control access to the Rails and Elixir consoles in production.
💈 Sign up from the CLI
We are really excited about this feature! Anyone can Sign Up for Runops directly from our CLI. New organizations get created when the first user in the company signs up with a company email. Users joining existing organizations can also use the CLI to do so. The
runops signup command in the CLI will route an user to the right workflow. We will identify the organization from the company's email domain. The approval mechanism in Slack for users joining an existing organization stays the same.
🍥 Major CLI experience improvements
The admin experience is way better in the CLI. The CLI now requires the minimum amount of parameter for any operation. You can do things like add new secrets, update runner, change the type, all providing only what you meant to change. Before this update you had to provide parameters you were not changing like the type and review mode for every command. We also cleaned up null values present in json-formated responses.
teams review mode got a new compliance enforcement feature: the creator of a Task can't review their own Tasks. This is important for companies that have resources with shared responsability across teams and require this type of locking mechanism.
That is it for this week, we'll see you next week with more Releases.
As always, please let us know of any feedback or comments you might have on Runops.