Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I need to give a freelancer access to my server and I am worried

Short answer

It can be safe if you give the freelancer their own named access with only the permissions the job needs, never your own login or root credentials, and you remove it when the work ends. AWS's guidance is to apply least privilege, use temporary credentials where possible and remove unused access.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • A freelancer asked for my server password or the root login.
  • I once shared a password in a chat and I am not sure who still has it.
  • I do not know what a freelancer could do if they wanted to.
  • I want to hire someone but I am afraid of data loss or leaks.
  • A past developer still has access and I have not removed it.

Why does this happen?

  1. Shared logins hide who did what

    If everyone uses one account, you cannot tell who changed something, and you cannot remove one person without changing the password for all.

  2. Too much access is the common mistake

    AWS's best practices say to grant only the permissions required to perform a task, and to start from managed policies and then narrow them. A freelancer fixing one site rarely needs access to billing, backups and every server.

  3. The main account is more dangerous than a normal user

    AWS tells owners to protect the root user credentials of the account like other sensitive personal information, and to require multi-factor authentication for any IAM user or root user.

  4. Access is forgotten after the job

    AWS recommends regularly reviewing and removing unused users, roles, permissions and credentials, and updating access keys when someone leaves. Without that review, past contractors keep access.

What can I do about it today?

  1. Never share your own loginDo not send your password or the main account details. Ask the freelancer to work with an access you create for them.
  2. Write what the job needsOne page: which server, which part, which task. Access should match it and nothing more.
  3. Turn on two-step sign-in on your own accountsHosting, domain and cloud accounts should ask for a second step. Do this before inviting anyone.
  4. Ask whoever manages the server to create the accessIf you cannot do it, ask a trusted technical person to create a named user, not hand over the owner login.
  5. Set a date to remove the accessPut it in your calendar for the end of the job and check afterwards.
  6. Keep a copy of your data firstCheck that a recent backup exists before any work begins. Do not delete anything while checking.

When should I bring someone in?

  • You do not know how to create limited access on your hosting or cloud account.
  • You think a past contractor still has access.
  • The server holds customer data and a leak would matter.

How do I handle it?

  1. Ask for the smallest access that worksI tell you exactly which permissions I need and why, and I work with a named account, never the owner login.
  2. Use keys, not passwordsI connect with keys that you can remove at any time, and where the platform allows it I use temporary credentials.
  3. Back up before production changesA backup is taken first, and every change has a way back that has been tested.
  4. Keep a written recordI note what I changed and when, so you can follow the work.
  5. Hand access back at the endWhen the work finishes, my access is removed and I list what was removed, so you can confirm.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Can a freelancer see my customer data?

If they have access to the database or server, yes. That is why access is limited to what the job needs and removed afterwards.

Should I use a password manager to share logins?

It is better than chat, but a separate named account is still safer than sharing yours.

Can I give read-only access?

Often yes for review or diagnosis. Whether it is enough depends on the task.

Can I be sure nothing will go wrong?

No access arrangement removes all risk. Limits, backups and a record reduce it.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.