Skip to content

Document that certain APIs don't work across accounts #139

@copumpkin

Description

@copumpkin

The documentation says this:

You can grant cross-account access for any API action that operates on an existing function. For example, you could grant access to lambda:ListAliases to let an account get a list of aliases, or lambda:GetFunction to let them download your function code. Add each permission separately, or use lambda:* to grant access to all actions for the specified function.

That would suggest that all actions on this page that operate on the function resource, except for CreateFunction, can work across accounts.

From my testing, in practice that list appears to be more restrictive. AddPermission, DeletePermission, and UpdateFunctionConfiguration at least also don't seem to allow me to use them across accounts.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions