RDS
Last updated
Last updated
Name | Description |
---|---|
Teleskope needs read access to automatically discover all of your RDS clusters and instances.
Attach the AmazonRDSReadOnlyAccess to the Teleskope role you created.
Teleskope needs write access take enforce remediation policies such as tagging, deletion, etc.
Attach the AmazonRDSFullAccess to the Teleskope role you created.
For each RDS cluster you would like to scan using Teleskope, you will need to create an IAM database user, or create/provide credentials for a database user, and grant that user permissions.
MySQL or MariaDB
Postgres
MySQL or MariaDB
Postgres
Launch an EC2 instance in a public subnet to serve as the SHH tunnel Bastion Host.
The public key for the key-pair parameter will be provided by Teleskope: teleskope-bastion-key.
Designate Teleskope AWS account access within your security group(s). IP addresses will be provided by Teleskope.
Assign an Elastic IP (EIP) to the bastion host.
Adjust route tables and security groups as needed to provide access to the RDS instance through the bastion host.
Provide Teleskope with the bastion username, and the bastion elastic IP.
Teleskope Role
Attach RDS read and/or write permissions to the Teleskope IAM role you created
Username and password
Create a read and/or write database user for each RDS cluster you'd like us to scan
SSH Tunnel (Optional)
If your RDS instances are in a private subnet and you don't want to enable VPC peering, create a bastion host for us to use to access your RDS instances.