I need to get SOC2 related report from AWS, and I downloaded it, but found no description of my company/organisation. Instead, the downloaded PDF contains some hexadeimal numbers with hyphens? what is it? Does AWS artifact report involves the user (organization)'s identity? It's not related?
Ah sorry, it was my misunderstanding that AWS is only responsible for its platform, such that the company (and its services) should obtain document separately. https://docs.aws.amazon.com/artifact/latest/ug/what-is-aws-artifact.html
sorry this was stupid question.
Related
Successfully able to upload the SCORM package zip and unzip in S3 bucket using drupal 8.
While trying to read the SCORM files in the extracted data folder we got the error message like
"ERROR – unable to acquire LMS API, content may not play properly and results may not be recorded. Please contact technical support"
I checked the access stuff all are in public only
Can anyone tell me where i missed
image
That content sounds like its setup to look for the API or API_1484_11 (SCORM API's for 1.2 and 2004) and pop up an alert.
With a runtime API present that alert would go away. Your next question - "How do I expose a runtime API?" the answer is normally you hand roll one, or look for a Runtime API paid or otherwise.
Something like https://github.com/cybercussion/SCOBot/blob/master/QUnit-Tests/js/scorm/SCOBot_API_1484_11.js might get you started if your looking for free.
If you plan to build a LMS you may want to look into paid options.
I'm currently trying to migrate a data science environment (jupyter notebook)running on Kubernetes to Sagemaker Studio.
I set up SSO and I now have privates work spaces for each user but I'd like to also have a shared folder between all the users. I've googled quite a bit to find an answer to this question without success.
Thanks for you help
As of today, there isn't an option to have a shared folder between users in Studio. Each user profile gets a dedicated directory on EFS that's private to them.
If you're sharing data, S3 is an alternative option.
I work at AWS and my opinions are my own.
We're using AWS's elasticsearch service. We have a custom synonyms package associated with the elasticsearch domain. The file lives in an s3 bucket, when the file is updated it triggers a lambda that updates the package version in AWS. We followed the documentation at https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/custom-packages.html and so far that all works great for uploading and updating a new version of the package. However, the way aws elasticsearch custom packages work, each domain that uses the custom package stores its own copy of the file as well. To keep search behavior predictable, domains continue to use their current package version until you explicitly update them.
The problem is that I can't find any way to programmatically tell the domain to use the new version of the package. It's like 2 clicks in the console, but I cannot for the life of me find a way to do it from my automation code. The update_package method just updates the package version, it doesn't tell the associated domains to use the new version.
We're looking for a way to programatically tell an AWL elasticsearch domain to update the version of an associated custom synonyms file.
So after banging my head on this for days and I finally figured it out 5 minutes after posting this question. You just need to call the associate_package method again after you update the package. I had actually tried that previously and it failed, but it turns out it fails if there is no new version of the package available. I think I was calling associate_package again before the update_package method was completed, so the new version wasn't available yet.
Anyway, hope this helps someone in the future.
Correct, you have to specifically call associate_package to link to the latest version of that package
I'm newbie in AWS, with my free tier account I'm trying to build my nodeJS project with AWS CodeBuild but I get this error:
Build failed to start The build failed to start. The following error occured: Cannot have more than 0 builds in queue for the account
I followed the simple aws tutorial, leaving all default settings for let aws create all service, image etc for me.
Also I stored source code in a AwsCodeCommit repository.
Could anybody help me?
In my case, there was a security vulnerability in my account and AWS automatically raised a support ticket and suspended all resources that were linked to it. I had to fix it and then on chat with aws support they resumed my service.
I've seen a lot of answers around the web suggesting to call support, which is a great idea, but I was actually able to get around this on my own.
As the root user I went in and put in a current credit card. The one that was currently there was expired. I then deleted my CodeBuild project and create a new one. Now my builds work! It makes sense that AWS just needed a valid payment method before it allowed me to use premium services.
My solution may not work for you, but sure I hope it does!
My error was Project-level concurrent build limit cannot exceed the account-level concurrent build limit of 1 when I tried to increase the Concurrent build limit under checkbox Restrict number of concurrent builds this project can start in CodeBuild Project Configuration. I resolved it by writing to support to increase the limit. They increased it to 20 and it works now as expected. They increased it even though I'm on Basic plan on AWS if anyone's wondering.
My solution was to add new service role name and the concurrent build to 1. This worked
I think your issue is resolved at the moment. Any way I faced the same issue. In my case I had a "code build project" connecting to a GitHub repository. And then I added AWS Access Key and Secret hard coding the buildspec.yml file. With this AWS identified it as an unauthorized login. So they added security restrictions to the resources while opening a support issue. In such a case you can look for the emails from AWS in which they explain the reason for this behavior and the steps to get this corrected.
As described here, WinQual has moved and mapping product data for Windows Error Reporting has to be done using Microsoft Ecosystem Metadata Exchange (MEME).
Within our automated build process, a script created the XML file for Winqual and automatically did the upload.
Now MEME offers a set of powershell cmdlets to create a mapping file from the product binaries.
By now, I could not find any Documentation for this cmdlets but this article. The powershell script described there unfortunately seems not to set the company name correctly.
Can anyone provide a better documentation?
Microsoft says, that there is a known bug in the EMX GUI, displaying the product name instead of the company name in the files listing. Bug will be fixed through EMX upgrades.
Microsoft now also provides an update of the FAQ on how to use the PowerShell Cmdlets of EMX.