Atomile Console provides IAM (Identity and Access Management) to help you control access to products and services for both end users and application code.

When using a Main Account, you can:

• Create and manage sub-accounts for your end users
• Establish secure access controls to protect your service resources
• Define identity credentials (login accounts and access keys) for sub-accounts
• Design custom permission policies to control allowed and denied actions in the Atomile Console
• Assign specific roles to each sub-account for precise access control

Understanding IAM Components

IAM manages digital identities and their privileges for functions and resources within the Atomile platform. Use IAM to determine who can authenticate and what permissions they have to access your services. Each account request follows a structured process of authentication, authorization, and operation execution.

Key IAM Concepts

Managing Principals

• A principal is any person or application that uses unique identity credentials to access Atomile resources.
• Principals make requests through the Console UI or API using their assigned identity credentials.
• Atomile offers two credential types:
  • Login Name and Password for human users
  • Access Key and Secret Key for application access

Processing Requests

• When principals perform actions in the Atomile Console, the system evaluates and authorizes each request.
• Every request goes through three sequential steps: authentication, authorization, and operation execution.

Working with Resources

• IAM stores critical information about roles, permissions, actions, policies, and control groups.
• You can create, update, enable, disable, and deploy resources, such as CDN domains, within the Atomile Console.

Performing Actions

• Actions represent operational functions within Atomile products.
• Each Atomile service provides various functions that principals can access based on their permissions.
• After successful authentication and authorization, the system allows the requested action.
• Actions can be used to view, create, and delete service resources. For example, creating a CDN domain requires permissions granted by the Main Account.

Implementing Policies

• A policy combines multiple actions with permission effects to control access to resources.
• Policies define which functions users can execute within the Atomile platform.

Understanding Permission Effects

• Permission effects determine whether actions are allowed or denied.
• Allow: Authorizes the action to execute the function.
• Deny: Prevents the action from executing the function.

Using Control Groups

• Atomile manages access control between service resources, such as CDN domains, and contracts.
• Each control group contains related accelerated domains running through Atomile products.
• Control groups help you assign users specific access to monitor traffic, view billing information, and modify service configurations.