- AWS Network Reach Tool — This Python tool was created to help analyze AWS network connectivity.
- AWS Public IPv4 Use
- Baseline AWS Network ACL — This network ACL http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_ACLs.html is the recommended baseline for VPC subnets in Cornell AWS accounts. It should be configured and used on all AWS VPC subnets. You are welcome to make your NACL more stringent, but we recommend careful consideration before making it less stringent.
- Cornell AWS Direct Connect
- 2023 Cornell AWS Direct Connect Architecture Migration — This document provides details about the Direct Connect architecture migration Cornell will be executing in early 2023.
- Cornell AWS Direct Connect Architecture
- Cornell AWS Direct Connect Costs — The management and routing simplification offered by the v2 (2023) architecture comes with a shift in costs seen by Cornell AWS accounts using Direct Connect, but the overall impact to Cornell AWS account costs are negligible.
- Cornell AWS Direct Connect FAQs
- Cornell AWS Direct Connect Routing Diagrams — This page shows and discusses the different routing options over the Cornell Direct Connect to AWS VPCs.
- Direct Connect Resources in Cornell AWS Accounts — This document provides details about the resources in Cornell AWS accounts that support the 2023 (v2) Direct Connect architecture.
- Peering AWS VPCs that Use Direct Connect — Since the 2023 Direct Connect architecture fully interconnects all VPCs using Direct Connect (i.e., attached to the Transit Gateway), individual peering between VPCs is no longer technically necessary.
- Route 53 Subdomain Delegation — Delegating specific sub-domains of cucloud.net to Route 53 allows your group or department the ability to create dynamic environments with the tools provided by Amazon Web Services. While anyone can create a Hosted Zone for a sub-domain in Route 53, DNS delegation requires the owner/administrator of the parent domain ("cucloud.net") to create nameserver (NS) and start-of-authority (SOA) records that direct incoming requests for your specific sub-domain to the nameservers AWS assigned to the Host
- Shared AWS VPC for Cornell AWS Accounts
- Shared AWS VPC FAQs — FAQs about the Multitenant Subnets and the Exclusive Use Subnets option within the Shared VPC offering.
- Using the AWS Shared VPC Offerings — This document provides practical information about using either the Multitenant Subnets or Exclusive Use Subnets options of the Shared VPC offering once its has been provisioned to your Cornell AWS account.
{"serverDuration": 281, "requestCorrelationId": "604fe999c73fb4d0"}