Skip to content

Commit 6eba400

Browse files
fix: spelling
1 parent 7a46dfb commit 6eba400

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

content/blog/infrastructure-as-code-with-aws-cdk.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ A CDK App represents the root of our infrastructure as code, an entry point of o
2727

2828
### Stacks (CloudFormation Stacks)
2929

30-
In CDK, a Stack is the unit of deployment. It represents a single cloudformation Stack, which is a collection of resources that are deployed together. A Stack is a root Construct that contains multiple Constructs, which represent the actual cloud components. An App can have multiple Stacks, each representing a separate deployment unit. Use Stacks to group resources that should be deployed and destroyed together.
30+
In CDK, a Stack is the unit of deployment. It represents a single Cloudformation Stack, which is a collection of resources that are deployed together. A Stack is a root Construct that contains multiple Constructs, which represent the actual cloud components. An App can have multiple Stacks, each representing a separate deployment unit. Use Stacks to group resources that should be deployed and destroyed together.
3131

3232
### Constructs (Cloud Components)
3333

@@ -48,12 +48,12 @@ As we discussed about CDK, there is much more information available in the offic
4848

4949
## The Scenario: Deploying Applications with Isolation and Scale
5050

51-
Our use case involves deploying multiple applications on AWS ECS, with each application using RDS Postgres as its database. The twist was that we had to deploy these applications multiple times for different clients, with each client requiring database isolation. This meant that we needed a solution that could efficiently manage multiple deployments with minimal effort.
51+
Our use case involves deploying multiple applications on AWS ECS, with each application using RDS PostgreSQL as its database. The twist was that we had to deploy these applications multiple times for different clients, with each client requiring database isolation. This meant that we needed a solution that could efficiently manage multiple deployments with minimal effort.
5252

5353
### The Requirements
5454

5555
* Deploy applications on AWS ECS
56-
* Use RDS Postgres as the database
56+
* Use RDS PostgreSQL as the database
5757
* Ensure database isolation for each client
5858
* Deploy the same application multiple times for different clients
5959
* Minimize onboarding effort for each new client

0 commit comments

Comments
 (0)