![]() If more tiers are required, you can create additional private subnets with unique CIDR ranges. An empty application tier for instances in private subnets.After deployment, you’ll modify the security group ingress rules to configure administrative access through TCP port 443 instead. A security group for Windows-based instances that will host the RD Gateway role, with an ingress rule permitting TCP port 3389 from your administrator IP address.A Network Load Balancer to provide RDP access to the RD Gateway instances.Each instance is assigned an Elastic IP address so it’s reachable directly from the internet. In each public subnet, up to four RD Gateway instances in an Auto Scaling group to provide secure remote access to instances in the private subnets.Managed network address translation (NAT) gateways to allow outbound internet access for resources in the private subnets.*.This gateway is used by the RD Gateway instances to send and receive traffic.* An internet gateway to allow access to the internet.A VPC configured with public and private subnets according to AWS best practices, to provide you with your own virtual network on AWS.*.A highly available architecture that spans two Availability Zones.*. ![]() ![]() Use this solution to set up the following RD Gateway environment on AWS: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |