[ansible-project] How to create AWS Hosted Virtual Interface using Ansible?

2019-09-21 Thread Kishore Ponniah
Hi All, Is there an Ansible module to create a Hosted Private or Public Virtual interface in AWS? I can see a module only for Standard Virtual Interface. Could someone please help? Thanks Kishore -- You received this message because you are subscribed to the Google Groups "Ansible Project" g

[ansible-project] Re: Custom module to allocate_private_virtual_interface

2019-02-15 Thread Kishore Ponniah
Hi all, Can someone help, please? Thanks Kishore On Wednesday, February 13, 2019 at 9:28:30 PM UTC, Kishore Ponniah wrote: > > Hi All, > > I am creating Direct Connect Private Virtual Interface but as a hosted > interface. Currently, there are no ans

[ansible-project] Custom module to allocate_private_virtual_interface

2019-02-13 Thread Kishore Ponniah
Hi All, I am creating Direct Connect Private Virtual Interface but as a hosted interface. Currently, there are no ansible modules to allocate_private_virtual_interface. This will create a private virtual interface to be owned by specified AWS account. This is the boto3 link for that https://

[ansible-project] Direct Connect Private Virtual Interface

2019-02-04 Thread Kishore Ponniah
Hi all, Is there an ansible module for creating hosted Private Virtual Interface in AWS? Thanks Kishore -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ans

[ansible-project] Re: How to convert the cloudformation template_url parameter to be the Jinja template substitution

2019-01-22 Thread Kishore Ponniah
:02 PM UTC, Kishore Ponniah wrote: > > Hi All, > > The cloudformation template_url parameter requires Amazon S3 URL which is > currently working by providing the complete URL of the file. But I wanted > to convert that to be the Jinja template substitution. > > My playbook below

[ansible-project] How to convert the cloudformation template_url parameter to be the Jinja template substitution

2019-01-22 Thread Kishore Ponniah
Hi All, The cloudformation template_url parameter requires Amazon S3 URL which is currently working by providing the complete URL of the file. But I wanted to convert that to be the Jinja template substitution. My playbook below: - name: create ps-cross-account-roles changeset cloud

[ansible-project] Re: Ansible s3_sync to upload multiple files

2019-01-22 Thread Kishore Ponniah
This has been resolved by adding a new task for the cross account role to assume from the same account and updated the account config with local account parameters. On Tuesday, January 15, 2019 at 4:44:34 PM UTC, Kishore Ponniah wrote: > > Hi everyone, > > I tried to debug s3_sync b

[ansible-project] Re: Ansible s3_sync to upload multiple files

2019-01-15 Thread Kishore Ponniah
I ran the playbook it completed successfully. Experts please advise if I miss something here. Thanks Kishore On Monday, January 14, 2019 at 5:04:44 PM UTC, Kishore Ponniah wrote: > > Hi All, > > I am trying to upload multiple yaml cloudformation templates to a s3 > bucket using

[ansible-project] Ansible s3_sync to upload multiple files

2019-01-14 Thread Kishore Ponniah
Hi All, I am trying to upload multiple yaml cloudformation templates to a s3 bucket using s3_sync. I have created a task in the playbook, looks like the tasks completed successfully but the file is not uploaded. Can someone please advise whether s3_sync is the proper method? If yes, can someone

Re: [ansible-project] S3 error: Requests specifying Server Side Encryption with AWS KMS managed keys require AWS Signature Version 4

2019-01-14 Thread Kishore Ponniah
create the desired change set > manually, either via the console or via the AWS CLI, just to check you > really do have the parameters right. > > Regards, K. > > > On Sun, Jan 13, 2019 at 12:40 AM Kishore Ponniah > wrote: > >> Hi Karl, >> >> Please find the

Re: [ansible-project] S3 error: Requests specifying Server Side Encryption with AWS KMS managed keys require AWS Signature Version 4

2019-01-12 Thread Kishore Ponniah
s require AWS Signature Version 4.\nFor more information check http://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html"} Thanks Kishore On Friday, January 11, 2019 at 9:45:17 PM UTC, Karl Auer wrote: > > You need to provide the actual playbook and the actual error. Use a

[ansible-project] S3 error: Requests specifying Server Side Encryption with AWS KMS managed keys require AWS Signature Version 4

2019-01-11 Thread Kishore Ponniah
Hi All, The template body has exceeded the maximum limit of 51200 bytes, so I wanted to upload the template to an encrypted s3 bucket. When I run the playbook it gives an error to explicitly mention s3v4. My config file has a line for s3 v4 but still, it shows the same error. I have tested usin

Re: [ansible-project] Re: Template format error: YAML not well-formed.

2019-01-08 Thread Kishore Ponniah
tly to yamllint and tell us what that says? > > DIck > > On Tue, 8 Jan 2019 at 11:06, Kishore Ponniah > wrote: > > > > Please find my code below: I checked the code using YAML validator and > looks like it is valid. But still complaining about Line 12 column 6. &g

Re: [ansible-project] Re: Template format error: YAML not well-formed.

