No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Any suggestions on how to create a mysql-provider for a rds-cluster inside a VPC? My current code looks like this but I guess I have to take my ip and add it to some rule maybe?

```const m2cluster = new aws.rds.Cluster(
  'magento2-cluster',
  {
    backupRetentionPeriod: 5,
    masterUsername: mysqlUser,
    masterPassword: mysqlPassword,
    preferredBackupWindow: '07:00-09:00',
    deletionProtection: !isDev,
    vpcSecurityGroupIds: [sg.id],
    dbSubnetGroupName: subnetGroup.name,
    tags: pulumiTags,
    clusterIdentifierPrefix: 'magento2-cluster',
    databaseName: 'MAGENTO',
    skipFinalSnapshot: isDev,
    // finalSnapshotIdentifier: 'magento2-cluster-snapshot',
    storageEncrypted: true,
  },
  {
    dependsOn: subnetGroup,
  },
);

const mysqlProvider = new mysql.Provider(
  'mysql',
  {
    endpoint: m2cluster.endpoint,
    username: m2cluster.masterUsername,
    password: m2cluster.masterPassword.apply((p) =&gt; p!.toString()),
  },
  {
    dependsOn: m2cluster,
  },
);```


Ran into similar, and tried to solve it by creating a lambda that runs the provisioner… but then ran into a secret “feature” that strips out pulumi packages…

So… I still think the correct route is to create an “operations microservice” in lambda that can run the pulumi provisioners, however, it will have to be deployed without pulumi, until pulumi removes that “feature”.