I'm new to RDS and I'm trying to access a recently created MySQL database from my machine at work. After some googling I saw that the DB Security Groups needed to be modified but I don't see that on my screen. I continued searching and found this and it seems to be a step in the right direction but I'm still no understanding what it means by the "VPC" group. I tried creating Parameter Groups, Option Groups, and Subnet Groups all to no avail. I just need to give my work IP access to the DB. Any help would be greatly appreciated
You can refer this blog post: http://aws.amazon.com/articles/Amazon-RDS/2935
If you are using RDS in a VPC, then you create / modify security groups in the AWS VPC console (this link). If not, security groups for RDS are located in the AWS RDS console (this link). Those links assume you are on US East 1 region but can be modified for any region.
Create a new Security group from the VPC area. name it something like rds-webhostaccess Put in the ip block you want to the rds to be accessible from. The port doesn't matter, but you can choose mysql if you like.
Click on EC2 in the AWS console. You'll find Security Groups under Network & Security section, in the left menu.
Then you can go ahead to create a new group or to modify an existing one.
Related
Every time I add an user, it gets duplicated to all virtual hosts. I've been facing this issue for a while and found a way to solve it, see this post, it says I have to configure a separate database to each virtual host.
What I can't understand is why Ejabberd has this default behavior in first place, what is the benefit to do so?
And what about mod_mam? How do I configure it to store each message into its own database?
My ejabberd.yml (mod_mam configuration at line 113)
Thank you. :)
and found a way to solve it
Since recent ejabberd versions, you can use the new SQL schema, and configure ejabberd to use it, see in
https://docs.ejabberd.im/admin/configuration/#relational-databases
What I can't understand is why Ejabberd has this default behavior in
first place, what is the benefit to do so?
One possibility is the saved space for very big servers. Of course, when having many small servers, it's preferable to use one single database.
And what about mod_mam? How do I configure it to store each message
into its own database?
It's the same with this module than with the other ones: if you configure it to use 'sql' storage, and you configured ejabberd to use a certain database for host "example.net", and a different one for "example.com"..., then mod_mam will use the correct SQL database to store the MAM messages depending on the user that wants to store them.
Se the first and second example configs in section https://docs.ejabberd.im/admin/configuration/#virtual-hosting
On the other hand, if you use the new SQL schema, you only define one database, so those doubts do not appear.
[also asked in https://github.com/processone/ejabberd/issues/2752 ]
I have purchased an Azure subscription through a reseller (so the offer is of the Azure in Open type) on which I would like to host a wordpress-based webpage (amongst other services). In order to do that I need to create a MySQL database and I would like to use a shared Clear DB for it. However, neither ClearDB nor MySQL database is available for me to be created on the subscription (these resources simply do not appear in the list). There is a credit card linked to the subscription already.
The only option Azure gives me is to create a VM with MySQL pre-installed, however the price for that is (obviously) way higher. I've checked the FAQ site for Clear DB on Azure (https://learn.microsoft.com/en-us/azure/store-cleardb-faq), but if I'm not wrong I already have the requirements fulfilled.
What settings do I have to change in order to be able to create a Clear DB instance on the subscription? Am I missing something?
I am trying to delete an instance from GUI web tool. It is showing that the instance have been deleted and it is removed from the list. Also the desk have been deleted. But after some time it is coming back in the list. Can some one please tell me what is the issue ?
Thanks!
As mention on my previous comment, if you have installed any of the click to deploy software packages in GCE, you need to delete the cluster in the same page.
If this is not the case, in the Developers Console, the 'Operation' option, provides information of instance being created and by whom. This can give you an idea on what is sniping back the instance. If is's a service account, you need to find the script that is creating the instance and stop it.
I'm looking into using CloudBees for some application prototyping. I am using free accounts right now, I am not paying any subscriptions at the moment.
The first step for me is to create a MySQL database to host my application's data. I've done so (and it was pretty easy!). I also use Liquibase to manage the database (I've started this work using local H2 databases for the pre-prototyping), and I've been able to construct everything as expected.
As part of checking whether liquibase created the tables, I brought up the MySQL database in NetBeans. And, it did function well. But I can also see other schemas as well as the schema I just created. They're all innocently named (test, test_6hob). But, I can see the tables and view their data.
My question is around the visibility of the data that's in the CloudBees database. Is the database created for the free accounts viewable to other people connecting to the same machine? Does this change if I use a paid account? Or is it more the nature of how the database was created? I can see other schemas (and their data) but I have no idea if other people can see mine? Is there a permissions-aspect I need to ensure I set? I've fairly ignorant with the inner-workings of MySQL.
While this is a prototype, were I to move into using CloudBees for production applications, I wouldn't want the data to be visible to anyone who happened to connect to the same database as my application. It's entirely possible that I'm missing something in this new cloud world. :)
Thanks for any info
All CloudBees MySQL databases are secured separately (although will be in shared instances unless you have a dedicated server) - they are not readable by any other account by default.
However, it is possible for the database owner to grant access to users from other accounts on that same database server if you really wanted to - even though it makes very little sense to do so (and your special user configuration will be lost during a failover).
So this is what has happened for the test databases that you can see - the database owner has opened up security on those databases / tables.
This question is probably off topic but i'll bite anyway. The database data is private to your account. Actual hardware/vm's maybe shared but the data/database is not.
Azure websites let us configure our site using a new MySQL Database instead of SQL Azure. But after creation it's never visible in admin panel. I beleive that it's because is hosted in a third party server, but I have no idea how to reach it, any tip?
For managing it from an external tool check out my response here.
Though the database is hosted by a third party (ClearDB), you should see it listed as a "linked resource" on the dashboard for your Web Site in the Windows Azure portal. When you delete the Web Site, it asks if you also want to delete the linked resource.
If you choose not to or you unlink the MySQL resource explicitly, it's still there and you'll see it a list of existing resources when you subsequently do an explicit link. (I haven't found a way to see a list of the unlinked MySQL databases, but will update this response when I hear).
So I'd say to delete the MySQL database you can
Delete the entire Web Site and, when prompted, select the MySQL database to be deleted too
Unlink the MySQL database from the Web Site you want to keep; create a new temp Web Site, and add the existing MySQL database as a Linked Resource to it. Then delete the new, temp Web Site along with the linked database. Not elegant, but seems to work in my testing.
Currently you can't manage the MySQL Server.
As for being third party - yes, the service (MySQL-as-a-Service) is provided by a third party byt lives in Azure! It is not on other servers, it is on the Azure servers. Most probably (just my guess) worker roles. But as the feature is still preview, the management is missing.
The third party vendor is ClearDB. They provide MySQL as a service on top of Windows Azure. so no worries, your data is in the same Data Center (of course if you chose same) as your web site. But you can't directly manage it, unless you install something like PhpMyAdmin on your website.
I had a slightly different issue where Jim O'Neil's #2 didn't fully work because the database that was orphaned was created through the "Add-On" gallery. To work around this, you can link the orphaned database to the new temporary site as suggested, and then click on the "Manage" link in the Linked Resources tab with the database selected. This will take you to ClearDB's management for the databases.
From there, you can click on the first tab, and then click "Delete" to manually delete the database from ClearDB. This is an async operation so it may take some time, and you may also have to refresh the portal because the entries are cached.
You can also add the ClearDB Add-on and create either the Free tier or the 9.99 a month Venus 1gb tier. The Free tier is only 20mb so that isn't much. For the database name, you can type in the existing MySQL database, and ClearDB Add-on will link to that.
I know this is a super old question, but it's the first result that came up when I did a Google search for deleting mysql azure databases. You can manage your MySql databases from the management portal now, via the Linked Resources page. Either click on the name of the mysql DB directly, or select the row and click manage down at the bottom.
i know that this is a late answer but i followed them to gain the exact access
Select Your web app
Clicked linked resources
Click on mysql db name (It will redirect you to cleardb website for your account)
Install mysql workbench
click on endpoint information
in mysql workbench give the value of hostname, and access credentials i.e. username, password
and you are good to go :)