Wird AWS-Services für Datenquellen unterstützt

In der folgenden Tabelle sind diejenigen aufgeführt AWS-Services , die automatisch nach CloudWatch Protokollen als Datenquellen kategorisiert werden:

Name der Datenquelle (@data_source_name -Feld)	Datenquellentyp (@data_source_type -Feld)
`amazon_api_gateway`	`access`
`amazon_bedrock_agentcore`	`browser_usage`
`amazon_bedrock_agentcore`	`code_interpreter_application`
`amazon_bedrock_agentcore`	`code_interpreter_usage`
`amazon_bedrock_agentcore`	`gateway_application`
`amazon_bedrock_agentcore`	`identity_workload_application`
`amazon_bedrock_agentcore`	`memory_application`
`amazon_bedrock_agentcore`	`online_evaluation_config`
`amazon_bedrock_agentcore`	`runtime_application`
`amazon_bedrock_agentcore`	`runtime_usage`
`amazon_bedrock_agents`	`application`
`amazon_bedrock_agents`	`event`
`amazon_bedrock_knowledge_bases`	`application`
`amazon_cloudfront`	`access`
`amazon_cloudfront`	`connection`
`amazon_cloudwatch`	`rum_app_monitor`
`amazon_cognito`	`user_pool`
`amazon_ec2`	`verified_access`
`amazon_eks`	`api_server`
`amazon_eks`	`audit`
`amazon_eks`	`authenticator`
`amazon_eks`	`controller_manager`
`amazon_eks`	`scheduler`
`amazon_elasticache`	`cluster`
`amazon_eventbridge`	`eventbus_error`
`amazon_eventbridge`	`eventbus_info`
`amazon_eventbridge`	`pipes_execution`
`amazon_interactive_video_service`	`chat`
`amazon_managed_prometheus`	`scraper`
`amazon_managed_prometheus`	`workspace`
`amazon_msk`	`broker`
`amazon_msk`	`connect`
`amazon_opensearch_service`	`pipeline`
`amazon_q_business`	`events`
`amazon_q_business`	`sync_job`
`amazon_q_connect`	`events`
`amazon_route53`	`global_resolver_query`
`amazon_route53`	`hosted_zones`
`amazon_route53`	`profiles_resolver_query`
`amazon_route53`	`resolver_query`
`amazon_sagemaker`	`workteam_activity`
`amazon_ses`	`ingress_endpoints`
`amazon_ses`	`rule_sets`
`amazon_ses`	`traffic_policy`
`amazon_vpc`	`flow`
`amazon_vpc`	`route_server_peer`
`amazon_vpc_lattice`	`access`
`amazon_vpc_lattice`	`resource_access`
`amazon_workmail`	`access_control`
`amazon_workmail`	`authentication`
`amazon_workmail`	`personal_access`
`amazon_workmail`	`workmail_access`
`amazon_workmail`	`workmail_availability`
`aws_b2b_data_interchange`	`execution`
`aws_backup`	`data_access`
`aws_backup`	`hypervisor`
`aws_clean_rooms`	`analysis`
`aws_client_vpn`	`connection`
`aws_client_vpn`	`event`
`aws_cloudtrail`	`data`
`aws_cloudtrail`	`management`
`aws_elemental_mediapackage`	`egress_access`
`aws_elemental_mediapackage`	`ingress_access`
`aws_elemental_mediatailor`	`ad_decision`
`aws_elemental_mediatailor`	`manifest`
`aws_elemental_mediatailor`	`transcode`
`aws_entity_resolution`	`id_mapping_workflow`
`aws_entity_resolution`	`matching_workflow`
`aws_iot_fleetwise`	`error`
`aws_mainframe_modernization`	`batch_job`
`aws_mainframe_modernization`	`config`
`aws_mainframe_modernization`	`console`
`aws_mainframe_modernization`	`dataset_import`
`aws_network_firewall`	`alert`
`aws_network_firewall`	`flow`
`aws_network_firewall`	`tls`
`aws_nlb`	`access`
`aws_pcs`	`job_completion`
`aws_pcs`	`scheduler`
`aws_shield`	`protection_flow`
`aws_step_functions`	`express`
`aws_step_functions`	`standard`
`aws_transfer_family`	`server`
`aws_waf`	`access`

Warnung JavaScript ist in Ihrem Browser nicht verfügbar oder deaktiviert.

Zur Nutzung der AWS-Dokumentation muss JavaScript aktiviert sein. Weitere Informationen finden auf den Hilfe-Seiten Ihres Browsers.

Dokumentkonventionen

Funktionen, die durch Datenquellen ermöglicht werden

Unterstützte Quellen von Drittanbietern für Datenquellen