AWS awssupport documentation change
Summary
Updated references from 'AWS Direct Connect' to 'Direct Connect' in multiple sections and links
Security assessment
Changes involve branding/naming updates rather than security content. No security vulnerabilities or mitigations are mentioned.
Diff
diff --git a/awssupport/latest/user/fault-tolerance-checks.md b/awssupport/latest/user/fault-tolerance-checks.md index 8ba6e40c9..d21a985c7 100644 --- a//awssupport/latest/user/fault-tolerance-checks.md +++ b//awssupport/latest/user/fault-tolerance-checks.md @@ -5 +5 @@ -ALB Multi-AZAmazon Aurora MySQL cluster backtracking not enabledAmazon Aurora DB Instance AccessibilityAmazon CloudFront Origin FailoverAmazon Comprehend Endpoint Access RiskAmazon DocumentDB Single AZ ClustersAmazon DynamoDB Point-in-time RecoveryAmazon DynamoDB Table Not Included in Backup PlanAmazon EBS Not Included in AWS Backup PlanAmazon EBS SnapshotsAmazon EC2 Auto Scaling does not have ELB Health Check EnabledAmazon EC2 Auto Scaling Group has Capacity Rebalancing EnabledAmazon EC2 Auto Scaling is not deployed in multiple AZs or does not meet the minimum number of AZsAmazon EC2 Availability Zone BalanceAmazon EC2 detailed monitoring not enabledAmazon ECS AWSLogs driver in blocking modeAmazon ECS service using a single AZAmazon ECS Multi-AZ placement strategy Amazon EFS no mount target redundancyAmazon EFS not in AWS Backup planAmazon ElastiCache Multi-AZ clustersElastiCache (Redis OSS) Clusters Automatic BackupAmazon MemoryDB Multi-AZ clustersAmazon MSK brokers hosting too many partitionsAmazon MSK Cluster Multi-AZAmazon OpenSearch Service domains with less than three data nodesAmazon RDS BackupsAmazon RDS Continuous Backup Not EnabledAmazon RDS DB clusters have one DB instanceAmazon RDS DB clusters with all instances in the same Availability ZoneAmazon RDS DB clusters with all reader instances in the same Availability ZoneAmazon RDS DB Instance Enhanced Monitoring not enabledAmazon RDS DB instances have storage autoscaling turned offAmazon RDS DB instances not using Multi-AZ deploymentAmazon RDS DiskQueueDepthAmazon RDS FreeStorageSpaceAmazon RDS log_output parameter is set to tableAmazon RDS innodb_default_row_format parameter setting is unsafeAmazon RDS innodb_flush_log_at_trx_commit parameter is not 1Amazon RDS max_user_connections parameter is lowAmazon RDS Multi-AZAmazon RDS Not In AWS Backup PlanAmazon RDS Read Replicas are open in writable modeAmazon RDS resource automated backups is turned offAmazon RDS sync_binlog parameter is turned offRDS DB Cluster has no Multi-AZ replication enabledRDS Multi-AZ Standby Instance Not EnabledAmazon RDS ReplicaLagAmazon RDS synchronous_commit parameter is turned offAmazon Redshift cluster automated snapshotsAmazon Route 53 Deleted Health ChecksAmazon Route 53 Failover Resource Record SetsAmazon Route 53 High TTL Resource Record SetsAmazon Route 53 Name Server DelegationsAmazon Route 53 Resolver Endpoint Availability Zone RedundancyAmazon S3 Bucket Replication Not EnabledAmazon S3 Bucket VersioningApplication, Network, and Gateway Load Balancers Not Spanning Multiple Availability ZonesAuto Scaling available IPs in SubnetsAuto Scaling Group Health CheckAuto Scaling Group ResourcesAWS CloudHSM clusters running HSM instances in a single AZAWS Direct Connect Location ResiliencyAWS Lambda functions without a dead-letter queue configuredAWS Lambda On Failure Event DestinationsAWS Lambda VPC-enabled Functions without Multi-AZ RedundancyAWS Outposts Single Rack deploymentAWS Resilience Hub Application Component checkAWS Resilience Hub policy breachedAWS Resilience Hub resilience scoresAWS Resilience Hub assessment ageAWS Site-to-Site VPN has at least one tunnel in DOWN statusAWS STS global endpoint usage across AWS RegionsAWS Well-Architected high risk issues for reliabilityClassic Load Balancer has no multiple AZs configuredCLB Connection DrainingELB Target ImbalanceGWLB - endpoint AZ independenceLoad Balancer OptimizationNAT Gateway AZ IndependenceNetwork Firewall endpoint AZ IndependenceNetwork Firewall Multi-AZNetwork Load Balancers Cross Load BalancingNLB - Internet-facing resource in private subnetNLB Multi-AZNumber of AWS Regions in an Incident Manager replication setSingle AZ Application CheckVPC interface endpoint network interfaces in multiple AZsVPN Tunnel RedundancyActiveMQ Availability Zone RedundancyRabbitMQ Availability Zone Redundancy +ALB Multi-AZAmazon Aurora MySQL cluster backtracking not enabledAmazon Aurora DB Instance AccessibilityAmazon CloudFront Origin FailoverAmazon Comprehend Endpoint Access RiskAmazon DocumentDB Single AZ ClustersAmazon DynamoDB Point-in-time RecoveryAmazon DynamoDB Table Not Included in Backup PlanAmazon EBS Not Included in AWS Backup PlanAmazon EBS SnapshotsAmazon EC2 Auto Scaling does not have ELB Health Check EnabledAmazon EC2 Auto Scaling Group has Capacity Rebalancing EnabledAmazon EC2 Auto Scaling is not deployed in multiple AZs or does not meet the minimum number of AZsAmazon EC2 Availability Zone BalanceAmazon EC2 detailed monitoring not enabledAmazon ECS AWSLogs driver in blocking modeAmazon ECS service using a single AZAmazon ECS Multi-AZ placement strategy Amazon EFS no mount target redundancyAmazon EFS not in AWS Backup planAmazon ElastiCache Multi-AZ clustersElastiCache (Redis OSS) Clusters Automatic BackupAmazon MemoryDB Multi-AZ clustersAmazon MSK brokers hosting too many partitionsAmazon MSK Cluster Multi-AZAmazon OpenSearch Service domains with less than three data nodesAmazon RDS BackupsAmazon RDS Continuous Backup Not EnabledAmazon RDS DB clusters have one DB instanceAmazon RDS DB clusters with all instances in the same Availability ZoneAmazon RDS DB clusters with all reader instances in the same Availability ZoneAmazon RDS DB Instance Enhanced Monitoring not enabledAmazon RDS DB instances have storage autoscaling turned offAmazon RDS DB instances not using Multi-AZ deploymentAmazon RDS DiskQueueDepthAmazon RDS FreeStorageSpaceAmazon RDS log_output parameter is set to tableAmazon RDS innodb_default_row_format parameter setting is unsafeAmazon RDS innodb_flush_log_at_trx_commit parameter is not 1Amazon RDS max_user_connections parameter is lowAmazon RDS Multi-AZAmazon RDS Not In AWS Backup PlanAmazon RDS Read Replicas are open in writable modeAmazon RDS resource automated backups is turned offAmazon RDS sync_binlog parameter is turned offRDS DB Cluster has no Multi-AZ replication enabledRDS Multi-AZ Standby Instance Not EnabledAmazon RDS ReplicaLagAmazon RDS synchronous_commit parameter is turned offAmazon Redshift cluster automated snapshotsAmazon Route 53 Deleted Health ChecksAmazon Route 53 Failover Resource Record SetsAmazon Route 53 High TTL Resource Record SetsAmazon Route 53 Name Server DelegationsAmazon Route 53 Resolver Endpoint Availability Zone RedundancyAmazon S3 Bucket Replication Not EnabledAmazon S3 Bucket VersioningApplication, Network, and Gateway Load Balancers Not Spanning Multiple Availability ZonesAuto Scaling available IPs in SubnetsAuto Scaling Group Health CheckAuto Scaling Group ResourcesAWS CloudHSM clusters running HSM instances in a single AZDirect Connect Location ResiliencyAWS Lambda functions without a dead-letter queue configuredAWS Lambda On Failure Event DestinationsAWS Lambda VPC-enabled Functions without Multi-AZ RedundancyAWS Outposts Single Rack deploymentAWS Resilience Hub Application Component checkAWS Resilience Hub policy breachedAWS Resilience Hub resilience scoresAWS Resilience Hub assessment ageAWS Site-to-Site VPN has at least one tunnel in DOWN statusAWS STS global endpoint usage across AWS RegionsAWS Well-Architected high risk issues for reliabilityClassic Load Balancer has no multiple AZs configuredCLB Connection DrainingELB Target ImbalanceGWLB - endpoint AZ independenceLoad Balancer OptimizationNAT Gateway AZ IndependenceNetwork Firewall endpoint AZ IndependenceNetwork Firewall Multi-AZNetwork Load Balancers Cross Load BalancingNLB - Internet-facing resource in private subnetNLB Multi-AZNumber of AWS Regions in an Incident Manager replication setSingle AZ Application CheckVPC interface endpoint network interfaces in multiple AZsVPN Tunnel RedundancyActiveMQ Availability Zone RedundancyRabbitMQ Availability Zone Redundancy @@ -137 +137 @@ You can use the following checks for the fault tolerance category. - * [AWS Direct Connect Location Resiliency](./fault-tolerance-checks.html#amazon-direct-connect-location-resiliency) + * [Direct Connect Location Resiliency](./fault-tolerance-checks.html#amazon-direct-connect-location-resiliency) @@ -3815 +3815 @@ Create at least one more instance for the cluster in a different Availability Zo -## AWS Direct Connect Location Resiliency +## Direct Connect Location Resiliency @@ -3820 +3820 @@ Create at least one more instance for the cluster in a different Availability Zo -Checks the resilience of the AWS Direct Connect used to connect your on-premises to each Direct Connect gateway or virtual private gateway. +Checks the resilience of the Direct Connect used to connect your on-premises to each Direct Connect gateway or virtual private gateway. @@ -3849 +3849 @@ Green: The Direct Connect gateway or virtual private gateway is configured with -To build Direct Connect location resiliency, you can configure the Direct Connect gateway or virtual private gateway to connect to at least two distinct Direct Connect locations. For more information, see [AWS Direct Connect Resiliency Recommendation](https://aws.amazon.com/directconnect/resiliency-recommendation/). +To build Direct Connect location resiliency, you can configure the Direct Connect gateway or virtual private gateway to connect to at least two distinct Direct Connect locations. For more information, see [Direct Connect Resiliency Recommendation](https://aws.amazon.com/directconnect/resiliency-recommendation/). @@ -3854 +3854 @@ To build Direct Connect location resiliency, you can configure the Direct Connec -[AWS Direct Connect Resiliency Recommendations](https://aws.amazon.com/directconnect/resiliency-recommendation/) +[Direct Connect Resiliency Recommendations](https://aws.amazon.com/directconnect/resiliency-recommendation/) @@ -3856 +3856 @@ To build Direct Connect location resiliency, you can configure the Direct Connec -[AWS Direct Connect Failover Test](https://docs.aws.amazon.com/directconnect/latest/UserGuide/resiliency_failover.html) +[Direct Connect Failover Test](https://docs.aws.amazon.com/directconnect/latest/UserGuide/resiliency_failover.html) @@ -4413 +4413 @@ In April 2025, AWS enhanced the global endpoint to automatically serve the STS g -Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. +Results for this check are automatically refreshed several times daily, each time covering the past 15 days. Refresh requests are not allowed. So, it might take up to 15 days for changes to appear in the Trusted Advisor check results. @@ -4415 +4415 @@ Results for this check are automatically refreshed several times daily, and refr -For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the [BatchUpdateRecommendationResourceExclusion](https://docs.aws.amazon.com/trustedadvisor/latest/APIReference/API_BatchUpdateRecommendationResourceExclusion.html) API to include or exclude one or more resources from your Trusted Advisor results. +For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the [BatchUpdateRecommendationResourceExclusion](https://docs.aws.amazon.com/latest/APIReference/API_BatchUpdateRecommendationResourceExclusion.html) API to include or exclude one or more resources from your Trusted Advisor results.