AWS guidance documentation change
Summary
Added comprehensive documentation covering prerequisites, supported regions, cost analysis, security measures, quotas, deployment sizing, and disaster recovery planning.
Security assessment
The changes include a dedicated 'Security' section detailing encryption, IAM practices, network controls, and compliance, but there's no evidence of addressing a specific vulnerability. This adds documentation about standard security features rather than responding to a security incident.
Diff
diff --git a/guidance/latest/connected-mobility-on-aws/plan-your-deployment.md b/guidance/latest/connected-mobility-on-aws/plan-your-deployment.md index c6b292e32..4a9499bd8 100644 --- a//guidance/latest/connected-mobility-on-aws/plan-your-deployment.md +++ b//guidance/latest/connected-mobility-on-aws/plan-your-deployment.md @@ -1 +1,3 @@ -[Documentation](/index.html)[Guidance for Connected Mobility on AWS](https://aws.amazon.com/solutions/guidance/connected-mobility-on-aws/)[Implementation Guide](guidance-overview.html) +[Documentation](/index.html)[Guidance for Connected Mobility on AWS](https://aws.amazon.com/solutions/guidance/connected-mobility-on-aws/)[Implementation Guide](solution-overview.html) + +PrerequisitesSupported AWS RegionsCostSecurityQuotasDeployment sizingDisaster recovery @@ -4,0 +7,723 @@ +This section describes the prerequisites, supported Regions, cost, security, and quota considerations before deploying the guidance. + +## Prerequisites + +Before deploying the guidance, ensure you have the following prerequisites: + +### Software requirements + +**Required software:** + + * [AWS CLI v2](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html) \- Command line tool for AWS + + * [Node.js 18.x or later](https://nodejs.org/) \- JavaScript runtime + + * [Python 3.9 or later](https://www.python.org/downloads/) \- Python runtime + + * [AWS CDK v2.100.0 or later](https://docs.aws.amazon.com/cdk/v2/guide/getting_started.html) \- Infrastructure as code framework + + * [Make](https://www.gnu.org/software/make/) \- Build automation tool + + * [Git](https://git-scm.com/) \- Version control system + + + + +### AWS account requirements + +**Account setup:** + + * An AWS account with appropriate IAM permissions + + * AWS credentials configured (via `aws configure` or environment variables) + + * Sufficient service quotas for the resources being deployed + + * CDK bootstrap completed in target account and region + + + + +**Required IAM permissions:** + +The IAM user or role deploying the guidance needs permissions to create and manage: + + * AWS CloudFormation stacks + + * IAM roles and policies + + * Amazon VPC and networking resources + + * Amazon DynamoDB tables + + * Amazon S3 buckets + + * AWS IoT Core resources + + * Amazon MSK clusters + + * Amazon Kinesis Data Analytics applications + + * AWS Lambda functions + + * Amazon API Gateway APIs + + * Amazon Cognito user pools + + * Amazon Location Service resources + + * Amazon CloudFront distributions + + * Amazon ElastiCache clusters + + + + +We recommend using the `AdministratorAccess` managed policy for initial deployment, then creating a custom policy with least-privilege permissions for production deployments. + +### Network requirements + +**VPC considerations:** + +The solution creates a new VPC by default with the following configuration: + + * CIDR block: 10.0.0.0/16 (customizable) + + * Public subnets: 2 (across 2 Availability Zones) + + * Private subnets: 2 (across 2 Availability Zones) + + * NAT Gateway: 1 per Availability Zone + + * Internet Gateway: 1 + + + + +**Existing VPC:** + +To use an existing VPC, set the `VPC_ID` environment variable before deployment. The VPC must have: + + * At least 2 private subnets across 2 Availability Zones + + * Internet connectivity via NAT Gateway or NAT instance + + * Sufficient IP address space for MSK and ElastiCache + + + + +## Supported AWS Regions + +For the most current availability of AWS services by Region, see the [AWS Regional Services List](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/). + +Guidance for Connected Mobility on AWS is supported in the following AWS Regions: + +Region name | Region code +---|--- +US East (Ohio) | us-east-2 +US East (N. Virginia) | us-east-1 +US West (Oregon) | us-west-2 +Europe (Ireland) | eu-west-1 +Europe (Frankfurt) | eu-central-1 +Asia Pacific (Tokyo) | ap-northeast-1 +Asia Pacific (Sydney) | ap-southeast-2 + +###### Note + +Not all AWS services are available in all Regions. Verify that Amazon MSK, Amazon Kinesis Data Analytics, and Amazon Location Service are available in your target Region before deployment. + +## Cost + +You are responsible for the cost of the AWS services used while running this solution. Prices are subject to change. For full details, see the pricing webpage for each AWS service used in this solution. + +We recommend creating a [budget](https://docs.aws.amazon.com/cost-management/latest/userguide/budgets-create.html) through [AWS Cost Explorer](https://aws.amazon.com/aws-cost-management/aws-cost-explorer/) to help manage costs. + +### Cost model assumptions + +The cost estimates below are based on the following telemetry profile per vehicle: + + * **Telemetry frequency:** 1 message every 2 seconds while driving (260 signals per message) + + * **Average driving time:** 2 hours per day per vehicle + + * **Messages per vehicle per day:** ~3,600 + + * **Message size:** ~2 KB (compressed JSON with 260 signals) + + * **Data per vehicle per month:** ~216 MB + + * **Active fleet percentage:** 30% of vehicles driving at any given time during peak hours + + + + +All estimates use US East (N. Virginia) pricing as of March 2026. + +### Cost by fleet size + +Fleet Size | MSK | Flink | Infrastructure | Application | Total/Month +---|---|---|---|---|--- +100 vehicles | $67 | $108 | $58 | $32 | **~$265** +500 vehicles | $67 | $108 | $58 | $35 | **~$268** +1,000 vehicles | $194 | $108 | $58 | $40 | **~$400** +5,000 vehicles | $194 | $324 | $58 | $55 | **~$631** +10,000 vehicles | $389 | $540 | $71 | $75 | **~$1,075** +25,000 vehicles | $583 | $864 | $84 | $120 | **~$1,651** +50,000 vehicles | $972 | $1,296 | $97 | $200 | **~$2,565** +100,000 vehicles | $1,944 | $2,160 | $130 | $350 | **~$4,584** + +**Cost per vehicle per month:** + +Fleet Size | Total/Month | Per Vehicle +---|---|--- +100 | $265 | $2.65 +1,000 | $400 | $0.40 +10,000 | $1,075 | $0.11 +50,000 | $2,565 | $0.05 +100,000 | $4,584 | $0.05 + +The per-vehicle cost drops dramatically as fleet size increases because the fixed infrastructure costs (MSK cluster, NAT Gateway, ElastiCache) are amortized across more vehicles. The breakpoint for cost efficiency is around **5,000–10,000 vehicles** , where per-vehicle cost drops below $0.15/month. + +### Detailed cost breakdown + +#### Amazon MSK (message streaming) + +MSK is the largest cost driver (40-50% of total). Cost scales with broker count and instance size. + +Fleet Size | Configuration | Messages/sec (peak) | Monthly Cost +---|---|---|--- +Up to 500 | 3 × kafka.t3.small (2 vCPU, 2 GB) | ~250 | $67