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::Route53Profiles::ProfileAssociation] [BUG] Route53Profiles unable to find vpc #2044

Closed
n3mawashi opened this issue May 16, 2024 · 1 comment

Comments

@n3mawashi
Copy link

n3mawashi commented May 16, 2024

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.

R53EndProfileAssociation:
    Type: AWS::Route53Profiles::ProfileAssociation
    Properties:
      Name: !Sub "${NamingPrefix}-${EnvType}-${AWS::Region}-R53-RPAssoc-End"
      ProfileId: !Ref R53AwsProfile
      ResourceId: !Sub arn:aws:ec2:${AWS::Region}::vpc/${EndVpcId}

Unfortunatey GetAtt VpcId doesn't provide an Arn hence the hand crafted version.

Other Details

image

@n3mawashi n3mawashi added the bug label May 16, 2024
@n3mawashi n3mawashi changed the title [Resource Type] - [BUG] - [AWS::Route53Profiles::ProfileAssociation] [BUG] Route53Profiles unable to find vpc May 28, 2024
@cfn-github-issues-bot cfn-github-issues-bot added this to Researching in coverage-roadmap May 28, 2024
@cfn-github-issues-bot cfn-github-issues-bot moved this from Researching to We're working on it in coverage-roadmap May 29, 2024
@amruthcAmazon
Copy link

amruthcAmazon commented May 30, 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.

@nmeisen nmeisen moved this from We're working on it to Shipped in coverage-roadmap May 30, 2024
@nmeisen nmeisen closed this as completed May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
coverage-roadmap
  
Shipped
Development

No branches or pull requests

4 participants