Access denied
A refusal is the service telling you what is not granted, not a fault. Each entry names the cause and the fix.
access denied
Section titled “access denied”Cause. The identity that made the call has no policy that allows that action on that resource. Nothing is granted by default, so a user or a role created a moment ago can do nothing until a policy is attached. A statement naming an action that no longer exists matches nothing and refuses silently, so a policy written before an action was renamed is the other cause.
Fix. Read what the identity carries, then attach what it needs:
deployport iam users policies list --username <username>deployport iam users policies attach --username <username> --policy <policy-name>A role takes the same pair with --role <role-name>. Write a policy builds the policy file, and its last section covers an action that was renamed.
Verify. The command that was refused runs, and deployport iam identity-policy show <policy-name> prints the statement that allows the action.
access denied, unknown or expired access key id
Section titled “access denied, unknown or expired access key id”Cause. The credentials in the profile are no longer accepted. A key that was replaced, an account that was deleted, and a CLI still pointed at an account it can no longer enter all answer this.
Fix. Sign in again, or move the profile to an account you can enter:
deployport logindeployport iam accounts switch <account-name>Verify. deployport iam users list answers with the account’s users instead of a refusal.
user not found
Section titled “user not found”Cause. The name is not a user in this account. It is the ordinary typo, and a user minted in another account reads the same way. The CLI prints it under its own line, so the whole answer reads failed to attach, user not found.
Fix. List the names and use one of them:
deployport iam users listA role answers role not found the same way, and deployport iam roles list has the names. A policy name that resolves to nothing answers identity policy not found, and deployport iam identity-policy list has those names.
Verify. The command that refused runs, and the name appears in the listing.
this account has no group named <group>, and no identity policy named <policy>
Section titled “this account has no group named <group>, and no identity policy named <policy>”Cause. The invitation names a group or a policy that does not exist in this account, so the access it would carry cannot be granted. The message lists every name it could not resolve.
Fix. List the names and invite again:
deployport iam identity-policy listdeployport iam invitations create teammate@company.com --group <group>Verify. The invitation is in deployport iam invitations list, with the groups and policies you named.
invitation is invalid, already used, revoked, or expired
Section titled “invitation is invalid, already used, revoked, or expired”Cause. The person accepting the invitation is holding a token that no longer works. It was already accepted, it was revoked, or it expired.
Fix. Revoke it and send a new one:
deployport iam invitations listdeployport iam invitations revoke <invitation-id>deployport iam invitations create teammate@company.com --group <group>Verify. The new invitation is in deployport iam invitations list, and the person is in deployport iam users list once they accept.
the invitation was sent to a different email address
Section titled “the invitation was sent to a different email address”Cause. An invitation carries the address it was sent to. Accepting it while signed in as another address is refused, and the refusal names the mismatch rather than the invitation.
Fix. Sign in as the invited address and accept it, or revoke it and invite the address you are using:
deployport iam invitations revoke <invitation-id>deployport iam invitations create <the address you are signed in as> --group <group>Verify. The person is in deployport iam users list.
Still stuck
Section titled “Still stuck”Ask us at Contact and include:
- the account name, and the identity that was refused
- the command you ran, and its output
- the time it happened, with your time zone