Here are some of the questions you should consider when designing your Partner Solution architecture.
How many Availability Zones should I specify? For high availability, use at least two.
Where should my workload be located? Your security and external-access settings determine whether to use public or private subnets.
How many public and private subnets should I use? If your workload needs to be isolated, consider setting up a second private subnet that uses a network access control list (ACL) in each Availability Zone.
What if my workload is distributed across multiple instances? Use Elastic Load Balancing to help ensure high availability and fault tolerance.
What if my workload is stateless or stateful? If you don’t save your session state within the workload instance, use Auto Scaling.
I want to store data. What kind of database should I use?
- If the data are relational, use Amazon RDS.
- If the data are non-relational (for example, NoSQL), use Amazon DynamoDB.
- If the database engine uses MySQL or PostgreSQL, use Amazon Aurora.
Are there any other AWS services that complement my software’s functionality? Consider including them in your architecture. Example:
If your workload needs to meet compliance requirements, such as NIST or PCI, consider using one of the compliance Partner Solutions for your infrastructure.