Skip to content
This repository has been archived by the owner on Oct 25, 2023. It is now read-only.

Commit

Permalink
Merge pull request #127 from ACloudGuru/kennu/master
Browse files Browse the repository at this point in the history
Allow deploying alert resources to an external CloudFormation stack
  • Loading branch information
subash adhikari authored Jun 30, 2020
2 parents 28c1590 + f552caa commit e4df498
Show file tree
Hide file tree
Showing 3 changed files with 556 additions and 1 deletion.
23 changes: 23 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -390,6 +390,29 @@ definitions:
treatMissingData: missing
```

## Using a Separate CloudFormation Stack

If your Serverless CloudFormation stack is growing too large and you're running out of resources,
you can configure the plugin to deploy a separate stack for the CloudWatch resources. The default
behaviour is to create a stack with a "-alerts" suffix in the stack name.

custom:
alerts:
externalStack: true

You can customize the name suffix:

custom:
alerts:
externalStack:
nameSuffix: Alerts

The separate stack will be automatically deployed after you've deployed your main Serverless
stack. It will also be automatically removed if you remove your main stack.

You can also enable the external stack on the command line with `sls deploy --alerts-external-stack'
which is equivalent to adding `externalStack: true` to the configuration.

## License

MIT © [A Cloud Guru](https://acloud.guru/)
Expand Down
Loading

0 comments on commit e4df498

Please sign in to comment.