-
Notifications
You must be signed in to change notification settings - Fork 53
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::Route53Profiles::ProfileAssociation] [BUG] Route53Profiles unable to find vpc #2044
Labels
Projects
Comments
n3mawashi
changed the title
[Resource Type] - [BUG] -
[AWS::Route53Profiles::ProfileAssociation] [BUG] Route53Profiles unable to find vpc
May 28, 2024
cfn-github-issues-bot
moved this from Researching
to We're working on it
in coverage-roadmap
May 29, 2024
Customer provided VPC Arn instead of VPC Id(vpc-0dbcce45527fca94f) in the ProfileAssociation request properties for ResourceId. So the service was unable to identify the VPC. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Name of the resource
AWS::Route53Profiles::ProfileAssociation
Resource Name
AWS::Route53Profiles::ProfileAssociation
Issue Description
When creating an association between VPC and Profile API complains that resource doesn't exist. However if I go to the console I can create it just fine.
Expected Behavior
VPC association should be created.
Observed Behavior
Resource handler returned message: "Can't find the resource with ID "arn:aws:ec2:ap-southeast-2::vpc/vpc-0dbcce45527fca94f (https://ap-southeast-2.console.aws.amazon.com/vpcconsole/home?region=ap-southeast-2#VpcDetails:VpcId=vpc-0dbcce45527fca94f)". (Service: Route53Profiles, Status Code: 400, Request ID: 487cabf7-6c9b-413e-96ce-576979f42927)" (RequestToken: b2bd188c-5068-6269-1e56-a231cac4d25b, HandlerErrorCode: GeneralServiceException)
Test Cases
code I used.
Unfortunatey GetAtt VpcId doesn't provide an Arn hence the hand crafted version.
Other Details
The text was updated successfully, but these errors were encountered: