This first video will walk you through, the one time process, of integrating your AWS environment with CloudManager:
The second video in our series shows you how to create users and teams. CloudManager Teams empower your staff to manage their projects, add and remove members of your organization, and keep all of your group permissions in one place. Say good-bye to leftover permissions or forgotten group membership.
One of the most powerful features in CloudManager is Cloudprints, a combination of Infrastructure as Code (IaC), a starter application, unit tests, integration tests, and a Continuous Integration/Continuous Delivery pipeline. Each Cloudprint also includes industry best practices in all areas of the project from infrastructure to code to CICD. In a few clicks, you can have a rock-solid project, configured, provisioned, and running in your AWS environment.
In this video, we look at some of the resources created by a Cloudprint, invoke the API that was generated, and touch on authentication.
To encourage a generative organization and empower your dev team to change the resources they need, Cloudpolicies were created. Cloudpolicies define basic access that any project should have. When someone changes infrastructure code to create new resources, change/add IAM policies or alter other AWS resources in any way, Cloudpolicies will examine the changes AND if they meet existing specifications, your build is allowed to proceed. If your changes are outside the allowed changes, your project will fail its validation. The video looks at how Cloudpolicies work and how to create CloudResolutions.
CloudResolutions coupled with Cloudpolicies enable your development teams to make changes to infrastructure as needed. When changes are made that violate a Cloudpolicy, their build will fail. At this point, the team can open a CloudResolution Request, a request to allow their build to continue. Organization
admins and the
root user will be notified of the CloudResolution Request, they can then discuss specifics with the dev team and once everyone is in agreement, the
admin can approve the CloudResolution Request. A CloudResolution Request not only empowers the team to make changes as needed, enusre company security and infrastructure policies are followed, it also provides a system of record for exceptions or reasons for why a policy wasn’t adequate for their needs.
CloudManager enables dev teams to create the infrastructure they need for their projects. CloudPolicies enable your organization to apply, company-wide, infrastructure policies. CloudResolutions provide teams a mechanism to request exemptions and your organization a way to adjust its policies, for a specific project, and a given period (including perpetual overrides). In this video, we’ll see how the CloudResolution requested earlier stays with your project and is applied to future builds.