Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/aws-samples/legacy-cycle-store-mvc-app/llms.txt

Use this file to discover all available pages before exploring further.

Before you begin setting up the Legacy Cycle Store application, make sure your local environment and AWS account are properly configured. The app is an ASP.NET MVC 4 project targeting .NET Framework 4.5, backed by a SQL Server Express database hosted on Amazon RDS. Getting each prerequisite in place first will make the deployment and local-run steps straightforward.

​
Required Tools and Accounts

1

AWS Account

You need an active AWS account with sufficient IAM permissions to create and manage the following services:
  • CloudFormation — create and delete stacks
  • RDS — provision SQL Server Express instances
  • Secrets Manager — store and retrieve database credentials
  • IAM — create roles and attach policies
  • EC2 — create and manage security groups
If you are operating under an organization-managed account, confirm with your AWS administrator that these permissions are available before proceeding.
2

Visual Studio 2013 or Later

The solution file is AdventureWorksMVC_2013.sln, created for Visual Studio 2013. Any later version of Visual Studio (2017, 2019, or 2022) can open and build the project without modification. During installation, ensure the ASP.NET and web development workload is selected so that the MVC tooling, web project templates, and IIS Express are available.
3

.NET Framework 4.5

The application targets .NET Framework 4.5. This runtime must be installed on your development machine. Visual Studio typically installs the required targeting packs automatically, but you can verify by checking Control Panel → Programs → Turn Windows features on or off and confirming that .NET Framework 4.5 (or a later 4.x version) is listed and enabled.
4

SQL Server Management Studio (SSMS)

You will need SQL Server Management Studio or an equivalent SQL client (such as Azure Data Studio) to connect to your RDS instance and execute the CYCLE_STORE_Schema_data.sql script that creates the database schema and loads seed data. SSMS is available as a free download from Microsoft and runs on Windows.
5

AWS CLI (Optional)

The AWS CLI is not strictly required, but it provides a convenient way to deploy the CloudFormation stack and retrieve stack outputs from the terminal rather than navigating the AWS Console. Install version 2 from the AWS CLI documentation and configure it with aws configure before using the CLI-based deployment steps.

​
Security Notice

The included CloudFormation template (SqlServerRDSFixedUidPwd.yaml) configures the RDS security group to accept inbound TCP connections on port 1433 from 0.0.0.0/0 — meaning the database is reachable from any IP address on the internet. This configuration is intentional for a local development or demo environment but is not suitable for production. Before deploying to a shared or production environment, restrict the inbound rule to your specific IP address or a private VPC CIDR range.

​
Next Steps

Deploy RDS

Provision the SQL Server Express RDS instance, Secrets Manager credentials, and security group using the included CloudFormation template.

Database Setup

Connect to the RDS instance with SSMS and run the schema script to create the CYCLE_STORE database and load product seed data.

Build docs developers (and LLMs) love

Get started for freeTalk to us