Resourcely Documentation
LoginSign Up
  • Get Started
    • 🎱What is Resourcely?
    • 👋Why Resourcely
    • 🏃Quickstart
      • Terraform policies integrated into CI
      • Remediate policy violations in existing infrastructure
      • Templates for generating Terraform
      • Glossary
  • Concepts
    • Foundry
      • Create Blueprints with Foundry
      • Creating Guardrails with Foundry
      • lmport Terraform Modules
    • Guardrails
      • Writing your own Guardrails
      • Editing Guardrails
      • Releasing Guardrails
      • Enabling Inactive Guardrails
      • Guardrails in Action
        • 🐱GitHub Actions
        • 🦊GitLab Pipelines
    • Campaigns
      • Get started with Campaigns
      • Creating Campaigns
      • Remediate Resources
      • Campaign Agent
        • State File Support
          • Amazon Simple Storage Service (S3)
          • Google Cloud Storage (GCS)
          • HCP Terraform
          • Spacelift
        • Running Campaigns with GitHub Actions and a Repo-Hosted State File
        • Running Campaigns Locally
    • Blueprints
      • Authoring Your Own Blueprints
      • Using Built-in Resourcely Blueprints
      • Configuring Global Contexts
      • Deep Linking
    • Resources
      • Provisioning Infrastructure
      • Editing Infrastructure
      • Shopping Cart
      • Config Roots and Environments
    • Other Features and Settings
      • Global Values
      • Global Context
      • Metrics
      • Resourcely-cli
      • Resourcely.yaml
      • VCS Proxy
      • Settings
        • User management
        • Company Information
        • Notification Settings
        • Change Management
          • 🐱Connect to GitHub
          • 🦊Connect to Gitlab
        • Generate API Token
    • ✨Production Setup
      • Single Sign-On (SSO)
        • Auth0
        • AWS Single Sign-On
        • Azure AD
        • Google Workspace
        • JumpCloud
        • Okta
        • Omnissa Workspace ONE (formerly VMware)
        • OneLogin
        • Ping Identity
        • Other SAML / OIDC Providers
      • Source Code Management
        • Page
        • 🐱GitHub
        • 🦊GitLab
        • Atlassian Bitbucket
        • Azure Repos
  • Tutorials and guides
    • Remediation Use Cases
      • Apply tags to resources for automating backups
      • Implement centralized logging
    • Blueprints Use Cases
      • Automate Data Pipeline Creation
      • Encryption for GCP
      • AWS Account Factory
      • Streamline and govern AI
      • IAM Factory
      • Cost optimization for FinOps
      • Guardrails for Terraform Modules
    • Using the Resourcely Terraform Provider
      • Setup Resourcely Provider
      • Blueprints
      • Guardrails
      • Global Context
  • Integrate
    • CI/CD & Terraform Runners
      • Atlantis
      • 🐟AWS CodeBuild
      • Azure Pipelines
      • Buildkite
      • CircleCI
      • CloudBees CI
      • Codefresh
      • Digger
      • Env0
      • 🎏GitHub Actions
        • 🐱Local Plan
          • 🐹AWS with OpenID Connect
        • 🐶Terraform Cloud Integration
      • 🦊GitLab Pipelines
      • Harness
      • 🗻HashiCorp Cloud Platform (formerly Terraform Cloud)
      • Jenkins
      • Octopus Deploy
      • Scalr
      • 🌌Spacelift
      • Terramate
      • 🌎Terrateam
    • Cloud Providers
      • 🌨️Amazon Web Services (AWS)
      • 🤓Google Cloud Platform (GCP)
        • Guardrail Gaunlet at Google Cloud Next 2025
      • 💾Microsoft Azure
      • Alibaba Cloud
      • Huawei Cloud
      • IBM Cloud
      • Oracle Cloud Infrastructure (OCI)
      • Tencent Cloud
      • VMware vSphere
    • Developer Portals
      • Atlassian Compass
      • Backstage
      • Cortex
      • Harness IDP
      • Home grown internal developer portals
      • OpsLevel
      • Port
      • Roadie
    • ITSM
      • Atlassian Jira
      • FreshWorks
      • ServiceNow ITSM
      • ZenDesk
    • CSPM
      • Wiz
    • More Terraform Provider Integrations
      • 🚂ConductorOne Provider
      • Databricks Provider
      • Kubernetes Provider
      • 🐕Datadog Provider
      • ❄️Snowflake Provider
Powered by GitBook
On this page
  1. Concepts
  2. Blueprints

Using Built-in Resourcely Blueprints

Create and manage secure-by-default cloud infrastructure templates

PreviousAuthoring Your Own BlueprintsNextConfiguring Global Contexts

Last updated 1 year ago

Resourcely allows you to create infrastructure from secure-by-default templates. You can see all blueprints available to you by clicking on the Blueprints tab in Resourcely's navigation menu. You can press the Create a blueprint button to begin the process of creating one.

Those with the Resourcely Developer role will only see the Blueprints that a Resourcely Admin role has configured

Resourcely provides a catalog with a wide set of available blueprints which can be further configured. In order to select a blueprint from our catalog you must choose the Select a Resourcely Blueprint option and then press the Continue button.

You must then determine what type of resource you would like to create, highlight it, and then click on the Continue button. You can sort by Provider, Category, and Keyword, as well as Search for an available blueprint.

In the next screen, you can remove guardrails. The appropriate guardrails enabled in your instances are added by default. After determining what guardrails you would like to maintain, press the Continue button.

Now you must configure the fields used to collect information from developers. To the right, you will see the fields inherited from your Global Context. These fields can be removed as needed.

To the left, you can see the fields configured by guardrails. You can press the lock icon in order to disable a particular guardrail.

Changes to guardrails will require approval from the guardrails owner(s)

You can also collect additional context from developers by adding a context question with custom fields. Once you have configured your required fields, press the Continue button to proceed.

Now you can configure the metadata for the Blueprint which determines how it will look within the main Blueprint screen that developers can use to provision infrastructure. The added information should be as descriptive as possible. Then press the Continue button to proceed.

In the next section, you can review and confirm that the Blueprint you are creating meets your requirements. Press the Publish Blueprint button to add the blueprint to your namespace.

After reviewing and confirming the blueprint, it will become available in the main Blueprint section that developers can select from.

Once a blueprint is available you can use it to provision infrastructure using CI/CD. To learn more about provisioning infrastructure from a blueprint, see the guide below:

Provisioning Infrastructure
Choose from Blueprint Catalog
Built-in Blueprint Catalog
Enable/Disable Guardrails
Configure fields and collect context
Collecting Additional Context
Provide blueprint metadata
Review and confirm Blueprint
Available Blueprints