You've calculated the CIDR ranges appropriately. However, that's a very large VPC. Having a lot of instances/containers in that VPC means a significantly large blast radius if things start to fail.
You might consider splitting the public and private subnets across a third Availability Zone. In the model you have, in order to survive a catastrophic failure of an AZ you need to have 100% of the capacity in a single AZ (meaning that you need to have 200% of your available capacity running at any one time). If you are working across three AZs then you only need to have 50% in each AZ (150% of your available capacity). It's less expensive to run in three AZs than it is in two.
Given the large scale at which you wish to operate I strongly recommend you reach out to your local AWS Solutions Architect to discuss this design.
Is possible to use RHEL Developer Subscription on AWS EC2?asked 4 months ago
Direct Connect Hide VPC CIDR Blocks from BGP PeerAccepted Answerasked 3 years ago
What is the best way to generate a visual diagram of the AWS environment which includes VPC, VPNAccepted Answerasked 2 years ago
AWS PrivateLink use case validationAccepted Answerasked 15 days ago
Why would a Case ID be completely missing on my AWS account?asked 7 months ago
Secondary CIDR VPC block - Direct ConnectAccepted Answerasked 4 years ago
Very new to IoT. Is AWS IoT correct for my business use case?asked 3 years ago
Advice on creating VPC for EC2 to use IPSec connectionasked 5 months ago
CIDR for VPC creation on below use caseasked 25 days ago
VPC/CIDR IPv4 issueasked 2 months ago