We want to place block to region on block creation time. How can we do that?
I mean programatically how can we add regions while creating the block.
Add regions? Can you use the regions that are already defined for your theme?
Related
I have a CF stack in the name gtm-test-commit-9ttyhf7old. I want to know if there is a way to update the same stack with the new commit ID. Something like gtm-test-commit-9ttyhf7new without creating a new stack altogether.
It's not possible to rename a stack. You have to delete it and create a new one with the name you want.
For most resources, changing the logical name of a resource is
equivalent to deleting that resource and replacing it with a new one.
Any other resources that depend on the renamed resource also need to
be updated and might cause to be replaced. Other resources require you
to update a property (not just the logical name) in order to initiate
an update.
Check out this doc: AWS Official Document
Is there any way to enforce the addition of labels while creating resources? If not, is there a way to automatically label resources when creating said resources in GCP?
My use case: I need this to investigate the price in Data Studio.
Thanks.
No, you can't enforce any one to put labels on resources on GCP (same for projects). BUT you can enforce TAG automatically by inheritance. (You can't oblige a user to use them, but, by default there is a tag).
The TAG are still in preview and were named "label next gen" during the Alpha period. So, you can use them like labels, but you can enforce authorization on them (who can up view/update/delete them). This feature is very interesting because today, anyone with admin/owner roles can update/change/delete labels and you lost the control and the monitoring of your resources.
You can also put IAM condition on them and enforce organization policies accordingly.
You can't enforce users to do so. However you can:
Create a log sink if a resource is created
Use that log sink to call a cloud function that will create an alert or give a default label
If you use infrastructure as code for example Terraform, you can put a CI/CD job that will check if a label is placed, and if not reject the PR.
I have a single stack with two instances RDS,EC2.I have to follow the structure that has root stack and two nested stack RDS,EC2.
Following should be the structure
1.Root stack
2.Webserver stack: All services related to EC2
3.DB stack: All services related to RDS
The general procedure would be as follows:
Extract rds and ec2 resources to its own template files (e.g. ec2.yaml, rds.yaml)
Parameterize ec2.yaml and rds.yaml, as well as add Outputs section to them. The Outputs are needed if you want to reference their return values in the Root stack.
Upload the ec2.yaml and rds.yaml into S3.
In the root stack create two resources of type AWS::CloudFormation::Stack, i.e. one for rds and one for ec2. Use TemplateUrl to provide paths to locations in S3 (step 3). Use Parameters to define input parameters created in step 2.
Use GetAtt to reference outputs of the nested stack in the root stack.
It seems that there are two different Web UI for AWS Tag Editor (you need an AWS account to try them):
https://resources.console.aws.amazon.com/r/tags
I got this link from AWS Doc
https://eu-west-1.console.aws.amazon.com/resource-groups/tag-editor/find-resources?region=eu-west-1
In Management Console, if you select Resource Group > Tag Editor on the top of the console page, it will take you to this page
The two WebUI behave differently:
The former is global but the latter is region-specific (it will put you into a region even if you don't put the region parameter in the URL)
The former allows you to search for Not tagged in the filter; but the latter does not
The UI are slightly different
Is one of UI a newer version?
Update (2019-05-14)
(Please also see an explanation about the two links being NEW and OLD UIs that AWS offered at a certain point in time) By now the first link is gone. If you visit it, you will get a 404 Not Found error from AWS.
I am part of the team building the new Tag Editor. Yes, you are correct: Classic Tag Editor is deprecated, and will be shut down soon entirely. We are working on full feature parity between the two Editors, so you will very soon find everything you can do in the old one as well in the new one.
To add some more context on your different items below:
1) Both old and new Tag Editor use the same underlying tagging infrastructure, so this should never happen. Maybe there is some browser issue involved here? Feel free to open a support issue so we can look deeper into it, if this continues the case.
2) Yes, the new one also includes Lambda, and will very soon add more resource types. The same by the way for regions: The old Tag Editor supports not all regions, for example eu-north-1 or eu-west-3.
3) No, Route53 Hosted Zones are supported in both Editors. Route53 resources only exists in the us-east-1 region, so maybe you used the Tag Editor in another region?
4) Both Editors show the same data. The old editor merged what you used as Name Tag and the ID in the same field - in the new one, you see only the ID in the column ID, and the Name Tag is displayed in the column Tag: Name.
Searching across regions is something the new Editor soon will support, too, and the same applies for the filter you mention. For showing resources without a specific tag, there is a workaround you already can do: Click on the settings icon in the top right of the table, and enable the tag you are interested in as a column. You then can sort this column so that all untagged ones show up on top.
If you have any other ideas or requests for the Tag Editor, please let us know. The fastest and most reliable way is to just use the 'Feedback' Button in the console in the bottom left.
Cheers,
Florian
Hi I am providing my own answer here (thanks my colleagues Kannan for the insight)
#1 above is what AWS called Class Tag Editor. If you click on the Question mark on the Web UI (upper right corner), you will be taken to a page that says:
This documentation is for classic Tag Editor, which has been
deprecated
So #2 is the version that AWS want us to use.
Below I will called #1 Old and #2 New
I compared the example outputs from our environment (about 50 resources). The two outputs differ in these respects:
New seems to retain past resources for a longer time. For example, if an EC2 instance has been terminated, it may take a
longer time to be removed from the listing of New
New seems to include resources for DynamoDB but Old does not
Old seems to include resources for Route 53 Hosted Zones but New does not.
Both New and Old show Security Groups, but the ID strings are rendered slightly differently.
New renders an ID as sg-xxxxxxxxxxxxxxxxxxxxxx
Old renders an ID as someName (sg-xxxxxxxxxxxxxxxxx)
I am new to Hygieia. I have setup Hygieia (https://github.com/capitalone/Hygieia) as per the documentation and I could start my application and see the dashboard successfully. In Hygieia-Dashboard, I could see values coming for all widget items (say utilization, instances stoped, and so on.) except the IP Utilization widget. When i see the mongodb that i configured with this (after I ran AWS module) i could see data for most of the documents except the cloud_subnetwork and cloud_virtual_network. Is this causing the issue?
Can anyone please assist me for populating IPUtilization widget ?
if I am still missing with anything? Anyfurther configuration to be made for this?
I found a solution for this issue., i.e., we need to fetch values for subnets and virtual_networks by using the AmazonEC2Client's instances by calling its describeSubnets() and describeVpcs() respectively and save these to database. After this, we could see values in the IPUtilization widgets. Hope this helps!