Does Your Church Need AWS? A Plain-English Guide to Amazon's Nonprofit Cloud Credits

Who this is actually for

AWS makes sense if your church or nonprofit is already doing (or planning to do) one of these things:

• Running a custom website or web application — not a template site on Squarespace or Wix, but something built specifically for you, like a custom donor portal or event registration system
• Hosting your own database of members, donors, or program participants outside of a pre-built church management system
• Storing and processing large amounts of data — video archives, research data, large media libraries
• Already paying a developer or IT contractor to manage hosting somewhere else, and looking to cut that cost with credit

If any of that describes you, the credit can genuinely offset real costs — one Ronald McDonald House affiliate reported the credit covering 95% of their annual AWS bill.

Who this is not for

If your main needs are email, file backup, video calls, and basic document sharing, AWS is the wrong tool entirely — and a more complicated, more expensive path to get there. You almost certainly want:

• Google Workspace for Nonprofits or Microsoft 365 for Nonprofits for email and office tools (both free for qualifying organizations)
• Google Drive or OneDrive for file backup and sharing (also included, both offering huge amounts of free storage)

These are already in the MissionGuard Resource Directory, they're free, and they take a fraction of the setup time. Don't let "free AWS credit" pull you into building infrastructure you don't need.

What you'll need before you apply

AWS is not a "sign up and go" tool. Before pursuing this credit, make sure you have one of the following:

1. A staff member or volunteer with technical experience — someone comfortable navigating a cloud console, configuring security settings, and troubleshooting when something breaks
2. A managed IT provider or contractor who can set it up and maintain it for you
3. A specific, defined project — a new website build, a data migration, an app your team is developing — rather than a vague sense that "we should probably be in the cloud"

If none of those apply yet, that's completely fine. Bookmark this program for later and focus on the free tools that give your church value today.

How to apply, if it's a fit

1. Confirm your nonprofit is a qualifying 501(c) organization (most 501(c)(3) churches and ministries qualify; a few other designations and public libraries also qualify). Note: schools and universities are not eligible here — they have a separate AWS Educate program.
2. Set up (or log into) your organization's account at TechSoup.
3. Request the AWS Nonprofit Credit Program offer through TechSoup.
4. Once approved, you'll receive a promo code by email. Log into your AWS account, go to the Billing Dashboard's Credits section, and redeem the code.
5. Set up a billing alarm in AWS CloudWatch immediately — this is the single most important step. It warns you before you accidentally rack up charges beyond your credit.

The watch-outs

• Charges resume automatically. Once your credit runs out or expires, AWS will start billing your organization's card for anything still running. Set calendar reminders to check your usage.
• Security is on you. AWS secures the underlying infrastructure, but you (or whoever manages your account) are responsible for configuring your own applications and data securely. This is often called the "shared responsibility model," and it's a real gap that trips up under-resourced organizations.
• It's a yearly application, not a one-time credit. You'll need to re-request it each fiscal year if you want to keep using it.

The bottom line

AWS's nonprofit credit is a genuinely good deal — for organizations that are already building or hosting something technical. For everyone else, it's a distraction dressed up as free money. Before you apply, ask your team one honest question: do we have a specific technical project, or the technical help, to actually use this? If the answer is no, start with the free, plug-and-play tools already in your toolkit, and revisit AWS when your needs grow into it.

Managing dozens of church passwords on sticky notes is risky. Learn why password managers are essential for church security and how to implement one today.