Rain is no longer actively maintained, and its repository is archived. What are the practical alternatives for deploying CloudFormation stacks, especially if you use its change set diff or other convenience features?
Rain is deprecated. What are you using for CloudFormation deployments instead?
Answers
If you mainly need rain deploy, the AWS CLI's aws cloudformation deploy command is a reasonable starting point. The --no-fail-on-empty-changeset option also handles deployments where there are no changes.
That doesn't replace every Rain feature, though. Check your existing commands and scripts before switching, especially if you rely on its diff display or template handling.
Reply to this answer
CDK is an option if you're willing to author infrastructure in a programming language and want reusable components. It's a bigger change than swapping deployment commands, though, and may not appeal if you prefer working directly with CloudFormation templates.
Reply to this answer
There isn't necessarily one replacement for the whole toolkit. The AWS CLI can handle CloudFormation operations, cfn-lint can validate templates, and cfn-guard can check policies. Those cover different jobs, so pick what fits your workflow rather than expecting a drop-in Rain clone.
Reply to this answer
Take stock of the smaller Rain features you use too. Formatting, directives and handling S3 references can matter just as much as the deploy command. Those workflows may need more rework than a simple command substitution.
Reply to this answer
Existing Rain releases are still available, but there are no planned bug fixes or security patches. A community fork could be an option, though someone would need to take on maintenance. For now, relying on the archived release means accepting that support gap.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_g46~ticketwrench.8:
The change set diff is the awkward part. A separate tool such as cfn-changeset-viewer can render changes, but it isn't the same all-in-one workflow.