You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/managed-inference/how-to/manage-allowed-ips.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ An API key is considered valid to access a deployment when:
51
51
- It belongs to the [Owner](/iam/concepts/#owner) of the Organization which owns the deployment, or
52
52
- It belongs to a [Member](/iam/concepts/#member) or [Application](/iam/concepts/#application) of the Organization which owns the deployment, and the Member/Application has appropriate [IAM permissions](/iam/reference-content/permission-sets/).
53
53
54
-
There are two IAM permission sets specific to Managed Inference deployments: `InferenceFullAccess` (allowing access to create, read, update and delete a deployment) and `InferenceReadOnly` (allowing read-only access). Alternatively, wide-scoped permission sets such as `AllProductsFullAccess` will also allow access.
54
+
There are two IAM permission sets specific to Managed Inference deployments: `InferenceFullAccess` (allowing access to create, read, update, and delete a deployment) and `InferenceReadOnly` (allowing read-only access). Alternatively, wide-scoped permission sets such as `AllProductsFullAccess` will also allow access.
55
55
56
56
Permissions are attributed via [policies](/iam/concepts/#policy), which are then attached to a Member or Application.
57
57
@@ -60,7 +60,7 @@ You can further restrict access by imposing **conditions** when defining a polic
60
60
### How to manage deployment access as an Organization Owner or Administrator
61
61
62
62
<Messagetype="note">
63
-
If you only want to access the deployment yourself, and you are Owner of the Organization that created the deployment, simply [generate an API key](/iam/how-to/create-api-keys/) for yourself, and it will automatically have full rights to access and manage the deployment.
63
+
If you only want to access the deployment yourself, and you are the Owner of the Organization that created the deployment, simply [generate an API key](/iam/how-to/create-api-keys/) for yourself, and it will automatically have full rights to access and manage the deployment.
64
64
65
65
Read on if you want to manage access to your deployment for others.
66
66
</Message>
@@ -74,7 +74,7 @@ You can revoke access to a deployment at any time by [modifying or deleting the
74
74
75
75
### How to access a deployment as an Organization Member
76
76
77
-
Your access to Managed Inference deployments owned by an Organization in which you are a Member, is dependant on the IAM permissions attributed to you by the Organization's Owner or administrators.
77
+
Your access to Managed Inference deployments owned by an Organization in which you are a Member depends on the IAM permissions attributed to you by the Organization's Owner or administrators.
78
78
79
79
Your permissions will be automatically applied to any API keys you generate for yourself in the Scaleway console. Check with your Organization Owner if you are unsure that you have the right permissions to access a Managed Inference deployment.
0 commit comments