Close

Let's get on each others' calendars.

Release Notes v2.0.18

AWS Tiered Access Control
A screenshot of the Aimably to AWS connection wizard where a user is asked to select which permission level to proceed with.
During setup, you can now select the appropriate access control tier for Aimably in AWS.

Following the first release of Aimably Beta, we learned that not all companies prefer that Aimably have access to make changes to server activity within AWS. As a result, we have updated our implementation workflow to offer either Readonly or Fully Featured access. Read on for a description of each.

Readonly Access to AWS

These options control what access Aimably is granted during AWS account connection. The Readonly option gives Aimably read-only access to your AWS account.

Why would you want to use Readonly access option? Some AWS users are under strict security guidelines; these guidelines may be enforced by the government or industry regulations and require document and strict control of the access to the infrastructure. Aimably needs to obtain at least read-only access to the AWS account. By adding Readonly access feature, we allow these organizations to adhere to their required regulations and still use Aimably.

Please note that if you choose to implement Aimably with the Readonly access policy, you will not be able to use Aimably Reduce for server cost reduction activities.

Fully Featured Access

In AWS you can organize multiple AWS accounts into an organization. We had made an initial assumption that only large organizations and DevOps style companies would use this feature. In that smaller companies would have a more straightforward structure. As a result, we had decided to defer the work on cracking the permissions nut for gaining access to the child accounts to a later date.

Very soon it became apparent that this wasn't the case. What we found was that at least half of the beta clients had an Organizational structure, so we decided to go ahead and add Full Organizational Access feature. Developing this feature and keeping AWS account connection setup simple is what took most of the time.

With this release, Aimably can now access all the necessary information in accounts within the organization. This access extends to monitoring the region usage, expensive server alerting, and all the cost base alerting that Aimably performs.

We appreciate all the feedback we have received during our beta period and continue to work closely with our early customers to learn more about their needs. If you have any feedback, please submit it to our team. If you’d like to be a beta tester, visit our Beta sign up page now!

Release Notes