(aws-wafv2): Received the CREATE_FAILED message, but resource was created.

It says that webacl could not be created due to lack of permission, but it is created in the console. And if I check in cloudformation, none of them made webacl.

Deleting the stack does not delete the webacl, I have to delete it directly from the console to clear it.

Reproduction Steps

code

export class CdkTestStack extends cdk.Stack {
  constructor(scope: cdk.Construct, id: string, props?: cdk.StackProps) {
    super(scope, id, props);

    new waf.CfnWebACL(this, "kkkkkkkkkkkhy", {
      defaultAction: {
        block: {}
      },
      scope:"REGIONAL",
      visibilityConfig:{
        cloudWatchMetricsEnabled: false,
        sampledRequestsEnabled: false,
        metricName: "123khymetricName"
      }

    })
  }
}

What did you expect to happen?

Since I received the message CREATE_FAILED No resource has been created.

What actually happened?

I was able to see CREATE_FAILED because I didn’t have wafv2:getWebACL permission, but the resource was actually created.

Environment

• CDK CLI Version : 1.75.0
• Framework Version: 1.75.0 (build 7708242)
• Node.js Version: v10.15.3
• OS : macOS 10.14.6
• Language (Version): TypeScript (3.8.3)

Other

1. I only have CloudformationFullAccessPolicy and wafv2:CreateWebACL.
2. With the above two rights, the CDK says that it is not authorized as follows.

User: arn:aws:iam::871697823052:user/khy is not authorized to perform: wafv2:GetWebACL on r
esource: arn:aws:wafv2:ap-northeast-2:871697823052:regional/webacl/kkkkkkkkkkkhy-gXkvdU7RGK
aQ/696fe192-a1df-4710-bb91-2fbbdb013173 

1. If I create it myself in the console with above two policy, the webACL is created without any errors.

---

This is 🐛 Bug Report

[shivlaks]

@HoYoung1 thanks so much for the great detail on the reproduction steps! it does indeed seem like an odd experience that when creation fails that the resource would still be created. I will pass this feedback along to the wafv2 team so we can better understand whether that’s a bug that they can fix.

since this isn’t quite a CDK bug, i’m going to drop the bug label and mark this as guidance. I’ll update this issue once I hear back from the team!

thanks a bunch!!

[github-actions[bot]]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.