aws-dms: CfnEndpoint S3 bucket takes a long time to provision

[alexandervandekleutab]

I am creating an s3 endpoint like

    const migrationBucketName = 'my-migration-bucket'

    const s3Endpoint = new dms.CfnEndpoint(this, 's3-endpoint', {
      endpointType: 'target',
      engineName: 's3',
      endpointIdentifier: 'my-migration-endpoint',
      s3Settings: {
        bucketName: migrationBucketName,
        dataFormat: 'csv',
        encryptionMode: 'SSE_S3',
        serviceAccessRoleArn: migrationBucketAccessRole.roleArn,
      },
    })

When I deploy this, it does not create the bucket right away. Last time i was confused because my connection tests were failing and then randomly started working. When I went to check, the bucket existed. I am deploying this endpoint in a separate environment and I am seeing that the bucket does not exist. It may exist in a few minutes. Is this expected behaviour?

[peterwoodworth]

Hey @alexandervandekleutab,

The CfnEndpoint resource won't create a bucket, you'll have to have created a bucket named my-migration-bucket already in the console, in another stack, or you can create the bucket in the same stack!

Your stack will deploy successfully even if the bucket you specify does not exist, but that doesn't mean the bucket will get created by this CfnEndpoint. That's something you'll still have to create separately

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.