What do you need to get back?
Every monthly charge on your card statement from AWS, GitHub, GoDaddy or an app service points to an account behind your app.
| What | Where it usually lives | How to tell it’s yours |
|---|---|---|
| Domain | GoDaddy or another registrar | It sits in a registrar account you can sign in to |
| Sign-in email | Your company email | The cloud and code accounts use an address on your domain |
| Cloud account | AWS, or another host | You can reset the root password yourself |
| Code | GitHub | The repository sits in an organization you own |
| Database | Inside the cloud account (on AWS, often Amazon RDS) | You can take a copy on your own |
| Other services | Payments, email sending, maps, text messages | The bill goes to your card and the login to your email |
List anything you can’t sign in to, with who holds it today.
How do you get the domain back?
- Find the registrar. The who hosts my website checker shows the registrar and the expiration date.
- If it’s in your company’s GoDaddy account, turn on auto-renew and check the card on file.
- If it’s in the developer’s account, ask that registrar’s support what proof of ownership they need. Under ICANN’s Transfer Policy, a change of registrant needs confirmation from both the prior and the new registrant, so with the developer gone you need the registrar’s help.
- Plan around the lock. The registrar “must impose a 60-day inter-registrar transfer lock following a Change of Registrant,” unless it let the holder opt out beforehand.
Do the domain first: if it expires, its email stops, and so do the password resets for every other account.
How do you get into the AWS account?
If you know the root email and can read it:
- In the AWS Management Console, enter the root user email and choose Next.
- Choose Forgot password? and complete the security check.
- Open the reset email. AWS says it comes “from an address ending in @signin.aws or @verify.signin.aws.”
- Set a new password. Then choose your account name (top right), then Account, scroll to Alternate contacts, choose Edit, enter company billing, operations and security contacts, and choose Update.
If you can’t find the root email, search company inboxes for mail from @signin.aws or @verify.signin.aws, and ask who opened the account.
If the root email is on your domain but the mailbox is gone, AWS says you can restore the deleted address or set up a catch-all that forwards mail sent to addresses that no longer exist.
If the root email is the developer’s personal address, AWS’s Billing and Account Support request is the route, but support “can’t discuss the details of any AWS account other than the account that you’re signed in to.” The reset still goes through that inbox.
If you see “Password recovery is disabled for my root user account,” the account may be a member account in AWS Organizations. AWS says only the management account or a delegated administrator for IAM can then perform root user actions, so find out who controls it.
Once you’re in, cut off old access:
- In IAM, choose Credential report, then Download Report. It lists every user, when each password was last used, and when and on which service each access key was last used.
- For each of the developer’s users, go to Users, open the user, and on the Security credentials tab, in Access keys, choose Actions, then Deactivate.
- Use the app for a few days. A deactivated key “can no longer be used by API calls,” and you can activate it again if the app itself was using it.
- Delete the key only when nothing broke. AWS says a deleted key “can’t be recovered.”
How do you get the code back from GitHub?
The address github.com/owner/name shows whether a person or an organization owns it.
If the developer owns it and answers one message, ask for a transfer:
- Create an organization for your company: your profile picture, then Settings, then Organizations, then New organization.
- Ask the developer to open the repository’s Settings, go to the Danger Zone, choose Transfer and enter your organization. GitHub says you “must have administrator access to the repository” to transfer it.
- Issues, pull requests, webhooks, secrets and deploy keys come with it, and old links redirect. The original owner becomes a collaborator. Remove them in Settings, then Collaborators & teams, then Remove.
If they don’t answer and you’re a collaborator, clone the repository to get every file with its full history. Code, then Download ZIP gives only a snapshot, and GitHub says snapshots “don’t contain the entire repository history.”
Who owns the code is a separate question. Circular 30 says a contractor’s work is made for hire only if it falls in one of nine listed categories and both sides signed a written agreement saying so. Software is not one of the nine, so ask your lawyer what your contract says.
How do you keep the app running meanwhile?
- Copy the database after hours. In the Amazon RDS console, choose Snapshots, then Take snapshot, pick the DB instance, enter a Snapshot name and choose Take snapshot. On a Single-AZ database, reads and writes pause for what AWS says “can last from a few seconds to a few minutes.” Manual “Snapshots don’t expire.”
- List what runs on its own: nightly jobs, emails, imports, and when each should happen.
- Look for keys inside the code. AWS says “Do NOT put access keys or credential information in your application files.” The developer has any key you find there, so replace it.
- Check it worked. Run one real order or job as a normal user, and confirm each scheduled job ran on its next date.
If the app replaced a spreadsheet, capturing a spreadsheet only one person understands applies too. The FileMaker end-of-life guide covers getting data out of an old system before a rebuild.
What are your options?
| Option | Good for | Watch for |
|---|---|---|
| Do it yourself with this checklist | A small app on accounts already in your name | Breaking the app when you remove a key it uses |
| Hire a freelance developer | Small fixes once you hold every login | Accounts opened in their name again |
| Ask a hosting provider to take it over | Keeping the servers running | Who changes the code, and who you call when it breaks |
| Bring in an outside team (Custom software) | Taking control, then fixing or rebuilding the app | Every account in your company’s name from day one, with written notes on how it runs |
FAQ
Can AWS or GitHub give me the account if the developer opened it? AWS support can’t discuss an account you aren’t signed in to or change its credentials. Start with the root email, since every reset goes there.
Should I delete the developer’s AWS user right away? Deactivate their access keys first and watch the app for a few days. A deactivated key can be turned back on; a deleted one can’t.
Do I own the code if I paid for it? Paying for it doesn’t make it a work made for hire under Circular 30. Ask your lawyer to read your contract for a written transfer of the copyright.
What should I do first if I only have an hour? Check the domain’s expiration date and the card on file, then search your inbox for AWS sign-in emails.
Sources
- Troubleshooting AWS account sign-in issues, Amazon Web Services,
- How an IAM administrator can manage IAM user access keys, Amazon Web Services,
- Generate credential reports for your AWS account, Amazon Web Services,
- Manage access keys for IAM users, Amazon Web Services,
- Update the alternate contacts for your AWS account, Amazon Web Services,
- Creating a DB snapshot for a Single-AZ DB instance for Amazon RDS, Amazon Web Services,
- Transferring a repository, GitHub Docs,
- Downloading source code archives, GitHub Docs,
- Transfer Policy (updated 21 February 2024), ICANN,
- Circular 30: Works Made for Hire, U.S. Copyright Office,