CloudFormation console link resource type coverage

Question

CloudFormation console link resource type coverage

Ricapar opened this issue 5 years ago · 8 comments

2. Scope of request

When CloudFormation provisions resources for you, you can check what it has created via the "Resources" tab on the stack.

The table lists out the Logical ID, Physical ID, Type, Status, etc.

On certain resources, the Physical ID will be a link that takes you to the page within the AWS Console that represents that resource.

One would expect that if the resource is not click-able that it doesn't exist as something viewable within the console, but this is not the case. There doesn't appear to be consistency between which resources are click-able and which ones are not.

Being able to click on the Physical ID and jump to the section of the console that describes that resource makes for quick drill-downs into what you're dealing with when looking at a stack.

3. Expected behavior

Any resource that can be linked to directly within the console should be linked to via CloudFormation.

Resources that don't have a presence within the console or are sub-sections of other resources should continue to behave as-is and not be linked.

4. Suggest specific test cases

If you create a resource of AWS::S3::Bucket, the Physical ID column will be the name of the bucket as link to the S3 bucket within the AWS Console. 👍
If you create a resource of AWS::ECS::Cluster, the Physical ID will be the name of the ECS Cluster, but it is not clickable even though it is possible to hotlink directly to a page for the ECS Cluster. 👎

Answer 1 · 2019-09-28T22:40:22.000Z

Supported resource types:

deepLinkResourceSpecification.json

Couldn't find links using PHYSICALID but could link closer:

Answer 2 · 2019-10-18T18:09:52.000Z

100+ resource type support rolling out regionally now

Still adding more resource type deeplink support

some percent-encoding issues with some characters in some other services' consoles (SNS, SSM, ECR, etc)

Also issues when physical resource IDs are dynamic references

Answer 3 · 2020-05-14T23:32:00.000Z

Any ETA? Would be nice!

Answer 4 · 2020-06-23T06:19:52.000Z

Is it also possible to leverage this functionality with Custom Resources? For example adding a link to the Log Group of the Lambda function?

Answer 5 · 2021-01-11T21:00:35.000Z

@gruebel If you are using a Resource Provider, you can add "resourceLink" to the schema, like the AWS implementation does;

Answer 6 · 2022-09-07T10:52:44.000Z

In the mean time before this gets fixed i've created a google chrome extension that adds links to ALB's, Listeners & TargetGroups - https://chrome.google.com/webstore/detail/aws-ui-helper/mphfofmlanhmdaldkcidkpgnnihimadm?hl=en&authuser=0 . If there is a list of resources with link patterns i can add more resources.

Answer 7 · 2022-10-11T19:05:53.000Z

@challapradyumna open source anywhere for contributions?

Answer 8 · 2022-10-13T19:47:29.000Z

@PatMyron https://github.com/challapradyumna/aws-ui-helper