View a markdown version of this page

Scenario and architecture overview - AWS Prescriptive Guidance

Scenario and architecture overview

The government agency has three workloads in the AWS Cloud:

A cloud team provides a centralised platform for the organisation, running core services for the AWS environment. A cloud team provides core services for the AWS environment. Each workload is owned by a distinct application team, also known as a developer team or delivery team.

Core architecture

The cloud team has already established the following capabilities in the AWS Cloud:

  • Identity federation links AWS IAM Identity Center to their Microsoft Entra ID (formerly Azure Active Directory) instance. The federation enforces MFA, automatic expiry of user accounts, and the use of short-lived credentials through AWS Identity and Access Management (IAM) roles.

  • A centralised AMI pipeline is used to patch OSs and core applications with EC2 Image Builder.

  • Amazon Inspector is enabled to identify vulnerabilities, and all security findings are sent to Amazon GuardDuty for centralised management.

  • Established mechanisms are used to update application control rules, respond to cyber security events, and review compliance gaps.

  • AWS CloudTrail is used for logging and monitoring.

  • Security events, such as login of the root user, initiate alerts.

  • SCPs and VPC endpoint policies establish data perimeters for your AWS environments.

  • SCPs prevent application teams from disabling security and logging services, such as CloudTrail and AWS Config.

  • AWS Config findings are aggregated from across the whole AWS organization into a single AWS account for security.

  • The AWS Config ACSC Essential 8 conformance pack is enabled across all AWS accounts in your organization.