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

CloudFormation console link resource type coverage #139

Open
Ricapar opened this issue Aug 22, 2019 · 8 comments
Open

CloudFormation console link resource type coverage #139

Ricapar opened this issue Aug 22, 2019 · 8 comments
Labels
enhancement New feature or request

Comments

@Ricapar
Copy link

Ricapar commented Aug 22, 2019

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. 👎
@TheDanBlanco TheDanBlanco added the enhancement New feature or request label Aug 22, 2019
@PatMyron
Copy link
Contributor

PatMyron commented Sep 28, 2019

Supported resource types:

deepLinkResourceSpecification.json


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

AWS::Amplify::App
https://console.aws.amazon.com/amplify/home
AWS::AppMesh::Mesh
https://console.aws.amazon.com/appmesh/meshes
AWS::AppStream::ImageBuilder
https://console.aws.amazon.com/appstream2/home#/images?topTab=image-builders
AWS::AppStream::User
https://console.aws.amazon.com/appstream2/home#/users
AWS::AppSync::GraphQLApi
https://console.aws.amazon.com/appsync/home#/apis
AWS::Athena::NamedQuery
https://console.aws.amazon.com/athena/saved-queries/home
AWS::Batch::JobDefinition
https://console.aws.amazon.com/batch/home#/job-definitions
AWS::CloudFront::CloudFrontOriginAccessIdentity
https://console.aws.amazon.com/cloudfront/home#oai:
AWS::CodeCommit::Repository
https://console.aws.amazon.com/codesuite/codecommit/repositories
AWS::CodeDeploy::DeploymentConfig
https://console.aws.amazon.com/codesuite/codedeploy/deployment-configs
AWS::ECS::TaskDefinition
https://console.aws.amazon.com/ecs/home#/taskDefinitions
AWS::EFS::FileSystem
https://console.aws.amazon.com/efs/home#/filesystems
AWS::ElastiCache::ParameterGroup
https://console.aws.amazon.com/elasticache/home#param-groups
AWS::GameLift::Alias
https://console.aws.amazon.com/gamelift/home#/r/aliases
AWS::GameLift::Build
https://console.aws.amazon.com/gamelift/home#/r/builds
AWS::Glue::Classifier
https://console.aws.amazon.com/glue/home#catalog:tab=classifiers
AWS::Glue::Workflow
https://console.aws.amazon.com/glue/home#etl:tab=workflows
AWS::Inspector::AssessmentTarget
https://console.aws.amazon.com/inspector/home#/target
AWS::RoboMaker::Fleet
https://console.aws.amazon.com/robomaker/home#fleets
AWS::SageMaker::CodeRepository
https://console.aws.amazon.com/sagemaker/home#/notebook-git-repositories
AWS::SageMaker::NotebookInstanceLifecycleConfig
https://console.aws.amazon.com/sagemaker/home#/notebook-instance-lifecycles/
AWS::SQS:Queue
https://console.aws.amazon.com/sqs/home

@PatMyron PatMyron changed the title AWS::CloudFormation::(User Interface?) -> AWS Console Link all resource types on CloudFormation console Sep 28, 2019
@PatMyron PatMyron self-assigned this Oct 3, 2019
@PatMyron
Copy link
Contributor

PatMyron commented Oct 18, 2019

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

@alexgurmanihsm
Copy link

Any ETA? Would be nice!

@gruebel
Copy link

gruebel commented Jun 23, 2020

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

@craigataws craigataws modified the milestone: cov Jul 21, 2020
@PatMyron PatMyron changed the title Link all resource types on CloudFormation console CloudFormation console link resource type coverage Aug 25, 2020
@benbridts
Copy link

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

@PatMyron PatMyron removed their assignment Sep 1, 2021
@challapradyumna
Copy link

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.

@PatMyron
Copy link
Contributor

PatMyron commented Oct 11, 2022

@challapradyumna open source anywhere for contributions?

@challapradyumna
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

8 participants