- Le plus récent
- Le plus de votes
- La plupart des commentaires
Looks like the accessiblity flag issue. You can check the same via CLI using the describe-db-clusters API and filtering or searching for PubliclyAccessible. Here is an example:
aws rds describe-db-instances --region us-west-2 --output json --query 'DBInstances[?Engine==aurora
].{instance:DBInstanceIdentifier, cluster:DBClusterIdentifier, isPublic:PubliclyAccessible }'
[
{
"instance": "MyInstance_1",
"isPublic": true,
"cluster": "MyAurora_Wrk-cluster"
},
{
"instance": "MyInstance_2",
"isPublic": false,
"cluster": "MyAurora_Wrk-cluster"
}
]
You modify an instance and enable public access on it using the modify-db-instance API.
Last night the same error occurred in an other region (us-west-1). Sounds like a problem that other AWS users should face too?
Contenus pertinents
- demandé il y a un an
- demandé il y a 7 mois
- demandé il y a 2 mois
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 4 ans
- AWS OFFICIELA mis à jour il y a un an
Our RDS servers are only available from private subnets. So no need for public accessibility.