AWS solutions documentation change
Summary
Formatting changes including removal of extra line breaks, changing bullet point formatting, and minor text formatting adjustments. Content remains largely the same.
Security assessment
The changes are purely formatting-related with no substantive content changes. The existing security-related content (AWS WAF, KMS, Secrets Manager) remains unchanged.
Diff
diff --git a/solutions/latest/scalable-analytics-using-apache-druid-on-aws/aws-services-in-this-solution.md index ae396c968..d4c1b1660 100644 --- a/solutions/latest/scalable-analytics-using-apache-druid-on-aws/aws-services-in-this-solution.md +++ b/solutions/latest/scalable-analytics-using-apache-druid-on-aws/aws-services-in-this-solution.md @@ -9,21 +9,15 @@ AWS service | Description -[Amazon S3](https://aws.amazon.com/s3/) | **Core.** The solution provisions the following S3 buckets: - - * Deep storage bucket to store the segments. - * Installation bucket to store the installation files as needed by the solution. - * Access logging bucket to store the access logs from ALB, and S3 buckets. - - -[Amazon Elastic Compute Cloud](https://aws.amazon.com/ec2/) | **Core.** The solution provisions EC2 instances to run Apache Druid and Apache ZooKeeper. -[Amazon Aurora](https://aws.amazon.com/rds/aurora/) | **Core.** The solution provisions an Aurora PostgreSQL cluster to serve as the metadata storage. -[Amazon Elastic Load Balancer](https://aws.amazon.com/elasticloadbalancing/) | **Core.** Application load balancer to distribute the incoming traffic among the Druid query nodes. -[AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) | **Core.** Secrets to store master user credentials for Aurora DB cluster, and credentials of the users “admin” and “druid_system”. -[AWS Key Management System](https://aws.amazon.com/kms/) | **Core.** KMS keys used to encrypt the data in S3 buckets, Aurora cluster, SNS topic, and EFS. -[Amazon Elastic Block Store](https://aws.amazon.com/ebs/) | **Core.** EBS volumes to serve as segment cache for historical nodes. -[Amazon CloudWatch](https://aws.amazon.com/cloudwatch/) | **Supporting.** The solution uses CloudWatch for logs, metrics, alarms, and dashboard. -[Amazon Simple Notification Service](https://aws.amazon.com/sns/) | **Supporting.** Topics to receive CloudWatch alarm notifications and auto scaling group scaling event notifications. -[AWS WAF](https://aws.amazon.com/waf/) | **Supporting.** Protect Druid web console and API endpoints from common application-layer exploits that can affect availability or consume excessive resources. -[AWS Systems Manager](https://aws.amazon.com/systems-manager/) | **Supporting.** Provides application-level resource monitoring and visualization of resource operations and cost data. -[Amazon EventBridge](https://aws.amazon.com/eventbridge/) | **Supporting.** The solution creates an EventBridge rule to receive the event from auto scaling group. -[Amazon Elastic Kubernetes Service](https://aws.amazon.com/eks/) | **Optional.** When opting for EKS deployment, the solution initializes an EKS cluster to execute the Apache Druid workload. -[Amazon Elastic File System](https://aws.amazon.com/efs/) | **Optional.** When opting for EKS Fargate deployment, the solution creates an EFS filesystem to provide storage to Fargate workloads. -[Amazon Route 53](https://aws.amazon.com/route53/) | **Optional.** The solution provides the option for integration with Route 53 to manage the domain for accessing the Druid cluster. +[Amazon S3](https://aws.amazon.com/s3/) | **Core**. The solution provisions the following S3 buckets: * Deep storage bucket to store the segments. * Installation bucket to store the installation files as needed by the solution. * Access logging bucket to store the access logs from ALB, and S3 buckets. +[Amazon Elastic Compute Cloud](https://aws.amazon.com/ec2/) | **Core**. The solution provisions EC2 instances to run Apache Druid and Apache ZooKeeper. +[Amazon Aurora](https://aws.amazon.com/rds/aurora/) | **Core**. The solution provisions an Aurora PostgreSQL cluster to serve as the metadata storage. +[Amazon Elastic Load Balancer](https://aws.amazon.com/elasticloadbalancing/) | **Core**. Application load balancer to distribute the incoming traffic among the Druid query nodes. +[AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) | **Core** Secrets to store master user credentials for Aurora DB cluster, and credentials of the users `admin` and `druid_system`. +[AWS Key Management System](https://aws.amazon.com/kms/) | **Core** KMS keys used to encrypt the data in S3 buckets, Aurora cluster, SNS topic, and EFS. +[Amazon Elastic Block Store](https://aws.amazon.com/ebs/) | **Core** EBS volumes to serve as segment cache for historical nodes. +[Amazon CloudWatch](https://aws.amazon.com/cloudwatch/) | **Supporting** The solution uses CloudWatch for logs, metrics, alarms, and dashboard. +[Amazon Simple Notification Service](https://aws.amazon.com/sns/) | **Supporting** Topics to receive CloudWatch alarm notifications and auto scaling group scaling event notifications. +[AWS WAF](https://aws.amazon.com/waf/) | **Supporting** Protect Druid web console and API endpoints from common application-layer exploits that can affect availability or consume excessive resources. +[AWS Systems Manager](https://aws.amazon.com/systems-manager/) | **Supporting** Provides application-level resource monitoring and visualization of resource operations and cost data. +[Amazon EventBridge](https://aws.amazon.com/eventbridge/) | **Supporting** The solution creates an EventBridge rule to receive the event from auto scaling group. +[Amazon Elastic Kubernetes Service](https://aws.amazon.com/eks/) | **Optional** When opting for EKS deployment, the solution initializes an EKS cluster to execute the Apache Druid workload. +[Amazon Elastic File System](https://aws.amazon.com/efs/) | **Optional** When opting for EKS Fargate deployment, the solution creates an EFS filesystem to provide storage to Fargate workloads. +[Amazon Route 53](https://aws.amazon.com/route53/) | **Optional** The solution provides the option for integration with Rout 53 to manage the domain for accessing the Druid cluster.