|
|
|
|
|
by scarface74
2231 days ago
|
|
This page is at least somewhat informative. But, it wasn’t until I saw the more granular permissions after you edited the policy did I get some idea of what you are doing. If you are aiming at a technical audience, the first thing we all did was look at what permissions were required because our first concern was security. Especially if we are handing over cross account permissions. The second thing I want to know is how you are doing it? But honestly, if you have a cloud native implementation like we do, just controlling EC2 and RDS only scratches the surface. We have DynamoDB, Fargate services, ElasticSearch clusters, Redshift clusters, etc. |
|
We wanted to start with something. There are other aspects of cloud cost optimization like rightsizing, unused resources, use of spot and reserved instances that are as important as instance scheduling. As well as additional supported services you've mentioned that we are planning to support in the future.
The solution is fully serverless, the scheduling as you are already familiar, is based on triggers that initiate calling certain AWS APIs to manage state of the resources. On top of it, we added support for enabling/disabling the schedule, on-demand start/stop of resources in case somebody needs the environment immediately, auto-tagging, cost per schedule etc. all integrated in one solution.
There are tools similar to ours on the market that could solve more complex saving workflows but are also more complicated to manage and are pretty expensive.
If you are interested in how it works, feel free to try it out it's free. Any feedback is welcome.