Here are some of the questions you should consider when designing your Quick Start architecture.
How many Availability Zones? You should use at least two for high availability.
Where should your workload be placed? Consider security and external access when deciding whether to install your software in a public or private subnet.
How many public and private subnets? If your workload needs an additional level of isolation, you might consider setting up a second private subnet with network ACL protection in each Availability Zone.
Is your workload distributed across multiple instances? If yes, use Elastic Load Balancing to help ensure availability and fault tolerance.
Is your workload stateless or stateful? Do you save session state in the workload instances? If you don’t, your workload instance would be a good candidate for Auto Scaling.
Are you storing data? What kind of database do you need?
- If relational, use Amazon RDS.
- If NoSQL, Amazon DynamoDB is a good option.
- If your database engine is MySQL or PostgreSQL, you can use Amazon Aurora.
Are there any other AWS services that will complement the functionality of your software in the cloud? If yes, consider including them in your architecture. For example:
If your workload needs to meet compliance requirements such as NIST or PCI, consider using one of the compliance Quick Starts for your infrastructure.