To enable AutoSavings to automatically resell your unused Reserved Instances (RIs), you must first complete the official seller registration process on the AWS Reserved Instance Marketplace.
There is no "Resell Registration" button within the OpsNow console. Instead, you need to register directly through AWS.

✅ Registration Steps:

1. Why registration is required
   • AWS requires seller registration to process payments and comply with tax regulations. You’ll need a U.S. bank account and tax information.
2. How to register
   • Go to the AWS Reserved Instance Marketplace Seller Registration page
   • Submit U.S. bank account details via the Manage Bank Account section
   • Complete the Tax Interview form to provide your tax classification and identity
   • Once approved, AWS will notify you via email
3. Integration with AutoSavings
   • After registration, OpsNow automatically recognizes the registered AWS account
   • Your Reserved Instances will then appear in the AutoSavings Inventory tab, and the resale feature will be activated if eligible
     ‍

⚠️ Note:

You do not need to manually notify OpsNow after AWS approval—AutoSavings syncs registration status automatically.
However, resale optimization will not begin until AWS seller registration is complete.

‍

AutoSavings is a performance-based cloud cost optimization service built specifically for Amazon Web Services (AWS).
It helps organizations reduce unnecessary cloud spend by automatically optimizing Reserved Instances (RI) and Savings Plans (SP).

✅ Key Features:

• Automated RI/SP Optimization
  AutoSavings analyzes your usage patterns and automatically purchases or adjusts RI and SP commitments to reduce reliance on expensive on-demand pricing.
  ‍
• Reselling Unused Commitments
  Any underutilized commitments are automatically resold through the AWS RI Marketplace to prevent waste and recover costs.
  ‍
• Real-Time Strategy Updates
  The system continuously monitors changes in cloud usage and updates optimization strategies accordingly.
  ‍

💰 Pricing Model:

AutoSavings follows a Pay-as-you-save model, which means:

• You only pay a fee when actual savings are achieved
• There are no subscription fees or upfront charges

This makes it a low-risk, results-driven solution for AWS cost optimization.

‍

OpsNow FinOps Plus defines user permissions across three roles: Owner, Admin, and Member. Each role determines what a user can see or manage within an organization.
‍

✅ Owner

• Has the highest level of access across the entire organization
• Can perform the following:
  • Invite, delete, and assign roles to users
  • Create and manage organizations
  • Register and remove cloud accounts
  • View and update billing and payment settings
• Best suited for enterprise administrators or cloud ops leads

✅ Admin

• Has limited management rights within the assigned organization
• Can:
  • Manage users within the same organization
  • Register and view cloud accounts
  • Access cost, resource, and optimization insights
• Ideal for team leads or technical managers

✅ Member

• Has read-only access to cloud cost and resource data
• Cannot invite users or change account settings
• Suitable for general users, analysts, or external stakeholders needing visibility only

‍

Organizations can be created through the 'Add' button in [Settings > Organizations]. When creating an organization, you need to input the name for the organization.

No. In OpsNow FinOps Plus, a single cloud account—such as an AWS account, Azure subscription, or GCP project—can only be registered to one organization at a time.

This restriction exists to ensure data integrity, security, and proper governance across all environments.
‍

✅ Why duplicate registration is not allowed:

• Consistent and accurate data
  Duplicate registrations may result in duplicated usage or cost data, skewing analytics and reports. OpsNow maintains a 1:1 relationship between cloud accounts and organizations to prevent this.
• Clear responsibility and permission control
  Cloud accounts are typically managed by specific departments or teams. Multiple registrations can cause conflicts in user roles, ownership, and permissions.
• Security and policy enforcement
  Since each organization in OpsNow can apply its own budgets, alerts, and governance policies, multiple registrations can lead to policy conflicts or compliance risks.
  ‍

📌 If multiple teams need access to a shared cloud account, consider:

• Structuring them under one organization with separate teams or projects
• Inviting users from different groups to a single organization with appropriate roles, instead of duplicating the account across organizations

‍

When registering an AWS account in OpsNow FinOps Plus, permissions are automatically provisioned using an AWS CloudFormation stack.
This ensures that only the minimum required privileges are granted, based on the principle of least privilege, to support functions such as cost analysis, resource monitoring, and tag-based management.
‍

✅ CloudFormation-Based Role Setup

Once the CloudFormation stack is launched from OpsNow, it automatically creates and configures:

• A secure CrossAccountRole that allows OpsNow to access your AWS account
• A predefined set of IAM policies tailored to cost, usage, and resource visibility
• External ID and AssumeRole conditions to enhance cross-account security
  ‍

📂 Key Permissions Included

• Cost & usage tracking: ce:Get*, cur:DescribeReportDefinitions, s3:GetObject
• Resource monitoring: ec2:Describe*, cloudwatch:ListMetrics, autoscaling:Describe*
• Tag-based analysis: tag:GetResources, tag:GetTagValues
• Read-only IAM access: iam:List*, iam:Get* (for visibility only, not modification)

📌 These permissions are read-only and strictly scoped, with no execution or deletion capabilities.
‍

🔍 How to verify and manage permissions

• After registration, you can review all permission settings in the [Settings > Cloud Accounts] menu
• You may also audit and modify the role and policy details in the AWS IAM console at any time
• If needed, OpsNow supports custom role scoping to meet your organization’s internal security policies

📌 Using CloudFormation for automated IAM role provisioning reduces configuration errors, ensures consistency, and enforces secure and transparent access for cloud cost and usage monitoring.

‍