ROLE-BASED ACCESS NOTE: Some of the user management features and functionality described in this article require the assignment of either the Admin or Manager user role to your user account. Some of the AWS connection features and functionality described require Admin or DevOps user role assignment. Without one of these roles assigned, some or all of the functionality may not be available to you.
From time to time, there may be features or functionality you encounter in the Aimably Reduce product that might not be possible for you to perform in the interface. The cause of this issue is either AWS policy levels or your own user permissions. This guide will teach you how to resolve each.
An example of limitations in Aimably Reduce functionality can be found in the Manual Control module, you may be able to see server statuses but not be able to turn them on or off, as expected, though there are many more examples.
A fully functional machine in Manual Control with the ability to edit server status via toggle or pencil icon.
A limited functionality machine in Manual Control without the ability to edit server status.
Diagnosing the Source of the Issue
If you find yourself with controls over some aspects of your AWS environment and not others, the issue is likely related to your AWS policy configuration and you should skip to the AWS Policy Levels section below. If you find yourself without access to some pages in the product navigation, the issue is likely related to your own user permissions and you should skip to the User Permissions section below. If neither of these is the case, we recommend starting with AWS Policy Levels and continuing to User Permissions depending on the outcome.
AWS Policy Levels
Aimably currently offers two distinct levels of policy for connection with AWS. The first level, named Usage Data Only, provides only informational data to be pulled from AWS and does not allow Aimably to perform changes to the AWS environment. As a result, this limits the features and functionality of the Aimably Reduce product. The second level, named Data & Scheduling, allows for the full Aimably Reduce product experience. Keep in mind that if you have multiple AWS accounts, they may be connected using different policies.
To verify which level of policy is in use at your company, open the Configure navigation menu group, then select the Connect to AWS option:
Once on the cloud accounts page, review the Granted Access column to determine the level of access granted by Aimably to your AWS environment:
If you find your AWS connection is leveraging the Usage Data Only policy and believe that it is important to take action with the Aimably Reduce module, you'll want to update the connection by clicking on the Wizard button for that connection:
For a detailed explanation of the wizard steps, please refer to our Connecting to AWS guide. For more detailed information on the Aimably AWS policies, please review our AWS policies guide.
When you were invited to your company account, the company administrator applied one or more roles to your user which govern your access to certain pages and functions within the product. If you are missing access to certain pages or functions in Aimably, this is possibly due to the role applied to your user.
To change a role assigned to your user and access more functionality of Aimably, a request must be made to your internal company administrator as Aimably is not able to make a determination of the features and functions that you should have access to at your business. If you don't know who your administrator is, feel free to contact Aimably Support to request contact information for your administrator.