liveBook · Manning

IAM policy

As explained in Build Python Web Apps with Streamlit

An IAM policy is a declarative AWS document that specifies which actions are allowed or denied on which resources.

When deploying a Streamlit app to AWS, an IAM policy defines which services a user or role can access. Attaching policies directly to a dedicated IAM user limits access scope and supports stronger security controls. section 12.3.4

A deployment setup attaches policies for the services it needs:

Preparing deployment credentials

Create an IAM user, attach the required policies, and generate an access-key and secret-access-key pair. Store the pair safely because AWS will not display it again. section 12.3.4

Figure 12.6 Adding the appropriate permissions for an IAM user

Use the console view to identify the permission-policy choices during IAM user creation. section 12.3.4

How Build Python Web Apps with Streamlit covers it

How deep it goes
Explains policy selection and attachment, but does not detail policy document syntax or evaluation rules.
Examples
Uses Elastic Beanstalk, EC2, and S3 policies in an AWS deployment setup.
What it assumes
Assumes an AWS account and access to the IAM console.
What you can do after
Operate/configure AWS deployment access by attaching named policies to an IAM user.
How it connects
Connects IAM policies with IAM users, access keys, roles, EC2, S3, and Elastic Beanstalk.

Also explained in

Compare how 3 books explain IAM policy →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build Python Web Apps with Streamlit. The section links point to the parts of the book it draws on.