--- sourceDocument: Yokohama IT Operations Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # AWS Elastic Beanstalk Application # AWS Elastic Beanstalk Application pattern-based discovery {#ariaid-title1} * Release version: Yokohama * * Updated May 13, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of AWS Elastic Beanstalk Application pattern-based discovery The AWS Elastic Beanstalk Application pattern-based discovery enables ServiceNow customers to identify and map Elastic Beanstalk applications within their AWS cloud environments. This discovery uses the Discovery and Service Mapping Patterns application, which must be updated to the latest version for optimal functionality. The process supports detailed inventory population in both CMDB and non-CMDB tables, providing comprehensive visibility of Elastic Beanstalk resources. Show full answer Show less ## Key Features * **Pattern Activation:** The Elastic Beanstalk discovery pattern is disabled by default and must be enabled. From Visibility Content version 6.28.0 onward, enabling or disabling patterns is simplified and does not count as a customization, ensuring patterns receive updates seamlessly. * **Discovery Prerequisites:** Customers must verify AWS discovery prerequisites and ensure that Elastic Beanstalk resources are not listed in the Resource Inclusion List to prevent duplicate discoveries. * **GovCloud Support:** Discovery of AWS GovCloud accounts requires configuration using a datacenter URL when creating AWS service accounts. * **Data Population:** Discovery populates data across: * **Non-CMDB Tables:** Using the "Amazon AWS - Elastic Beanstalk Application - Extended Inventory (LP)" pattern, data is stored in non-CMDB AWS tables accessible via ServiceNow navigation. * **CMDB Tables:** Key Elastic Beanstalk application data is stored in the Cloud App Server \[cmdbcicloudappserver\] table, including name, ARN, type, install status, and operational status. * **CI Relationships and References:** The discovery pattern creates relationships such as "Hosted on" between Cloud App Servers and AWS Datacenters, and references that link Elastic Beanstalk applications to their Cloud App Server records. * **AWS Tag Collection:** Tags associated with Elastic Beanstalk applications are collected and stored in the Key Value \[cmdbkeyvalue\] table, linked back to the Cloud App Server configuration item. ## What to Expect By implementing this discovery pattern, ServiceNow customers can expect automated, up-to-date detection of AWS Elastic Beanstalk applications within their cloud environments. This facilitates improved configuration management, operational insight, and asset tracking. The discovery populates detailed application metadata and relationships in the CMDB, enhancing service mapping and impact analysis. Discovery and Service Mapping Patterns finds AWS Elastic Beanstalk Applications on your cloud environment. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store. ## Pattern-based discovery and mapping requirements {#aws-elastic-beanstalk-application__section_rpj_fj2_bgc} Verify the AWS discovery prerequisites : For more information, see the prerequisites section in [Amazon AWS Cloud components discovery using patterns](https://servicenow-prod.fluidtopics.net/nnBwzYmMo_kpTZpG3y5~xQ "Discovery and Service Mapping Patterns uses patterns to discover components of the Amazon AWS Cloud deployment during horizontal discovery. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store."). Remove resources from the Resource Inclusion List table : Verify that the relevant resource isn't listed in the Resource Inclusion List \[sa_cloud_inventory_resource_whitelist\] table to avoid duplicate discovery. For more information on removing resources from the Resource Inclusion List, see [Amazon Web Services (AWS) Resource Inventory](https://servicenow-prod.fluidtopics.net/U2bwxjeyIbyEXySOOJQkYA "The ServiceNow Discovery and Service Mapping applications can find and map the AWS resources available by AWS Config Service. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store."). Enable the relevant pattern : The pattern for this service is disabled by default. Starting with Visibility Content version 6.28.0, activating or deactivating a pattern won't be considered a customization, and it will continue to receive updates. Patterns that were previously activated or deactivated will reset to the latest predefined version after upgrading while retaining the last active field value. For more information on enabling patterns, see [Activate a disabled pattern](https://servicenow-prod.fluidtopics.net/R5W5GP640V_5uNIhVNRPCw "If you want to use a pattern for discovery that's disabled by default, activate it manually.").{#aws-elastic-beanstalk-application__activating-disabled-pattern-not-customization} Configure the Discovery schedule to support GovCloud : Discovering AWS GovCloud (US) accounts requires using a datacenter URL when setting up an AWS service account. For more information, see [Create AWS service accounts](https://servicenow-prod.fluidtopics.net/CvTA68TY3ph_FRR49RbdPg "Create AWS service accounts on the ServiceNow AI Platform to access your AWS account during AWS discovery."). Discovery and Service Mapping Patterns application populates data in both CMDB and non-CMDB tables. ## Data stored in non-CMDB tables {#aws-elastic-beanstalk-application__section_aq4_qkq_hfc} Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Amazon AWS - Elastic Beanstalk Application - Extended Inventory (LP) pattern. You can review the non-CMDB AWS tables by navigating to AllConfigurationAWS. You can also search the navigation filter for the specific pattern name. {#aws-elastic-beanstalk-application__table_non_cmdb__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the Elastic Beanstalk application. | | Object ID \[object_id\] | The Amazon Resource Name (ARN) of the Elastic Beanstalk application. | | Configuration Item \[configuration_item\] | References the Cloud App Server \[cmdb_ci_cloud_appserver\] table. | [Table 1. AWS Elastic Beanstalk Application \[cmdb_aws_elastic_beanstalk_application\]] {#aws-elastic-beanstalk-application__table_non_cmdb} ## Data stored in CMDB tables {#aws-elastic-beanstalk-application__section_ggp_ql2_bgc} Discovery and Service Mapping Patterns application populates data in the CMDB when running the Amazon AWS - Elastic Beanstalk Application - Extended Inventory (LP) pattern. {#aws-elastic-beanstalk-application__table_cmdb__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the Elastic Beanstalk application. | | Object ID \[object_id\] | The ARN of the Elastic Beanstalk application. | | Type \[type\] | Type of resource. The value is set to AWS::ElasticBeanstalk::Application. | | Install Status \[install_status\] | Install status of the resource. Default value is Installed. | | Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. | [Table 2. Cloud App Server \[cmdb_ci_cloud_appserver\]] {#aws-elastic-beanstalk-application__table_cmdb} ## CI relationships {#aws-elastic-beanstalk-application__section_dc4_ghc_dgc} The Amazon AWS - Elastic Beanstalk Application - Extended Inventory (LP) pattern creates the following relationships and references to support AWS Elastic Beanstalk Application discovery. References link to records in other tables and don't appear in the CI Relationship \[cmdb_rel_ci\] table. {#aws-elastic-beanstalk-application__table_relationships__entry__3} | CI | Relationship | CI | |-|-|-| | Cloud App Server \[cmdb_ci_cloud_appserver\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | [Table 3. CI relationships] {#aws-elastic-beanstalk-application__table_relationships} {#aws-elastic-beanstalk-application__table_ci_references__entry__3} | CI | Field | Referenced CI | |-|-|-| | AWS Elastic Beanstalk Application \[cmdb_aws_elastic_beanstalk_application\] | Configuration Item \[configuration_item\] | Cloud App Server \[cmdb_ci_cloud_appserver\] | | Key Value \[cmdb_key_value\] | Configuration item \[configuration_item\] | Cloud App Server \[cmdb_ci_cloud_appserver\] | [Table 4. CI references] {#aws-elastic-beanstalk-application__table_ci_references} ## AWS Tag discovery {#aws-elastic-beanstalk-application__section_lyw_zhc_dgc} The Amazon AWS - Elastic Beanstalk Application - Extended Inventory (LP) pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#aws-elastic-beanstalk-application__table_ojy_vss_5hc__entry__2} | Field | Description | |-|-| | Key \[key\] | Tag name. | | Value \[value\] | Tag value. | | Configuration item \[configuration_item\] | References the Cloud App Server \[cmdb_ci_cloud_appserver\] table. | [Table 5. Key Value \[cmdb_key_value\]] {#aws-elastic-beanstalk-application__table_ojy_vss_5hc} *[\>]: and then