Not Able to create IAM in AWS Educate - amazon-web-services

I am trying to create IAM in my AWS Educate but it don't allow me to create.
You need permissions:
You do not have the permission required to perform this operation. Ask your administrator to add permissions.

AWS Educate Starter Account are very limited:
AWS Services Supported with AWS Educate Starter Account
One of the limitations is lack of IAM permissions. There is no solution for that. You have to re-architect your project not to require the new IAM permissions.

Related

AWS IAM Policy for specific subaccount(s)

I have one organization with multiple sub accounts. I would like to create IAM Policies that grant users full administrator access to any resources in specific sub account (or sub accounts). How can this be achieved?
From an AWS Organization perspective, you have control over the accounts and resources via Service Control policies (SCPs).
"However, an SCP never grants permissions. Instead, SCPs are JSON policies that specify the maximum permissions for the affected accounts."
With that in mind, you can't grant users full administrator access to any resources in a specific subaccount(s) using AWS Organization and AWS IAM Policies only.
This leads us to (roughly) 3 paths:
By default, if you create a member account as part of your organization, AWS automatically creates a role in the account that grants administrator permissions to IAM users in the management account who can assume the role.
The IAM Role in question is OrganizationAccountAccessRole. You can customize its name and use it to grant your users full administrator access across all the resources inside the AWS account.
See: https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_access.html
Observations: Since this IAM Role is created in every account. You would need to intervene and limit the IAM Cross-Account access manually in each sub-account.
You can use AWS CloudFormation StackSets to deploy across multiple AWS accounts a list of IAM Roles your users could use for admin purposes (eg RoleFullAdmin, RoleReadOnly, RoleDevOps), and AWS Organizations enables you to create stack sets with service-managed permissions, using a service-linked role that has the relevant permission in each member account.
From your AWS Organizations management account (or delegated administrator account) you can deploy Stack Sets to current accounts and they are automatically deployed to every new account your create, keeping your resources in sync.
You can target accounts via account ID or organizational units (OUs).
See: https://docs.aws.amazon.com/organizations/latest/userguide/services-that-can-integrate-cloudformation.html
Observations: Similar to 1, since you are using IAM Role Cross-Account access, you need to manually intervene in the policy trust relationship.
Add AWS IAM Identity Center (successor to AWS Single Sign-On) to your AWS Organizations
What you are looking for can be achieved by Permission Sets in the AWS IAM Identity Center.
You can customize the access per user and have a many-to-many relationship between User <-> Accounts <-> Roles. You can define one or more IAM Policies in the Permission Set.
AWS provides predefined permissions that you can use too.
See: https://docs.aws.amazon.com/singlesignon/latest/userguide/permissionsetsconcept.html and https://docs.aws.amazon.com/singlesignon/latest/userguide/permissionsetpredefined.html
Observations: You need to add an extra resource to your AWS Organization and configure the identity source of your users. This also requires a change in the process of "how to login to our aws account". Now you need to use the AWS SSO etc.

AWS Organizations permission denied

I'm working with AWS. Specifically, I have an AWS Educate account with $ 100 free. When I go to the AWS Organizations service, I get a message saying: you don't have permission to access this resource. I've tried to add a full organization permission to the user, but I still have the same error.
Furthermore, I use the EMR cluster and the S3 bucket.
Anyone could help me?
AWS Organizations is one of the services that are not supported in AWS Educate Starter Accounts. Please refer to this document to learn about supported services.
If you want to use AWS Organizations, you can create a regular AWS account here. You can have as many accounts as you want (in fact, that’s something that AWS Organization helps you with: Multi-account management).

Alternative to AWS Organization

I'm using AWS Educate with a EMR cluster and S3 bucket. I would need to share the instances of two different AWS Educate accounts, but with AWS Educate, AWS Organization is not compatible. Is there other service or similar way that would allow you to share instances for Amazon Educate?
Thank you so much in advance.
Unfortunately, the AWS Educate Starter Accounts are very limited.
A usual procedure to enable cross-account access to resources is through IAM roles. However, the AWS Educate Starter Account FAQ states:
You can create users, but cannot associate login profile or access keys for them. *Additional restrictions may apply
It's not clear if you can create such IAM roles and allow other accounts to assume them. But you can check. Using IAM console its rather easy to create a cross-account role, thus you can verity that.
Alternatively can ask AWS Educate support for such possibility.

How to store data using s3?

I am new to aws and I want to integrate IAM in my aws account.
I have gone through this link:
https://www.youtube.com/watch?v=KQheV84Ae40&list=PL_OdF9Z6GmVZCwyfd8n6_50jcE_Xlz1je&index=3
but not getting the proper idea.
Is there any example for that?
You can use IAM to create Users in your AWS Account.
You can then associate policies with those users, which grant them permission to use particular AWS services, such as Amazon S3. IAM is automatically integrated with every AWS service.
See: Writing IAM Policies: How to Grant Access to an Amazon S3 Bucket | AWS Security Blog
IAM service in AWS is used for user management, that helps you securely control access to AWS resources. In IAM you can create users and you can assign roles to the users based on your needs. you can create custom policies also, AWS provides many custom policies by default once go through Its mostly self-explanatory.

Why ROLES and POLICIES Exist?

I understand the difference between roles and policies but the question
is why these two exists?
I mean why not use AWS Services with Policies?
thanks
IAM roles are similar to IAM users. We create roles to execute operations on required AWS Service.
For example: We can create a role that can perform a write operation
on DynamoDB table and assign that role to a lambda function. Then the
lambda function can use this role's privilege to write something on
DynamoDB.
Policies are simply JSON documents in which we can specify permissions: operations can be allowed or denied. Policies are attached to IAM identities such as users, groups and roles.
So the question is why both exists, why not use AWS service with Policies. The simple answer is we actually are using the AWS services with policies but in the name of IAM user or roles.
Policies get assigned to Roles. Roles do nothing on their own. You should use roles for services for simplicity and security. When assigning roles to a service you don't need to provide AWS access keys directly to these services anymore since they will be provided to the environment by the role. This is much more secure and simple then needing to pass these items to a service or application running on AWS and needing to secure them both on the service and in code.