Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Are Cognito AdminDelete Operations Charged as MAUs in Essentials Tier?

0

I'm currently using AWS Cognito with the "Essentials" pricing tier. I have approximately 50,000 existing users that I need to delete from my User Pool using admin-delete-user API. These users are a mix of both External Providers (e.g., federated users) and local Cognito users.

The documentation states that a user is counted as a Monthly Active User (MAU) if "customers’ application generates an identity operation for that user, like administrative creation or update, sign-up, sign-in, sign-out, token refresh, password change, a user account attribute update, or an attribute query on a user (AdminGetUser API)."

My question is: Will deleting 50,000 users, particularly through an administrative operation, incur charges under the Cognito Essentials tier?

I understand that "administrative creation or update" counts as an identity operation. I need clarification on whether deletion is also considered an "identity operation" that would trigger an MAU charge, especially since I'm trying to reduce my user count.

Any insights or official AWS guidance on this would be greatly appreciated. Thank you!

Topics
Cloud Financial ManagementSecurity, Identity, & Compliance
Tags
Amazon Cognito Federated IdentitiesAmazon CognitoPricingAmazon Cognito User Pools
Language
English

asked a year ago254 views

2 Answers
0

AdminDeleteUser does not count the deleted user as MAU. That means, if the user has no other identity related (MAU countable) operations during one calendar month and this user is deleted by the API AdminDeleteUser within this calendar month, this user would not be counted as MAU for this calendar month.

AWS

answered a year ago

  • AWSExplorer
    a year ago

    Just to confirm: if I run a script that first lists users from the Cognito User Pool and then deletes each user using the AdminDeleteUser API — assuming these users haven’t had any other identity operations during the current calendar month — I shouldn't incur any MAU-related charges, even if I'm deleting a large number of users. Is that correct?

    I just want to ensure that the listing and deletion process itself doesn't trigger any chargeable identity operations.

    Thanks again for your support!

-1

Based on the available information, user deletion (including administrative deletion) is considered an identity operation that would count toward your Monthly Active User (MAU) charges in Amazon Cognito.

According to the documentation, a user is counted as a MAU if there is an identity operation related to that user within a calendar month. The list of activities that make a user active specifically includes "User activation, deactivation or deletion."

This means that if you delete 50,000 users from your User Pool using the admin-delete-user API, these users would likely be counted as MAUs for billing purposes under your Essentials tier for that calendar month.

For cost management, you might want to consider:

  1. Spreading the deletion over multiple months if possible
  2. Contacting AWS Support to discuss your specific situation
  3. Exploring if there are any bulk deletion options that might have different billing implications

Keep in mind that you're only charged once per user per month regardless of how many operations are performed on that user within the same month. So if these users have already been active in the current month, deleting them wouldn't incur additional MAU charges.
Sources
Cognito：Are users with unconfirmed status also considered MAU? | AWS re:Post
Quotas in Amazon Cognito - Amazon Cognito
Monitoring and managing costs - Amazon Cognito
Amazon Cognito - Pricing

answered a year ago

  • yunganw
    a year ago

    The Cognito Price document has been updated and "User activation, deactivation or deletion." description has been removed from that page. One of the reason is user deletion is not counted as a MAU activity.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content