Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →toddkasper/aws-solutions-architect-professional
Designing and evaluating complex AWS architectures — multi-account AWS Organizations, hybrid and cross-account networking (Transit Gateway, PrivateLink, Direct Connect), business-continuity and DR design, migration and modernization strategy (the 7 Rs), and cost/resilience/performance trade-offs at enterprise scale.
Passed 18 of 22 test cases with the skill, and 16 of 22 without it.
2 fixed16 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are designing an immutable audit logging service for financial compliance. An engineer proposed using Amazon QLDB for the append-only ledger database. What database service should we select for ledger and immutable-audit workloads on AWS today?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends Aurora PostgreSQL for ledger and immutable audit workloads instead of Amazon QLDB. | Missed | Passed |
| Identifies Amazon QLDB as deprecated or no longer supported. | Passed | Passed |
The instructions your model reads when the skill loads.
Operational playbook for designing complex AWS architectures. Each section states the rule an architect applies when reviewing or designing: decision criteria for picking services, anti-patterns to catch in design reviews. Verify against the live account — limits, pricing, and feature availability change frequently.
Load this skill when… evaluating or designing complex AWS architectures across multiple accounts or regions; choosing connectivity patterns (TGW, VPC Peering, Direct Connect, PrivateLink); planning migration strategy (7 Rs, tooling, wave planning); or making cost/resilience/performance trade-offs at enterprise scale. Not this skill: pipeline/IaC delivery → see
aws-devops-engineer-professional; deep security control design → seeaws-security-specialty.
Study resources, whitepapers, practice exams, and credential logistics: references/study-resources.md.
Verify steps assume nothing about your tooling — use your project's MCP/automation, the AWS CLI (
aws) or CloudShell, or the AWS Console, in that order of preference.
[volatile — verify live], Direct Connect port speeds and availability by location [volatile — verify live], Lambda default concurrent executions per account per region [volatile — verify live], Shield Advanced monthly pricing [volatile — verify live], Snow family device capacity and lead times [volatile — verify live], and service quota defaults for any critical-path service before a scaling event.[volatile — verify live] (changes with AWS service updates) or [opinion — house style] (a defensible default, not the only valid choice).An AWS Organization with multiple accounts is the baseline for any enterprise. Accounts are the primary isolation boundary — IAM policies cannot span accounts without explicit cross-account trust.
Pick the right structure:
| Scenario | Recommendation |
|---|---|
| Enforce policy guardrails org-wide | Service Control Policies (SCPs) on OUs in AWS Organizations |
| Automate account vending + guardrails | AWS Control Tower with Landing Zone |
| Central identity with SSO across accounts | IAM Identity Center (formerly SSO) with SAML/OIDC federation |
| Share resources across accounts (VPCs, subnets, RAM) | AWS Resource Access Manager |
| Centralize security findings | Security Hub with delegated admin account |
| Centralize CloudTrail logs | Org-level trail to a dedicated logging account |
test cases passed, vs 16 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.