AWS Well-Architected Security Pillarvs6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673)
See exactly how AWS Well-Architected Security Pillar controls map to 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673). Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
AWS Well-Architected Security Pillar maps to 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) with 24% coverage across 6 directly mapped controls. Analysis of 25 AWS Well-Architected Security Pillar controls identifies 19 compliance gaps — primarily concentrated in AWS Well-Architected Security Pillar: Identity & Access in Cloud.
Source: TheArtOfService Knowledge Graph | 25 controls analysed | 693 frameworks | 819K+ cross-framework mappings
Control Mappings
Showing 11 of 11 mapped controls across 3 domains. Sign up to explore all 819K+ mappings across 693 frameworks.
AWS Well-Architected Security Pillar: Cloud Governance(7 mappings)
AWS Well-Architected Security Pillar: Data Protection in Cloud(3 mappings)
AWS Well-Architected Security Pillar: Cloud Operations & Monitoring(1 mappings)
Related Comparisons
Other AWS Well-Architected Security Pillar comparisons
Other 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 693 frameworks — at a fraction of consulting costs.
Free
- ✓ 693 framework browser
- ✓ Cross-framework mappings (819K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between AWS Well-Architected Security Pillar and 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673)?
AWS Well-Architected Security Pillar has 25 controls across its framework, while 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) covers 41 controls. Direct mapping analysis identifies 6 overlapping controls (24% coverage). The frameworks diverge most significantly in AWS Well-Architected Security Pillar: Identity & Access in Cloud, where 5 AWS Well-Architected Security Pillar controls have no direct 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) equivalent.
How many controls map between AWS Well-Architected Security Pillar and 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673)?
Of 25 total AWS Well-Architected Security Pillar controls, 6 map directly to 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) controls — representing 24% coverage. The remaining 19 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping AWS Well-Architected Security Pillar to 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673)?
19 AWS Well-Architected Security Pillar controls have no direct equivalent in 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673). The highest concentration of gaps is in AWS Well-Architected Security Pillar: Identity & Access in Cloud with 5 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.
Which control domains have the most gaps between AWS Well-Architected Security Pillar and 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673)?
The domain with the highest gap count is AWS Well-Architected Security Pillar: Identity & Access in Cloud (5 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.