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