Supported AWS regions, resources, and lines

Written by:  Shanna S
Last updated:  

Lucidscale can be used to import cloud infrastructure data from AWS. For a comprehensive list of the supported regions, resources, and lines from AWS that are available in Lucidscale read this article. 

For instructions on importing cloud infrastructure data from AWS and using it to generate diagrams in Lucidscale, refer to our Import and manage AWS infrastructure data in Lucidscale article.

Supported regions

AWS offers two types of regions:

  • Default regions: Enabled for all AWS users. 
  • Opt-in regions: AWS users must explicitly enable these regions. They are often used to comply with specific country regulations.

Default regions

You can import AWS accounts hosted in any of the following AWS regions:

  • ap-northeast-1
  • ap-northeast-2
  • ap-northeast-3
  • ap-south-1
  • ap-southeast-1
  • ap-southeast-2
  • ca-central-1
  • eu-central-1
  • eu-north-1
  • eu-west-1
  • eu-west-2
  • eu-west-3
  • sa-east-1
  • us-east-1
  • us-east-2
  • us-west-1
  • us-west-2

Opt-in regions

You can import AWS accounts hosted in any of the following opt-in regions. You may encounter import errors if you have not enabled these regions in AWS.

The following opt-in regions are supported:

  • af-south-1
  • ap-east-1
  • ap-east-2
  • ap-south-2
  • ap-southeast-3
  • ap-southeast-4
  • ap-southeast-5
  • ap-southeast-6
  • ap-southeast-7
  • ca-west-1
  • eu-central-2
  • eu-south-1
  • eu-south-2
  • il-central-1
  • me-central-1
  • me-south-1
  • mx-central-1

If you receive an error after importing from one of these opt-in regions, verify the region is enabled in your AWS account before trying again.

Supported resources

Lucidscale provides automated diagramming for the following AWS resources, also known as mapped resources:

Compute

  • Amazon ElastiCache (supports Redis and Memcached)
    • Clusters
  • Amazon Elastic Compute Cloud (EC2)
    • Instances
  • Amazon EC2 Auto Scaling
    • Auto Scaling Groups (ASG)
    • Launch Configurations
  • Amazon Elastic Container Service (ECS) (Designated “ECS View”)
    • Clusters (broken down by EC2 and Fargate launch types)
    • Services
    • Tasks
  • Amazon Elastic Kubernetes Service (EKS)
    • Clusters
  • AWS Lambda
    • Functions
  • Elastic Load Balancing (ELB)
    • Application Load Balancers (ALB)
    • Classic Load Balancers (CLB)
    • Target Groups
      • Target Health metadata

Storage

  • Amazon Simple Storage Service (S3)
    • Buckets (with additional metadata regarding associated roles, groups, etc.) 
  • Amazon S3 Glacier
    • Vaults
  • Amazon Elastic File System (EFS)
    • File Systems
  • Amazon EC2 Volumes (EBS) 
    • Volumes

Databases

  • Amazon Relational Database Service (RDS)
    • DB Clusters (e.g., for Aurora)
    • DB Instances (nested under respective cluster and standalone)
    • DB Proxies
  • Amazon DynamoDB
    • Tables
  • Amazon DocumentDB (with MongoDB Compatibility)
    • Clusters

Networking & Content Delivery

  • Amazon Virtual Private Cloud (VPC)
    • VPCs
    • Customer Gateways
    • Elastic Network Interfaces
    • Internet Gateways
    • NAT Gateways
    • Network Access Control Lists (NACLs)
    • Route Tables
    • Security Groups
    • Subnets
    • Transit Gateways
    • VPC Endpoints
    • VPC Peering Connections
    • VPN Gateways
    • VPN Connections
  • Amazon CloudFront
    • Distributions
  • Amazon Route 53
    • Hosted Zones
  • AWS Network Firewall
    • Network Firewalls
  • Amazon API Gateway
    • API Gateway REST APIs (v1)
    • API Gateway HTTP APIs (v2)

Analytics

  • Amazon Managed Streaming for Apache Kafka (MSK)
    • MSK Clusters
  • Amazon Kinesis Data Streams
    • Kinesis Data Streams
  • Amazon Kinesis Data Firehose 
    • Delivery Streams
  • Amazon Elastic MapReduce (EMR)
    • Clusters
  • Amazon OpenSearch Service (Formerly Amazon Elasticsearch Service)
    • Domains
  • Amazon Redshift
    • Clusters

Application Integration

  • Amazon Simple Notification Service (SNS)
    • Topics
      • Topic Attributes
  • Amazon Simple Queue Service (SQS)
    • Queues
  • AWS Step Functions
    • Activities
    • State Machines
  • Amazon EventBridge
    • Event Buses
    • Rules
  • AWS AppSync
    • GraphQL APIs

Security, Identity, & Compliance

  • Amazon Cognito
    • User Pools
  • AWS CloudTrail (Management & Governance, but often related to security audits)
    • Trails

Additional imported resource metadata is available in your Cloud Inventory for manual placement.

Supported lines

Lucidscale can draw lines between mapped resources that explicitly reference another in the metadata:

Content Delivery

  • CloudFront Distribution to S3 Bucket [CloudFront -> S3]
  • Route 53 Hosted Zone to ALB’s [Hosted Zone -> ELBs (V2)]
  • Route 53 Hosted Zone to CloudFront Distributions [Hosted Zone -> CloudFront]
  • Route 53 Hosted Zone to ELB’s [Hosted Zone -> ELBs]
  • Route 53 Hosted Zone to S3 Buckets [Hosted Zone -> ELBs]

Load Balancing

  • ALB to EC2 instances [ELB (V2) -> EC2]
  • ELB -> ASG
  • ELB to EC2 instance

Networking

  • Route Table (Routes) -> Internet Gateways
  • Route Table (Routes) -> NAT Gateways
  • Transit Gateway to Peered Transit Gateway [Transit Gateway -> Transit Gateway]
  • Transit Gateway -> VPCs
  • VPC Peering Connections (to Requester and Accepter VPCs)
  • VPN Connections via Transit Gateways [Transit Gateway →  VPN Connection → Customer Gateway]
  • VPN Connections via VPN gateway  [VPN Gateway →  VPN Connection →  Customer Gateway]

Serverless

  • API Gateway (V1) -> Lambda Function
  • API Gateway (V2) -> Lambda Function
  • CloudFront Distribution -> API Gateway (V2)
  • CloudFront Distribution -> Lambda Function
  • Cognito User Pool -> Lambda Function
  • DynamoDB Table -> Lambda Function
  • Kinesis Data Stream -> Lambda Function
  • MSK Cluster -> Lambda Function
  • S3 Bucket -> Lambda Function
  • SNS Topic -> SQS Queue
  • SQS Queue -> Lambda Function
  • Step Function State Machine -> Lambda Functions

Note: If you’ve elected to summarize resources within a Lucidscale View, you need to un-summarize them in order for lines to be rendered in the document.

Did you find what you were looking for?

Still have a question or want to share what you have learned? Visit our Community   to get help and collaborate with others.