• Documentation
  • Pricing
© 2026 Serverless, Inc. All rights reserved.

Framework

  • Overview
  • Documentation
  • Plugins360
  • Pricing

Learn

  • Blog
  • GuidesUpdated
  • Examples240
  • Courses

Resources

  • Support
  • Security
  • Trust Center
  • Status

Community

  • Slack
  • GitHub47k
  • Forum
  • Meetups

Company

  • About
  • Careers
  • Contact
  • Partners

Legal

  • Terms of Service
  • Privacy Policy
  • Trademark
  • DMCA
Serverless Framework Logo

Serverless Framework

Intro
SetupUpgrading To V4ConceptsTutorialAWS CredentialsLicense Keys
DeployingPackagingBuildingTestingServicesFunctions
OverviewHTTP (API Gateway v2)REST (API Gateway v1)ActiveMQApplication Load BalancerAlexa SkillAlexa Smart HomeCloudWatch EventCloudWatch LogCloudFrontCognito User PoolEventBridge EventIoTIoT Fleet ProvisioningKafkaKinesis & DynamoDBMSKRabbitMQS3ScheduleSNSSQSWebsocket
LayersManaged InstancesAlertsVersion PruningDomainsIAM Function PermissionsParameters
OverviewSelf-reference serverless.ymlServerless CoreEnvironment VariablesCLI OptionsExternal YAML/JSON FilesJavascript propertiesGitDoppler
OverviewS3 ObjectsSSM Parameter Store & Secrets ManagerCloudFormation Stack Outputs
OverviewVaultTerraform State Output
ResourcesComposing ServicesDeployment BucketStatePython support
OverviewRuntimeGatewayMemoryBrowserCode InterpreterDev Mode
API Gateway Proxy
OverviewGeneral ConfigurationAuthenticationAPI KeysData SourcesResolversPipeline FunctionsCachingDelta SyncCustom DomainWAFCLI Commands
Deploying SAM/CFN TemplatesWorkflow Tips
OverviewCreating PluginsCLI OutputCustom CommandsCustom VariablesExtending the Configuration schemaExtending and overriding configuration
OverviewDashboardAxiom
Overviewdeploydeploy functiondeploy listdevdiffinfoinvokeinvoke localloginlogin awslogin aws ssologsmetricspackageplugin installplugin uninstallprintprunereconcileremoverollbackrollback functionsupportusage
Overview
OverviewMetricsTracesTroubleshoot
OverviewNode.jsPython
OutputsProviders
OverviewBranch DeploymentsPreview DeploymentsCustom ScriptsTestingPrivate PackagesNotificationsMono ReposDeploy in your own CI/CDBest PracticesTroubleshootingFAQ
OverviewSetupToolsAWS Integration
Serverless.yml Reference
Examples and TutorialsConfiguration Validation
  1. CLI Reference
  2. Reconcile

Reconcile

The reconcile command reconciles your org's list of billable instances with the actual CloudFormation stacks currently in your AWS account, making it an essential tool to recover credits for stacks that were removed manually without running the remove command.

We generally recommend to always use the remove command to remove Serverless Framework stacks to ensure the removal is reported, but if you must remove stacks manually or your organization has a custom workflow, this command is the only way for us to know that your service instance was removed and that it should no longer be consuming credits.

Note: The reconcile command is a global, account-wide command. It is not a per-service command and does not need to be run from inside a service directory. A single invocation reconciles every billable instance reported for your org against all CloudFormation stacks in the AWS account associated with the credentials it is run with, so you only need to run it once per AWS account — not once per service or per serverless.yml.

If you have Serverless Framework stacks in multiple AWS accounts, you should run this command once for each AWS account (using credentials for that account) for a complete reconciliation and more accurate usage reporting and billing.

Note: This command might take a few minutes to complete depending on how many CloudFormation stacks you have in your AWS account.

AWS Region Configuration

By default, the reconcile command uses the us-east-1 region to fetch your AWS account ID. If you're working in a restricted environment where access to specific regions is blocked or where VPC endpoints are only available for certain regions, you can override this default behavior by setting the AWS_REGION environment variable:

AWS_REGION=eu-central-1 serverless reconcile

Usage

serverless reconcile

The command can be run from any directory — it does not need to be executed inside a service directory and does not read your serverless.yml. It operates at the AWS account level using the AWS credentials available in your environment.

Options

  • --org The org name to reconcile instances for. Defaults to your service org if found, or your default personal org.

Example

The example below runs reconcile from an arbitrary directory (no serverless.yml required):

~ $ serverless reconcile

Successfully recovered 3 Instance Credits from the 123456789012 AWS account.

If you have any questions about your usage, please contact support@serverless.com.

~ $
Edit this page
Prev pruneNextremove

Contents

  • Reconcile
  • AWS Region Configuration
  • Usage
  • Options
  • Example

Related

GuidesPluginsExamplesSlack CommunitySupport