A Full Access policy grants an IAM entity (user, group, or service account) unrestricted permissions to perform any action on all resources within your Greennode AI Platform account. While convenient, such policies should be used with caution due to the significant security risks they pose.

Steps to Create a Full Access Policy

1. Access the IAM Console: Log in to the IAM console at: https://iam.console.greennode.ai/

2. Create a New Policy:

   • Click on "Policies" in the left menu.
   • Click "Create a policy."
   • Provide a descriptive name for your policy (e.g., "AIPlatfomrFullAccess").
   • Optionally, add a description.

3. Define Policy Permissions (Visual Editor):

   • Click "Next step" to open the Visual editor.
   • At "Product" section, select "ai-platform" to limit the scope.
   • Under "Actions," choose "All actions."
   • Under "Resources," select "All resources."
   • Leave "Request Conditions" blank (unless you want to add specific time-based restrictions).
4. Review and Create:
   
1. Carefully review the policy to ensure it matches your intent.
   
2. Click "Create policy" to finalize the policy creation.
   

Important Considerations

• Security Risks: Granting Full Access permissions to any entity should be done with extreme caution. It can significantly increase the risk of accidental or malicious actions that could compromise your cloud resources.
• Principle of Least Privilege: Always strive to follow the principle of least privilege, granting only the minimum necessary permissions for each entity to perform its intended tasks.
• Alternative Approach: Instead of a Full Access policy, consider creating more granular policies that grant specific permissions for specific resources. This provides better security and control over your cloud environment.

When to Use a Full Access Policy (Caution):

• Temporary Administrative Tasks: If you need to perform temporary administrative tasks that require unrestricted access, you can create a Full Access policy for a limited time and then delete it once the tasks are completed.
• Trusted Service Accounts: For service accounts that require broad access to automate tasks or manage resources, a Full Access policy might be appropriate. However, ensure that the service account's credentials are securely managed.

Recommendation: We strongly recommend using Full Access policies sparingly and only when absolutely necessary. In most cases, it's better to create more specific policies that align with the principle of least privilege.