FinOps ECO and ECO Migration to Flexera One FAQs
Eco
How are savings calculated when I purchase reserved instances?
Eco gathers data about all of your instances before you are using reserved instances. Savings are calculated each month. This means that you are not charged at the purchasing moment, but for each month separately. The calculation of each purchase is multiplied by the number of instances. For example, Eco purchases one reserved instance at a price of $24 for a duration of one year (amounting to $2 per month). Running an on-demand instance would cost $3 per month. Therefore, Eco saves you $1 per month, and you are charged based on $1 savings each month.
Does Eco also recommend Spot instances in the projected savings?
Eco is a tool for management and optimization of commitment discounts (reservations and savings plans). The projected savings by using Eco relate to commitments. You can use Eco for managing commitments in your organization, while using Elastigroup or Ocean to optimize the combined use of Spot and reserved instances in the workload.
If my management account already has reserved instances when I install Eco, how are the savings calculated?
Eco charges only for the reserved instances that have a start date after Eco started.
How does ECO consider reserved instance volume discounts?
Reserved instance volume discounts drive the cost of reservations down. When Eco makes a large reserved instance purchase which generates the reserved instance volume discount, it is by design. Eco includes the cost reductions in the net savings calculations, which may impact your Eco fee.
What does the reservation end date mean for renewals?
When a reservation expires, Eco first makes sure a renewal is the right course of action. If so, expired coverage is replaced with the best commitment to provide a blend of flexibility and savings. When an expiration is renewed, a new lease ID is created. Depending on the situation, an expired reservation may be renewed under different parameters, so do not be concerned if you do not see an exact match.
AWS: Is there a best practice template for limiting a policy?
You can use the AWS restricted Eco policy.
AWS: What are the minimum permissions Spot needs to my AWS environment?
You can see the list of permissions required for Spot in Sample AWS policies.
AWS: Does the pricing for Eco include the AWS charge for selling reserved instances in the marketplace?
If there is a fee for selling on the marketplace, you pay AWS based on the current AWS selling fee. Eco pricing is based on the actual savings you achieve.
AWS: If I have convertible AWS reserved instances, does the savings recommendation include the savings by exchanging these?
Yes. Eco is not able to sell convertible reserved instances. It can only replace them with other reserved instances under AWS constraints. Therefore, Eco suggests how to manage your convertibles. Also, Eco may purchase convertibles for you.
AWS: Can I connect my bank account to the AWS marketplace if my company is not in the United States?
Contact your account manager for more information.
AWS: Why does Eco need to sync my S3 bucket instead of just reading it?
Eco syncs your S3 bucket to Spot instead of reading the data each time from your S3 bucket. This improves response time and reduces your costs. Also, if you delete your S3 bucket, then Spot still has the historical data saved.
AWS: Why am I getting an Invalid ARN message?
Review the Getting Started documentation for Eco and compare it to your management account resources. Make sure the CloudFormation stack providing the ARN has not been changed. Additionally, make sure no AWS Service Control Policies restrict access.
Contact Spot support.
AWS: Why am I getting a No access to S3 bucket message?
There are insufficient permissions. Review the Getting Started documentation for Eco. Confirm that the S3 bucket still exists, bucket policies and Service Control policies have not changed, and the Cost and Usage report is still scheduled to create data within the bucket.
If you continue to get this message, contact Spot support.
AWS: Why am I getting an S3 bucket no longer exists message?
Review the Getting Started documentation for Eco. Confirm that the S3 bucket still exists, bucket policies and Service Control policies have not changed, and the Cost and Usage report is still scheduled to create data within the bucket.
If you continue to get this message, contact Spot support.
AWS: Why am I getting a No new data in S3 bucket for over 48 hours message?
Review the Getting Started documentation for Eco. Confirm that the Cost and Usage report is still scheduled to create data within the bucket.
If you continue to get this message, contact Spot support.
AWS: Why am I getting a No CE access message?
Make sure the Eco permissions policy includes reading Cost Explorer data.
If you continue to get this message, contact Spot support.
AWS: Why am I getting a We were not able to access data in the S3 bucket message?
This is normal if the AWS CUR was only recently configured. If your CUR was configured more than 48 hours ago, submit a support ticket.
AWS: Why am I getting a Failure to retrieve data message?
If you get a Failure to retrieve data from < bucket >. Last Successful sync is < insert last_cur_sync_timestamp >. Expecting parquet format. message, review the Getting Started documentation for Eco.
If you continue to get this message, contact Spot support.
AWS: Why don't I see data in the Eco Dashboard?
If you cannot see data in the Eco Dashboard, check if:
- 48 hours have passed since registration with Eco. Data appears for the first time 48 hours after registration.
- The S3 bucket name is missing. Verify that the bucket name you inserted during your registration to Eco appears in the AWS Cost and Usage report list.
- The IAMRole permissions may be missing or incorrect. Verify that your permissions are complete and the same as in the Eco Policy.
If you continue to get this message, contact Spot support.
Azure: Why I am getting an Invalid credentials (tenant ID doesn't match) message?
If you get a Tenant ID in request does not match tenant ID where Eco Azuer app was consented message during setup, make sure to sign in to the Azure tenant that you would like to register for Eco.
Azure: Why I am getting a billing permission message?
If you get a Permission is not valid, pleae update permissions as needed and try again message during setup, make sure you have billing account admin access to Azure. Check your access:
Azure: Why I am getting a Registration failure (permission is not valid) message?
If you get a Permission is not valid, pleae update permissions as needed and try again message during setup, make sure you have reservation admin access to Azure. Check your access.
If you are not able to add reservation administrator permissions to your user, you might need to elevate the global admin access first.
Azure: Why don't I see data in the Eco Dashboard?
Contact Spot support.
Azure: Where can I find my tenant ID and billing account ID?
You can get your tenant ID and billing ID from Azure.
Azure: How can I update my expired client secret?
If your client secret expires, you need to update Eco with your new expiration date.
When you get a notification in the Eco dashboard that your secret key has expired, click:
- Automatically to sign in to your Azure account to give Spot application permission to programmatically set up the Eco Azure dashboard. Spot will create a new secret key and update your expiration date.
- Manually to add the new secret key and its expiration date in the Spot console.
ECO Migration to Flexera One
Why are we migrating?
We’re moving to Flexera One to provide a more modern, integrated platform. Our new name is Cloud Commitment Management. Cloud Commitment Management (CCM) supports future enhancements and better visibility into your cloud costs. You will continue to get new features and improvements in the new platform, but Spot’s Eco dashboard will no longer be updated.
What should I expect from the migration?
The migration will be seamless with no downtime. Your data stays on the same infrastructure, and your core functionality remains the same. After migration, you’ll log in to Flexera One instead of Spot, where you’ll access all future updates and features. For a detailed overview, check out our migration blog and watch the video walkthrough for a step-by-step guide.
Will my data be migrated to a new infrastructure?
No, your data will be located on the same infrastructure it has always been. We are not migrating your data. We are continuing to use the existing infrastructure to ensure consistency and minimize disruptions.
Will my data be safe and secure during this process?
Yes, your data security is our top priority. All existing security protocols remain in place.
How will migration affect the location of my data?
The migration does not change where your data is stored or how it is protected. All existing compliance and security measures remain in place. The only change is how you access the platform—through Flexera One instead of Spot.
The Spot to Flexera One Customer migration only involves a change in the user interface. All backend-related APIs and workflow activities remain unchanged.
The migration only transferred user information from Spot to Flexera One. After the migration, you sign into the Flexera One platform. If you sign in to the Spot platform, you get redirected to Flexera One.
No physical data was moved or relocated. No changes have been made to the storage infrastructure. All customer data resides in the same environment before and after the user migration.
All contractual obligations regarding data residency, protection, and confidentiality remain in effect. No alteration is needed.
Does the migration impact my contract?
No. Contractual terms do not change and will not require new contractual terms from Flexera.
Will there be any downtime during the migration?
No downtime is expected. All services will remain operational throughout the transition.
Will I need to update my sign-in credentials or access methods?
You won’t need to change how you access the platform today. However, once your account moves to Flexera One, you’ll receive a Welcome Email with a link to set up your new Flexera One password.
Is any action required from me before or after the migration?
There’s very little you need to do. Before migration, just keep an eye out for our emails and in-app banner with details and timing. After migration, you’ll use the Welcome Email to set up your Flexera One password and sign in. If you would like to enable SSO, that will be an additional step that our support team is happy to help with. That’s it. Your data and features will already be in place.
Will there be any changes to the user interface or functionality?
The core functionality will remain the same. Any updates to the interface will be communicated in advance. Going forward, all updates to features and functionality will be made to the Flexera One console. Spot’s Eco dashboard will not be updated.
How will I know when we are ready to migrate?
You’ll receive clear communication from us before your migration begins. This will include the timeline, what to expect, and any actions you need to take. We’ll also provide a banner on your current Spot dashboard and an email notification.
Who will be working with me?
Our dedicated migration team will manage the process end-to-end. If you have questions, your sales representative and our support team will be available to assist you at every step.
Who can I contact if I experience issues after the migration?
You have two main options to get technical support after migration to Flexera One:
-
Send your question directly to the Flexera support team by email.
-
Via the Flexera Community Hub:
- Click the Help button in the top-right corner of Flexera One.
- Create an account for the Flexera Community Hub (if you don’t already have one).
- After logging in, create a new support case.
Where can I find Eco Functionality in Flexera One?
- First, open your invitation email and follow the link to reset your password and create a new one.
- Log in to Flexera One with your new credentials.
- Navigate to Cloud Commitment Management:
- In the left-hand panel, go to the Cloud tab.
- Then select Cloud Commitment Management.