All Collections
AWS vs. Tailwarden
Tailwarden for DevOps
Article #1: Tagging Multiple Resources
Article #1: Tagging Multiple Resources
Cyril avatar
Written by Cyril
Updated over a week ago

The Challenge: Adding tags to 10 ec2 instances

In this opening round, we tackle the task of applying the tag "Owner": "Cyril" to 10 ec2 instances roles, comparing the workflow between AWS and Tailwarden.

AWS Method:

Steps to update one ec2 instance:

  1. Open ec2.

  2. Click on instances.

  3. Look for a given instance.

  4. Realize it's in another region.

  5. Realize it's already annoying to do that.

  6. Change region.

  7. Look for the instance.

  8. Open it.

  9. Click on the "Tags" tab.

  10. Click on "Add new tag".

  11. Click again on "Add new tag" (yes, it’s repetitive 😒).

  12. Type "owner" then "Cyril".

  13. Realize that it was "Owner" with a capital O, not "owner". Correct it.

  14. Click on "Save Changes".

It took you 10 steps just to update one ec2 instance. Now, multiply that effort by 10 roles—it’s clear we need a better way.

Tailwarden Method:

And now for the Tailwarden approach... Less than 25 seconds to complete the entire task! Check out the video here for a real-time demonstration of how swiftly and efficiently Tailwarden handles what can be a tedious process in AWS.

Conclusion

In the DevOps arena, where time is of the essence, Tailwarden not only simplifies the process but slashes the time it takes to perform essential tasks. Round 1 clearly goes to Tailwarden, showcasing our platform’s ability to turn prolonged chores into quick, effortless victories. Stay tuned for more rounds where Tailwarden continues to outpace AWS, providing not just solutions but supercharged shortcuts to common DevOps hurdles.

Ready for Round 2? With Tailwarden, you’re always one step ahead.

Did this answer your question?