# facts from rds module obsfucated?

**URL:** <https://forum.ansible.com/t/facts-from-rds-module-obsfucated/19689>\
**Category:** Ansible Project\
**Tags:** aws\
**Created:** [November 4, 2015, 4:20pm UTC](https://forum.ansible.com/t/facts-from-rds-module-obsfucated/19689 "2015-11-04T16:20:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![John\_Withers](https://avatars.discourse-cdn.com/v4/letter/j/47e85d/32.png) [@John\_Withers](https://forum.ansible.com/u/John_Withers)\
**Post date:** [November 4, 2015, 4:20pm UTC](https://forum.ansible.com/t/facts-from-rds-module-obsfucated/19689/1 "2015-11-04T16:20:51Z")

</div>

Folks,

I am creating an rds postgres instance on aws and need to get the endpoint. The creation goes fine, but when trying to get the endpoint it obsfucates the start of it with \*\*\*\*\*\*. The relevant creation code is:

- name: create rds  
rds:  
region: “{{ region }}”  
command: create  
instance\_name: “blastar-{{ environ }}”  
db\_engine: postgres  
size: 20  
instance\_type: db.t2.medium  
username: “{{ dbuser }}”  
password: “{{ dbpass }}”  
tags: { type: postgres, env: “{{ environ }}” }  
subnet: db\_subnets\_blastar  
vpc\_security\_groups: “{{ db\_sec\_group }}”  
register: rds
- set\_fact: “postgres\_end={{ rds.instance.endpoint }}”
- name: rds vars  
debug: var=rds

And what I get back is:

TASK [rds vars] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

ok: [127.0.0.1] =\> {

“changed”: false,

“rds”: {

“\_ansible\_no\_log”: false,

“changed”: false,

“instance”: {

“availability\_zone”: “us-west-2c”,

“backup\_retention”: 1,

“create\_time”: 1446570076.047,

“endpoint”: “\*\*\*\*\*\*\*\*-staging.cpodljjqrhou.us-west-2.rds.amazonaws.com”,

“id”: “\*\*\*\*\*\*\*\*-staging”,

“instance\_type”: “db.t2.medium”,

“iops”: null,

“maintenance\_window”: “mon:10:50-mon:11:20”,

“multi\_zone”: false,

“port”: 5432,

“replication\_source”: null,

“status”: “available”,

“username”: “VALUE\_SPECIFIED\_IN\_NO\_LOG\_PARAMETER”,

“vpc\_security\_groups”: “sg-dcd2abr3”

},

“invocation”: {

“module\_args”: {

“\_ansible\_no\_log”: false,

“command”: “create”,

“db\_engine”: “postgres”,

“instance\_name”: “blastar-staging”,

“instance\_type”: “db.t2.medium”,

“password”: “notmypass”,

“region”: “us-west-2”,

“size”: 20,

“subnet”: “db\_subnets\_blastar”,

“tags”: {

“env”: “staging”,

“type”: “postgres”

},

“username”: “blastar”,

“vpc\_security\_groups”: “sg-dcd2abr3”

},

“module\_name”: “rds”

}

}

}

TASK [endpoint] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

ok: [127.0.0.1] =\> {

“changed”: false,

“msg”: “\*\*\*\*\*\*\*\*-staging.cpodljjqrhou.us-west-2.rds.amazonaws.com”

}

All those \*\*\* things are in the actual output, not obsfucation I have done and I am stumped where they are coming from. Using the aws cli doesn’t produce them, I can’t find a setting in ansible.cfg that would produce them, and I am not using no log parameters (although I tried setting it to False).

If anyone can point me in the right general direction it would be spiffy. I haven’t had any luck searching on this.

-john

---

<div class="post-metadata">

**Author:** ![John\_Withers](https://avatars.discourse-cdn.com/v4/letter/j/47e85d/32.png) [@John\_Withers](https://forum.ansible.com/u/John_Withers)\
**Post date:** [November 5, 2015, 4:31pm UTC](https://forum.ansible.com/t/facts-from-rds-module-obsfucated/19689/2 "2015-11-05T16:31:15Z")

</div>

Okay, I have figured out what is happening, although still not why precisely. In my first post I changed some details cause pointless paranoia and the instance name didn’t actually start with blastar, it started with authtool. Apparently on my local machine, haven’t tested on others yet, starting an rds name with authtool- produces \*\*\*\* obsfucation in the resulting register command. And -vvvvv on the playbook shows that is what appears to be coming from the wire as well. Any other name to start the id works fine.

Since it isn’t that big a deal to change my ids, this probably solves the problem for me, but I would still love to know why this happens in the first place if anyone happens to know off the top of their head.

j