10

Yes, you can rename an RDS instance... at your own peril. When you rename a DB instance, the [DNS] endpoint [hostname] for the DB instance changes, because the URL includes the name you assigned to the DB instance. http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_RenameInstance.html Your application code requires configuration changes to ...


4

Why not something like Redis? (can use it through ElastiCache). Hard to answer this without knowing the operational requirements of this project. Is this data strictly for logging/research, or is it operational (i.e. this "table" is consulted in order to know which lambda to invoke). Dynamo vs. RDS - depends how spiky your traffic is. Dynamo is very ...


3

Either use the --query attribute aws rds describe-db-snapshots --query "DBSnapshots[?Encrypted].DBSnapshotIdentifier" If the [?Encrypted] does not work, try [?Encrypted == 'true'] as the first is from JMESPath improved filters. The quotes might need to be backticks in some case. It all depends. Second way: aws rds describe-db-snapshots --output json | jq ...


3

Yes you can change the name of the RDS instance, but it is highly discouraged to do so in LIVE Production environment. It would change the EndPoint which might impact other resources actively accessing the RDS server (like an application server). This would probably require a property / env-variable change in your code or configs (which would ideally end up ...


3

If I am understanding your question correctly, what you are describing sounds like a perfect use case for SSM. You can store your RDS password as a secure string parameter encrypted by KMS, then reference it in you terraform file as a data source with decryption. With this method, you only have to reference your decrypted password, and never directly store ...


2

For question #1) I think this could perhaps be better answered on SoftwareEngineering SE. Nonetheless, I'll risk an answer: for this kind of information (states) coming from that kind of architecture (distributed), I recommend event sourcing. It removes the complexity and many headaches that come with the nature of distributed systems if someone try to ...


2

On top of protecting your root account as best as you can, you should be able to reduce the risk of such resource deletion if you have more than 1 resource to protect. For example if all AWS resources you had to protect were 2 RDS database servers, you could create 2 other accounts that have access to only copy the snapshots of one of your database servers ...


2

First try to review current caching parameter values. Then check list in AuroraMySQL.Reference.ParameterGroups And try to tune/increase caching parameters like query_cache_size Alternative solution is to use architecture redesign with AWS CloudFront to reduce load on primary system (probbly web?).


2

If I understood you correctly, you need free strategy. It will run all tasks ASAP, not waiting for anything. https://docs.ansible.com/ansible/latest/plugins/strategy/free.html Bear in mind, that logs will be a mess :)


1

As per the error, it looks like the resolution is not happening for host xxxxx-xxxxx-xxxx.xxxxxxxxx.us-east-2.rds.amazonaws.com'. I mean the hostname is not getting resolved to the IP address from inside the container. You may need to check if the DNS resolver is working properly from inside the container or not. For testing, you can try to use the IP ...


1

I don't have a SQL Server on AWS to check, but you could see if it's in xp_msver, or figure it out from ProcessorCount, ProcessorType and PhysicalMemory in that sproc.


1

Restoring a snapshot simply creates a new RDS instance. So if you restore the prod DB snapshot to staging then you will be creating a new RDS instance with the restored data in it. If both of the RDS instances are in the same aws account then You will either have to delete/rename the staging DB and then restore the prod DB If both of the RDS instances are ...


1

You can look at Aurora Global Database for this. Based on this news announcement, you can also configure the setup, so you can write to your local db cluster and this is forwarded to your primary region. Of course there would be some lag in write requests, essentially of the length of time it takes to write to the primary region and replicate the data ...


1

Your assumption is correct: you will not need to perform patching on an RDS instance, AWS handles that for you. There is a caveat, though: the majority of updates are not forced by AWS, but require an automated maintenance window to execute. Periodically, Amazon RDS performs maintenance on Amazon RDS resources. Maintenance most often involves updates to the ...


1

I believe you are correct, a single long-running connection will prevent AWS Aurora Serverless from triggering the pause-and-resume feature. Aurora Serverless v1 can also scale to zero capacity when there are no connections if you enable the pause-and-resume option for your DB cluster's capacity settings. Source: How Aurora Serverless v1 works Take this ...


1

I am not sure it will be helped. I have similar design in my office. I have some Kubernetes Cluster. all node and master running on local ip from a PVC. And my rds too, only have local ip run on same PVC. Kubernetes Cluster already connect to RDS using local ip. Then, I build VPN server on bastion server. Have local ip and public ip, run on same PVC with RDS ...


1

As far as I read, client using that db instance has to update certificate if the client has added the db in it's truststore. When you schedule this operation, make sure that you have updated your client-side trust store beforehand. https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.SSL-certificate-rotation.html I don't think ...


1

I am not completely sure that Ubuntu 18.04 will have this CA in their certificates packages because they announced this CA replacement recently. If you are using the SSL/TLS to connect to your DB instances, then only this will be required, otherwise you can simply ignore this. You can find the complete details of this CA certificate rotation and it's ...


1

I don't think any database services "internal traffic" is available to AWS services directly. That being said, you should be able to dump all sql queries to a log file on S3 and also extract all database/table combinations to a text file as well. It then becomes a text processing exercise that you can possibly solve with AWS Athena


1

To my knowledge there are only Tag based Iam policies available to limit access to resources for certain users or user groups. Because of this, you should simply be able to tag an RDS snapshot both production and development for you to access it with your development user or group. There are a large number of security considerations to think through, so ...


1

I found the solution to my problem: In the main.yml task : - include: wait_rds_are_stopped.yml when: chosen_action == "stop" loop: "{{ vars[ 'list_rds_resources_ids1_' + environment ] + vars[ 'list_rds_resources_ids2_' + environment ] }}" loop_control: loop_var: outer_item In the wait_rds_are_stopped.yml task: - name: Wait for RDS stop to ...


1

It's been a while since posting the question, and a comment I made above seems to be helpful despite the fact it's using a quantitative assessment, so I'll post it here as an answer. As per comment above: @030 I can offer my experiences since asking the question, albeit it's a subjective view as I have no quantitative data. I can offer that a year and a ...


1

You're not showing how the response example you shown relates to response1 (there is no 'TagList' in your example). It looks like response1['TagList'] is an empty list. Otherwise you're on the right track (you can always check your exact case directly in the python shell): $ python Python 2.7.12 (default, Jul 01 2016, 15:36:53) [GCC] on linux2 Type "help", ...


1

Your proposed snapshot-id is not syntactically valid. When you tried hard-coding the value, you used a valid identifier. Underscores are not allowed, and the identifier can't begin with a number. Here are the constraints on snapshot identifiers, from the API Reference: DBClusterSnapshotIdentifier The identifier of the DB cluster snapshot. This ...


1

You will require a script that interacts with the AWS cli to accomplish your goal. To list encrypted drives I use the following query when describing the DB snapshots --query 'DBSnapshots[*].[DBSnapshotArn,Encrypted]' I have put together the following script which will look for all encrypted DBS snapshots and then copy all of them to a different region. It ...


1

The cost will depend on the number of messages you write per second. Most often DDB is cheaper. If you have a large throughput, 10k requests per second, then your DDB costs will need to be carefully considered vs. RDS. In this case however, I would actually reccommend using S3 to output your log messages to a file. I think technically this will be a good ...


Only top voted, non community-wiki answers of a minimum length are eligible