To meet the requirements of not having to share internal IP addresses and avoid connecting over the internet despite IP address overlap, deploying the SaaS service endpoint behind a Network Load Balancer (NLB) allows for highly available, scalable architecture and presents a single IP address to customers. Configuring an endpoint service and granting customers permission to create a connection allows them to securely and privately connect to the SaaS service using their own private IP addresses without traversing the internet.
To meet all the requirements for the workload, the network engineer should take the following steps: AWS Direct Connect with MACsec support ensures that all data to and from the on-premises environment is encrypted in transit, satisfying the requirement for encryption. Using Gateway Load Balancers to insert third-party firewalls allows for the inspection of all traffic in the cloud before it leaves the cloud, fulfilling the need for inline traffic inspection. Lastly, configuring AWS Shield Advanced provides protection against DDoS attacks and also offers financial protection for services that scale out during a DDoS event.
To investigate the increased usage of a NAT gateway, enabling VPC flow logs on the NAT gateway's elastic network interface and publishing the logs to either Amazon CloudWatch Logs or an Amazon S3 bucket are both effective solutions. Publishing to CloudWatch Logs allows for the use of CloudWatch Logs Insights to query and analyze the logs directly. Alternatively, publishing to an S3 bucket and using Amazon Athena to create a custom table for querying and analyzing the logs can also provide detailed insights. These methods allow tracking and analyzing the traffic passing through the NAT gateway, helping identify the sources of increased usage.
An egress-only internet gateway is a horizontally scaled, redundant, and highly available VPC component that allows outbound communication over IPv6 from instances in your VPC to the internet, while preventing inbound IPv6 traffic from the internet to your instances. This solution meets the requirement of not permitting IPv6 traffic from the public internet and ensures that the company's servers initiate all IPv6 connectivity. The other options either do not support IPv6 or do not align with the requirement to block inbound IPv6 traffic from the internet.
To deliver Network Firewall flow logs to the company’s Amazon OpenSearch Service (Amazon Elasticsearch Service) cluster in the shortest possible time, the best solution is to create an Amazon Kinesis Data Firehose delivery stream that includes the Amazon OpenSearch Service cluster as the destination. Kinesis Data Firehose can stream data in near real-time, ensuring that the logs are delivered to the Elasticsearch cluster efficiently and quickly compared to other methods. This makes it the most effective and streamlined option for the required task.