A financial services company runs a multi-tier application across a multi-account structure in AWS Organizations. The application consists of a web layer running on AWS Fargate in private subnets across two Availability Zones (AZs), a batch processing layer on Amazon EC2 m6i.large instances, and a reporting API built with AWS Lambda. To minimize costs, the operations team proposes deploying a single NAT Gateway in one AZ to route outbound internet traffic from the private subnets. Additionally, the company plans to share specialized network resources via AWS Resource Access Manager (RAM) to a partner's AWS account that is outside their AWS Organization. The company wants to purchase Savings Plans to reduce compute costs for EC2, Fargate, and Lambda, while keeping maximum flexibility for future microservice migrations. Which combination of actions should a Solutions Architect recommend to optimize costs, maintain high availability, and ensure successful resource sharing?
- APurchase EC2 Instance Savings Plans for the m6i instance family at the AWS Organizations management account level. Deploy a NAT Gateway in each Availability Zone. Enable sharing with external accounts in the AWS Resource Access Manager settings to share resources with the partner account.
- Purchase Compute Savings Plans at the AWS Organizations management account level. Deploy a NAT Gateway in each Availability Zone. Enable sharing with external accounts in the AWS Resource Access Manager settings to share resources with the partner account.Answer
- CPurchase Compute Savings Plans at the AWS Organizations management account level. Keep the single NAT Gateway configuration to minimize NAT Gateway hourly fees and data processing costs. Enable sharing with external accounts in the AWS Resource Access Manager settings to share resources with the partner account.
- DPurchase Compute Savings Plans at the AWS Organizations management account level. Deploy a NAT Gateway in each Availability Zone. Share the resources using AWS Resource Access Manager without enabling external account sharing, relying on cross-account IAM trust relationships.