Unanswered Questions tagged with AWS Account Management
Content language: English
Sort by most recent
Is anyone aware of expiry dates of some of the AWS APN programs?
My team is an AWS APN partner and Here are some of the questions they have: - We have recently been approved for AWS Service Delivery Program for a particular Service, how long is it valid for? - We have recently been approved for AWS Competency Program for a particular Competency, how long is it valid for? AWS Service Ready Program as well. I understand that the AWS FTR are valid for 2years and AWS Certifications for 2/3 years depending on which you choose. What about this programs, If anyone can share some information, that would really help.
Issue adding user to the list
Hello all, we are using a dashboard: https://app.monitron.aws/ We want to add a general user to the list in order to have only read rights. The user is: email@example.com When I try to add it, the button of 'Add' remains grey. Can you please help me with this case? Kind regards,
Account blocked from creating free-tier EC2 instances
My account appears to be blocked from creating free-tier EC2 instances. I've tried this with several different settings and from the free, US-East zones; the same account block message persists. I emailed firstname.lastname@example.org but have yet to receive any feedback. In reviewing my account from admin and root, there are no indications my account is blocked. Any insight and advice to resolve is greatly appreciated.
Deleting Nimble Studio "Delete Failed" Launch Profile
I'm following the instructions to delete a studio, but when I try to delete the 'launch profile' Workstation-Default I get "Delete Failed" any tips on how to delete it? Also, the Streaming session is in "Ending" status after being terminated for too long.
Question regarding Lightsail/Plesk and snapshots
Hello, I am going through the process of upgrading one of my LightSail instances. In order to do this I created a snapshot from the original then created a new instance. However I noticed something strange, and maybe my lack of knowledge in AWS is to blame. I cannot gain access to plesk in the new instance I created from the snapshot. Plesk is asking for a username/pw yet the original did not have one set up. I only gained access to the original instance by using the following command: sudo plesk login | grep -v internal:8. I would then use the url provided and it gave me access, no need for username/pw. Yet on this new instance (which I assume should be a straight copy) is forcing a username/pw, as well as sending me to the ip address of the old instance. How do I gain access to the plesk on my new instance? Any insight into this issue would be greatly appreciated, as of right now I have no way of accessing plesk for the new instance.
AWS GovCloud Login Page
A couple of weeks ago, I typed in the customized URL address for the GovCloud account and was able to log in as the Administrator. This week after typing in the URL, I am only allowed to log in as![Enter image description here](/media/postImages/original/IMXTygDhEvRpqKpl6hIRyCGA) the IAM user. Why?
Is it possible to map the group as an attribute?
Hi, I am using AWS IAM as IDP from Root account with AWS SSO (not AD or external), so I have AWS SSO and a SAML application for Jenkins configured on the root account. I have configured the SAML Jenkins app with the following attributes: ![Enter image description here](/media/postImages/original/IMAT8AyKcITPm2Ug8org3pgg) And i need propagate to Jenkins the groups to which that user belongs in the AWS SSO, to assign permissions in Jenkins according to the groups that the user has. Is it possible? Regards!
New AWS accounts are limited to provisioning only 5 AWS Chime phone numbers?
We're in the process of migrating to a new AWS account and we found out that we're limited to provisioning only 5 AWS Chime phone numbers. Contrary to other similar cases, we didn't get a "Your service has been restricted" error message but rather "Service received a bad request" after successfully provisioning the 5 phone numbers. Looks like AWS has tweaked the error message to make it more vague? We did try to delete some numbers, and was able to provision more numbers but we're still limited to just 5 phone numbers in our inventory. The service quota was like 25 and yet, we're limited to just 5. Doesn't make a lot of sense to me if you want to know how I feel about it. I'm not quite sure what to think but would love some answers. Thank you!