In the previous guide, you built a control plane project and created a new claim for your infrastructure. In this guide, you’ll deploy that configuration through Upbound’s Consumer Portal.

The Consumer Portal is a self-service tool that you and users in your organization can use to deploy infrastructure based on claims and configurations you create. This portal is what your developers interact with when they want to deploy infrastructure on your control plane platform. For more information on adding users to Upbound, review the Identity Management guide

Follow the flow below to create a resource based on your claim.

Login to the Upbound Console and navigate to the Consumer Portal. Your browser will redirect you to the Consumer Experience portal, which only displays information necessary for consumers to deploy infrastructure.

First, navigate to the Control Plane you created in the previous guides and select the claim resource. Add a name and create your resource. Follow the interactive guide below:

Modify a claim

You can modify your resource directly from the Consumer Portal. Navigate to the resource and go to Details. From here, you can edit the fields or select Edit YAML and create additional YAML specifications.

Verify your resources

After creating and configuring your resources, you can verify your bucket configuration using AWS CLI commands. Below are examples of how to confirm the existence of an S3 bucket and verify its encryption settings.

List buckets

To verify your S3 bucket has been created, use the following command:

aws s3api list-buckets

Expected output:

{
    "Buckets": [
        {
            "Name": "devex-aws-bucket",
            "CreationDate": "2024-11-04T10:30:45+00:00"
        }
    ],
    "Owner": {
        "DisplayName": "<Your-AWS-Account>",
        "ID": "<Your-AWS-Account-ID>"
    }
}

In this output, verify your bucket is under "Buckets", along with its creation date.

Check bucket encryption

To verify encryption policy, use the following command, replacing <your-bucket-name> with your bucket’s name:

aws s3api get-bucket-encryption --bucket <your-bucket-name>

Expected output:

{
    "ServerSideEncryptionConfiguration": {
        "Rules": [
            {
                "ApplyServerSideEncryptionByDefault": {
                    "SSEAlgorithm": "AES256"
                },
                "BucketKeyEnabled": true
            }
        ]
    }
}

This output confirms that server-side encryption is configured with AES256 as the encryption algorithm with BucketKeyEnabled set to true. This means your bucket is encrypted based on the composition configuration. The Consumer Portal user doesn’t have to specify any additional information to get this.

Destroy your resources

You can delete resources directly from the Consumer Portal. Select the resource you want to delete and go to Settings then select Delete Resource.

Follow the interactive guide below:

To verify bucket deletion, run the AWS S3 CLI again.

aws s3api get-bucket-encryption --bucket <your-bucket-name>

This command should return with an error:

{
    "Error": {
        "Code": "NoSuchBucket",
        "Message": "The specified bucket does not exist",
        "BucketName": "devex-aws-bucket"
    }
}

Next steps

You just drove an entire deployment lifecycle with an Upbound control plane! Now you’re ready for more Upbound concepts.

Check out the Core Concepts section for more information about authoring compositions or configuration with Python and KCL.