Cloudscape Design System
  • Get started
  • Foundation
  • Components
  • Patterns
  • Demos
  • GitHub 
Cloudscape Design System
  • Get started
  • Foundation
  • Components
  • Patterns
  • Demos
  • GitHub 
  • About

Patterns


  • General

    • Actions
      • Global actions
      • In-context actions
    • Announcing new features
    • Announcing beta and preview features
    • Communicating unsaved changes
    • Data visualization
      • Chart metric drill down
    • Density settings
    • Disabled and read-only states
    • Drag-and-drop
    • Errors
      • Error messages
      • Validation
    • Empty states
    • Feedback mechanisms
    • Filtering patterns
      • Saved filter sets
      • Filter persistence in collection views
    • Hero header
    • Help system
    • Image magnifier
    • Loading and refreshing
    • Onboarding
      • Hands-on tutorials
    • Selection in forms
    • Service navigation
      • Side navigation
      • Top navigation
    • Service Dashboard
      • Static dashboard
      • Configurable dashboard
      • Dashboard items
    • Secondary panels
    • Timestamps
    • User feedback

  • Generative AI patterns

    • Pattern abstraction
    • Generative AI chat
    • Ingress
    • Generative AI output label
    • Generative AI loading states
    • Progressive steps

  • Resource management

    • Create resource
      • Multipage create
      • Single page create
      • Sub resource create
    • Delete patterns
      • One-click delete
      • Delete with simple confirmation
      • Delete with additional confirmation
    • Edit resource
      • Page edit
      • Inline edit
      • Attribute editing
    • View resources
      • Table view
      • Card view
      • Split view
      • Table with expandable rows
    • Resource details
      • Details page
      • Details page with tabs
      • Details page as a hub
  1. Cloudscape Design System
    • Patterns
    • Resource management: Create resource
    1. Cloudscape Design System
    2. Patterns
    3. Resource management: Create resource

    Create resource

    With the create new resource pattern, users can create new resources.

    Published: June 25, 2020 | Last updated: March 6, 2025

    On this page

    1. Create resource patterns and components
    2. Sub-resource create patterns
    3. Flow charts
    4. Criteria

    Did this page help you?

    Tell us more - optional

    1000 character(s) available. Do not disclose any personal, commercially sensitive, or confidential information.

    Create resource patterns and components

    Users can create resources from multiple entry points. If it's the user's first time, or a recurrent creation, we provide four solutions.

    Single page create

    Use single page create if you want your users to create a resource on a single page. This component is optimized for simple to medium-complex forms.

    Multipage create

    Use the multipage create, which employs the wizard component, when you want users to create resources by completing a set of interrelated tasks. We recommend multipage create for long or complex configurations.

    Modal

    A user interface element subordinate to an application's main window. It prevents interaction with the main page content, but keeps it visible with the modal as a child window in front of it.

    Sub-resource create patterns

    Sub-resource create

    Enables users to create new sub-resources within a single or multipage create.

    Flow charts

    Criteria

    ModalSingle page createMultipage create
    Length= 1 fieldBetween 2 and 15 fields in the primary section or up to 5 groups of settingsMore than 16 fields in primary sections or more than 5 groups of settings
    ComplexityBasic text input fields and simple selectsFlow does not require any category to have its own pageConcepts require in-depth interactions that benefit from having their own page
    RecoveryInput is mutable after creationInput mutable after creationInput immutable after creation
    Error handlingIn trigger pageIn creation pageIn every single step and in summary step
    Frequencyn/aFrequentInfrequent
    Sub-resource createNoYesYes

    Length

    Deciding how many fields are in the primary section:

    • Any required field that we can’t provide a good default for (for example, a password).

    • Any field that 80% or more users would expect to see and want to know the value of in order to be successful (for example, knowing the security group associated with the resource, even when we provide a good default).

    • All other fields go into the additional configuration section with appropriate defaults.

    Some flows have variables that are based on what the user chose in a previous step. The total number of fields should be considered for the longest possible variation of your form.

    Complexity

    Complexity refers to the types of interactions in your flow. In some cases, interactions are complex enough that having their own page will make it easier for users to complete and make better decisions.

    Recovery

    For configurations that allow or disallow a correction or modification without creating a new one.

    Error handling

    Where in the flow errors can be caught, so the user can modify them in context.

    Frequency

    Only use frequency as a criterion if you’re unsure which pattern to use.

    Sub-resource create

    Sub-resources are either dependencies or optional enhancements used to complete the parent resource creation. For example, adding roles, policies, or security groups to an EC2 instance. These can be selected from existing options or, created and then added. Sub-resources may be owned by the same service or require cross-service creation. Follow the guidelines for sub-resource create.

    Did this page help you?

    Tell us more - optional

    1000 character(s) available. Do not disclose any personal, commercially sensitive, or confidential information.
    • About
    • Connect
    • Privacy 
    • Site terms 
    • © 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.
    Made with love atAWS