title: AWS Cloudwatch Rules and Glue with Separate Environment Dev, QA, Staging and Prod
body: <p>We have an AWS hosted solution which uses Cloudwatch Rules, Lambdas, AWS Glue, Databases and Docker containers. 
  We need a separate environment for dev,qa...
  Databases and Docker containers can be part of different VPC in the same account for different environments. But what is the standard practice of having Cloudwatch Rules, Lambdas and AWS Glue for different environment. 
  For AWS lambdas alone we see there is a Versioning concept for this. But nothing found for AWS Glue and Cloudwatch. 
  What is the standard practice in this kind of situation? </p>