#crossaccount

[mkznews]

SD Occasions information digest: TypeScript 4.4 RC, AWS broadcasts cross-account information sharing for Amazon Redshift, JetBrains releases GoLand 2021.3 roadmap

Microsoft introduced the discharge candidate of TypeScript 4.4, and mentioned it expects no additional modifications aside from vital bug fixes for the secure launch.  Main highlights of the discharge candidate embrace management move evaluation of aliased situations and discriminants, image and template string sample index signatures, defaulting to the ‘unknown’ sort in catch variables, and extra.  As a substitute of getting to persuade TypeScript of a variable’s sort at any time when it's used, the type-checker leverages management move evaluation to infer the sort inside each language assemble. Extra particulars on the brand new launch can be found right here.  AWS broadcasts cross-account information sharing for Amazon Redshift This new function provides customers a easy and safe option to share contemporary, full, and constant information of their  Amazon Redshift information warehouse with any variety of stakeholders throughout AWS accounts. Customers can now share information throughout organizations and collaborate with exterior events whereas assembly compliance and safety necessities. The entire permissions required for authorization and affiliation are managed with AWS Id and Entry Administration (IAM), so customers can create IAM insurance policies to manage which operations every person can full. Additionally, each the producer and shopper clusters should be encrypted and in the identical AWS Area.= Extra particulars can be found right here.  JetBrains releases GoLand 2021.3 roadmap New options for GoLand 2021.3 embrace new skills to manage the conduct of go checklist, the flexibility to reload the go.mod file after making modifications, and the flexibility to run default built-in and gofmt formatters one after the other.  JetBrains is planning so as to add code inspections, refactorings, and intention actions for working with generics on Go 1.18. Additionally on the drafting board is help for WSL, the mixing of go linters proper inside GoLand, in addition to different debugger and code enhancing modifications.  Extra particulars can be found right here.  Apache weekly replace  Final week on the Apache Software program Basis noticed the discharge of Apache Geode 1.13.4, which supplies a database-like consistency mannequin, dependable transaction processing and a shared-nothing structure to take care of very low latency efficiency with excessive concurrency processing. Different new releases included Flink 1.12.5, OFBiz 17.12.08, EventMesh (incubating) 1.2.0, Pulsar 2.7.3, Hop (Incubating) 0.99, Tomcat 9.0.52, 10.1.0-M4 (alpha), and 10.0.10. Apache addressed an arbitrary file add vulnerability in OFBiz, a ServiceComb ServiceCenter listing traversal, and a no authentication on logging server vulnerability in Apache Workflow.  Extra particulars on the entire newest from Apache can be found right here.    Source link Read the full article

[tensult]

How To Configure Cross-Account Cross-Region AWS CloudWatch Dashboard

Cloudwatch Dashboard Sharing between AWS accounts Monitoring using AWS CloudWatch becomes quite hectic when you are handling multiple customers. Sure, you can use SessionBox and switching between accounts but what if you have a single dashboard for monitoring purposes? Then things will be much more simpler because then you don't have to switch between accounts. In this blog, I am going to explain how to configure Cross-Account Cross-Region CloudWatch dashboard. For the simplicity of this blog, I will be considering two AWS accounts. The steps mentioned here could be repeated for multiple account as well. First AWS account is the target account whose CloudWatch metrics you wish to monitor. Second AWS account is the monitoring account which is the source account from where you will be monitoring other accounts. Enabling the functionality in target AWS account CloudWatch We must first enable sharing in the target account's CloudWatch so that we can access the data from our monitoring account. Go to CloudWatch and check the left side panel for Settings.

2. Click on Settings and then in the next window which opens, you need to click on Configure.

By default, both the options Share your data and View cross-account cross-region will be disabled. You need to click on configure so as to enable the share your data option for target account. 3. In the next page, click on Share Data button and add the account ID of the monitoring account.

Permission settings 4. You will get the above options in the same window itself. Here you need to select on Full read-only... option and then click on Launch CloudFormation template. This will create a cross account sharing role with your monitoring account. Once it's done, you will be able to see the option enabled in the account as shown below. Next you can proceed with the monitoring AWS account setup.

CloudWatch>Settings Enabling monitoring account to view the CloudWatch dashboard Similarly, go to the monitoring account and we need to enable the option of viewing cross-account cross-region CloudWatch information. Go to CloudWatch>Settings and then click on Enable in the bottom half of the window which says 'View cross-account cross-region'.

View Cross-account cross-region enabled Once the viewing data option is enabled, then go to CloudWatch>Dashboards and you should see something like this:

Updated CloudWatch dashboard You must have noticed the new option above, 'View Data for' which can be used to access other accounts in various regions. Enter the account ID and region in that space and you will be able to see that account's CloudWatch dashboard. You can also click on Create Dashboard using which you can create a dashboard of the account which you want to monitor, on this monitoring account. The steps used for selecting the metrics are the same, just be aware of the account ID and region that you are selecting.

Selecting metrics and creating dashboard Once the dashboard has been created, we can monitor our customers' Cloudwatch dashboard from our own account and avoid switching every time to their account for monitoring purposes. The only thing I wish this feature had was for us to be able to export an already existing dashboard from the destination AWS account to our account. But for now, we have to configure the monitoring dashboard from scratch, metric by metric, graph by graph. Conclusion I hope this blog helps you in efficiently monitoring CloudWatch for your customer accounts. Kindly share this blog with AWS enthusiasts and also comment below if you have any suggestions. You can also subscribe to our newsletter by visiting here. Read the full article