Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws_ec2_verified_access: Resource handler returned message: "null" #29808

Open
andreprawira opened this issue Apr 12, 2024 · 2 comments
Open
Labels
@aws-cdk/aws-ec2 Related to Amazon Elastic Compute Cloud bug This issue is a bug. effort/medium Medium work item – several days of effort p2

Comments

@andreprawira
Copy link

Describe the bug

I'm creating aws verified access endpoint using cfn construct found here. Before i deployed this part of the code, i was able to create Verified Access Trust Provider, Instance, Groups but failed when deploying the endpoint. Here is the code to deploy the endpoint

# Verified Access Endpoint
        cfnVerifiedAccessEndpoint = ec2.CfnVerifiedAccessEndpoint(
            self,
            "CfnVerifiedAccessEndpoint",
            application_domain="my-sandbox.com", 
            attachment_type="vpc",
            domain_certificate_arn="my-dummy-cert-arn",  
            endpoint_domain_prefix="development",  
            endpoint_type="load-balancer",
            verified_access_group_id=cfnVerifiedAccessGroup.attr_verified_access_group_id,
            description="Verified Access Endpoint",
            load_balancer_options=ec2.CfnVerifiedAccessEndpoint.LoadBalancerOptionsProperty(
                load_balancer_arn="my-load-balancer-dummy-arn",
                subnet_ids=["subnet-private-1", "subnet-private-2"],  
            ),
            security_group_ids= ["my-dummy-sg-id"], 
        )

but when i deploy it, i get this weird non descriptive error

Resource handler returned message: "null" (RequestToken: d2ecd91a-a841-b67d-c5ca-6de761e1af83, HandlerErrorCode: InternalFailure)

Expected Behavior

Verified access endpoint is created

Current Behavior

Deployment failed with non descriptive error message

Reproduction Steps

Please view the code above

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.117.0 (build 59d9b23)

Framework Version

No response

Node.js Version

v18.18.0

OS

Windows

Language

Python

Language Version

Python 3.11.5

Other information

No response

@andreprawira andreprawira added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Apr 12, 2024
@github-actions github-actions bot added the @aws-cdk/aws-ec2 Related to Amazon Elastic Compute Cloud label Apr 12, 2024
@pahud
Copy link
Contributor

pahud commented Apr 12, 2024

This is probably a bug of CFN as it's a L1 construct and the error is from cloudformation.

Can you deploy the CFN stack from CFN console using the synthesized template? If it fails like that, I would recommend reaching out to the AWS Premium support for investigation as this could be a bug from CFN.

@pahud pahud added p2 response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. effort/medium Medium work item – several days of effort and removed needs-triage This issue or PR still needs to be triaged. labels Apr 12, 2024
@andreprawira
Copy link
Author

andreprawira commented Apr 12, 2024

@pahud

Can you deploy the CFN stack from CFN console using the synthesized template

there are 3 templates that shows up for my verified access stack which are template.json, template.json.config, and assets.json, i deployed the one that says template.json only and it failed with the same error msg

"Resource handler returned message: "null" (RequestToken: b2116264-f6a1-e554-6954-e26a5adf9bec, HandlerErrorCode: InternalFailure)"

@github-actions github-actions bot removed the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-ec2 Related to Amazon Elastic Compute Cloud bug This issue is a bug. effort/medium Medium work item – several days of effort p2
Projects
None yet
Development

No branches or pull requests

2 participants