2019-01-08 Thread Kishore Ponniah
9 at 2:04:24 PM UTC+13, Karl Auer wrote: >> >> What is the problem that it reports on line 22? >> >> When posting code, please post in a fixed-width font if you can. Makes it >> easier to check indentation. >> >> Regards, K. >> >> >> O

Re: [ansible-project] Re: Template format error: YAML not well-formed.

2019-01-08 Thread Kishore Ponniah
; On Tuesday, January 8, 2019 at 2:04:24 PM UTC+13, Karl Auer wrote: >> >> What is the problem that it reports on line 22? >> >> When posting code, please post in a fixed-width font if you can. Makes it >> easier to check indentation. >> >> Regards, K. >&g

Re: [ansible-project] Template format error: YAML not well-formed.

2019-01-07 Thread Kishore Ponniah
UTC, Karthik Chandrashekar wrote: > > It would have shown line number as well in the error. Please look into > yaml file. > > May be it could be an issue with unnecessary tab/space. > > Regards, > Karthik.C > > On Mon 7 Jan, 2019, 10:04 PM Kishore Ponniah

[ansible-project] Re: Template format error: YAML not well-formed.

2019-01-07 Thread Kishore Ponniah
7, 2019 at 4:34:25 PM UTC, Kishore Ponniah wrote: > > Hi all, > > My cloudformation template has exceeded the template body limit more than > 51200 bytes and I am trying to upload to s3 and deploy using cross account. > I used template_url parameter in the playbook but givin

[ansible-project] Template format error: YAML not well-formed.

2019-01-07 Thread Kishore Ponniah
Hi all, My cloudformation template has exceeded the template body limit more than 51200 bytes and I am trying to upload to s3 and deploy using cross account. I used template_url parameter in the playbook but giving an error. Before adding template_url, I had template_body which was working fine

[ansible-project] Re: Ansible Play error - Template error while templating string: no filter named 'map'. String:

2018-10-25 Thread Kishore Ponniah
Hello all, I have managed to sort out this issue. I had an old version of Python-Jinja2 in my virtual environment. Once upgraded it resolved. Thanks On Wednesday, October 24, 2018 at 10:08:49 AM UTC+1, Kishore Ponniah wrote: > > Hello all, > > This is the continuation of m

[ansible-project] Ansible Play error - Template error while templating string: no filter named 'map'. String:

2018-10-24 Thread Kishore Ponniah
Hello all, This is the continuation of my other Post creating direct connect gateway. This is the same but using assume roles and cross-account deployment. I have added loops but there are 2 sections which are not working (debug role arns & assume cross account roles). Can some one help? Error

[ansible-project] Re: Ansible Playbook error - Dict object has no attribute.

2018-10-22 Thread Kishore Ponniah
7;].params.amazon_asn }}" register: created_aws_direct_connect_gateway tags: rxgt-ps-mgmt-dxgw-deploy On Monday, October 22, 2018 at 6:38:03 PM UTC+1, Kishore Ponniah wrote: > > ok, I used the below > > template_parameters: "{{ > rxgt_mgmt_account.accoun

[ansible-project] Re: Ansible Playbook error - Dict object has no attribute.

2018-10-22 Thread Kishore Ponniah
ne expects dictionaries, got Undefined"} to retry, use: --limit @/home/ec2-user/.ansible-retry/site.retry On Monday, October 22, 2018 at 5:06:42 PM UTC+1, Tony Chia wrote: > > It seems there is one level between account_config and stack. > Maybe try account_config.xx.stack

[ansible-project] Re: Ansible Playbook error - Dict object has no attribute.

2018-10-22 Thread Kishore Ponniah
I did -vvv and I don't see anything different. Same error and it gathered the facts. Not sure if my debug stack task is correct. On Monday, October 22, 2018 at 2:37:50 PM UTC+1, Adrian Sebastian Dutu wrote: > > I think the indentation appears wrong just in the preview. I downloaded > the file

[ansible-project] Re: Ansible Playbook error - Dict object has no attribute.

2018-10-22 Thread Kishore Ponniah
I have corrected that. I am concerned if line 17 is correct Thanks On Monday, October 22, 2018 at 2:32:27 PM UTC+1, Vladimir Botka wrote: > > > The indentation is wrong (line 10, column 5). Should be: > > tasks: > > - name: create rxgt-ps-mgmt-direct-connect-gateway stack > > > -- You

[ansible-project] Re: Ansible Playbook error - Dict object has no attribute.

2018-10-22 Thread Kishore Ponniah
t-gateway: params: name: mgmt-dxgw amazon_asn: 65000 override_tags: rx:billing:service-name: identity rx:billing:environment-name: xxx On Monday, October 22, 2018 at 1:17:31 PM UTC+1, Kishore Ponniah wrote: > > Hi, > > I am trying to create a Direct connect Gateway in AWS account

[ansible-project] Ansible Playbook error - Dict object has no attribute.

2018-10-22 Thread Kishore Ponniah
Hi, I am trying to create a Direct connect Gateway in AWS account using ansible. I have the main playbook and an account config yaml template. When I run the playbook I am getting an error fatal: [infrastructure]: FAILED! => {"msg": "The task includes an option with an undefined variable. Th