I'm following a course on AWS Beanstalk that might be out of date. In IAM Management Console a user is added and one of the existing policies attached directly is AWSElasticBeanstalkFullAccess
, which I cannot find while filtering policies myself.
Has this changed name? How can I find it or an equivalent?
AWS Elastic Beanstalk provides two managed policies that enable you to assign full access or read-only access to all resources that Elastic Beanstalk manages. You can attach the policies to AWS Identity and Access Management (IAM) users or groups, or to roles assumed by your users.
A service role is the IAM role that Elastic Beanstalk assumes when calling other services on your behalf. For example, Elastic Beanstalk uses a service role when it calls Amazon Elastic Compute Cloud (Amazon EC2), Elastic Load Balancing, and Amazon EC2 Auto Scaling APIs to gather information.
AWS Elastic Beanstalk provides two managed policies that enable you to assign full access or read-only access to all resources that Elastic Beanstalk manages. You can attach the policies to AWS Identity and Access Management (IAM) users or groups, or to roles assumed by your users.
In the list of policies, select the check box next to AWSElasticBeanstalkReadOnly or AdministratorAccess-AWSElasticBeanstalk . Choose Policy actions, and then choose Attach . Select one or more users and groups to attach the policy to. You can use the Filter menu and the search box to filter the list of principal entities. Choose Attach policy .
Elastic Beanstalk managed policies don't provide granular permissions—they grant all permissions that are potentially needed for working with Elastic Beanstalk applications. Our managed policies also don't cover permissions to custom resources that you might add to your solution, and that aren't managed by Elastic Beanstalk.
It provides read-only access to all Elastic Beanstalk resources, and to other AWS resources that the Elastic Beanstalk console retrieves. Note that read-only access does not enable actions such as downloading Elastic Beanstalk logs so that you can read them.
AWSElasticBeanstalkFullAccess
was a managed IAM policy by AWS. They are now transitioning towards a new policy which is called AdministratorAccess-AWSElasticBeanstalk
. Its not completely the same policy. If needed to follow along with your tutorial you could create the old AWSElasticBeanstalkFullAccess
again. I would first try to use AdministratorAccess-AWSElasticBeanstalk
.
If you want to read about the transition you can do that here:
Previously, Elastic Beanstalk supported two other managed user policies, AWSElasticBeanstalkFullAccess and AWSElasticBeanstalkReadOnlyAccess. We plan on retiring these previous policies. You might still be able to see and use them in the IAM console. Nevertheless, we recommend that you transition to using the new managed user policies, and add custom policies to grant permissions to custom resources, if you have any.
You can use the waybackmachine to copy over the old policy if needed
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With