A utility enterprise is designing a new cloud-based smart-grid monitoring platform. The system handles two primary data workloads. First, a time-series telemetry ingest workload receives smart meter readings at a rate of writes/second with sub-millisecond latency. Second, an online transaction processing (OLTP) workload manages customer billing and subscription metadata. The billing metadata requires a disaster recovery strategy with a Recovery Time Objective (RTO) of less than minutes and a Recovery Point Objective (RPO) of less than seconds across AWS regions. Additionally, weekly billing reports must be saved to object storage and securely shared with a third-party auditing AWS account. Encryption-at-rest is mandatory for these reports, and the primary account must maintain full control over the encryption key policy. Which database and storage architecture should a solutions architect design to satisfy these requirements with the lowest operational overhead?
- ADeploy Amazon DynamoDB with auto-scaling to ingest the smart meter telemetry. Deploy Amazon Aurora PostgreSQL in the primary region for billing metadata, and configure automated hourly snapshots copied to a secondary region. In a disaster recovery event, restore the database from the latest snapshot in the secondary region using AWS CloudFormation. Store the weekly reports in an Amazon S3 bucket encrypted with a KMS Customer Managed Key (CMK) and share them with the auditing account.
- BDeploy Amazon DynamoDB with auto-scaling to ingest the smart meter telemetry. Use a Multi-AZ deployment of Amazon RDS for PostgreSQL for the billing metadata, and configure the billing application to read from the standby database instance in the secondary Availability Zone to scale read capacity during report generation. Store the weekly reports in Amazon S3 encrypted with a KMS Customer Managed Key (CMK) and grant cross-account permissions via the key policy.
- Deploy Amazon DynamoDB with auto-scaling to ingest the smart meter telemetry. Deploy Amazon Aurora Global Database for the transactional billing metadata, utilizing cross-region replicas to achieve the target RPO. Store the weekly reports in an Amazon S3 bucket encrypted with a KMS Customer Managed Key (CMK), and configure both the KMS key policy and the S3 bucket policy to allow access to the auditing account.Cevap
- DDeploy Amazon DynamoDB with auto-scaling to ingest the smart meter telemetry. Deploy Amazon Aurora Global Database for the billing metadata to meet the cross-region disaster recovery requirements. Store the weekly reports in an Amazon S3 bucket encrypted with the default AWS-managed KMS key (aws/s3), and configure an S3 bucket policy that permits read access to the external auditing account.