【SaaS架构】使用C#和AWS CDK在SaaS架构中为简仓模型注册租户

Code repository:

• Tennat Onboarding Silo

Environment: PoC or pilot

Technologies: Modernization; Cloud-native; SaaS; DevOps

Workload: Open-source

AWS services: AWS CloudFormation; Amazon DynamoDB; Amazon DynamoDB Streams; AWS Lambda; Amazon API Gateway

Verify Node.js installation.

To verify that Node.js is installed on your local machine, run the following command.  

Install AWS CDK Toolkit.

To install AWS CDK Toolkit on your local machine, run the following command.

If npm is not installed, you can install it from the Node.js site.

Verify the AWS CDK Toolkit version.

To verify that the AWS CDK Toolkit version is installed correctly on your machine, run the following command.  

Set up AWS credentials.

To set up your AWS credentials, run the aws configure command and follow the prompts.    

Clone the repository.

Clone the repository, and navigate to the \tenant-onboarding-in-saas-architecture-for-silo-model-apg-example folder.

In Visual Studio 2022, open the \src\TenantOnboardingInfra.sln solution. Open the TenantOnboardingInfraStack.cs file and review the code.

The following resources are created as part of this stack:

• DynamoDB table

• S3 bucket (Upload the CloudFormation template to the S3 bucket.)

• Lambda execution role

• Lambda function

• API Gateway API

• Event source to Lambda function

Review the CloudFormation template.

In the \tenant-onboarding-in-saas-architecture-for-silo-model-apg-example\template folder, open infra.yaml, and review the CloudFormation template. This template will be hydrated with the tenant name retrieved from the tenant onboarding DynamoDB table.

The template provisions the tenant-specific infrastructure. In this example, it provisions the AWS KMS key, Amazon SNS , Amazon SQS, and the CloudWatch alarm.

Review the tenant onboarding function.

Open Function.cs, and review the code for the tenant onboarding function, which is created with the Visual Studio AWS Lambda Project (.NET Core- C#) template with the .NET 6 (Container Image) blueprint.

Open the Dockerfile, and review the code. The Dockerfile is a text file that consists of instructions for building the Lambda container image.

Note that the following NuGet packages are added as dependencies to the TenantOnboardingFunction project:

• Amazon.Lambda.APIGatewayEvents

• AWSSDK.DynamoDBv2

• Newtonsoft.Json

Review the Tenant InfraProvisioning function.

Navigate to \tenant-onboarding-in-saas-architecture-for-silo-model-apg-example\src\InfraProvisioningFunction.

Open Function.cs, and review the code for the tenant infrastructure provisioning function, which is created with the Visual Studio AWS Lambda Project (.NET Core- C#) template with the .NET 6 (Container Image) blueprint.

Open the Dockerfile, and review the code.

Note that the following NuGet packages are added as dependencies to the InfraProvisioningFunction project:

• Amazon.Lambda.DynamoDBEvents

• AWSSDK.DynamoDBv2

• AWSSDK.Cloudformation

Build the solution.

To build the solution, perform the following steps:

1. In Visual Studio 2022, open the \tenant-onboarding-in-saas-architecture-for-silo-model-apg-example\src\TenantOnboardingInfra.sln solution. 

2. Open the context (right-click) menu for the solution, and choose Build solution.

Note: Make sure that you update the Amazon.CDK.Lib NuGet package to the latest version in \tenant-onboarding-in-saas-architecture-for-silo-model-apg-example\src\TenantOnboardingInfra project before you build the solution.

Bootstrap the AWS CDK environment.

Open the Windows command prompt and navigate to the AWS CDK app root folder where the cdk.json file is available (\tenant-onboarding-in-saas-architecture-for-silo-model-apg-example). Run the following command for bootstrapping.

If you have created an AWS profile for the credentials, use the command with your profile.

List the AWS CDK stacks.

To list all the stacks to be created as part of this project, run the following command.

If you have created an AWS profile for the credentials, use the command with your profile.

Review which AWS resources will be created.

To review all the AWS resources that will be created as part of this project, run the following command.

If you have created an AWS profile for the credentials, use the command with your profile.

Deploy all the AWS resources by using AWS CDK.

To deploy all the AWS resources run the following command.

If you have created an AWS profile for the credentials, use the command with your profile.  

After the deployment is complete, copy the API URL from the outputs section in the command prompt, which is shown in the following example.  

Create a new tenant.

To create the new tenant, send the following curl request.  

Change the place holder <TenantOnboardingAPIEndpoint* from CDK Output> to the actual value from AWS CDK, as shown in the following example.  

The following example shows the output.

Verify the newly created tenant details in DynamoDB.

To verify the newly created tenant details in DynamoDB, perform the following steps.

1. Open AWS Management Console, and navigate to the Amazon DynamoDB service.

2. In the left navigation, choose Explore items, and choose the TenantOnboarding table.

   Note: The tenant name will be prepended with tenantcluster-. For more information, see the Additional information section.

3. Verify that a new item is created with the tenant details.

Verify the stack creation for the new tenant.

Verify that the new stack was successfully created and provisioned with infrastructure for the newly created tenant according to the CloudFormation template.

1. Open the CloudFormation console.

2. In the left navigation, choose Stacks, and verify that a stack with the tenant name was successfully created.

3. Choose the newly created tenant stack, and then choose the Resources tab. Note the alarm resource and the Amazon SQS resource.

4. Open a new terminal with AWS credentials configured, and point to the correct Region. To raise a test alarm, enter the following code, replacing <alarm resource name> with the alarm resource name noted in step 3.  

   aws cloudwatch set-alarm-state --alarm-name <alarm resource name> --state-value ALARM --state-reason 'Test setup'

   The following example shows the code with an alarm resource name.  

   aws cloudwatch set-alarm-state --alarm-name tenantcluster-tenant123-alarm --state-value ALARM --state-reason 'Test setup'

5. Open the console and navigate to the Amazon SQS console. Choose the Amazon SQS resource name identified in step 3. Follow the AWS documentation instructions to receive and delete the test message from the alarm that was raised in step 4.

Delete the tenant stack.

To delete the tenant stack, send the following curl request.

Change the place holder <TenantOnboardingAPIEndpoint* from CDK Output> to the actual value from AWS CDK, and change <Tenant Name from previous step> to the actual value from the previous tenant creation step, as shown in the following example.  

The following example shows the output.  

Verify the stack deletion for the existing tenant.

To verify that the existing tenant stack got deleted, perform the following steps:

1. Open console and navigate to the CloudFormation console.

2. In the left navigation, verify that the existing stack with the tenant name is no longer in console (if the CloudFormation console is set up to show only Active stacks) or is in the process of being deleted. If the stack is no longer in the CloudFormation console, use the dropdown list to change the console's setting from Active to Deleted to see the deleted stack and verify that the stack was deleted successfully.

Destroy the environment.

Before the stack clean up, ensure the following:

• All records in DynamoDB are removed either through the previous tenant deletion operation or through the DynamoDB console or API. Each tenant record deletion will initiate the cleanup of its AWS CloudFormation counterpart. 

• All tenant-based AWS CloudFormation stacks are cleaned up (in case the DynamoDB trigger cleanup logic fails) on the AWS CloudFormation console.

After testing is done, AWS CDK can be used to destroy all the stacks and related resources by running the following command.  

If you created an AWS profile for the credentials, use the profile.

Confirm the stack deletion prompt to delete the stack.

Clean up Amazon CloudWatch Logs.

The stack deletion process will not clean up CloudWatch Logs (log groups and logs) that were generated by the stack. Manually clean up the CloudWatch resources by using the CloudWatch console or the API.