π‘οΈ AWS Connect Instance flow logs are not enabledπ’
- Contextual name: π‘οΈ Instance flow logs are not enabledπ’
- ID:
/ce/ca/aws/connect/instance-flow-logs - Tags:
- π’ Policy with categories
- π’ Policy with type
- π’ Production policy
- Policy Type:
COMPLIANCE_POLICY - Policy Categories:
SECURITY,RELIABILITY
Logicβ
- π§ prod.logic.yamlπ’
Similar Policiesβ
Descriptionβ
Descriptionβ
This policy identifies AWS Connect Instances the are not configured to generate contact flow logs and deliver them to a designated Amazon CloudWatch Logs log group.
Rationaleβ
Contact flow logs capture detailed execution data as customer interactions traverse defined contact flows. When streamed to CloudWatch Logs, this information enables:
- Operational troubleshooting by identifying failed, stalled, or dropped interactions.
- Performance monitoring through analysis of queue wait times, latency, and contact flow execution behavior.
- Security and compliance auditing by maintaining a centralized and immutable audit trail of customer interactions and agent actions.
Impactβ
If contact flow logging is not enabled, visibility into customer interaction behavior is significantly reduced, making issue diagnosis and experience optimization more difficult.
Enabling contact flow logs may result in additional costs associated with CloudWatch Logs data ingestion, storage, and retrieval.
Auditβ
This policy flags an AWS Connect Instance as
INCOMPLIANTif the the instance'sCONTACTFLOW_LOGS Attributeis set to false.
Remediationβ
Remediationβ
Enable Contact Flow Logsβ
To ensure that contact flow execution data is captured and delivered to CloudWatch Logs, enable the Contact Flow Logs attribute for the Amazon Connect instance.
From Command Lineβ
Use the following command to enable contact flow logging for the specified instance:
aws connect update-instance-attribute \
--instance-id {{connect-instance-id}} \
--attribute-type CONTACTFLOW_LOGS \
--value trueConsiderationsβ
- Enabling contact flow logs applies only to new contact flow executions; historical data is not retroactively captured.
- Ensure that the Amazon Connect service-linked role has sufficient permissions to publish logs to the configured CloudWatch Logs log group.
- Additional costs may be incurred for CloudWatch Logs ingestion, storage, and retrieval.
policy.yamlβ
Linked Framework Sectionsβ
| Section | Sub Sections | Internal Rules | Policies | Flags | Compliance |
|---|---|---|---|---|---|
| πΌ AWS Foundational Security Best Practices v1.0.0 β πΌ [Connect.2] Amazon Connect instances should have CloudWatch logging enabled | 1 | no data | |||
| πΌ Cloudaware Framework β πΌ Logging and Monitoring Configuration | 75 | no data |