No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

steps followed:

• create new pulumi typescript project
• install `@pulumi/cdk` dependency
• install `aws-cdk-lib` dependency
• added small chunk of code to create S3 bucket (next message)
• `pulumi preview` or `pulumi up` 

```import * as pulumi from "@pulumi/pulumi";
import * as pulumicdk from "@pulumi/cdk";
import * as s3 from "aws-cdk-lib/aws-s3";

class TestStack extends pulumicdk.Stack {
    bucketName: pulumi.Output&lt;string&gt;;

    constructor(id: string, options?: pulumicdk.StackOptions) {
        super(id, options);

        const testBucket = new s3.Bucket(this, "TestBucket", {
            bucketName: "juan-pulumi-cdk-test-bucket",
        });
        this.bucketName = this.asOutput(testBucket.bucketName);

        this.synth();
    }
}

const stack = new TestStack("teststack");
export const url = stack.bucketName;```

tried --verbose flag without better results

You do need to bootstrap your environment first: <https://docs.aws.amazon.com/cdk/v2/guide/bootstrapping.html>

thanks for the answer that helps a lot!

I was pointing to an already bootstrapped AWS account where we are using CDK v1 so I guess that is asking for v2 bootstrapping, do you know if I can use v1?

As in use the v1 bootstrap? I am not sure how compatible they are? For the most bit we have only tried with v2

yep, that was my question, because I,ve already checked that bootstrap of v2 breaks bootstrap of v1 in the same account/region

but with your answer I can continue testing it even if I need to do it in a different region or account :smile:

I will share any related finding afterwards 

There are different versions of the bootstrap in AWS CDK. If you have used CDK v1 bootstrap without the feature flag to set the "new CDK bootstrap" there are probably some issues. Also, different releases of CDK may have dependencies towards certain bootstrap versions. The CDK bootstrap sets an SSM parameter which version the bootstrap is, and regular AWS CDK deployments have a check in the generated CloudFormation which version is required.