Modifying the resources that Elastic Beanstalk creates for your environment - AWS Elastic Beanstalk

Modifying the resources that Elastic Beanstalk creates for your environment

The resources that Elastic Beanstalk creates for your environment have names. You can use these names to get information about the resources with a function, or modify properties on the resources to customize their behavior. This topic describes the AWS resources that Elastic Beanstalk uses in the different types of environments.


The previous topic Custom resources provides some uses cases and examples for customizing environment resources. You can also find more examples of configuration files in the later topic Custom resource examples.

Web server environments have the following resources.

Web server environments
  • AWSEBAutoScalingGroup (AWS::AutoScaling::AutoScalingGroup) – The Auto Scaling group attached to your environment.

  • One of the following two resources.


    If your environment uses functionality that requires Amazon EC2 launch templates, and your user policy lacks the required permissions, creating or updating the environment might fail. Use the AdministratorAccess-AWSElasticBeanstalk managed user policy, or add the required permissions to your custom policy.

  • AWSEBEnvironmentName (AWS::ElasticBeanstalk::Environment) – Your environment.

  • AWSEBSecurityGroup (AWS::EC2::SecurityGroup) – The security group attached to your Auto Scaling group.

  • AWSEBRDSDatabase (AWS::RDS::DBInstance) – The Amazon RDS DB instance attached to your environment (if applicable).

In a load-balanced environment, you can access additional resources related to the load balancer. Classic load balancers have a resource for the load balancer and one for the security group attached to it. Application and network load balancers have additional resources for the load balancer's default listener, listener rule, and target group.

Load-balanced environments

Worker environments have resources for the SQS queue that buffers incoming requests, and a Amazon DynamoDB table that the instances use for leader election.

Worker environments
  • AWSEBWorkerQueue (AWS::SQS::Queue) – The Amazon SQS queue from which the daemon pulls requests that need to be processed.

  • AWSEBWorkerDeadLetterQueue (AWS::SQS::Queue) – The Amazon SQS queue that stores messages that cannot be delivered or otherwise were not successfully processed by the daemon.

  • AWSEBWorkerCronLeaderRegistry (AWS::DynamoDB::Table) – The Amazon DynamoDB table that is the internal registry used by the daemon for periodic tasks.